Database Reference
In-Depth Information
3.
Install the bundle patch again, but instruct the
opatch
to apply only the patches that don't
conflict with the installed PSU this time. This can be done by subtracting the patches in the
“Following patches have conflicts” list from the “OPatch continues with these patches” list
spooled by the initial run of the
opatch
. The remaining list of patches should be passed to
opatch
by using the
-id
parameter:
[oracle@s1 16342486]$ opatch napply -skip_subset -skip_duplicate -id 12942119,12949905,12949919,129
51696,12955701,12965899,12985184,13023632,13040331,13146719,13258936,13366268,13388104,13477790,134
95307,13602312,13808632,14005749,14013094,14207902,14237793,14296972,14698700,14832335,16040940,163
42486,4247037
4.
Watch as the installation progresses and applies the patches to both new Oracle Homes.
5.
Install the remaining patches from My Oracle Support note 1349240.1. Some of the
patches may conflict with the installed PSU again.
6.
Check the My Oracle Support note “Database Patch Set Update Overlay Patches
Required for Use with PSUs and Oracle E-Business Suite (Doc ID 1147107.1)” to find the
replacement patches for the conflicting patches found during the previous steps.
7.
Create service requests for Oracle Support if any of the patch conflicts are still unresolved.
There's no point in listing all the patches here because these PSUs are released quarterly, and Oracle tries to keep
up the same pace with the new versions of the Oracle Appliance Kit that delivers the new Patch Set Updates to the
Oracle Database Appliance. It's also likely the patching requirements of R12.2 database home will change because the
Release 12.2 version of e-Business Suite was recently released. The installation of patches in the new home completes
this step, and the database can be started from the new home.
Configure the New Oracle Home
AutoConfig
manages the configuration of the Oracle Home in an e-Business Suite environment. It is not enough to
copy initialization and Net services' configuration files from the existing database home to the new one to start using
it. A few additional steps need to be taken to implement the
AutoConfig
in the new Oracle Home. You will use a set of
tools delivered by e-Business Suite to clone the configuration of the old home (referenced as the OLD_OH later in the
text) to the new home (referenced as the NEW_OH).
Follow the instructions outlined next to implement
AutoConfig
and prepare the configuration files needed for the
existing e-Business Suite database:
1.
Run the
adpreclone.pl
utility to capture the configuration details of the existing Oracle
Home and save them in the
$OLD_OH/appsutil
directory. Then stop the listener and shut
down the database. Here are the commands to execute this step:
[oracle@s1 11.2.0]$
. $OLD_OH/PROD_s1.env
[oracle@s1 ~]$
cd $OLD_OH/appsutil/scripts/$CONTEXT_NAME
[oracle@s1 PROD_s1]$
perl adpreclone.pl dbTier
[oracle@s1 PROD_s1]$
./addlnctl.sh stop PROD
[oracle@s1 PROD_s1]$
./addbctl.sh stop immediate
