Oracle AutoConfig in Oracle Apps 11i/R12

1. What is AutoConfig ?

AutoConfig is a configuration tool that automates the configuration of an Oracle Applications system. The information required for configuring an Applications system is collected into a repository, called the Applications Context; there is one Applications Context for each application tier (example: /APPS/visappl/admin/VIS_apps.xml), and one for the database tier (example: /APPS/visdb/9.2.0/appsutil/VIS_apps.xml). When AutoConfig runs, it uses information from the Applications Context file to generate all configuration files and update database profiles.

2. How do I determine if AutoConfig is enabled ?

• On the Database Node:

         1. Source the database:    

             . /APPS/visdb/9.2.0/VIS_apps.env       (example)

       

         2. Go to the listener folder:

             cd $ORACLE_HOME/network/admin/VIS_apps  (example)

         3. Show the listener.ora file

            $ more listener.ora   (on Linux/ UNIX, Solaris)

            If the header of this file contains the following message, that means the database is AutoConfig enable:

# ###############################################################
#
# This file is automatically generated by AutoConfig. It will be read and
# overwritten. If you were instructed to edit this file, or if you are not
# able to use the settings created by AutoConfig, refer to Metalink document
# 165195.1 for assistance.
#
# ###############################################################

For this header we can check each application and DB configuration file as well. 

 NOTES:

• If the database is AutoConfig enabled, the Applications tier must be AutoConfig enabled as well. 
• For the APPL_TOP:
  $AD_TOP/bin/adcfginfo.sh contextfile=<CONTEXT> 
  
  For products:
  $AD_TOP/bin/adcfginfo.sh contextfile=<CONTEXT> show=enabled 

       Example:

       $AD_TOP/bin/adcfginfo.sh contextfile=/APPS/visappl/admin/VIS_apps.xml      (Use a full path here !)

       This system is AutoConfig enabled

       Log file created at location :/APPS/visappl/admin/VIS_apps/log/03210211.log

       [oracle@APPS bin]$ more /APPS/visappl/admin/VIS_apps/log/03210210.log
       #----------------------------------------------
       #------Log File created at: 14:10:20------------
       #----------------------------------------------

       # AUTOCONFIG ENABLED PRODUCTS

       AD ENABLED
       FND ENABLED
       ABM ENABLED
       AHL ENABLED
       AMS ENABLED
       AR ENABLED
       BIS ENABLED
       . . . 

      # AUTOCONFIG DISABLED PRODUCTS

      AK DISABLED
      AU DISABLED
      AHM DISABLED

• If you manually changed any file containing this file header, it is no longer considered as officially AutoConfig enabled !

3. Is AutoConfig compatible with Oracle Applications 11.5.x ?     

Yes, it is compatible with all 11i releases. You can use AutoConfig to configure and maintain any Oracle Applications 11i environment. 

Release 11.5.1 - 11.5.6 (all tiers)
Apply the latest AutoConfig consolidated patch to obtain the AutoConfig utility.

Release 11.5.7 and higher (application tier)
AutoConfig is included in new Applications installations and in the associated maintenance packs.

Release 11.5.9 and higher (database tier)
AutoConfig is included in new Applications installations and in the associated maintenance packs.

NOTE: 

If you upgrade from a maintenance pack version that does not include AutoConfig to a maintenance pack version that includes AutoConfig (for example you upgrade from 11.5.3 to 11.5.10), you have to separately migrate to AutoConfig as part of the pre-upgrade process. Follow the instructions of the corresponding maintenance pack. 

4. When should I run AutoConfig ?

• You did updates to your Applications Context file. 
• An Oracle Metalink Note instructs you to run AutoConfig as part of an upgrade, migration, cloning and/or configuration process. 
• The Readme of an Oracle patch instructs you to run AutoConfig after the application of the patch. 
• You apply any ADX Product patch. 

Note: When you have AD.I or higher applied on your system, then adpatch will automatically invoke AutoConfig if the patch that you apply requires AutoConfig to run.

To find the AD patch level you can run SELECT PATCH_LEVEL FROM FND_PRODUCT_INSTALLATIONS WHERE PATCH_LEVEL LIKE '%AD%';

5. How could I run AutoConfig ?

a) Log on as the appropriate user and set the environment

b) Stop all server processes

c) Start the AutoConfig on the Application Tier

    <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>/adautocfg.sh  ( UNIX; for Windows : adautocfg.cmd )

d) Start the AutoConfig on the DB Tier

    <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh    ( UNIX; for Windows : adautocfg.cmd )

    NOTE:

    adautocfg.sh script runs the AutoConfig utility $AD_TOP/bin/adconfig.sh    ( UNIX; for Windows : adconfig.cmd ) 

e) Start all server processes

6. Where is the AutoConfig log file ?

The log file that AutoConfig creates is located at: 

On the application tier:
<APPL_TOP>/admin/<Context_name>/log/<MMDDhhmm>/adconfig.log 

On the database tier:
<RDBMS ORACLE_HOME>/appsutil/log/<Context_name>/<MMDDhhmm>/adconfig.log 

where: <MMDDhhmm> = (month, day, hour and minute of the AutoConfig run) 

7. How can I roll back an AutoConfig session ?

The backup configuration files from each AutoConfig session are stored in: 

On the application tier:
<APPL_TOP>/admin/<Context_name>/out/<MMDDhhmm>/ 

On the database tier:
<RDBMS ORACLE_HOME>/appsutil/out/<Context_name>/<MMDDhhmm>/ 

where: <MMDDhhmm> = (month, day, hour, and minute of the AutoConfig run)

You can run restore.sh (Unix) or restore.cmd (Windows) to roll back an AutoConfig session.

 

Migrating to AutoConfig on the Database Tier

1. Copy AutoConfig to the RDBMS ORACLE_HOME

as the APPLMGR user:

- source the environment file:

 . /APPS_MI/visappl/APPSORA.env

- Create appsutil.zip file
perl $AD_TOP/bin/admkappsutil.pl

[applmgr@apps ~]$ perl $AD_TOP/bin/admkappsutil.pl
Starting the generation of appsutil.zip
Log file located at /APPS_MI/visappl/admin/log/MakeAppsUtil_05072343.log
output located at /APPS_MI/visappl/admin/out/appsutil.zip
MakeAppsUtil completed successfully.

- Copy the appsutil.zip to the <RDBMS ORACLE_HOME>

- On the Database Tier (as the ORACLE user):

cd <RDBMS ORACLE_HOME>
unzip -o appsutil.zip

For a database upgrade:

cd /APPS_DB_R12/db/tech_st/10.2.0

unzip -o appsutil.zip

2. Generate your Database Context File
cd <RDBMS ORACLE_HOME>
. <CONTEXT_NAME>.env
cd <RDBMS ORACLE_HOME>/appsutil/bin
perl adbldxml.pl tier=db appsuser=<APPSuser>

For a database upgrade:

cd /APPS_DB_R12/db/tech_st/10.2.0

. VIS_db.env  (this file is the one from 9i OHome modified with the new 10g OHome)

cd $ORACLE_HOME/appsutil/bin

perl adbldxml.pl tier=db appsuser=APPS

If the listener.ora is not created in /APPS_DB_R12/db/tech_st/10.2.0/network/admin/VIS_db this will generates an error which can be ignored. 

The following context file will be generated: 

/APPS_DB_R12/db/tech_st/10.2.0/appsutil/VIS_db.xml

3. Review and Resolve Manual Configuration Changes

cd  <RDBMS ORACLE_HOME>/appsutil/bin

adchkcfg.sh contextfile=<CONTEXT>

cd $ORACLE_HOME/appsutil/bin

./adchkcfg.sh contextfile=/APPS_DB_R12/db/tech_st/10.2.0/appsutil/VIS_db.xml

The following report will be generated: /APPS_DB_R12/db/tech_st/10.2.0/appsutil/out/VIS_db/05072108/cfgcheck.html

This report provide information about all file changes, profile option changes and other important database updates that will be done during the next normal execution of AutoConfig

4. Generate and Apply AutoConfig Configuration files

cd <RDBMS ORACLE_HOME>/appsutil/bin
adconfig.sh contextfile=<CONTEXT>

cd $ORACLE_HOME/appsutil/bin

./adconfig.sh contextfile=/APPS_DB_R12/db/tech_st/10.2.0/appsutil/VIS_db.xml

This command creates /APPS_DB_R12/db/tech_st/10.2.0/appsutil/scripts/VIS_db/adautocfg.sh and run it. 

/APPS_DB_R12/db/tech_st/10.2.0/network/admin/VIS_db/listener.ora will be created as well.