Database Reference
In-Depth Information
Database opened.
SQL>
exit
[oracle@s1 PROD_s1]$
./adautocfg.sh
Enter the APPS user password:
...
AutoConfig completed successfully.
The preceding eight steps complete the configuration of the new Oracle Home for your e-Business Suite
database; however, you need to remember that the new Oracle Home has a different set of patches installed on top of
it, at least because it contains a Patch Set Update. You have to complete all the post-installation tasks for the patches
installed to the new Oracle Home. Most of the patches are the same in the old and new Oracle Homes, therefore it's
best to compare the lists of installed patches and execute the post-installation tasks for the ones that are not present
in the old Oracle Home. Listing 11-18 shows how to extract nicely formatted and sorted lists of patches that are easy to
compare, and identify the differences in each Oracle Home.
Listing 11-18.
Extracting the List of Installed Patches
[oracle@s1 ~]$
cd $ORACLE_HOME/OPatch/
[oracle@s1 OPatch]$
./opatch lsinventory | grep "^Patch " | awk -F ":" {'print $1'} | sort
Patch 12942119
Patch 12949905
Patch 12949919
Patch 12951696
...
Once you have compared the installed patches in both Oracle Homes and executed the remaining
post-installation, the configuration of e-Business Suite with the ODA's natively created Oracle Home
is completed.
Migrate to ASM and RAC
Migration to ASM and RAC is quite a complex change that can be implemented in a number of ways, including a
manual reconfiguration of the database. However, that would require much time and it is relatively easy to miss
something or make an error in the process due to the large number of items to address. Instead, it is good to automate
the migration.
My Oracle Support note “Using Oracle 11g Release 2 Real Application Clusters and Automatic Storage
Management with Oracle E-Business Suite Release 12.2 (Doc ID 1453213.1)” lists the
RCONFIG
utility as one of the
tools that can be used to automate the RAC conversion. An additional benefit of
RCONFIG
is the fact it can move the
database to ASM as part of the operation. This is why the tool is especially useful in our situation.
One deficiency of
RCONFIG
is its inability to work with user-defined Oracle listeners. Therefore, before you run
the utility, make sure the following standard configuration is present:
Local_listener
parameter is not set in your database.
•
Remote_listener
parameter is set to
'<scanname>:1521'
(i.e.
'scan.odalab.com:1521')
.
•
•
The scan listeners are started.
•
The default listener (one named “LISTENER”) is started on each ODA Base node.
•
And your DB is properly registered with the default listener on the same server that the DB is
running on and with the scan listeners on both nodes.
