Running the Installer in Silent Mode
You should run the installer on a host that has the same operating system as the host on which you generated the state file. If you cannot do this, refer to Creating a Platform-Appropriate State File ID.
If you have problems during installation, refer to Chapter 9, Troubleshooting.
To Run the Installer in Silent Mode
Silent installation can be lengthy, depending on the quantity and type of product components that you are installing.
-
Verify that your state file is edited correctly for the host.
Caution – In a state file created for silent installation, some parameters specify sensitive data, such as administrator passwords. Make sure to secure the file as appropriate for your deployment.
-
If you are not logged in as root, become superuser.
-
Navigate to the directory where the installer utility is located.
cd installer-directory
-
Run the installer using the following syntax:
./installer -noconsole -state statefile
- —noconsole
-
Start the installer in silent mode, suppressing the user interface.
- —state
-
Use the specified state file as input to a silent installation.
- statefile
-
Specify an absolute or relative pathname to a state file.
-
After installation is complete, proceed to the next host and repeat Steps 1 through 4.
To Monitor the Progress of a Silent Installation
-
To monitor a silent installation, navigate to the log file directory:
Solaris OS: cd /var/sadm/install/logs
Linux: cd /var/opt/sun/install/logs
-
Locate the log files for the current installation.
The shared components are installed first and the product components follow. The timestamp variable represents the time the log was created. The variable has the format MMddhhmm.
- MM
-
Specifies the month
- dd
-
Specifies the date
- hh
-
Specifies the hour
- mm
-
Specifies the minute
-
Use the tail command to watch messages as they are written to the logs:
tail -f logfile-name
To exit the tail program, press Ctrl+C.
- © 2010, Oracle Corporation and/or its affiliates