- What is AutoConfig?
- What is the difference between the application tier and
the database tier?
- How can I identify the application tier and the
database tier in a multi-node system?
- How do I configure AutoConfig for a multi-node system?
- What user do I log in as to use AutoConfig in a typical
multi-node system?
- How do I determine if AutoConfig is enabled?
- Is AutoConfig compatible with Oracle Applications
11.5.x?
- What does the term "Context_name" mean?
- What are the basic components of AutoConfig ?
- What are the different AutoConfig scripts and what do
they do?
- How will the adbldxml utility name the Applications
Context file it generates?
- How do I make changes to the Applications Context file?
- 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?
- I was instructed to change the value of the context
variables s_adperlprg and s_perl5lib. How can I achieve that?
- When should I run AutoConfig?
- Which files / profile options get changed when I run
AutoConfig?
- Where is the log file located that AutoConfig creates?
- Which directories based on the Context_name will
AutoConfig create?
- I see multiple directories under
<COMMON_TOP>/admin/scripts - which one do I use?
- How do I roll back an AutoConfig session?
- How does AutoConfig know which scripts to create for
service controls?
- How does AutoConfig know what application tier node
type the APPL_TOP supports?
- How do I preserve customizations to an
AutoConfig-maintained environment?
- What do I do when a patch or Oracle documentation
instructs me to manually modify an AutoConfig-maintained file?
- What is the Net Services Topology Data Model?
- When is the Net Services Topology Data Model seeded?
- What mechanism is used to generate the tnsnames.ora
file?
- How do I seed the Net Services Topology Data Model?
- When do I need to deregister a database tier or an
application tier?
- How do I deregister an application tier from the Net
Services Topology Data Model?
- How do I deregister a database tier from the Net
Services Topology Data Model?
- When do I need to purge the complete Net Services
Topology Data Model?
- How do I purge the complete Net Services Topology Data
Model?
- How do I seed the Net Services Topology Data Model
after purging it?
- I want to deregister an application tier or a database
tier from the Net Services Topology Data Model. I can't use the
adgentns.pl because I already decommissioned the tier or removed the
context file. How can I deregister the tier?
- I want to purge the complete Net Services Topology Data
Model. I can't use the adgentns.pl script because I removed the relevant
context file(s). How can I purge the Data Model?
- How do I configure AutoConfig to generate the failover
aliases?
- For which database versions can I define failover
aliases?
- Should the database server remain available during the
AutoConfig run?
- What is the use of the context variable
s_apps_jdbc_connect_descriptor?
- When do I need to reset (empty) the context variable
s_apps_jdbc_connect_descriptor?
- What steps do I need to follow to maintain my database
connectivity when I migrate my database from one host/platform to another?
- 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?
- My 11i instance is configured with RAC. Now I want to
migrate to AutoConfig. How do I achieve that?
- My 11i instance is configured as non-RAC. Now I want to
migrate to RAC using AutoConfig. What steps should I follow?
- I applied all the required RAC patches, but my TWO_TASK
variables still point to the instance aliases. How can I point them to
load balanced aliases?
- What is the correct setting for MSDEVDIR?
- After running AutoConfig, the Apps.cmd and
<CONTEXT_NAME>.cmd contain slashes instead of backslashes on
Windows. How do I resolve this issue?
- Can I use the perl shipped by MKS to run adconfig.cmd
on Windows?
- After I run AutoConfig in my 11.5.9 Windows environment
I have two Apache services and two forms services. Which ones should I
use?
- After I run AutoConfig in my 11.5.9 Windows environment
I have two Apache services, two forms services, two metrics client
services, and two metrics server services. Which ones should I use?
- The script adsvalsn.cmd fails when I run AutoConfig.
How do I resolve this issue?
- What should I do if my AutoConfig script exits with
non-zero status?
- How do I configure AutoConfig to start the TCF servlet?
- How can I resolve TNS-12500 while trying to start GSM?
- My concurrent managers don't start after running
AutoConfig? How do I resolve this issue?
- How do I resolve a FileNotFoundException while running
adupdts.sh?
- How do I resolve an address in use (could not bind to
port) when starting Apache?
- I get the message "You are not authorized to view
this page" when I access the application. How do I resolve this
problem?
- On HP/UX Itanium adconfig.pl fails because of a missing
POSIX module. How do I resolve this problem?
Questions
and Answers
Answer:
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.
Refer to Metalink Note 165195.1 for details on installing, using and updating AutoConfig. The Oracle Applications Maintenance Procedures and the Oracle Applications Maintenance Utilities provide further information on how to use AutoConfig in the context of maintaining your system.
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.
Refer to Metalink Note 165195.1 for details on installing, using and updating AutoConfig. The Oracle Applications Maintenance Procedures and the Oracle Applications Maintenance Utilities provide further information on how to use AutoConfig in the context of maintaining your system.
- What is the difference between
the application tier and the database tier?
Answer:
Before we can answer that, let's define a few terms in the context of the Release 11i architecture:
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.
- How can I identify the
application tier and the database tier in a multi-node system?
Answer:
A node can contain one or more servers, and can therefore belong to one or more tiers.
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.
- How do I configure AutoConfig
for a multi-node system?
Answer:
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.
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
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
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
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.
Reference:
- What user do I log in as to use
AutoConfig in a typical multi-node system?
Answer:
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 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).
- How do I determine if
AutoConfig is enabled?
Answer:
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:
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!
|
- Is AutoConfig compatible with
Oracle Applications 11.5.x?
Answer:
Yes, it is compatible with all 11i releases. You can use AutoConfig to configure and maintain any Oracle Applications 11i environment.
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.
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.
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.
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.
|
- What does the term
"Context_name" mean?
Answer:
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>.
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>.
- What are the basic components
of AutoConfig?
Answer:
Components
|
Location
|
Description
|
Applications Context
|
On the application tier:
<APPL_TOP>/admin
On the database tier:
<RDBMS ORACLE_HOME>/appsutil |
An XML repository
(<Context_name>.xml) contains information specific to that Applications
instance. Can be updated by running the Context Editor.
Do not manually update this file! |
AutoConfig Template Files
|
On the application tier:
<PROD_TOP>/admin/template For example: <AD_TOP>/admin/template <FND_TOP>/admin/template
On the database tier:
<RDBMS ORACLE_HOME>/appsutil/template |
Include named tags which are
replaced with instance-specific information from the Applications Context.
There is one template file for each configuration file.
For example: apps_nt.conf apps_ux.conf |
AutoConfig File Driver
|
On the application tier:
<PROD_TOP>/admin/driver For example: <AD_TOP>/admin/driver/adtmpl.drv <FND_TOP>/admin/driver/fndtmpl.drv
On the database tier:
<RDBMS ORACLE_HOME>/appsutil/template |
Used by AutoConfig to list the
AutoConfig Template Files, their destination locations, and the commands to
be executed, for example, the commands to update profile options. Every
Product Top contains its own AutoConfig File Driver.
|
AutoConfig Scripts
|
On the application tier:
<AD_TOP>/bin
On the database tier:
<RDBMS ORACLE_HOME>/appsutil/bin |
Provide a simplified
interface to the AutoConfig APIs. For example: adautocfg.sh / adautocfg.cmd adconfig.sh / adconfig.cmd |
- What are the different
AutoConfig scripts and what do they do?
Answer:
The scripts are listed in the following table.
The scripts are listed in the following table.
Note: .sh scripts are for UNIX users and .cmd scripts are for
Windows users.
|
Scripts
|
Location
|
Description
|
adautocfg.sh
adautocfg.cmd
|
On the application tier:
<COMMON_TOP>/admin/scripts/ <Context_name>
On the database tier:
<RDBMS ORACLE_HOME>/appsutil/ scripts/ <Context_name> |
A wrapper script that calls
adconfig.sh/ adconfig.cmd. Instantiates template files with values specific
to the instance (taken from the Applications Context). Updates configuration
files and profile options.
|
adconfig.sh
adconfig.cmd
|
On the application tier:
<AD_TOP>/bin
On the database tier:
<RDBMS ORACLE_HOME>/appsutil/bin/ |
A wrapper script that calls
adconfig.pl. In earlier versions of AutoConfig adconfig.sh/adconfig.cmd used
to call the Java API to start AutoConfig.
|
adconfig.pl
|
On the application tier:
<AD_TOP>/bin
On the database tier:
<RDBMS ORACLE_HOME>/appsutil/bin |
A wrapper script that calls the
Java API to start AutoConfig.
|
adbldxml.sh
adbldxml.cmd
|
On the application tier:
<AD_TOP>/bin
On the database tier:
<RDBMS ORACLE_HOME>/appsutil/bin |
Creates the Applications Context
File. Before running this script, you need to source the environment.
On the application tier: Source APPS<Context_name>.env (or APPSORA.env if APPS<Context_name>.env doesn't exist). On the database tier: Source <Context_name>.env |
adchkcfg.sh
adchkcfg.cmd
|
On the application tier:
<AD_TOP>/bin
On the database tier:
<RDBMS ORACLE_HOME>/appsutil/bin |
Generates a report that highlights
differences between the original config files and AutoConfig-generated config
files. The report is named cfgcheck.html. It is located under:
On the application tier: <APPL_TOP>/admin/ <Context_name>/out/<MMDDhhmm> On the database tier: <RDBMS ORACLE_HOME>/appsutil/out/ <Context_name>/<MMDDhhmm> |
Answer:
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:
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.
- How can I make changes to the
Applications Context file?
Answer:
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.
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.
|
- 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?
Answer:
The adbldxml utility requires the following environment variables to be set:
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
- I was instructed to change the
value of the context variables s_adperlprg and s_perl5lib. How can I
achieve that?
Answer:
Apply the latest AutoConfig patch, then perform the following steps depending on your use case:
Apply the latest AutoConfig patch, then perform the following steps depending on your use case:
- You were instructed to use a certain perl version. You
have perl and its libraries installed in the perl standard location for
your os (e.g. /usr/lib/perl5 on Linux) and perl is in your PATH:
- unset PERL5LIB
- perl $AD_TOP/bin/adconfig.pl
- Source the environment file
(APPS<Context_name>.env)
- Review your Applications
Context file; s_adperlprg and s_perl5lib will now point to your system
perl location.
- You were instructed to use a certain perl version. You
installed perl and its libraries into a custom - non perl standard
location (e.g. perl is installed at /u03/myperl/bin and the perl
libraries at /u03/myperl/lib).
- PERL5LIB=<location of the
new PERL5LIB that you want to use>
- export PERL5LIB
- <location of the new perl
you want to use> <AD_TOP>/bin/adconfig.pl
- Source the environment file
(APPS<Context_name>.env)
- Review your Applications
Context file; s_adperlprg and s_perl5lib will now point to your customized
perl location.
Example:
§ PERL5LIB=/u03/myperl/lib/5.00503:/u03/myperl/lib/site_perl/5.005
§ export PERL5LIB
§ /u03/myperl/bin/perl
$AD_TOP/bin/adconfig.pl
AutoConfig
will update the context variables in the context file accordingly. After the
AutoConfig run subsequent utilities and tools can use the context variables
s_adperlprg and s_perl5lib.
Answer:
You should run AutoConfig in the event of the following cases:
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.
|
Answer:
Run the adchkcfg utility to get an html report that lists all the files and profile options that get changed when you 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, see Appendix B of the Metalink Note 165195.1.
Where is
the log file located that AutoConfig creates?
Answer:
The log file that AutoConfig creates is located at:
The log file that AutoConfig creates is located at:
On the
application tier:
<APPL_TOP>/admin/<Context_name>/log/<MMDDhhmm>/adconfig.log
<APPL_TOP>/admin/<Context_name>/log/<MMDDhhmm>/adconfig.log
On the
database tier:
<RDBMS ORACLE_HOME>/appsutil/log/<Context_name>/<MMDDhhmm>/adconfig.log
<RDBMS ORACLE_HOME>/appsutil/log/<Context_name>/<MMDDhhmm>/adconfig.log
where:
<MMDDhhmm> = (month, day, hour, and minute of the AutoConfig run)
Which
directories based on the Context_name will AutoConfig create?
Answer:
AutoConfig creates the following directories based on the Context_name:
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.
I see
multiple directories under <COMMON_TOP>/admin/scripts - which one do I
use?
Answer:
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.
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.
How can I
roll back an AutoConfig session?
Answer:
All backup configuration files from each AutoConfig session are stored in:
On the application tier:
<APPL_TOP>/admin/<Context_name>/out/<MMDDhhmm>/
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>/
<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.
For additional
information see Oracle Applications Maintenance
Procedures.
How does
AutoConfig know which scripts to create for service controls?
Answer:
The following variables in the Applications Context File let AutoConfig know which scripts to create:
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
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:
Context
Variable
|
Node
1
|
Node
2
|
Value
|
Value
|
|
s_isAdmin
|
NO
|
YES
|
s_isConc
|
NO
|
YES
|
s_isWeb
|
YES
|
NO
|
s_isForms
|
YES
|
NO
|
How does
AutoConfig know what application tier node type the APPL_TOP supports?
Answer:
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:
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.
|
s_isAdConc
|
If set to Yes, the APPL_TOP can be
used to provide the CP and Reports services. All binaries, scripts, 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:
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 contains the following values:
Context
Variable
|
Node
1
|
Node
2
|
Value
|
Value
|
|
s_isAdAdmin
|
NO
|
YES
|
s_isAdConc
|
NO
|
YES
|
s_isAdWeb
|
YES
|
NO
|
s_isAdForms
|
YES
|
NO
|
Answer:
Refer to Metalink Note 270519.1 for details on how to implement customizations.
Refer to Metalink Note 270519.1 for details on how to implement customizations.
What do I
do when a patch or Oracle documentation instructs me to manually modify an
AutoConfig-maintained file?
Answer:
Contact Oracle Support to incorporate the necessary changes in the AutoConfig templates:
Contact Oracle Support to incorporate the necessary changes in the AutoConfig templates:
0.
Identify the patch or the note that
is requesting the manual change.
1.
Log a Service Request with Oracle
Support, providing the same information.
Answer:
Updates to AutoConfig are delivered in the TXK AutoConfig and Templates patch. The latest patch at the time of this writing are patch number 9535311.
Updates to AutoConfig are delivered in the TXK AutoConfig and Templates patch. The latest patch at the time of this writing are patch number 9535311.
How do I
apply the latest AutoConfig patch?
Answer:
Perform the following steps in the order listed:
Perform the following steps in the order listed:
o
Review the
pre-requisites as documented in Metalink Note 165195.1.
o
Apply the
AutoConfig patch
Update the Oracle Applications file system with the AutoConfig files by applying patch 9535311. to all application tier nodes in the Applications instance.
Update the Oracle Applications file system with the AutoConfig files by applying patch 9535311. to all application tier nodes in the Applications instance.
o
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:
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
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
unzip -o appsutil.zip
o
Run
AutoConfig on the Database Tier
If you enabled AutoConfig on the Database Tier, run AutoConfig on the database tier node.
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.
|
o
Run AutoConfig
on the Application Tiers
Run AutoConfig on all application tier nodes.
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.
|
Answer:
The Net Services Topology Data Model stores the entire topological information about a single Oracle Application instance. The data model stores information about each node in the Oracle Applications instance which is then used to generate the Net Service configuration files (for example tnsnames.ora). AutoConfig seeds the data model with relevant data.
The Net Services Topology Data Model stores the entire topological information about a single Oracle Application instance. The data model stores information about each node in the Oracle Applications instance which is then used to generate the Net Service configuration files (for example tnsnames.ora). AutoConfig seeds the data model with relevant data.
The Net
Services Topology Data Model stores the following information:
o
On the database tier: Hostname,
Database SID, Database Name, Instance Name, TNS Descriptors.....
o
On the application tier: Hostname,
FNDFS and FNDSM alias descriptors.........
When is
the Net Services Topology Data Model seeded?
Answer:
The Net Services Topology Data Model is seeded every time you run AutoConfig on the respective tier. Every time you run AutoConfig on the database tier, the relevant data is seeded/updated for the database tier. Respectively, every time you run AutoConfig on the application tier, the relevant data is seeded/updated for the application tier.
The Net Services Topology Data Model is seeded every time you run AutoConfig on the respective tier. Every time you run AutoConfig on the database tier, the relevant data is seeded/updated for the database tier. Respectively, every time you run AutoConfig on the application tier, the relevant data is seeded/updated for the application tier.
What
mechanism is used to generate the tnsnames.ora file?
Answer:
In ADX.D and earlier, AutoConfig instantiates the tnsnames.ora file based on an AutoConfig template. To support enhanced configuration scenarios (for example RAC), the adgentns.pl script dynamically generates the tnsname.ora file. It generates the tnsnames.ora based on the information in the Net Services Topology Data Model. The adgentns.pl script was introduced with ADX.E. Refer to the following matrix to understand when tnsnames.ora is generated from a template or from the adgentns.pl script:
In ADX.D and earlier, AutoConfig instantiates the tnsnames.ora file based on an AutoConfig template. To support enhanced configuration scenarios (for example RAC), the adgentns.pl script dynamically generates the tnsname.ora file. It generates the tnsnames.ora based on the information in the Net Services Topology Data Model. The adgentns.pl script was introduced with ADX.E. Refer to the following matrix to understand when tnsnames.ora is generated from a template or from the adgentns.pl script:
PRE ADX.E
|
ADX.E and higher
|
||||
FND_NODES.NODE_ID column is present
|
FND_NODES.NODE_ID column is not
present
|
TXK.G and FND_NODES.NODE_ID column is
present
|
Exceptions like database not
available
|
||
AutoConfig on database tier
|
template
|
adgentns.pl
|
template
|
adgentns.pl
|
template
|
AutoConfig on application tier
|
template
|
adgentns.pl
|
template
|
template
|
template
|
How do I
seed the Net Services Topology Data Model?
Answer:
The Net Services Topology Data Model can be seeded/updated by running AutoConfig on the database tier followed by all application tiers.
The Net Services Topology Data Model can be seeded/updated by running AutoConfig on the database tier followed by all application tiers.
When do I
need to deregister a database tier or an application tier?
Answer:
You have to deregister a tier from the Net Services Topology Data Model in one of the following cases:
You have to deregister a tier from the Net Services Topology Data Model in one of the following cases:
o
You want to delete an application
tier
o
Your database is upgraded/migrated
resulting in a change in one of the following parameters:
§ Database Host
§ Database Port
§ Database Name
§ Database SID
You should
deregister the tier before the tier is decommissioned.
How do I
deregister an application tier from the Net Services Topology Data Model?
Answer:
To deregister the current application tier from the Net Services Topology Data Model, invoke the following command:
To deregister the current application tier from the Net Services Topology Data Model, invoke the following command:
perl
<AD_TOP>/bin/adgentns.pl appspass=<APPSpwd>
contextfile=<CONTEXT> -removeserver
How do I
deregister a database tier from the Net Services Topology Data Model?
Answer:
To deregister the current database tier from the Net Services Topology Data Model, invoke the following command:
To deregister the current database tier from the Net Services Topology Data Model, invoke the following command:
perl
<RDBMS ORACLE_HOME>/appsutil/bin/adgentns.pl appspass=<APPSpwd> \
contextfile=<CONTEXT> -removeserver
contextfile=<CONTEXT> -removeserver
When do I
need to purge the complete Net Services Topology Data Model?
Answer:
You need to purge the complete Net Services Topology Data Model, when the Database Name is changed as a result of a database upgrade/migration.
You need to purge the complete Net Services Topology Data Model, when the Database Name is changed as a result of a database upgrade/migration.
How do I
purge the complete Net Services Topology Data Model?
Answer:
To purge the complete Net Services Topology Data Model, invoke the following command:
To purge the complete Net Services Topology Data Model, invoke the following command:
perl
<AD_TOP>/bin/adgentns.pl appspass=<APPSpwd> contextfile=<CONTEXT>
-removesystem
How do I
seed the Net Services Topology Data Model after purging it?
Answer:
See question "How do I seed the Net Services Topology Data Model".
See question "How do I seed the Net Services Topology Data Model".
I want to
deregister an application tier or a database tier from the Net Services
Topology Data Model. I can't use the adgentns.pl script because I already
decommissioned the tier or removed the context file. How can I deregister the
tier?
Answer:
In this case you can use the PL/SQL API. Perform the following steps in the order listed:
In this case you can use the PL/SQL API. Perform the following steps in the order listed:
o
Locate the System Name:
§ The System name is the database name
§ Verify with sql query: select DB_NAME from FND_DATABASES;
o
Locate the server name corresponding
to the tier in question:
§ Query on the database tier:
select NAME, SERVER_TYPE from FND_APP_SERVERS, FND_NODES
where FND_APP_SERVERS.NODE_ID = FND_NODES.NODE_ID and
SERVER_TYPE='DB' and FND_NODES.NODE_NAME=upper('hostname');
select NAME, SERVER_TYPE from FND_APP_SERVERS, FND_NODES
where FND_APP_SERVERS.NODE_ID = FND_NODES.NODE_ID and
SERVER_TYPE='DB' and FND_NODES.NODE_NAME=upper('hostname');
§ Query on the application tier:
select NAME, SERVER_TYPE from FND_APP_SERVERS, FND_NODES
where FND_APP_SERVERS.NODE_ID = FND_NODES.NODE_ID and
SERVER_TYPE='APPS' and FND_NODES.NODE_NAME=upper('hostname');
select NAME, SERVER_TYPE from FND_APP_SERVERS, FND_NODES
where FND_APP_SERVERS.NODE_ID = FND_NODES.NODE_ID and
SERVER_TYPE='APPS' and FND_NODES.NODE_NAME=upper('hostname');
o
Run the following PL/SQL block:
begin
FND_NET_SERVICES.remove_server(SYSTEM_NAME, SERVER_NAME);
end;
/
commit;
/
begin
FND_NET_SERVICES.remove_server(SYSTEM_NAME, SERVER_NAME);
end;
/
commit;
/
I want to
purge the complete Net Services Topology Data Model. I can't use the
adgentns.pl script because I removed the relevant context file(s). How can I
purge the Data Model?
Answer:
In this case you can use the PL/SQL API. Perform the following steps in the order listed:
In this case you can use the PL/SQL API. Perform the following steps in the order listed:
o
Locate the System Name:
§ The System name is the database name
§ Verify with sql query: select DB_NAME from FND_DATABASES;
o
Run the following PL/SQL block:
begin
FND_NET_SERVICES.remove_system(SYSTEM_NAME);
end;
/
commit;
/
begin
FND_NET_SERVICES.remove_system(SYSTEM_NAME);
end;
/
commit;
/
How do I
configure AutoConfig to generate the failover aliases?
Answer:
To generate the failover aliases use the database tier context variable s_alt_service_instances.
To generate the failover aliases use the database tier context variable s_alt_service_instances.
You can
specify a comma separated list of "servicename:instance" to use
connect time failover management.
For
example 'SERVICE_NAME:INSTANCE_NAME1,SERVICE_NAME:INSTANCE_NAME2' will generate
a TNS Alias in the tnsnames.ora file that fails over to INSTANCE_NAME1 when the
current instance is not available. If INSTANCE_NAME1 is not available it fails
over to INSTANCE_NAME2.
To set up
the failover listing, perform the following steps in the order listed:
0.
Update the context variable
s_alt_service_instances in the database tier context file applying the failover
rules as described above.
1.
Run AutoConfig on all database
tiers.
2.
Run AutoConfig on all application
tiers.
These
steps will generate tns aliases <INSTANCE_NAME>_FO with description lists
as configured in s_alt_service_instances. These aliases will still not be used
anywhere. You will have to set the two task variables like s_tool_twotask to
actually use these aliases.
Check the
question "For which database versions can I define failover aliases for information about the availability of failover aliases
on different database versions.
Note: On database versions that are 8.1.7.4 or higher the
generated alias <INSTANCE_NAME>_FO can only be used for failover. On
8.0.6 the generated alias can't be used for failover. However, it can be used
for load balancing.
|
For which
database versions can I define failover aliases?
Answer:
You can generate failover aliases for all database versions that are 8.1.7.4 or higher. Currently, Oracle Applications does not support failover aliases for the 8.0.6 Oracle Home.
You can generate failover aliases for all database versions that are 8.1.7.4 or higher. Currently, Oracle Applications does not support failover aliases for the 8.0.6 Oracle Home.
Answer:
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.
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.
What is
the use of the context variable s_apps_jdbc_connect_descriptor?
Answer:
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.
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.
When do I
need to reset (empty) the context variable s_apps_jdbc_connect_descriptor?
Answer:
You should reset the value for s_apps_jdbc_connect_descriptor to an empty value (" "), when one of the following value changes:
You should reset the value for s_apps_jdbc_connect_descriptor to an empty value (" "), when one of the following value changes:
o
Database Host
o
Database Port
What steps
do I need to follow to maintain my database connectivity when I migrate my
database from one host/platform to another?
Answer:
Perform the steps in the order listed:
Perform the steps in the order listed:
o
Before the migration:
0.
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.
If you haven't enabled AutoConfig on the database tier, you can ignore this step.
o
After the migration:
0.
Reset the context variable
s_apps_jdbc_connect_descriptor in the context file for the application tier to
an empty string.
1.
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.
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?
Answer:
Your old database tier is still registered in the Net Services Topology Data Model. Perform the following steps:
Your old database tier is still registered in the Net Services Topology Data Model. Perform the following steps:
o
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?".
o
Perform the step described in the
question: "How do I seed the Net Service Topology Data Model?"
Answer:
To migrate to AutoConfig on a RAC instance, follow these steps in the order listed:
To migrate to AutoConfig on a RAC instance, follow these steps in the order listed:
0.
Enable AutoConfig on all database
tiers. Follow the instructions in the AutoConfig Metalink Note 165195.1.
1.
AutoConfig will not overwrite your
existing init.ora file. However, AutoConfig will generate a RAC conform
init.ora file when no init.ora file exists. We recommend that you backup your
existing init.ora file and let AutoConfig generate an init.ora file for you.
This will ensure that the init.ora file conforms to the Oracle's standards (for
example using of DB_Name as the service name or handling local and remote
listeners).
2.
Run AutoConfig on the database tier.
3.
Stop and start the database
listener.
4.
Enable and run AutoConfig on all
your application tiers. Follow the instructions in the AutoConfig Metalink Note 165195.1.
Note: You need to enable and run AutoConfig on the database
tiers FIRST! followed by the application tiers. This order is required
because the RAC configuration data needs to be uploaded to the Net Services
Topology Data Model, so that a correct tnsnames.ora file can be created on
the application tier.
|
My 11i
instance is configured as non-RAC. Now I want to migrate to RAC using
AutoConfig. What steps should I follow?
Answer:
To migrate an Oracle Applications 11i instance from non-RAC to RAC, follow the instructions as described in Metalink Note 279956.1.
To migrate an Oracle Applications 11i instance from non-RAC to RAC, follow the instructions as described in Metalink Note 279956.1.
I applied
all the required RAC patches, but my TWO_TASK variables still point to the
instance aliases. How can I point them to load balanced aliases?
Answer:
Update your application tier context file and set the values of the following context variables to the desired load balanced alias names:
Update your application tier context file and set the values of the following context variables to the desired load balanced alias names:
o
s_tools_twotask
o
s_weboh_twotask
Answer:
Use the path to the VC98 directory, not the MSDev98 directory. The vcvars32.bat file exists only under the VC98 directory. For example:C:\CPP\VC98.
Use the path to the VC98 directory, not the MSDev98 directory. The vcvars32.bat file exists only under the VC98 directory. For example:C:\CPP\VC98.
After
running AutoConfig, the Apps.cmd and <CONTEXT_NAME>.cmd contain slashes
instead of backslashes on Windows. How do I resolve this issue?
Answer:
Download patch 2690783 from OracleMetaLink and follow the instructions in Readme.
Download patch 2690783 from OracleMetaLink and follow the instructions in Readme.
Can I use
the perl shipped by MKS to run adconfig.cmd on Windows?
Answer:
No. The perl shipped by MKS is not certified. Use the perl available in your Applications Environment (iAS for the application tier, 9i for the database tier) or download the ActivePerl from perl.com. Perl has to be in the PATH in order for AutoConfig to run.
No. The perl shipped by MKS is not certified. Use the perl available in your Applications Environment (iAS for the application tier, 9i for the database tier) or download the ActivePerl from perl.com. Perl has to be in the PATH in order for AutoConfig to run.
After I
run AutoConfig in my 11.5.9 Windows environment I have two Apache services and
two forms services. Which ones should I use?
Answer:
o
The two Apache services are:
§ Oracle Apache Server <SID> (original service)
§ Oracle Apache Server <Context_name> (new service)
o
The two forms services are:
§ OracleFormsServer-Forms60<SID> (original service)
§ OracleFormsServer-Forms60<Context_name> (new service)
Run the
rem_srv.cmd script delivered in patch 3197605 to remove the duplicate services.
After I
run AutoConfig in my 11.5.9 Windows environment I have two Apache services, two
forms services, two metrics client services, and two metrics server services.
Which ones should I use?
Answer:
o
The two Apache services are:
§ Oracle Apache Server <SID> (original service)
§ Oracle Apache Server <Context_name> (new service)
o
The two forms services are:
§ OracleFormsServer-Forms60<SID> (original service)
§ OracleFormsServer-Forms60<Context_name> (new service)
o
The two metrics client services are:
§ Oracle Metrics Client <SID> (original service)
§ Oracle Metrics Client <Context_name> (new service)
o
The two metrics server services are:
§ Oracle Metrics Server <SID> (original service)
§ Oracle Metrics Server <Context_name> (new service)
Run the
rem_srv.cmd script delivered in patch 3695041 to remove the duplicate services.
The script
adsvalsn.cmd fails when I run AutoConfig. How do I resolve this issue?
Answer:
Check in your Service Control Panel to see if the 806 listener service is set to automatic or manual.
If your service is set to automatic, then you hit a known issue, that can be ignored. You can use the following workaround to resolve the issue:
copy %AD_TOP%\bin\adsstart.exe %COMMON_TOP%\util\SrvStart.exe
Check in your Service Control Panel to see if the 806 listener service is set to automatic or manual.
If your service is set to automatic, then you hit a known issue, that can be ignored. You can use the following workaround to resolve the issue:
copy %AD_TOP%\bin\adsstart.exe %COMMON_TOP%\util\SrvStart.exe
Answer:
If AutoConfig exits with non-zero status, open the adconfig.log and check for the reported errors:
If AutoConfig exits with non-zero status, open the adconfig.log and check for the reported errors:
o
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.
If the template files exist, check for permission issues. If you cannot fix the issue, report the problem to Oracle Support.
o
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.
Note: Refer to the question "Where is the log file located
that AutoConfig creates?" for the location of the log file.
|
How do I
configure AutoConfig to start the TCF servlet?
Answer:
Perform the following steps:
Perform the following steps:
0.
Apply the Thin Client Framework
(TCF) Servlet Implementation patch.
1.
Apply TXK.A or higher.
2.
Verify that the s_tcfstatus variable
is set to "disabled" in your <Context_name>.xml file.
3.
If set to "enabled", use
the Context Editor to update the TCF Process Status to "disabled" and
save the changes.
4.
Stop all application tier services.
5.
Run AutoConfig to update the
configuration files.
6.
Make additional updates based on
your system configuration (see Note 164942.1).
7.
Restart all application tier
services.
References:
How can I
resolve TNS-12500 while trying to start GSM?
Answer:
Change the profile option CONC_GSM_ENABLED to N until GSM is configured. If GSM is configured, check listener.ora located in
<8.0.6 ORACLE_HOME>/network/admin/<Context_name>
Change the profile option CONC_GSM_ENABLED to N until GSM is configured. If GSM is configured, check listener.ora located in
<8.0.6 ORACLE_HOME>/network/admin/<Context_name>
AutoConfig
depends on the CONC_GSM_ENABLED profile option to create entries for FNDSM in
the listener.ora file. If listener.ora contains entries for FNDSM and the
corresponding executable is not found, the listener will not to start.
Apply the
latest AutoConfig patch. The patch creates the FNDSM entry in listener.ora.
Reference:
Reference:
My
concurrent managers don't start after running AutoConfig? How do I resolve this
issue?
Answer:
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.
How do I
resolve a FileNotFoundException while running adupdts.sh?
Answer:
If the script adupdts.sh fails with a "FileNotFoundException", apply the latest AutoConfig patch.
If the script adupdts.sh fails with a "FileNotFoundException", apply the latest AutoConfig patch.
References:
How do I
resolve an address in use (could not bind to port) when staring Apache?
Answer:
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.
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:
I get the
message "You are not authorized to view this page" when I access the
application. How do I resolve this problem?
Answer:
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". Alternatively, you can change the value of this variable 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.
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". Alternatively, you can change the value of this variable 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.
On HP/UX
Itanium adconfig.pl fails because of a missing POSIX module. How do I resolve
this problem?
Answer:
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 .
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 .
Additional References
To read more about configuring Oracle Applications and the features of AutoConfig follow these links:
No comments:
Post a Comment