Oracle has introduced two new features in autoconfig. These two new features for sure gonna help to reduce the downtime of application for maintenance tasks.1.  AutoConfig: Parallel Run Option

The “Parallel Run” feature enables
AutoConfig to be executed simultaneously across multiple nodes of an Oracle
E-Business Suite instance. Certain AutoConfig configurations of one node depend
on the configurations of other nodes. When running in parallel mode, AutoConfig
uses dbms_locks so that the configuration of one node does not interfere with
the configuration of other nodes. During the instantiation (INST) phase,
locking is done at the script level. During the execution (EXEC) phase, locking
is done at the product_top level.

AutoConfig can be run in parallel mode on
the application tier with the following command:
perl $AD_TOP/bin/adconfig.pl contextfile=<CtxFile>
[product=<product_top>] –parallel
Where <CtxFile> is the absolute path of the applicaton tier context file,
and <product_top> is the short name of the product to be configured.

AutoConfig can be run in parallel mode on
the database tier with the following command:
perl $ORACLE_HOME/appsutil/bin/adconfig.pl contextfile=<CtxFile>
-parallel
Where <CtxFile> is the absolute path of the database tier context file.

In parallel mode,
AutoConfig must be invoked with the “–parallel” option on all nodes of a multi-node
environment.

This feature can be obtained by applying following patch :

This feature is currently not available for
Oracle E-Business Suite 11i

2. AutoConfig: Profiler

This new feature provides a consolidated HTML report of an
AutoConfig run. The report displays a summarized view that lists all the
product tops, along with the total instantiation and execution time of the
templates within each product top. You can drill down further into this report
to view the following:

  • Source and
    target location of each template
  • Time
    consumed to instantiate/execute individual template scripts
  • Execution
    report for each template script

AutoConfig can be run in profile mode on the application
tier with the following command:
$AD_TOP/bin/adconfig.pl contextfile=<CtxFile>
[product=<product_top>] –profile
Where <CtxFile> is the absolute path to the application tier context file
and <product_top>is the short name of the product to configure.

AutoConfig can be run in profile mode
on the database tier with the following command:
perl $ORACLE_HOME/appsutil/bin/adconfig.pl contextfile=<CtxFile> -profile
Where <CtxFile> is the absolute path to the database tier context file.

This feature can be obtained by applying following patch:

Also refer to below oracle blog links for more details.

References:

Oracle Applications Technology Stack Release Notes, Release 12.0.6 [ID
742110.1]

http://blogs.oracle.com/stevenChan/2009/03/power_tools_optimizing_autoconfig_performance.html

http://blogs.oracle.com/stevenChan/2009/03/power_tools_autoconfig_parallel_runs_in_ebs12.html