Frequently Asked Questions Cloning Oracle Applications Release 11i

Frequently Asked Questions
Cloning Oracle Applications

Release 11i
1. What is cloning?
Cloning is the process of creating an identical copy of an already existing Oracle Applications system.
2. How can I clone an Oracle Applications system?

• Cloning Oracle Applications Release 11i
• Cloning Oracle Applications Release 11i with Rapid Clone
3. What are the differences between the two cloning methods?

Cloning Oracle Applications Release 11i was originally published in conjunction with Release 11.5.5 and is applicable for
all 11i releases up to 11.5.5 that are not AutoConfig enabled. Cloning Oracle Applications Release 11i with Rapid Clone
is applicable for all 11i systems that have migrated to AutoConfig and enabled Rapid Clone. This method contains steps
to install AutoConfig and Rapid Clone.
4. What is the AD Cloning utility?

AD Cloning utility (adclone.pl) is the name of the cloning command line utility. This utility is used to preserve and apply
configuration information to the cloned target system.
5. What is Rapid Clone?

Rapid Clone is the new cloning utility introduced in Release 11.5.8. Rapid Clone leverages the new installation and
configuration technology utilized by Rapid Install. See Oracle MetaLink Note 230672.1 (Cloning Oracle Applications 11i
with Rapid Clone) for instructions on installing and enabling Rapid Clone.
6. How do I determine if my system is Rapid Clone enabled?

First, verify that your system is AutoConfig enabled. Then, verify that you have applied the latest Rapid Clone patch
documented in OracleMetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone). See Searching the
Patch History Database in the AD Procedures Guide for instructions on searching for patches applied to your system.
7. What is AutoConfig?
AutoConfig is a configuration tool that supports automated configuration of an Oracle Applications Instance. All of the
information required for configuring an Applications instance is collected into a central repository, called the Applications
Context. When the AutoConfig tool runs, it uses information from the Applications Context file to generate configuration
files and update database profiles. See OracleMetaLink Note 165195.1 for details on installing and migrating to
AutoConfig.
8. How do I determine if my system is AutoConfig enabled?

There are several identifiers for when the system is AutoConfig enabled. The following are two common indicators:
Open the environment file APPSORA.env in your APPL_TOP. If the top of the file says that it is maintained by Auto
Config, then your system is probably using AutoConfig. Check if there is an Applications Context file in the APPL _TOP
/admin directory. This file will typically be named <SID>.xml or <SID>_<HOSTNAME>.xml. Check if there is an
Applications Context file in the RDBMS ORACLE_HOME under the appsutil directory. This file will typically be named
<SID>.xml or <SID>_<HOSTNAME>.xml.
9. We are running Release 11.5.7 (or any prior release), which cloning method can we use?
Due to the advancements in the cloning solution with Rapid Clone, all customers are now recommended to move to
using Rapid Clone. if you are on release 11.5.7 or any release before 11.5.7, you will need to first enable AutoConfig on
your system, if not already done, before you can use Rapid Clone as documented in the Cloning Oracle Applications
Release 11i with Rapid Clone white paper.
10. We are running Release 11.5.8 (or any later release), which cloning method can we use?
In 11.5.8 AutoConfig is enabled on the middle tier out of the box. In 11.5.9 and any later release, AutoConfig is
enabled by default on both the database tier and the middle tier. Update AutoConfig and Rapid Clone code to the latest
code line and use Rapid Clone to clone your system. Full instructions are in Cloning Oracle Applications Release 11i with
Rapid Clone document 230672.1 on Oracle Metalink.
11. Our Oracle Applications system is on Windows, which cloning method can we use?
If your system is on a release prior to 11.5.7 and is not AutoConfig enabled, use the method documented in the Cloning
Oracle Applications Release 11i white paper. If your system is on any AutoConfig-enabled 11i release, use the method
documented in the Cloning Oracle Applications Release 11i with Rapid Clone white paper.
12. We have a Platinum installation of Oracle Applications. Can we clone our system?
Yes, cloning a Platinum system using the Rapid Clone method is no different than cloning a non-Platinum installed
system.
13. Can I clone from one operating system version to another?
Yes, if the target system platform is binary compatible with the source system platform. For example, if you have an
existing single-node Oracle Applications system on Solaris 2.6, you could clone it to a node running Solaris 8, but not to
a node running HP-UX. Note that cloning from a higher version of a platform to a lower version is not supported, for
example, from Solaris 8 to Solaris 2.6. Other examples of binary compatibility for Oracle Applications are:
AIX 4.3.3 to AIX 5.1 (32-bit)
HP-UX 11.0 to HP-UX 11i
Created by Bhaskar Ivaturi 1

Windows NT to Windows 2000
14. Can I clone from one platform to a different platform?

Yes, you can clone or migrate the Applications middle tier from any platform to Linux or any supported UNIX platform
using the procedure described in document 238276.1 "Migrating to Linux with Oracle Applications Release 11i".
15. Can I reclone just the database?

Yes, if the source system has changed and you want to update the target system with these changes, you can reclone
just the changed database. If Applications patches were applied to the source system, the APPL_TOP and the database
must be cloned to keep the file system and database synchronized. See the Recloning section in the white papers for
details.
16. Can I clone a single-node system to a multi-node system?

The Rapid Clone cloning method allows for cloning a single-node system to a multi-node system. See the Cloning Oracle
Applications Release 11i with Rapid Clone white paper for details.
17. What cloning options are available for each cloning method?
The table below shows the cloning options that are currently available for each cloning method.
Multi-node Single node
Single node to Multi-node to With Oracle9i Windows
Recloning to to
Single node Single node Database Platform
Multi-node Multi-node
Cloning Oracle
Available Available Available Not Available Not Available Not Available Available
Applications
Cloning Oracle
Applications
Available Available Available Available Available Available Available
with Rapid
Clone
18. Can I clone a multi-node system to a single-node system?

You can use Rapid Clone to merge multiple APPL_TOP and COMMON_TOP file systems into a single APPL_TOP and
COMMON_TOP file system. For more details about this procedure, see "Section 3: Merging existing APPL_TOPs into a
shared APPL_TOP" in document 233428.1 on OracleMetaLink.
19. Does Rapid Clone modify the source system?

No, Rapid Clone does not modify the source system. adpreclone.pl prepares the source system to be cloned by
collecting information about the database and creating generic templates of files containing source specific hardcoded
values. These templates are stored in the appsutil/template directory leaving the original files untouched. This process
usually takes a few minutes to complete the first time. Migrating to Autoconfig on the database node (pre-req to Rapid
Clone), however, will update the RDBMS init.ora and network listener files. See the instructions in the Autoconfig
document 165195.1 (Section 4: Migrating to AutoConfig on the Database Tier) on how to preserve customizations to these
files.
20. What is the port pool? What if I want to give a specific value to a Server Port?
If you are cloning on the same machine or want to redefine the server ports, you will be prompted for a port pool. The
port pool provides a way to use a set of predefined server ports. There are 100 port pools. For example, if you select 3,
the default database port number (1521) becomes 1524. The following table lists all the server ports. To see how the
port pool calculation works, enter a number between 0 and 99(both inclusive) in the form and click "Get Ports". If you
want to give a specific value to a port on the target system, independently from the port pool, you must first complete
the Target System configuration with adcfgclone.pl (temporarily select a value for the port pool). Once adcfgclone.pl
completes successfully, edit the new target context file with editcontext or OAM and modify
22. Does Rapid Clone preserve the patch history?

Yes, Rapid Clone preserves the patch history of the complete Applications Stack:
RDBMS ORACLE_HOME: preserve the OUI oraInventory.
iAS ORACLE_HOME: preserve the OUI oraInventory.
806 ORACLE_HOME: preserve the patch level and ORCA inventory.
APPL_TOP and Database: preserve the patch level and history tables.
23. Can I clone a clone?

Yes, a cloned system created with Rapid Clone can then be used as the Source System in the next cloning. Rapid Install
itself is now a clone of a clone using the Rapid Clone technology.
24. Can I change the database dbf files layout while cloning?
Yes, Rapid Clone allows adding or removing database mount points or redistribute dbf files among mount points in the
target system. As long as all the source system dbf files are present in the target system database mount points
specified during the adcfgclone prompts (see question "How does adcfgclone.pl know the target system values?"),
Rapid Clone will find them and re-create the database control file accordingly.
25. What is the oraInventory?

The oraInventory is the location for the OUI (Oracle Universal Installer)'s bookkeeping. The inventory stores information
about: All Oracle software products installed in all ORACLE_HOMES on a machine Other non-Oracle products, such as
the Java Runtime Environment (JRE). In a 11i Application system the RDBMS and iAS ORACLE_HOMEs are registered in

the oraInventory. The 806 ORACLE_HOME, which is not managed through OUI, is not. On Unix/Linux, the location of
the oraInventory is defined by the content of oraInst.loc, at:/var/opt/oracle/oraInst.loc on Solaris, HP-UX and Tru64
- /etc/oraInst.loc on Linux and AIX. On Windows, the location of the oraInventory is defined by the value of the registry
key HKEY_LOCAL_MACHINE|Software\Oracle\INST_LOC or if this value is not defined, at C:\ProgramFiles\Oracle\
Inventory
26. What is a binary oraInventory? Is my Inventory binary?

Before OUI 2.X, the oraInventory was binary. A binary oraInventory centralizes, in a binary format, the location of every
Oracle products on the machine and the detail of their patch level. The oraInventory location is defined by the content
of oraInst.loc. You will have a binary inventory only if ALL of the following conditions are met: you are on 11.5.7 or
earlier (11.5.8+ install XML inventory out of the box) you have never installed OUI 2.X or higher (Install converts the
inventory to XML) you have never run Rapid Clone (Rapid Clone converts the inventory to XML) If the following file
exists, the oraInventory is NOT binary: <oraInventory location as pointed by oraInst.loc>/ContentsXML/inventory.xml
27. What is a XML oraInventory? Is my Inventory XML?

Starting with OUI 2.X and 11.5.8, the information in the inventory is stored in Extensible Markup Language (XML)
format. The XML format allows for easier diagnosis of problems and faster loading of data Rapid Clone requires the
inventory to be in XML format in order to clone it, and will take care of performing the binary to XML convertion if
necessary. Unlike the binary oraInventory, The XML inventory is divided into 2 distinct components:
The Global inventory (or Central inventory), The Local inventory (or Home inventory) More information about these
components is available under other questions in this FAQ. The inventory is XML if the following file exists: $ORACLE
_HOME /inventory/ContentXML/comps.xml
28. What is the Global (or Central) Inventory?

The Global Inventory is the part of the XML inventory that contains the high level list of all oracle products installed on a
machine. There should therefore be only one per machine. Its location is defined by the content of oraInst.loc. The
Global Inventory records the physical location of Oracle products installed on the machine, such as ORACLE_HOMES
(RDBMS and IAS) or JRE. It does not have any information about the detail of patches applied to each ORACLE_HOMEs.
The Global Inventory gets updated every time you install or de-install an ORACLE_HOME on the machine, be it through
OUI Installer, Rapid Install, or Rapid Clone. Note: If you need to delete an ORACLE_HOME, you should always do it
through the OUI de-installer in order to keep the Global Inventory synchronized.
29. What is the Local (or Home) Inventory?

There is one Local Inventory per ORACLE_HOME. It is physically located inside the ORACLE_HOME at $ORACLE_HOME/
inventory and contains the detail of the patch level for that ORACLE_HOME. The Local Inventory gets updated whenever
a patch is applied to the ORACLE_HOME, using OUI.
30. How does Rapid Clone deal with the oraInventory?

Rapid Clone requires OUI 2.2 to be installed in the ORACLE_HOME as a prerequisite and will performs all the actions
necessary to clone the inventory: Converts the Global inventory to xml format when it was binary on either the source
system or the target system Registers the cloned ORACLE_HOME in the target system Global Inventory Updates the
Local Inventory of the target ORACLE_HOME to reflect the new machine, paths, users, etc.
31. Why don't I need to manually copy the oraInventory when cloning?
The local inventory is automatically copied from the source system to the target system as part of copying the ORACLE
_HOME itself. The Global Inventory is machine specific and therefore should not be copied. If you are cloning from one
machine to a different machine, Rapid Clone will simply register the target ORACLE_HOME in the target machine Global
Inventory (This action will automatically create the Global Inventory if it did not exist on that machine).
32. What does OUISetup.pl do?

OUISetup.pl is shipped with the OUI patch, listed as a prerequisite to Rapid Clone (see Metalink Node 230672.1). It
should be run as part of the OUI patch installation and will perform the following tasks: Register the OUI program in the
Global Inventory. Register the JRE in the Global Inventory. Ensure that the ORACLE_HOME in which the patch is install
is properly registered in the Global Inventory. In doing so, it will attempt to automatically fix Inventory corruptions that
are known to cause problem while cloning, such as - Home indexes out of sync between the Global and Local Inventory
- Duplicate Home Names entries - Duplicate Home Path entries
Frequently Asked Questions about

Using AutoConfig with Oracle Applications
Release 11i
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, and one for the database tier. When AutoConfig runs, it uses
information from the Applications Context file to generate all configuration files and update database profiles.
2. What is the difference between the application tier and the database tier?
Before we can answer that, let's define a few terms in the context of the Release 11i architecture: A node or machine is
a computer. A server is a collection of one or more computer processes that perform a specific function. A tier is a
logical grouping of one or more servers or computer processes. Now let's answer the question. The application tier (also
called the middle tier) consists of a number of servers, such as the concurrent processing server, web server, forms

server, and administration server, that process the transactions of the Release 11i system, as well as provide
communication between the desktop tier and the database tier. (Such servers are also referred to as application tier
servers. Likewise, the nodes on which such servers run are also referred to as application tier server nodes.) The
database tier consists of the database server, which stores all the data of the Release 11i system. The primary location
of the files used by the application tier servers is the APPL_TOP, whereas the primary location of the files used by the
database server is the Oracle8i or Oracle9i ORACLE_HOME. For more information about the Release 11i architecture,
refer to Oracle Applications Concepts, Release 11i.
3. How can I identify the application tier and the database tier in a multi-node system?
A node can contain one or more servers, and can therefore belong to one or more tiers. In a single node system, that
node belongs to both the application tier and the database tier, since all servers are contained on that single node.
In a multi-node system, each node contains one or more servers, and therefore belongs to one or both tiers. If the
node contains any of the application tier servers, including the web server, forms server, concurrent processing server,
or administration server, which means that there is an APPL_TOP on the node, then the node belongs to the application
tier, and is considered an application tier server node. If the node contains the database server, which means that there
is an Oracle8i or Oracle9i ORACLE_HOME and the Applications database instance on the node, then the node belongs to
the database tier, and is considered a database server node.
Let's analyze a common configuration where the database server and the concurrent processing server exist on one
node (Node 1), and the other servers exist on a second node (Node 2). Since Node 1 contains both an application tier
server (the concurrent processing server) and the database server, Node 1 belongs to both the database tier and the
application tier. But since Node 2 contains only application tier servers, Node 2 belongs only to the application tier.
4. How do I configure AutoConfig for a multi-node system?

The AutoConfig patch is applied using AutoPatch. Therefore, it must be applied to each application tier server node,
which means to each node that contains an APPL_TOP. If the database server node contains only the database server
and no other servers, then you would not apply an AutoConfig patch on that node. Once all the application tier servers
have been updated by the AutoConfig patch, there is a separate process for updating the database server, which is
documented in Metalink Note 165195.1. This process consists of running the admkappsutil utility on one (only one)
application tier, copying the generated appsutil.zip file to the database tier and unzipping the appsutil.zip file into the
RDBMS ORACLE HOME.
Example 1: The system has two nodes. Node 1 = administration server, concurrent processing server, database server
Node 2 = forms server, web server Since both nodes are application tier server nodes, the AutoConfig patches need to
be applied to both nodes. Once the patches are applied, you have to update the database server Node1 by running the
admkappsutil utility from the APPL_TOP on Node1, copying the generated appsutil.zip to your RDBMS ORACLE_HOME
on Node1 and unzipping the appsutil.zip file into the RDBMS ORACLE_HOME.
Example 2: The system has two nodes. Node 1 = database server Node 2 = administration server, concurrent
processing server, forms server, web server Since Node 2 is the only application tier server node, the AutoConfig patch
needs only be applied to Node 2. Once the patch is applied, you have to update the database server Node1 by running
the admkappsutil utility from the APPL_TOP on Node2, copying the generated appsutil.zip to your RDBMS
ORACLE_HOME on Node1 and unzipping the appsutil.zip file into the RDBMS ORACLE_HOME.
Example 3: The system has three nodes. Node 1 = database server Node 2 = administration server, concurrent
processing server Node 3 = forms server, web server Since Node 2 and Node 3 are application tier server nodes, the
AutoConfig patch needs to be applied to Node 2 and Node3. Once the patches are applied, you have to update the
database server Node1 by running the admkappsutil utility either from the APPL_TOP on Node1 or Node2 (it does not
matter on which Node you run the admkappsutil utility), copying the generated appsutil.zip to your RDBMS
ORACLE_HOME on Node1 and unzipping the appsutil.zip file into the RDBMS ORACLE_HOME.
5. What user do I log in as to use AutoConfig in a typical multi-node system?

For nodes running Windows, there is only one user that owns both the application tier servers and the database server,
so you would log in as that user. For nodes running UNIX or Linux, if you want to configure the application tier servers,
log in as the user that owns the application tier servers (sometimes referred to as the applmgr user). If you want to
configure the database server, log in as the user that owns the database server (sometimes referred to as the oracle
user).
6. How do I determine if AutoConfig is enabled?

Check for the script adcfginfo.sh (adcfginfo.cmd on Windows) under <AD_TOP>/bin. If it exists, use it to check whether
AutoConfig is enabled. For the APPL_TOP: adcfginfo.sh contextfile=<CONTEXT>
For products:
adcfginfo.sh contextfile=<CONTEXT> show=enabled
If adcfginfo.sh doesn't exist, look in any configuration file in your APPL_TOP. If the file header contains the following,
AutoConfig has been run on your instance :
################################################################
# AutoConfig automatically generates this file. 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.
################################################################
Note: If you manually changed any file containing this file header, it is no longer considered as
officially AutoConfig enabled!
7. 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.
8. What does the term "Context_name" mean?

The "Context_name" is the logical name for your Context. The default value for Context_name is <SID>_<hostname>.
In earlier versions of AutoConfig the default was set to <SID>.
9. What are the basic components of AutoConfig?

Components Location Description
Applications Context On the application tier: An XML repository (<Context_name>.xml) contains

<APPL_TOP>/admin information specific to that Applications instance. Can
On the database tier: be updated by running the Context Editor.
<RDBMS ORACLE_HOME>/appsutil Do not manually update this file!
AutoConfig Template On the application tier: Include named tags which are replaced with instance-
Files <PROD_TOP>/admin/template specific information from the Applications Context.
For example: There is one template file for each configuration file.
<AD_TOP>/admin/template For example:
<FND_TOP>/admin/template apps_nt.conf
On the database tier: apps_ux.conf
<RDBMS
ORACLE_HOME>/appsutil/template
AutoConfig File Driver On the application tier: Used by AutoConfig to list the AutoConfig Template
<PROD_TOP>/admin/driver Files, their destination locations, and the commands
For example: to be executed, for example, the commands to
<AD_TOP>/admin/driver/adtmpl.drv update profile options. Every Product Top contains its
<FND_TOP>/admin/driver/fndtmpl.drv own AutoConfig File Driver.
On the database tier:

<RDBMS
ORACLE_HOME>/appsutil/template
AutoConfig Scripts On the application tier: Provide a simplified

<AD_TOP>/bin interface to the AutoConfig APIs.
On the database tier: For example:
<RDBMS adautocfg.sh / adautocfg.cmd
ORACLE_HOME>/appsutil/bin adconfig.sh / adconfig.cmd
10. What are the different AutoConfig scripts and what do they do?
Scripts Location Description
adautocfg.sh On the application tier: A wrapper script that calls adconfig.sh/ adconfig.cmd.
adautocfg.cmd <COMMON_TOP>/admin/scripts/ Instantiates template files with values specific to the
<Context_name> instance (taken from the Applications Context). Updates
On the database tier: configuration files and profile options.
<RDBMS ORACLE_HOME>/appsutil/
scripts/ <Context_name>
adconfig.sh On the application tier: A wrapper script that calls adconfig.pl. In earlier versions of
adconfig.cmd <AD_TOP>/bin AutoConfig adconfig.sh/adconfig.cmd used to call the Java
On the database tier: API to start AutoConfig.
<RDBMS ORACLE_HOME>/appsutil/bin/
adconfig.pl On the application tier: A wrapper script that calls the Java API to start AutoConfig.
<AD_TOP>/bin
<RDBMS ORACLE_HOME>/appsutil/bin

adbldxml.sh On the application tier: Creates the Applications Context File. Before running this
adbldxml.cmd <AD_TOP>/bin script, you need to source the environment.
On the database tier: On the application tier:
<RDBMS ORACLE_HOME>/appsutil/bin Source APPS<Context_name>.env (or APPSORA.env if
APPS<Context_name>.env doesn't exist).
Source <Context_name>.env
adchkcfg.sh On the application tier: Generates a report that highlights differences between the
adchkcfg.cmd <AD_TOP>/bin original config files and AutoConfig-generated config files.
On the database tier: The report is named cfgcheck.html. It is located under:
<RDBMS ORACLE_HOME>/appsutil/bin On the application tier:
<APPL_TOP>/admin/
<Context_name>/out/<MMDDhhmm>
<RDBMS ORACLE_HOME>/appsutil/out/
<Context_name>/<MMDDhhmm>
AutoConfig pre-requisites
Do I need to upgrade to Apache 1.3.12s?
Answer: If you are applying the AutoConfig patch to an instance created with a Rapid Install version lower than Release
11.5.5, upgrade to Apache 1.3.12s.
Refer to Metalink Document 161779.1 on OracleMetalink.
Note: Rapid Install for versions 11i7 and higher installs Oracle HTTP Server 1.3.19 from iAS
1.0.2.2
The Context file

10. How will the adbldxml utility name the Applications Context file it generates?
When adbldxml generates the Context file, it first checks for the existence of an Applications Context file conforming to
specific requirements in the <APPL_TOP>/admin directory on the application tier and in the <RDBMS ORACLE_HOME>
/appsutil directory on the database tier. If an xml file exists, adbldxml creates the Applications Context file using the
same name. Specific requirements are:
The Context file refers to the hostname for which we generate the file.
The Context file refers to the Database SID for which we generate the file.
The default name for the Context file is <Context_name>.xml.
11. How can I make changes to the Applications Context file?

Go to the OAM Login page. Sign in and navigate to Site Map. Click on AutoConfig. Use this link to update your
Applications Context file. For additional information see the Oracle Applications Maintenance Procedures.
Note: Manually editing the Applictions Context file is not supported. Many context variables have dependencies
between each other. The OAM AutoConfig resolves all these dependencies when changing the value of a variable. By
manually editing the Applications Context file you will bring the data into an inconsistent state.
12. I want to execute the adbldxml utility on a fresh RDBMS Oracle Home. How can I build the Context file,
when the database environment file is not present?
The adbldxml utility requires the following environment variables to be set:
ORACLE_HOME
ORACLE_SID (LOCAL on Windows)
TNS_ADMIN
Set the variables according to your instance. For example:
On UNIX
export ORACLE_SID=PROD
On Windows set LOCAL=PROD
14. When should I run AutoConfig?

You should run AutoConfig in the event of the following cases:
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.
15. Which files / profile options get changed when I run AutoConfig?
Run the adchkcfg utility to get an html report that lists all the files and profile options that get changed when you run
AutoConfig. If you have AD.I or higher applied and you want to see the list of files and profile options that will get
changed when adpatch is run, then run adpatch with the apply=no option before applying the patch. For more
information, refer to Oracle Applications Maintenance Procedures - Section Patching - Testing a Patch before Applying it. For
instructions on how to run the adchkcfg utility and a discussion about the report that the utility generates

16. Where is the log file located that AutoConfig creates?
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)
17. Which directories based on the Context_name will AutoConfig create?

AutoConfig creates the following directories based on the Context_name:
Install Scripts : <COMMON_TOP>/admin/install/<Context_name>
Control Scripts : <COMMON_TOP>/admin/scripts/<Context_name>
Log files : <COMMON_TOP>/admin/log/<Context_name>
Beginning with Release 11.5.7, Oracle Applications comes with the modified directory structure.
18. I see multiple directories under <COMMON_TOP>/admin/scripts - which one do I use?

Previously, AutoConfig generated the directory <SID> in <COMMON_TOP>/admin/scripts. To provide support for a
shared APPL_TOP, AutoConfig now creates the directory <SID>_<hostname>. If your system contains both directory
names, use the scripts under <SID>_<hostname>. You can safely delete directories named <SID>, after backing them
up. Refer to MetaLink Document 233428.1 on OracleMetalink to learn more about the Shared APPL_TOP configuration.
19. How can I roll back an AutoConfig session?

All 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.
20. How does AutoConfig know which scripts to create for service controls?
The following variables in the Applications Context File let AutoConfig know which scripts to create:
Context Variable Action
s_isAdmin If set to Yes, create administration service scripts
s_isConc If set to Yes, create concurrent processing and reports service scripts
s_isWeb If set to Yes, create web service scripts
s_isForms If set to Yes, create forms service scripts
The variables are set according to your configuration when you create the Applications Context file:
Single-node system: All the service control scripts are present on the same node. Therefore, all variables are set to
"YES" in the Applications Context file.
Multi-node system: Example
Node 1 = forms server, web server
Node 2 = concurrent processing server, administration server, database server
On Node 1 only the forms and web service control scripts are created. On Node 2 only the admin and concurrent
processing service control scripts are created. The Applications Context files contain the following values:
Node 1 Node 2
Context Variable
Value Value
s_isAdmin NO YES
s_isConc NO YES
s_isWeb YES NO
s_isForms YES NO
21. How does AutoConfig know what application tier node type the APPL_TOP supports?
The AD Utilities such as AutoPatch and AD Administration patch and maintain files based on the application tier node
type that the APPL_TOP supports. The following variables in the Applications Context file define which files are patched
and maintained for the APPL_TOP:
Context Variable Action
s_isAdAdmin If set to Yes, the APPL_TOP contains binaries and scripts used to maintain the Applications system.
If set to Yes, the APPL_TOP can be used to provide the CP and Reports services. All binaries, scripts,
s_isAdConc
reports and other files related to these services exist in the APPL_TOP.
s_isAdWeb If set to Yes, the APPL_TOP contains the necessary files to provide Oracle HTTP services
s_isAdForms If set to Yes, the APPL_TOP contains the necessary files to provide Forms services
The variables are set according to your configuration when you create the Applications Context file: Single-node system
All the application tier types are present on the same node and there is only one APPL_TOP. All variables are set to ‘YES’
in the Applications Context file. Multi-node system sharing the same APPL_TOP: A shared APPL_TOP contains all the
necessary software components to run any service. All variables are set to "YES" in the Applications Context files
sharing the APPL_TOP. Multi-node system, where every node has a separate APPL_TOP: Example:
Node 1 = forms server, web server
Node 2 = concurrent processing server, administration server, database server
Every node has its own APPL_TOP that only patches and maintains the files specific to the node. The Applications
Context files contain the following values:

Node 1 Node 2
Context Variable
Value Value
s_isAdAdmin NO YES
s_isAdConc NO YES
s_isAdWeb YES NO
s_isAdForms YES NO
22. What do I do when a patch or Oracle documentation instructs me to manually modify an AutoConfig-
maintained file?
Contact Oracle Support to incorporate the necessary changes in the AutoConfig templates: Identify the patch or the
note that is requesting the manual change. Log a Service Request with Oracle Support, providing the same information.
Patching AutoConfig
23. How do I get the latest changes to AutoConfig?
Updates to AutoConfig are delivered in the ADX product patch. The latest patch at the time of this writing are patch
number 3453499.
24. How do I apply the latest AutoConfig patch?

Perform the following steps in the order listed: Review the pre-requisites as documented in Metalink Note 165195.1.
Apply the AutoConfig patch. Update the Oracle Applications file system with the AutoConfig files by applying patch
3453499. to all application tier nodes in the Applications instance. Copy AutoConfig to the RDBMS ORACLE_HOME
If you enabled AutoConfig on the Database Tier, update the RDBMS ORACLE_HOME file system with the AutoConfig files
by performing the following steps: On the Application Tier (as the APPLMGR user): Log in to the APPL_TOP environment
(source the environment file) Create appsutil.zip file, perl <AD_TOP>/bin/admkappsutil.pl, This will create appsutil.zip
in $APPL_TOP/admin/out .
On the Database Tier (as the ORACLE user): Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME> cd
<RDBMS ORACLE_HOME> unzip -o appsutil.zip Run AutoConfig on the Database Tier If you enabled AutoConfig on the
Database Tier, run AutoConfig on the database tier node.
Attention: The database server must remain available during the AutoConfig run. All the other database tier services
should be shut down.
Run AutoConfig on the Application Tiers, Run AutoConfig on all application tier nodes.
Attention: The database server must remain available during the AutoConfig run. Only the application tier servers should
be shut down.
Database connectivity
39. Should the database server remain available during the AutoConfig run?
Yes. The database server and the database listener must remain available during the AutoConfig run. This is true when
running AutoConfig on the application tier, as well when running AutoConfig on the database tier. If you run AutoConfig
on the application tier, then the 806 database listener must remain available also.
40. What is the use of the context variable s_apps_jdbc_connect_descriptor?

The s_apps_jdbc_connect_descriptor stores the connect string for jdbc connections. All jdbc connections are done using
this context variable. The value for this context variable is generated by AutoConfig. When the value is reset (empty),
AutoConfig tries to connect to the database using the s_dbSid, s_dbhost and s_dbport context variables.
41. When do I need to reset (empty) the context variable s_apps_jdbc_connect_descriptor?

You should reset the value for s_apps_jdbc_connect_descriptor to an empty value (" "), when one of the following value
changes: Database Host, Database Port
42. What steps do I need to follow to maintain my database connectivity when I migrate my database from
one host/platform to another?
Perform the steps in the order listed: Before the migration: Deregister the database tier from the Net Services Topology
Data Model. Refer to the question "How do I deregister a database tier from the Net Services Topology Data Model?" If
you haven't enabled AutoConfig on the database tier, you can ignore this step. After the migration: Reset the context
variable s_apps_jdbc_connect_descriptor in the context file for the application tier to an empty string. Update the
context variables s_dbhost and s_dbport in the context file for the application tier to reflect the new values in the
middle tier context file.
43. I migrated my database tier to a new host/platform, but the application tier still tries to connect to the
old database. How can I fix this situation, so that the application tier connects to the new database?
Your old database tier is still registered in the Net Services Topology Data Model. Perform the following steps: You have
to clean up the data model by following the steps described in the question: "How do I purge the complete Net Services
Topology Data Model?" Perform the step described in the question: "How do I seed the Net Service Topology Data
Model?"
Troubleshooting
53. What should I do if my AutoConfig script exits with non-zero status?
If AutoConfig exits with non-zero status, open the adconfig.log and check for the reported errors: Errors in the
instantiation phase: Check to see if the template files listed in the error summary exist in your file system. If they do
not exist, the AutoConfig File Driver of the product is faulty. Report the problem to Oracle Support. If the template files
exist, check for permission issues. If you cannot fix the issue, report the problem to Oracle Support. Error encountered
in the SETUP/PROFILE/APPLY phase: Check the adconfig.log file to see the reason for the failure. If you cannot fix the
issue, report the problem to Oracle Support.
56. My concurrent managers don't start after running AutoConfig? How do I resolve this issue?
Look in the file APPLSYS_ux.env (UNIX) or APPLSYS_nt.env (Windows) located in <AD_TOP>/admin/template. If the
version of the file is 115.15 or lower, your environment file hard codes variables, which prevent the concurrent manager
to start. Apply the latest AutoConfig patch to get the templates that use Application Context variables.
58. How do I resolve an address in use (could not bind to port) when staring Apache?
The error "Address already in use: make_sock could not bind to port" occurs when non-SSL Apache and SSL Apache
occupy the same port. The latest AutoConfig patch makes sure, that these ports don't conflict.
Reference:
59. I get the message "You are not authorized to view this page" when I access the application. How do I
resolve this problem?
After applying TXK AutoConfig Template Rollup F (patch 3104607) or later, the Apache configuration won't allow
symbolic links per default. Standard security practice and our strong recommendation is that you don't use symbolic
links for E-Business Suite files. If you want to enable symbolic links, use the Context Editor to change the value of the
variable s_options_symlinks from "Options -FollowSymLinks" to "# Options -FollowSymLinks". Run AutoConfig to reflect
the change and restart the applications services. The pre-patch report txkValidateRollup of TXK AutoConfig Template
Rollup G (patch 3239694) or later provides you more detailed instructions.
60. On HP/UX Itanium adconfig.pl fails because of a missing POSIX module. How do I resolve this
problem?
When you get the error message "Can't locate loadable object for module POSIX @INC." while running AutoConfig on
HP/UX Itanium, then download and apply patch 4261525 .
Concurrent Manager
Note: 105133.1
FND Concurrent Manager FAQ's
1. When would one be required to bounce (stop and restart) the Concurrent Manager?
Using the printer definition process within Applications, it is imperative that the Internal Manager (ICM) is bounced in
order to pick up the changes. If only a concurrent program definition is modified, running a verify on the Internal
Manager will pick up the changes without the need for bouncing the manager.
2. Does the Internal manager schedule requests to be run or does it put requests into queues to be run by
other managers?
This is a very common misconception. The ICM really does not have any such scheduling responsibilities. It has nothing
to do with scheduling requests, or deciding which manager will run a particular request. Its function is only to run
‘queue control' requests, which are requests to startup or shutdown, other managers. It is responsible for startup and
shutdown of the whole concurrent processing facility, and it also monitors the other managers periodically, and restarts
them if they should go down. It can also take over the Conflict Resolution manager's job, and resolve incompatibilities.
If the ICM itself should go down, requests will continue to run normally, except for 'queue control' requests. You can
restart it with 'startmgr', you do not need to kill the other managers first.
3. How can I check to see if a concurrent manager is running?

One way to see if a manager is running is to use the 'Administer Concurrent Managers' form. Navigate to Concurrent-
>Managers->Administer. You will see two columns labeled 'Actual' and 'Target'. The Target column lists the number of
processes that should be running for each manager for this particular workshift. The Actual column lists the number of
processes that are actually running. If the Actual column is zero, there are no processes running for this manager. If the
Target column is zero, then either a work shift has not been assigned to this manager, or the current workshift does not
specify any target processes. If the target column is not zero, then the manager processes have either failed to start
up, or gone down. You should check the manager's logfile and the ICM logfile. You can also search for OS processes
using the 'ps' command. It is possible for the form to be inaccurate, i.e. it may show actual processes even though they
are not really running. When in doubt, check for processes at the OS level. On NT, you can check to see if the
Concurrent Manager Service is running using the Services control panel.
4. Where do concurrent request or manager logfiles and output files go?

The concurrent manager first looks for the environment variable $APPLCSF. If this is set, it creates a path using two
other environment variables: $APPLLOG and $APPLOUT It places log files in $APPLCSF/$APPLLOG, output files go in
$APPLCSF/$APPLOUT So for example, if you have this environment set: $APPLCSF = /u01/appl/common
$APPLLOG = log, $APPLOUT = out
The concurrent manager will place log files in /u01/appl/common/log, and output files in /u01/appl/common/out Note
that $APPLCSF must be a full, absolute path, and the other two are directory names. If $APPLCSF is not set, it places
the files under the product top of the application associated with the request. For example, a PO report would go under
$PO_TOP/$APPLLOG and $PO_TOP/$APPLOUT Logfiles go to:u01/appl/po/9.0/log Output files to: /u01/appl/po/9.0/out.
All these directories must exist and have the correct permissions. Note that all concurrent requests produce a log file,
but not necessarily an output file. Concurrent manager logfiles follow the same convention, and will be found in the
$APPLLOG directory
5. What are the logfile and output file naming conventions?

Request logfiles: l<request id>.req Output files: If $APPCPNAM is not set: <username>.<request id>

If $APPCPNAM = REQID: o<request id>.out If $APPCPNAM = USER:<username>.out Where:<request id>=the request
id of the concurrent request And: <username> = the id of the user that submitted the request Manager logfiles:
ICM logfile: Default is std.mgr, can be changed with the mgrname Startup parameter Concurrent manager log:
w<XXXXXX>.mgr. Transaction manager log:t<XXXXXX>.mgr, Conflict Resolution manager log:c<XXXXXX>.mgr.
Where: <XXXXXX> is the concurrent process id of the manager
6. Can I delete a concurrent manager?

You can disable the manager by checking the 'Enabled' checkbox, or you can simply terminate the manager and it will
not run again unless you reactivate it. If it is really necessary, you can query the manager in the 'Define Manager' form,
and delete the row. (It is recommended that you DO NOT do this)
7. What is the function of the 'Conflict Resolution Manager'?

Concurrent managers read requests to start concurrent programs running. The Conflict Resolution Manager Checks
concurrent program definitions for incompatibility rules. If a program is identified as Run Alone, then the Conflict
Resolution Manager prevents the concurrent managers from starting other programs in the same conflict domain.
When a program lists other programs as being incompatible with it, the Conflict Resolution Manager prevents the
program from starting until any incompatible programs in the same domain have completed running.
8. What is the 'Internal Scheduler/Prereleaser' manager?

The short name for this manager is FNDSCH. It is also known as the Advanced Scheduler/Prereleaser Manager. This
manager is intended to implement Advanced Schedules. Its job is to determine when a scheduled request is ready to
run. Advanced Schedules were not fully implemented in Release 11.0; they are implemented in Release 11.5, but are
not widely used by the various Apps products. General Ledger uses FNDSCH for financial schedules based on different
calendars and period types. It is then possible to schedule AutoAllocation sets, Recurring Journals, MassAllocations,
Budget Formulas, and MassBudgets to run according to the General Ledger schedules that have been defined. If
financial schedules in GL are not being used then it is not a problem to deactivate this manager.
9. What is the 'Internal Monitor' manager/service?

This manager/service is used to implement Distributed Concurrent Processing. It monitors whether the ICM is still
running, and if the ICM crashes, it will restart it on another node. You do not need to run this manager/service unless
you are using Distributed Concurrent Processing.
10. How do I check/set the PMON method?

To check the PMON method:
1) cd $FND_TOP/sql
2) sqlplus apps/apps @afimchk.sql
This will tell whether the internal manager is running, what the PMON method is, and where the log file is.
To set the PMON method:
1) first shut the concurrent managers down
2) cd $FND_TOP/sql
3) sqlplus apps/apps @afimpmon.sql LOCK (or RDBMS)
11. How do I enable/disable the Conflict Resolution Manager?

Use the system profile option 'concurrent: Use ICM'. Setting this to 'No' (which is the default) allows the CRM to be
started. Setting it to 'Yes' cause the CRM to be shutdown and the Internal Manager (ICM) will take over the conflict
resolution duties. If the CRM will not start (it is started automatically by the ICM), check this profile option. Note that
using the ICM to resolve conflicts is not recommended. The CRM's sole purpose is to resolve conflicts, while the ICM has
other functions to perform as well. Only set this option to 'YES' if you have a good reason to do so.
12. How do I clean out the Concurrent Manager tables?

Cleaning out the tables is a useful method of making sure that there are no invalid statuses that can prevent the
managers from starting. Previously, this has been done by truncating fnd_concurrent_processes and/or fnd_concurrent
_requests. Truncation of the tables is a little drastic, and can cause problems later when trying to purge requests, not to
mention losing all of the request information. Run the script, cmclean.sql, article Note 134007.1 CMCLEAN.SQL - Non
Destructive Script to Clean Concurrent Manager Tables It will make sure the relevant status codes are valid without
deleting any information.
13. How do I tell concurrent manager processes apart at the OS level?

Use: pf -ef | grep FNDLIBR
This will produce output like:
vd11 13703 13660 0 May 11? 0:01 FNDLIBR FND Concurrent_Processor
MANAGE OLOGIN="APPS/94A491A1000000000000000000
n1070161 24936 24927 0 Apr 29? 0:05 FNDLIBR FND Concurrent_Processor
MANAGE OLOGIN="APPS_APPDEMO/94C4B1C10000000000
n1070161 24938 24927 0 Apr 29? 0:06 FNDLIBR FND Concurrent_Processor
MANAGE OLOGIN="APPS_APPDEMO/94C4B1C10000000000
n1070161 24927 24922 0 Apr 29? 2:03 FNDLIBR FND CPMGR FNDCPMBR sysmgr
="“sleep=60 pmon=20 diag=N logfile=/u16/app
The last process, #24927, shows 'FNDLIBR FND CPMGR', this one is the Internal Manager (ICM). Notice that it gives
some of the parameters it was started with; the other processes showing 'Concurrent_Processor' are Standard manager
processes. Notice that the ICM process is the parent process of the Standard managers. (Processes 24936 and 24938)
Other managers will have the name of the executable, like ARLIBR or INVLIBR:
$ ps -ef | grep ARLIBR

vd11 13683 13660 0 May 11? 0:20 ARLIBR
APPS/82A2A4940000000000000000000000000000000000000000000000000000 AR ART
The Conflict Resolution manager will look like:
$ ps -ef | grep FNDCRM
n1070161 24941 24927 0 Apr 29? 1:17 FNDCRM
APPS_APPDEMO/84BFBEB9000000000000000000000000000000000000000000000000000
14. What is the syntax for controlling the concurrent manager using startmgr and concsub in NT?
On NT, the concurrent manager is run as an NT service; you start and stop the managers using the Services control
panel. See the Applications Installation manual for NT, Appendix A for details. See pg. 5-9 of this manual for
instructions on creating the concurrent manager service.
15. Why am I seeing pinging entries like this in the ICM logfile?
PING (0.0.0.0): 56 data bytes
64 bytes from 192.75.91.2: icmp_seq=0 ttl=255 time=0.705 ms
Process monitor session ended : 29-FEB-2000 10:38:43
Pinging other machines is used in Distributed Concurrent Processing.
This means you have DCP turned on, using the environment variable
APPLDCP. Set APPLDCP to OFF and restart the managers.
16. I hit the Restart button to start the Standard manager, but it still did not start?
Telling a manager to restart just sets the status to Restart. The ICM will start it the next process monitor session or the
next time the ICM starts. Use Activate to start a manager immediately. When a manager is deactivated manually, the
ICM will not restart it, you will need to set it to Restart, or activate it manually.
17. How many rows are in FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROCESSES tables?

When tables reach above 3000-4000 rows, the performance begins to diminish. You may want to run Purge Concurrent
Request on a regular basis, dependant on the amount of requests being run. The Purge Concurrent Requests job can be
used to purge: Requests, Mgr logs, and All requests depending on what is chosen. Use the following options: Enter =
All, Mode = AGE, Mode Value = 15 . The std.mgr log continuously grows where it may good to archive it regularly. Any
processes pending in Internal or Conflict Resolution Manager? Best course of action before starting the Concurrent
Managers is to cancel any "Deactivate" or "Verify" jobs pending in the Internal Manager and place any other pending
jobs on hold.
18. How do I turn on transaction manager diagnostics?

Set the profile option 'Concurrent:Debug Flags' to 'TCTM1' at the site level. This will cause transactions to make debug
entries in the FND_CONCURRENT_DEBUG_INFO table. Truncate this table before running a tranasction, then select the
entries from the table. Starting the managers with diag=Y will also produce more information in the transaction
manager logfile.
19. How do transaction managers work?

Briefly: (See the server documentation for details on the DBMS_PIPE package)
1) A transaction manager is started on the concurrent processing server, and periodically reads the pipe for incoming
transactions.
2) A client program (usually a form) calls the FND_TRANSACTION.SYNCHRONOUS function.
3) This function writes a message into the pipe containing the program to be run and its parameters.
4) FND_TRANSACTION.SYNCHRONOUS begins reading a return pipe for the return status.
5) The manager sees the message in the pipe, retrieves the program id and parameters.
6) The manager runs the program with the specified parameters. The program will be of type 'Immediate', so there will
not be a separate concurrent request run.
7) The program completes, and the manager packs its return status into the return pipe.
8) FND_TRANSACTION.SYNCHRONOUS reads the return value and passes it back to its caller.
Note that these events take place essentially simultaneously on the client and server. This is a synchronous transaction
because the client waits for the server to return, or times out waiting for it.
Problem....
When you try to submit a request like Active users or Active responsibilities, request gets submitted.
When we view the help requests, you find that it is inactive / nomanager.
Within 12 to 15 seconds, you refresh-it gets completed.
Initially, you could find only inactive and we look at the diagnostic- the concurrent manager assigned is not picking up.
There is no specialization rules in any managers except the include program this source.
Solution....
Most often when this occurs where a request goes "inactive/no manager" and is then processed a short time later, the
solution is to either increase the cache size for your Standard manger, or increase the actual number of Standard
manager processes.
Cache Size is set on the CONCURRENT/MANAGER/DEFINE form. Basically, this regulates how many requests a
manager will pick up for each sleep cycle.
20. How do I process more concurrent requests concurrently?

The Concurrent Manager parameters, (Query the concurrent manager by Login as Sysadmin, navigate -> Concurrent
-> Manager -> Define and Query for the relevant concurrent manager), should be modified to handle more concurrent
requests concurrently, this can be done in two steps:
(i) Increase the Number of Target processes for the manager
(ii) Change the cache size of the concurrent manager as this determines how many requests will be evaluated by a
manager at a time and should match the target (process) value as set above.
Sysadmin
1. How to delete an Oracle Applications user
The ability to delete applications users is not planned. Applications users cannot be deleted since records belonging to
users are kept for security and monitoring purposes. The only thing to do is to invalidate the user by assigning an end
date to the effective period for the user. The user is recorded in Who columns, so deleting would cause foreign table
data integrity problems. The only supported method for "deleting" users from Apps is to END DATE them from within
Apps. Do so by navigating to Security -> User -> Define.
2. How to manually change the APPLSYS, APPS and APPLSYSPUB passwords for Applications
The APPLSYS and APPS passwords always have to be the same. Always change both at the same time. When changing
these passwords, it is important to change the APPLSYS password first and the APPS password second. If the correct
procedure, to change these passwords is not followed, users will not be able to login after the change. As a precaution,
please back up the FND_ORACLE_ID and FND_USER tables before beginning.
1. Have all users log out of applications.
2. Shutdown the concurrent managers.
3. Log in to applications as System Administrator.
4. Navigate to Security> Oracle> Register
5. Query up all available Oracle Ids. (NOTE: do not log out of this session of Applications until you have verified that all
the following steps have been completed successfully).
6. At the same time, login to SQL*PLUS as the SYSTEM user.
7. In the applications session, enter the new password for APPLSYS. Re-enter the same password when asked to re-
enter the password to confirm.
8. Save the change.
Note: At this point of the procedure you will see a "Caution" dialog
box which states the following: You are changing the APPLSYS password. Doing so will affect the whole system.
NOTE: The first character of the APPLSYS password MUST NOT BE a numeric. Use only alpha characters for the first
character in the APPLSYS password.
In Application Object Library release 10.7 or later, you must also change all APPS schema passwords to match the
APPLSYS password. You should only change the APPLSYS password while no other users are signed on. After you
change the APPLSYS and all APPS schema passwords, you should exit and sign-on again. Be sure to change the
APPLSYS and APPS schema passwords in the database before signing on again. Use: ALTER USER <APPLSYS
USERNAME> IDENTIFIED BY <NEW PASSWORD>& #059; While the instructions contained in this dialog box are critical
to successfully changing the APPLSYS & APPS passwords the dialog box does not indicate that you have made an error.
Once you have read and understand the caution information you can simply click OK and proceed.
9. In the same applications session, change the APPS password.
10. In the same applications session, change the APPLSYSPUB password if necessary.
11. Save the change.
Note:Re-query the form (query - run) every time after changing the APPS password. If it is not re-queried and the
APPS password is changed again, it is
impossible to continue.
12. In the SQL*Plus session, issue the following statements to change the passwords in the database, where 'XXX' is
the password assigned to that user in the previous steps:
sql>ALTER USER APPLSYS IDENTIFIED BY XXX;
sql>ALTER USER APPS IDENTIFIED BY XXX;
13. Log out of SQL*Plus.
14. Open a NEW session in applications, WITHOUT CLOSING THE PREVIOUS SESSION,
and log in. If log in is successful, the change was successful. Otherwise, repeat steps 5 onward, ensuring the same
password is used for both APPLSYS and APPS, in both applications and SQL*Plus.
15. Restart the concurrent managers.
3. How to exclude menu choices from a new SSWA responsibility?

You are using Applications rel.11.03 and Self Service Web Applications. You want to exclude some menu choices from a
new SSWA responsibility.
System Administrator's responsibility Naviagtion: Security/Responsibility/Define
FNDSCRSP 11.0.15.1100.5 You defined a new responsibility for Web Expenses and assigned menu
AP_WEB_EXP_REP_NAVIGATE to this responsibility. You want to exclude, for example, these menu choices:
a. Upload Expense spreadsheets
b. Download Expense spreadsheets
c. Valid projects and tasks
When you log back in these menu choices still available. You click on Upload Expense spreadsheets and following error
appears on a
screen: 'Your session is no longer valid'
Solution Description
Sysadmin responsibility Navigation: Application/Menu Open menus form. 11.0.3
Define a new menu and include only functions you want to use in Expense Reports.
Assign this menu to your new responsibility.
Explanation
Do not use menu AP_WEB_EXP_REP_NAVIGATE. Define responsibilities form (FNDSCRSP) does not support menu
exclusions for Self-Service Web Applications responsibilities
4. How to delete a responsibility from Oracle Applications?

The ability to delete responsibilities is not planned. Responsibilities cannot be deleted since those records are kept
for security and monitoring purposes. However, responsibilities can be disabled by assigning an end date to the
effective period Responsibilities ValueSet assignation (FNDRSGRP)
5. How to Run Oracle Applications Network Test

The Network Test is used to evaluate the performance of the network with Oracle
Applications. It provides the following tests:
a. Latency Test. It examines the time taken for a single packet to make a round trip from the client side application
to the server.
b. Bandwidth Test. It examines the data rate to see how many bytes per second the network can transfer from the
server to the client.
1. Login to Core Applications as the Sysadmin Responsibility.
2. Navigate to Application > Network Test.
3. Click the 'Clear Old Test Data' button to purge previous test results from
the database.
4. Specify the number of Trials and the Iterations for each trial for both the
latency and bandwidth blocks. The default settings for both are 5 trials of 100 iterations each.
5. Select the Run Test button to perform the test.
6. You receive an APPLMNT error when trying to view output using the Report Review Agent.
Problem
When trying to view the output of a report from the PC, you receive the following error: Environment variable APPLMNT
is not set.
Solution
Follow the steps listed below:
a) Log into Applications as system administrator.
b) Open the System Profiles form.
c) Set the Fileserver Enabled profile option to 'Yes' at the site level.
d) Stop and restart the concurrent manager.
e) Log out of Applications on the PC, and log back in for the change to take effect.
7. You receive an APP-0075 error when trying to delete an assigned printer. How can you find out who it is
assigned to?
Problem
You try to delete a printer through the Register Printers form and receive the following error: APP-0075 printer is
currently in use
CAUSE: A profile option currently uses this printer. You cannot delete the printer until it is no longer in use.
ACTION: Change the profile option value.
Solution
To determine where the printer is defined, and to correct the problem, perform
the following steps:
Note: Issue the commands in SQL*Plus logged in as apps.
a. sql> select profile_option_id,profile_option_name from fnd_profile_options where profile_option_name like
'%PRINTER%';
You see output similar to the following:
PROFILE_OPTION_ID PROFILE_OPTION_NAME
----------------- -------------------
109 PRINTER
b. sql>select level_id,profile_option_id,profile_option_value,level_value from fnd_profile_option_values where
profile_option_id=109
You see output similar to the following:
LEVEL_ID PROFILE_OPTION_ID PROFILE_OPTION_VALUE LEVEL_VALUE
-------- ----------------- -------------------- -----------
10004 109 colprt21 1036
c. sql>select user_id,user_name form fnd_user where user_id = 1036
The output looks similar to:
USER_ID USER_NAME
------- ---------
1036 ACLARK
This is the responsible user profile that needs to have the Printer profile option deleted.
d. Log into Applications under the \navigate profile system screen.
e. Query up the user profile option for ACLARK. The printer profile option should correspond to the printer you need to
delete.
f. Delete this line and then you can delete the printer.
8. You are unable to delete a printer because it has been referenced by a concurrent program.

Problem: You try to delete a printer in the Register Printers form and receive the message: This printer is referenced in
a concurrent program definition. You cannot delete a printer while it is referenced.
Solution: You can use the following SQL statement to find which concurrent programs reference the printer.
Note: In this example you are looking for concurrent programs that are setup to run against the printer TEST
select USER_CONCURRENT_PROGRAM_NAME ,
PRINTER_NAME from FND_CONCURRENT_PROGRAMS
where PRINTER_NAME = 'TEST'
9. Adadmin fails because it cannot find applcreg.txt with 10.7.

Problem: You try to run adadmin on 10.7 and it fails with the following message:
Ad Administrator error: Unable to open file for reading /u15/app/applmgr/10.7/applcreg.txt
You are logged into UNIX as applmgr and have read/write access to the APPL_TOP directory. You cannot find the
applcreg.txt file on any of the other systems. What is this file and where can it be found?
Solution: You chose 'Client' configuration, but need to choose the same configuration that was chosen when you ran
AutoInstall against this APPL_TOP. AutoInstall creates applcreg.txt when you choose 'Client' configuration during an
installation or upgrade.
10. How can you display the name of the Applications user on a form?
Problem:How can the user name of the user currently signed into Applications be displayed on a form that they are
accessing?
Solution:In GUI use: FND_PROFILE.GET('USERNAME'). In character mode use:#FND_GETPROFILE
NAME="USERNAME"
FIELD="<block>.<field>"
11. How can you find the name of a needed profile option?
Problem: If you want to find a value that is stored in a profile option, but you do not know what the profile is called,
how can you find the profile option name?
Solution: To find the name of the profile option, go into Dev Utils examine and select $PROFILE$. Then search for the
profile. It may be necessary to add Dev Utils to a character menu.
12. How do you tell what product is installed Full and Shared within Applications?
This information can be accessed within Applications from the Alert Manager Responsibility. Navigation Path: SYSTEM
-> INSTALLATIONS
13. How to compile an Oracle Reports file or PLL?

UNIX: Oracle Reports
adrepgen userid=apps\<psswd> source=<$PRODUCT_TOP>\srw\filename.rdf
dest=<$PRODUCT_TOP\srw\filename.rdf
stype=rdffile dtype=rdffile logfile=x.log overwrite=yes batch=yes
dunit=character PLL File
adrepgen userid=apps\<psswd> source=<$PRODUCT_TOP>\srw\filename.rdf
dest=<$PRODUCT_TOP\srw\filename.rdf
stype=pllfile dtype=pllfile logfile=x.log overwrite=yes batch=yes
dunit=character
14. How do you test out the Initilization strings used in Applications Printer Drivers?
UNIX
- Create a sample directory and copy a rpt file into that directory.
- Type: FNDPRESC "init_string" > foo (init_string = the exact
init string used wtihin applications)
- vi the report file and insert a line at the top of the report.
Shift + o
- vi the foo file and copy / paste the init string at the inserted
line of the report file.
- lp -d<printername> l#####.out
15. What is the proper way to change the Applications privileged passwords?
- Shutdown the Concurrent Manager
- Change the APPS, APPLSYS and APPLSYSPUB passwords at the
Database level
- Change the APPS, APPLSYS and APPLSYSPUB passwords at the
Application level
- Change the APPS password in any Concurent Manager startup
scripts
16. How to manually change the APPLSYS, APPS and APPLSYSPUB passwords for Applications?
The APPLSYS and APPS passwords always have to be the same. Always change both at the same time. When changing
these passwords, it is important to change the APPLSYS password first and the APPS password second. If the correct
procedure to change these passwords is not followed, users will not be able to login after the change. As a precaution,
please back up the FND_ORACLE_ID and FND_USER tables before beginning.
1. Have all users log out of applications.
2. Shutdown the concurrent managers.
3. Log in to applications as System Administrator.

4. Navigate to Security> Oracle> Register
5. Query up all available Oracle Ids.
NOTE: do not log out of this session of Applications until you have verified that all the following steps have been
completed successfully).
6. At the same time, login to SQL*PLUS as the SYSTEM user.
7. In the applications session, enter the new password for APPLSYS. Re-enter the same password when asked to re-
enter the password to confirm.
8. Save the change. At this point of the procedure you will see a "Caution" dialog box which states the following:
You are changing the APPLSYS password. Doing so will affect the whole system.
NOTE: The first character of the APPLSYS password MUST NOT BE a numeric. Use only alpha characters for the first
character in the APPLSYS password. In Application Object Library release 10.7 or later, you must also change all APPS
schema passwords to match the APPLSYS password. You should only change the APPLSYS password while no other
users are signed on. After you change the APPLSYS and all APPS schema passwords, you should exit and sign-on
again. Be sure to change the APPLSYS and APPS schema passwords in the database before signing on again.
Use: ALTER USER <APPLSYS USERNAME> IDENTIFIED BY <NEW PASSWORD>& #059; While the instructions contained
in this dialog box are critical to successfully changing the APPLSYS & APPS passwords the dialog box does not indicate
that you have made an error. Once you have read and understand the caution information you can simply click OK and
proceed.
9. In the same applications session, change the APPS password.
10. In the same applications session, change the APPLSYSPUB password if
necessary.
11. Save the change.
Note: Re-query the form (query - run) every time after changing the APPS password. If it is not re-queried and the
APPS password is changed again, it is impossible to continue.
12. In the SQL*Plus session, issue the following statements to change the passwords in the database, where 'XXX' is
the password assigned to that user in the previous steps:
sql>ALTER USER APPS IDENTIFIED BY XXX;
13. Log out of SQL*Plus.
14. Open a NEW session in applications, WITHOUT CLOSING THE PREVIOUS SESSION, and log in. If log in is successful,
the change was successful. Otherwise, repeat steps 5 onward, ensuring the same password is used for both APPLSYS
and APPS, in both applications and SQL*Plus.
15. Restart the concurrent managers.
17. How to Reset only the SYSADMIN Password?

PROBLEM DESCRIPTION
You have forgotten the SYSADMIN applications password and cannot login. You know the apps and applsys passwords
but does not want to follow the steps to reset all passwords since resetting applsys would require re-registering all
applications user passwords.
How can you reset only the SYSADMIN password?
SOLUTION DESCRIPTION
The applsys password provides the basis for all user passwords so resetting applsys will require re-registering all user
passwords.
If there are any other users with System Administrator privileges, then they can reset the SYSADMIN user's password
from within applications. Otherwise SYSADMIN can be reset without affecting other users as follows:
1. Log in to SQL*Plus as applsys
2. Backup FND_USER and FND_ORACLE_USERID tables using create table FND_USER_BAK as select * from FND_USER;
create table FND_ORACLE_USERID_BAK as select * from FND_ORACLE_USERID;
update FND_USER
set ENCRYPTED_FOUNDATION_PASSWORD ='
2DF3E509EB6A33F9607959C0976E25D997166FAB694ACDDAE466414791A44411',
ENCRYPTED_USER_PASSWORD=' D2FCA9810D86BCA9BE944D3E2E7A4A9E6CDF89AAD633179B701774083F907C13'
where user_name='SYSADMIN';
sql>commit;
The SYSADMIN password is now set to WELCOME.
18. Profile Options Concurrent Manager Release 11

PURPOSE
The intent of this note is to list and provide a brief explanation of the system administration profile options that relate
to the concurrent manager in Oracle Applications release 11.
SCOPE & APPLICATION
To access the system profile options, log into Oracle Applications and select responsibility 'System Administrator'.
Within the System Administrator responsibility navigate to:
Profile > System
Within the 'Find System Profile Values' (FNDPOMPV) form and in column 'Profile' query using the following,
%concurrent:%"
Note: This is to query all the concurrent manager system profile options.
CONCURRENT MANAGER PROFILE OPTIONS
1. Concurrent: Active Request Limit
Value: Numeric
This profile options will restrict the number of concurrent requests that may be run simultaneously by each user. If you
do not specify a limit, then no limit is imposed.

2. Concurrent: Attach URL
Values: YES/NO
If you set this option to YES, then this causes a URL to be attached to request completion notifications. For example,
when a user submits a request and uses the 'Defining Completion Options' region to specify people to be notified,
a notification is sent each of the people designated.
3. Concurrent: Collect Request Statistics
Values: YES/NO
If you set this option to YES, this causes applications to collect statistics on your run-time concurrent processes.
4. Concurrent: Conflicts Domain
Values: LOV (list of values: domains) This option identifies the domain within which all the incompatibilities between
programs has to be resolved
5. Concurrent: Debug Flags
This option is used to debug the transactions managers. You should only use this option at the request of Oracle
Support.
6. Concurrent: Directory for Copy
You can identify a directory on your operating system to store copies of your report output or log files. This directory is
used when a copy operation is requested in character mode of the applications.
7. Concurrent: Enable Request Submission in View Mode
Values: YES/NO
Setting this option to YES will enable the 'Submit a New Request' button when users invoke the form FNDRSRUN (Find
Requests Form). Navigation path is either: (1) Menu: Help > View My Requests, or (2) navigate (with system
administrator responsibility) to, Requests > View.
8. Concurrent: Hold Requests
Values: YES/NO
This option enables you to automatically place requests on hold after submission.
9. Concurrent: Multiple Time Zones
Values: YES/NO
When the client's session and the concurrent manager are running in different times zones, use this option to ensure
that the request is scheduled immediately regardless of you client session's time zone.
10. Concurrent: PMON Method
This option is presented for documentation purposes only. Users cannot see or alter this profile option. This option is
not visible or cannot be updated from the System Profile Option (FNDPOMPV) form. The PMON method refers to the
process monitor. The Internal Concurrent Manager (ICM) monitors the individual concurrent managers' processes to
verify the managers are running. Normally, the PMON method must be set to LOCK. To change the profile option
setting, you must execute the SQL script "afimpmon.sql" which resides in directory "$FND_TOP/sql/".
11. Concurrent: Report Access Level
Values: RESPONSIBILITY/USER
This option determines access privileges to report output files and log files generated by a concurrent program. This
option can be set by a system administrator or by the user.
12. Concurrent: Report Copies
Values: Numeric
This option determines the number of default copies that print for each submitted concurrent request.
13. Concurrent: Request Priority
Values: Numeric
Concurrent requests in Oracle Applications are queued. Requests normally run according to a start time on a first
submitted, first run basis. Priority overrides this request start time. A higher priority request starts before an earlier
request. This option displays the default priority for you concurrent requests. Only a system administrator can change
your request priority.
14. Concurrent: Request Start Time
Values: Numeric (Date/Time)
With this profile option, you can set the date and time that your requests are available to start running
* If the start time is at or before the current date and time, requests are available to run immediately
* Start a request in the future, for example, at 6:00 PM on December 31, 2000, enter the following value,
31-DEC-2000 18:00
* This profile option requires the date and time, for example, 31-DEC-2000 18:00
* Changing values does not affect request already submitted
15. Concurrent: Save Output
Values: YES/NO
Setting this option to YES will save the output from a concurrent request to a file.
16. Concurrent: Sequential Requests
Values: YES/NO
Setting this option to YES will force concurrent requests to run sequentially in the order in which they were submitted.
17. Concurrent: Show Requests Set Stages
Values: YES/NO
Set this option to YES to show request set stages in the concurrent request screens.
18. Concurrent: Show Requests Summary After Each Request Submission
Values: YES/NO
By default the Request Summary (FNDRSRUN) form appears after every request submission. Set this option to NO if
you have multiple requests to submit and do not wish to see the Request Summary form after each submission.
19. Concurrent: URL Lifetime
Value: Numeric

If the profile option 'Concurrent: Attach URL' has been set to YES, a URL is associated the output of an execution and is
passed to anyone flagged for notification during the request submission. This option specifies how long (in minutes)
the URL is to be kept active.
20. Concurrent: Use ICM
Values: YES/NO
ICM (Internal Concurrent Manager)
Set this option to YES to use the Internal Concurrent Manager to resolve request conflicts (result from programs that
are defined to be incompatible) instead of using the Conflict Resolution Manager (CRM).
21. Concurrent: Wait for Available TM
Value: Numeric
TM (Transaction Manager)
Use this option to specify the number of minutes that a client will wait for a given transaction manager to become
available before trying a different transaction manager.
19. Why do I have invalid objects? What causes them?

Invalid objects can and will occur for many reasons. You will usually find invalid objects after running (or failing to run)
adprepdb, doing an export/import, upgrading, or applying patches. Invalid objects are usually caused by missing
grants, synonyms, views, tables or packages, but can also be caused by corrupted packages.
20. Why does Oracle Support always tell me to recompile my invalid objects?
Compiling invalid objects on your database is almost the equivalent of running scandisk on a PC hard drive. This should
be one of the first things you check if you start experiencing problems with your Oracle database. It is also a good idea
to schedule regular checks for invalid objects.
When you call in to Oracle Support with a database or installation issue, one of the first questions they will probably ask
is whether you have checked for and resolved any invalid objects.
21. Are invalid objects ever acceptable? How many is too many?
If the invalid objects exist for a product or application that is not installed, it may be ok to have some, but it is
preferable to have no invalid objects existing at all. If invalid objects exist for a product or application that you do have
installed and are using, then it should be considered unacceptable and any existing invalid objects should be resolved
before further issues can occur.
There is no set number of invalid objects that could be considered 'acceptable' as each situation will vary widely from
one database to the next. You could just have a few invalid objects or they could number in the hundreds or even
thousands, but every effort should be made to resolve them one way or another.
22. How can I get a quick count of my invalid objects (if any) for regular maintenance?
To get a quick count of the number of existing invalids (if any), use the following select statement:
SELECT COUNT(*)
ROM DBA_OBJECTS
HERE STATUS = 'INVALID';
For a more detailed query, use the following script:
ELECT OWNER, OBJECT_TYPE, COUNT(*)
FROM DBA_OBJECTS
HERE STATUS = 'INVALID'
ROUP BY OWNER, OBJECT_TYPE;
23.How can I manually recompile individual invalid objects?

To recompile an individual object, connect to SQL*PLUS as the owner of the object (generally apps). Use one of the
following depending on the object type:
SQL> alter package <package_name> compile; (package specification)
SQL> alter package <package_name> compile body; (package body)
SQL> alter view <view_name> compile; (view)
If the object compiles with warnings, use either of the following to see the errors that caused the warnings:
SQL> show errors or
SQL> select * from user_errors where name = '<OBJECT_NAME>';
24. How can I recompile all my invalid objects using ADCOMPSC.pls?

Within Applications, there is a script to compile INVALID objects – called ADCOMPSC.pls Arguments for ADCOMPSC.pls:
1 - Schema to run in
2 - Password for schema
3 - Check errors for objects starting with #3
NOTE: The order in which to compile Invalid Objects in schemas is SYS, SYSTEM, APPS and then all others. APPS_DDL
and APPS_ARRAY_DDL should exist in all schema's. If you encounter an ORA-1555 error while running adcompsc.pls,
just restart the script.
The script can be run as follows:
cd $AD_TOP/sql
sqlplus @adcompsc.pls SCHEMA_NAME SCHEMA_PASSWORD %
Example: SQL> @adcompsc.pls apps apps %
After the script completes, check for invalid objects again. If the number has decreased, but you still have invalid
objects, you should run adcompsc.pls again. Keep running adcompsc.pls until number of invalid objects stops
decreasing.
25. What if I still have invalid objects than can not be resolved by ADCOMPSC.pls?

If there are any objects still left INVALID, you can verify them by using aderrchk.sql to record the remaining INVALID
objects. Aderrchk.sql use the same syntax as adcompsc.pls. This script is also supplied with the Applications. You can
send the aderrchk.sql to a file using the spool <file> command in sqlplus.
e.g. sqlplus x/y @aderrchk.sql SCHEMA_NAME SCHEMA_PASSWORD %
For objects will not compile, try the following:
select text
from user_source
where name = 'OBJECTNAME'
and text like '%Header%';
This script will give you the sql that creates the packages. You can then recreate the packages. SQL>@packageheader
SQL>@packagebody If recreating the package does not make the package valid you will have to analyze the
user_errors table to try to determine the cause of the invalid package.
select text
from user_errors
where name = 'PACKAGENAME';

Frequently Asked Questions Cloning Oracle Applications Release 11i

Uploaded by

Copyright:

Available Formats

Frequently Asked Questions Cloning Oracle Applications Release 11i

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Frequently Asked Questions Cloning Oracle Applications Release 11i

Uploaded by

Copyright:

Available Formats

Frequently Asked Questions

Cloning Oracle Applications

2. How can I clone an Oracle Applications system?

3. What are the differences between the two cloning methods?

4. What is the AD Cloning utility?

5. What is Rapid Clone?

6. How do I determine if my system is Rapid Clone enabled?

8. How do I determine if my system is AutoConfig enabled?

Created by Bhaskar Ivaturi 1

14. Can I clone from one platform to a different platform?

15. Can I reclone just the database?

16. Can I clone a single-node system to a multi-node system?

18. Can I clone a multi-node system to a single-node system?

19. Does Rapid Clone modify the source system?

22. Does Rapid Clone preserve the patch history?

23. Can I clone a clone?

25. What is the oraInventory?

Created by Bhaskar Ivaturi 2

26. What is a binary oraInventory? Is my Inventory binary?

27. What is a XML oraInventory? Is my Inventory XML?

28. What is the Global (or Central) Inventory?

29. What is the Local (or Home) Inventory?

30. How does Rapid Clone deal with the oraInventory?

32. What does OUISetup.pl do?

Frequently Asked Questions about

Created by Bhaskar Ivaturi 3

4. How do I configure AutoConfig for a multi-node system?

5. What user do I log in as to use AutoConfig in a typical multi-node system?

6. How do I determine if AutoConfig is enabled?

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

8. What does the term "Context_name" mean?

9. What are the basic components of AutoConfig?

Applications Context On the application tier: An XML repository (<Context_name>.xml) contains

On the database tier:

AutoConfig Scripts On the application tier: Provide a simplified

Created by Bhaskar Ivaturi 5

The Context file

11. How can I make changes to the Applications Context file?

14. When should I run AutoConfig?

Created by Bhaskar Ivaturi 6

17. Which directories based on the Context_name will AutoConfig create?

18. I see multiple directories under <COMMON_TOP>/admin/scripts - which one do I use?

19. How can I roll back an AutoConfig session?

Created by Bhaskar Ivaturi 7

24. How do I apply the latest AutoConfig patch?

40. What is the use of the context variable s_apps_jdbc_connect_descriptor?

41. When do I need to reset (empty) the context variable s_apps_jdbc_connect_descriptor?

3. How can I check to see if a concurrent manager is running?

4. Where do concurrent request or manager logfiles and output files go?

5. What are the logfile and output file naming conventions?

Created by Bhaskar Ivaturi 9

6. Can I delete a concurrent manager?

7. What is the function of the 'Conflict Resolution Manager'?

8. What is the 'Internal Scheduler/Prereleaser' manager?

9. What is the 'Internal Monitor' manager/service?

10. How do I check/set the PMON method?

11. How do I enable/disable the Conflict Resolution Manager?

12. How do I clean out the Concurrent Manager tables?

13. How do I tell concurrent manager processes apart at the OS level?