Since 2010, OraERP is a Oracle Forums, Community of Oracle Professionals including Fusion/Cloud Application Consultants, Enterprise Architects, ERP Cloud, HCM Cloud, CX Cloud and OCI Experts, ERP Experts, Oracle Apps Functional Consultants, Apps DBAs, DBAs, Cloud DBAs, Digital Architect, PaaS Experts, IaaS, OCI Architects, Technical Consultants, Fusion Middleware Experts, SQL, PL/SQL Developers and Project Managers. Welcome to OraERP.com Social Community, a friendly and active community of Oracle Technology Professionals who believe that technology can ‘make the world a better place’. By joining Oracle ERP Community you will have the ability to Post Topics, Receive our Newsletter, subscribe to threads and access many other special features. Registration is Quick and Simple. Get unlimited access to Oracle Tutorials, Articles, eBooks, Tools and Tips .
Thread Rating:
  • 48 Vote(s) - 3.17 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Enable AutoConfig on Applications Database Tier
01-23-2012, 06:19 PM,
#1
Enable AutoConfig on Applications Database Tier

Enable AutoConfig on Applications Database Tier

Steps to Perform On All Oracle RAC Nodes

1> Execute $AD_TOP/bin/admkappsutil.pl on the applications tier to generate an
appsutil.zip file for the database tier.

[Image: AAAAABJRU5ErkJggg==]


2> Copy (e.g. via ftp) the appsutil.zip file to the database tier in the 11gR2_ORACLE_HOME

On linux1


On linux2



3> Unzip the appsutil.zip file to create the appsutil directory in the 11gR2_ORACLE_HOME

unzip appsutil (on linux1 and linux2)

4> Copy the jre directory from SOURCE_ORACLE_HOME>/appsutil to
11gR2_ORACLE_HOME>/appsutil.
On linux1


On linux2

5. Create a <CONTEXT_NAME> directory under <11gR2_ORACLE_HOME>/network/admin. Use
the new instance name while creating the context directory. For example, if your database name
is VISRAC, and you want to use "vis" as the instance prefix, create the <CONTEXT_NAME>
directory as vis1_<hostname>.


7. Set the following environment variables:

ORACLE_HOME =<11gR2_ORACLE_HOME>
LD_LIBRARY_PATH = <11gR2_ORACLE_HOME>/lib,
<11gR2_ORACLE_HOME>/ctx/lib
ORACLE_SID = <instance name for current database node>
PATH= $PATH:$ORACLE_HOME/bin;
TNS_ADMIN = $ORACLE_HOME/network/admin/<context_name>

export ORACLE_HOME =
/d01/oracle/app/oracle/product/11.2.0/dbhome_1
export LD_LIBRARY_PATH = $ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib
ORACLE_SID = RACDB1
export PATH= $PATH:$ORACLE_HOME/bin;
export TNS_ADMIN = $ORACLE_HOME/network/admin/racdb1_linux1

8> Copy the tnsnames.ora file from $ORACLE_HOME/network/admin to the $TNS_ADMIN
directory, and edit the aliases for SID=<new RAC instance name>.


9. As the APPS user, run the following command on the primary node to de-register the
current configuration:

SQL>exec fnd_conc_clone.setup_clean;

PL/SQL procedure successfully completed.

10. From the 11gR2 ORACLE_HOME/appsutil/bin directory, create an instance-specific XML
context file by executing the command:

cd $ORACLE_HOME/appsutil/bin

perl adbldxml.pl appsuser=apps appspass=apps

nCopy tnsnames.ora and listener.ora from Source ORACLE Home

cd /d01/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/RACDB_linux1

modify listener.ora as follows


Perform the same on linux2
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  VALIDATE DATABASE command admin 0 3,173 12-08-2010, 05:13 AM
Last Post: admin



Users browsing this thread: 2 Guest(s)