Enable AutoConfig on Applications Database Tier

Enable AutoConfig on Applications Database Tier

1. Ensure that you have applied the Oracle Applications patches mentioned in the pre-requisites section above.
2. Execute AutoConfig utility on the application tier. Verify the AutoConfig log file located at $APPL_TOP/admin//log/.

NOTE	For more information on AutoConfig, see My Oracle Support Knowledge Document 165195.1 , Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i.

3. Execute $AD_TOP/bin/admkappsutil.pl to generate appsutil.zip for the database tier.
4. Transfer this appsutil.zip to database tier in the 10g ORACLE_HOME.
5. Unzip this file to create appsutil directory in the 10g ORACLE_HOME.
6. Create a directory under $ORACLE_HOME/network/admin. Use the new instance name while creating the context directory. Append the instance number to the instance prefix you are going to add to the Rconfig XML file. 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_.
7. Set the following environment variables:
   ORACLE_HOME =<10g oracle_home="">
   LD_LIBRARY_PATH = <10g 10g="" ctx="" lib="" oracle_home="">
   ORACLE_SID = instance name running on this database node.
   PATH= $PATH:$ORACLE_HOME/bin;
   TNS_ADMIN = $ORACLE_HOME/network/admin/< context_name > 
8. Copy the tnsnamesora file from $ORACLE_HOME/network/admin to $TNS_ADMIN/tnsnames.ora file. Change the aliases for SID= . 
9. To preserve TNS aliases (LISTENERS_ and LISTENER_) of ASM , create a file _ifile.ora under $TNS_ADMIN, and copy those entries to that file.
10. Shutdown the existing listener and copy the listener.ora file from $ORACLE_HOME/network/admin to $TNS_ADMIN directory. Set the environment for the listener using $CRS_HOME/bin/srvctl setenv nodeapps -n -t TNS_ADMIN=$ORACLE_HOME/network/admin/


11. Start the Listener.
12. From the 10g ORACLE_HOME/appsutil/bin directory, create an instance-specific XML context file by executing the command:adbldxml.pl tier=db appsuser= appspasswd=
    

    NOTE	If this command cannot connect to the database, you will be prompted for hostname, SID and port values: supply the instance details for the current node.

13. De-register the current configuration using Apps schema package FND_CONC_CLONE.SETUP_CLEAN 
SQL>exec fnd_conc_clone.setup_clean;
14. Set the value of s_virtual host_name to point to the virtual hostname for the database host, by editing the database context file $ORACLE_HOME/appsutil/ _hostname.xml.

    NOTE	If you have created the named db listener in Section 3.6 step 2.5, modify s_db_listener context variable in the context file to match the new listener name.

    
    
15. Rename $ORACLE_HOME/dbs/init.ora to a new name (such as init.ora.old), in order to allow AutoConfig to regenerate the file using the RAC specific parameters.
16. From the 10g ORACLE_HOME/appsutil/bin directory, execute AutoConfig on the database tier by running the adconfig.pl script. 
17. Check the AutoConfig log file located in 10g ORACLE_HOME/appsutil/log//.
18. Shut down the instances.
19. Edit $ORACLE_HOME/dbs/_APPS_BASE.ora file. Change the parameter shown below
    • control_files =
20. Create an spfile from the pfile to start/stop the instances using srvctl. 
    1. From the pfile, create an spfile in a temporary location, then create a new pfile from the spfile. Repeat on all nodes.
       SQL>create spfile=from pfile;
       SQL>create pfile=/tmp/init.ora from spfile; [Example location shown]
    2. Combine the initialization parameter files for all instances into a single initdbname.ora file by copying all shared content as is. All the shared parameters defined in your initdbname.ora file are global, with the format *.parameter=value
    3. Modify all instance-specific parameter definitions in the init.ora file using the following syntax, where the variable sid is the system identifier (SID) of the instance: .parameter=value Ensure that the parameters
       1. local_listener, background_dump_dest,core_dump_dest,user_dump_dest,utl_file_dir
       2. undo_tablespace, thread, instance_number, and instance_name are in . format; for example, < sid > .LOCAL_LISTENER= .
          All these parameters will have one entry for an instance.
    4. Create the spfile in the shared location (where Rconfig created the spfile) from the pfile created in step 1 above.
       SQL> create spfile='' from pfile;

    NOTE	This step is required as the database and instance(s) resources registered with CRS use the spfile for startup. If you are using ASM Diskgroup as location for spfile, specify it in using the above command.

21. As AutoConfig creates the listener and tnsnames files in a context directory and not in the $ORACLE_HOME/network/admin directory, the new TNS_ADMIN path must be updated in CRS. Use the command: 
    srvctl setenv nodeapps -n -t TNS_ADMIN= /network/admin/
22. Run AutoConfig on all nodes to ensure each instance registers with all remote listeners.
23. Start up all the database instances.

3.11 Establish Applications Environment for RAC

Carry out the following preparatory steps on all application tier nodes:

1. Source the Applications environment.
2. Ensure that you are able to connect to one of the instance in the RAC environment before running AutoConfig.
3. Execute AutoConfig by running the command:$AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/. For more information on AutoConfig execution see My Oracle Support KnowledgeDocument 165195.1 :Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i.
4. Check the $APPL_TOP/admin//log/ AutoConfig log file for errors.
5. Source the environment by using the latest environment file generated.
6. Verify the tnsnames.ora and listener.ora files located in the 8.0.6 ORACLE_HOME, under $ORACLE_HOME/network/admin and $IAS_ORACLE_HOME/network/admin. Ensure that the correct TNS aliases have been generated for load balance and fail over. Ensure that all the aliases are defined using the virtual hostnames.
7. Verify the dbc file located at $FND_SECURE. Ensure that the parameter APPS_JDBC_URL is configured with all instances in the environment and load_balance is set to ON.

Now implement load balancing for the Applications database connections:

1. Run the Context Editor through Oracle Applications Manager interface to set the value of "Tools OH TWO_TASK"(s_tools_twotask) ,"iAS OH TWO_TASK"(s_weboh_twotask) and "Apps JDBC Connect Alias" (s_apps_jdbc_connect_alias).
2. To load balance the forms based applications database connections, set the value of "Tools OH TWO_TASK" to point to the _806_balance alias generated in the tnsnames.ora file.
3. To load balance the self-service applications database connections, set the value of iAS OH TWO_TASK" and "Apps JDBC Connect Alias" to point to the _balance alias generated in the tnsnames.ora file
4. Execute AutoConfig by running the command:$AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/
5. Restart the Applications processes by using the new scripts generated by AutoConfig execution.
6. Ensure that value of the profile option "Application Database ID" is set to dbc file name generated at $FND_TOP/secure/.