Fusion Application Installation - Oracle Fusion Applications Administration Essentials - page 27

The default logging level can be changed in a situation where a more detailed level
of logging is required. To change the default log level, change the trace level in
the framework_location/provisioning/bin/prov-logging-config.xml
file.

Although it is not recommended, the log level for the ant scripts can also be
changed to get more detailed information during ant-based deployments of the in-
stallation. To increase the log level, set ANT_ARGS=-debug -verbose in the
$PROVISIONING_FRAMEWORK/provisioning/bin/envConfig.sh file.

Cleanup and restore

If an error occurs during the installation process, the installer will stop. Once the is-
sue has been resolved, the installer can be restarted. Restarting the installer will ini-
tiate a cleanup process for that phase of the installation. This cleanup process is ini-
tiated with the primordial host, but the action is initiated across all hosts involved in
the installation.

The steps performed during cleanup depend on the phase and the products being
installed. It usually includes:

• Shutting down Admin Server and Managed Server (for failed products)

• Shutting down BI processes

• Shutting down web-tier processes

• Shutting down Informatica Identity Resolution ( IIR )

This cleanup is in anticipation of the restore process. During the restore process, the
response files and other variables are read, and the installation process is restarted.
It is assumed that the issue that caused the original error has been resolved at this
point. The steps performed during the restore step are as follows:

1. Deleting the restart phase, that is, the name.grd file located at

$APPLICATION_BASE/provisioning/restart .

2. Restoring instance.tar from the backup taken after the last successful

phase.

3. Starting the Common Domain Admin Server.

4. Starting the web-tier processes.

5. Performing Lighweight Directory Access Protocol ( LDAP ) cleanup.