Database Reference
In-Depth Information
The next step is to create the NLS directories by executing the
cr9idata.pl
script on each node. Make sure to set
the database
ORACLE_HOME
variable before running the script. Listing 11-16 shows an example.
Listing 11-16.
Creating the NLS Directories in the New Oracle Home
[oracle@s1 ~]$
export ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_3
[oracle@s1 ~]$
perl $ORACLE_HOME/nls/data/old/cr9idata.pl
Creating directory /u01/app/oracle/product/11.2.0.3/dbhome_3/nls/data/9idata ...
Copying files to /u01/app/oracle/product/11.2.0.3/dbhome_3/nls/data/9idata...
Copy finished.
Please reset environment variable ORA_NLS10 to /u01/app/oracle/product/11.2.0.3/dbhome_3/nls/
data/9idata!
The last and the most complicated step is the installation of the required database patches. The list of one-off
patches can be obtained from My Oracle Support note “Database Preparation Guidelines for an E-Business Suite
Release 12.2 Upgrade (Doc ID 1349240.1).” The R12.2 database Oracle Home requires 57 patches; fortunately, not all
of them need to be applied manually because patch 16342486 (n-apply bundle patch III for RDBMS 11.2.0.3.0 with
eBS Release 12.2) delivers 51 of all the required patches. But the task is especially complex because a PSU is already
applied to the new Oracle Home and many of the patches conflict with it.
I found the following approach effective in dealing with all the patch conflicts:
1.
Apply the latest OPatch version first (patch 6880880).
Install the bundle patch (16342486) as instructed by running
opatch napply -skip_
subset -skip_duplicate
. The installation will fail because of the conflicts; however, the
outputs will provide useful information about which exact patches conflicts with the CPU
patch that's already applied. Listing 11-17 shows the important outputs.
2.
Listing 11-17.
Identifying the Conflicting Patches
[oracle@s1 16342486]$
opatch napply -skip_subset -skip_duplicate
...
Verifying environment and performing prerequisite checks...
Checking skip_duplicate
Checking skip_subset
These patches will be skipped because they are subset patches of some patch(es) in the Oracle Home:
11071989,12764337,12780983,12845115,12849688,12971775,13036331,13070939,13366202,13466801,13499128,
13528551,13544396,13923995,14398795,8547978,9858539
OPatch continues with these patches:
12942119,12949905,12949919,12951696,12955701,12965899,12985184,13004894,13023632,13040331,13146719,1
3258936,13259364,13366268,13388104,13477790,13495307,13602312,
13808632,14005749,14013094,14207902,14237793,14296972,14598522,14649883,14698700,14751895,14832335,
15967134,16040940,16163946,16342486,4247037
...
Following patches have conflicts: [ 16619892 13004894 14727310 13923374 13259364
14598522 16056266 14275605 13696216 13343438 14649883 14751895 15967134 16163946 ]
Refer to My Oracle Support Note 1299688.1 for instructions on resolving patch conflicts.
