Database Reference
In-Depth Information
Copy the
appsutil
directory from the old Oracle Home to the new one and rename the
existing database context file because the same filename needs to be used for the new
context file. For example:
2.
[oracle@s1 ~]$
cp -rp $OLD_OH/appsutil $NEW_OH/
[oracle@s1 ~]$
cd $NEW_OH/appsutil
[oracle@s1 appsutil]$
mv PROD_s1.xml PROD_s1.xml.old
3.
Use
adclonectx.pl
to create a new context file by using the old one as a template. This
utility will launch a command-line wizard that will ask a few questions about the new
configuration. Here's an example run:
[oracle@s1 appsutil]$ cd $NEW_OH/appsutil/clone/bin
[oracle@s1 bin]$ perl
adclonectx.pl
contextfile=$OLD_OH/appsutil/PROD_s1.xml.old
Enter the APPS password :
notimportant
Target System Hostname (virtual or normal) [s1] :
s1
Do you want the inputs to be validated (y/n) [n] ? :
n
Target Instance is RAC (y/n) [n] :
n
Target System Database SID :
PROD
Target System Base Directory :
/u01/app/oracle
Oracle OS User [oracle] :
oracle
Oracle OS Group [dba] :
dba
Target System utl_file_dir Directory List :
/usr/tmp
Number of DATA_TOP's on the Target System [3] :
1
Target System DATA_TOP Directory 1 :
/u02/prod/data
Target System RDBMS ORACLE_HOME Directory [/u01/app/oracle/11.2.0] :
/u01/app/oracle/
product/11.2.0.3/dbhome_3
Do you want to preserve the Display [null] (y/n) :
y
Target System Port Pool [0-99] :
11
New context path and file name [/u01/app/oracle/product/11.2.0.3/dbhome_3/appsutil/PROD_s1.xml] :
/u01/app/oracle/product/11.2.0.3/dbhome_3/appsutil/PROD_s1.xml
contextfile=/u01/app/oracle/product/11.2.0.3/dbhome_3/appsutil/PROD_s1.xml
4.
A new context file was created in the previous step, but the configuration files still need
to be prepared by running
AutoConfig
. Normally,
AutoConfig
connects to the database
too, but at this moment, you're unable to start it because the configuration is still missing.
You need to run a subset of all
AutoConfig
actions (called the “Instantiate phase”) that
will prepare the configuration files, but will not attempt to apply the configuration to the
database. Specifying the
run=INSTE8
option to the
adconfig.pl
utility allows you to do this.
When the configuration is ready, the new environment file can be sourced and the listener
can be started from the new Oracle Home, as in the following example:
[oracle@s1 bin]$
perl adconfig.pl contextfile=$NEW_OH/appsutil/PROD_s1.xml run=INSTE8
[oracle@s1 bin]$
. $NEW_OH/PROD_s1.env
[oracle@s1 bin]$
cd $NEW_OH/appsutil/scripts/$CONTEXT_NAME
[oracle@s1 PROD_s1]$
./addlnctl.sh start PROD
