Archive for September 2014

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora   Leave a comment

Autoconfig Log shows below error

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora. [ID 1324667.1]

There is no information in the table FND_NODES for the database node.

This means that autoconfig has not been executed in the database tier or there was a problem
when it was executed in the database tier.
So you need to run autoconfig on the database tier to gather the information.

There is no database node declared in the FND_NODES table

To implement the solution, please execute the following steps:

1. Ensure that you have taken a backup of your system before applying the recommended solution.

2. Clean the Data Topology Model
Sqlplus apps/…
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;

3. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers, to repopulate the required system tables

Posted September 4, 2014 by balaoracledba.com in OracleAppsR12

Output Post Processor is Down with Actual Process is 0 And Target Process is 1   Leave a comment

If you see OPP is Down with Actual Process is 0 And Target Process is 1 then do the following

1. Shutdown concurrent server via command adcmctl.sh under $COMMON_TOP/admin/scripts/<context_name>

3. To ensure concurrent manager down; check there is no FNDLIBR process running.
ps -ef | grep applmgr | grep FNDLIBR

4. Run adadmin to relink FNDSVC executable.

a. Invoke adadmin from command prompt
b. Choose option 2 (2. Maintain Applications Files menu)
c. Choose option 1 (1. Relink Applications programs )
d. Then type “FND” When prompted; ( Enter list of products to link (‘all’ for all products) [all] : FND )
e. Ensure adrelink is exiting with status 0

5. Start Concurrent Managers using adcmctl.sh

Posted September 4, 2014 by balaoracledba.com in 11i/R12, OracleAppsR12

AutoConfig: Parallel Run Option on R12.1.1   1 comment

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

AutoConfig can be run in parallel mode on the application tier with the following command:

perl $AD_TOP/bin/adconfig.pl contextfile=<CtxFile> [product=<product_top>] –parallel

Where <CtxFile> is the absolute path of the applicaton tier context file, and <product_top> is the short name of the product to be configured.

AutoConfig can be run in parallel mode on the database tier with the following command:

perl $ORACLE_HOME/appsutil/bin/adconfig.pl contextfile=<CtxFile> -parallel

Where <CtxFile> is the absolute path of the database tier context file.

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

Posted September 4, 2014 by balaoracledba.com in 11i/R12, OracleAppsR12