Managing Fusion Applications - Oracle Fusion Applications Administration Essentials - page 99

which should be utilized to collect all the relevant information required for
cloning.

• Take a complete tar backup of the source environment and copy it in the tar-

get environment.

• Restore the database on the target server using the RMAN duplicate or any

other preferred method.

• Extract the tar backup using the faclone.sh file on the target servers and

rewire the components with target server details.

• Validate the new clone environment.

• Perform post-clone steps, such as changing passwords, masking data, rein-

tegrating with third-party applications, or other custom applications.

Patching steps

There are several steps involved in patching Oracle Fusion Applications. In this sec-
tion we will discuss each of these steps:

• Preparing to patch

• Reporting patches

• Validating patches

• Applying patches

• Monitoring and resolving patching issues

• Postpatching steps

Preparing to patch

Before applying a patch, carefully examine the readme file provided with the patch.
The readme file will list all the steps required by the patch. It will contain information
about prerequired patches or steps, installation steps, and post-installation steps vi-
tal to the successful completion of the patch.

A full backup of the application needs to be taken before any patching activities are
carried out. Oracle Fusion Applications does not allow any automatic steps to roll
back a patch. Before modifying any artifacts, Oracle Fusion Applications does take
a backup of file in the $FA_ORACLE_HOME/admin/pbackup folder, but it's highly
recommended to take a complete backup as a fallback option.