Welcome to My Oracle World

09 October, 2016

FNDSM Entries missing in tnsnames.ora after running autoconfig.

Cloning Issue:

While cloning we always have this issue on our non-prod environments, as we have two concurrent manager nodes.

Lets assume that there are 2 Concurrent Manager (CM) nodes called ‘Node A’ and ‘Node B’.

The FND_NODES table is cleaned via the API FND_CONC_CLONE.SETUP_CLEAN as part of post clone.

1. When AutoConfig is run on Node A:
a. FND_NODES is populated with Node A information.
b. tnsnames.ora file on Node A will have an FNDSM entry for that node only, as the application has no information for Node B yet.

2. When AutoConfig is run on Node B:
a. FND_NODES is populated with Node B information.
b. tnsnames.ora file on Node B will have FNDSM entries for Node A as well as Node B.

In order to have a FNDSM entry for Node B in the tnsnames.ora file of Node A, AutoConfig has to be run again on Node A, because the application now has the information about Node B.

I hope this is clear!

RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X while running adcfgclone.pl

Cloning Issue

[orastg@eboso bin]$ perl adcfgclone.pl dbconfig /clone/oracle/product/11.2.0/appsutil/CLONE_ebso.xml

Redwood Shores, California, USA

Oracle Applications Rapid Clone

Version 12.0.0

adcfgclone Version 120.31.12010000.8

Enter the APPS password :

Running Rapid Clone with command:

perl /clone/oracle/product/11.2.0/appsutil/clone/bin/adclone.pl java=/clone/oracle/product/11.2.0/appsutil/clone/bin/../jre mode=apply stage=/clone/oracle/product/11.2.0/appsutil/clone component=dbconfig method=CUSTOM dbctxtg=/clone/oracle/product/11.2.0/appsutil/CLONE_ebso.xml showProgress contextValidated=false

Running:

APPS Password :

Beginning dbconfig Apply – Fri May 17 01:37:14 2013

/clone/oracle/product/11.2.0/appsutil/clone/bin/../jre/bin/java -Xmx600M -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/clone/oracle/product/11.2.0/oui -classpath /clone/oracle/product/11.2.0/appsutil/clone/jlib/xmlparserv2.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/ojdbc5.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/java:/clone/oracle/product/11.2.0/appsutil/clone/jlib/oui/OraInstaller.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/oui/ewt3.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/oui/share.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/oui/srvm.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/ojmisc.jar oracle.apps.ad.clone.ApplyDatabase -e /clone/oracle/product/11.2.0/appsutil/CLONE_ebso.xml -stage /clone/oracle/product/11.2.0/appsutil/clone -showProgress -noRmanRecovery yes -checkDBConnection

APPS Password : Log file located at /clone/oracle/product/11.2.0/appsutil/log/CLONE_ebso/ApplyDatabase_05170137.log

| 0% completed RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.

Please make sure you have UnZip 5.X in your path and try again…

ERROR while running Apply…

ERROR: Failed to execute /clone/oracle/product/11.2.0/appsutil/clone/bin/adclone.pl

Please check logfile.

[orastg@ebso bin]$

Solution:

Which unzip shud point to $ORACLE_HOME/bin/unzip

Take the backup of existing unzip from $ORACLE_HOME/bin

cd $ORACLE_HOME/bin

mv unzip unzip_bkp

cp /usr/bin/unzip to $ORACLE_HOME/bin

Make sure the unzip utility under /usr/bin should be of version 5.X and not 6

R12.1.3 Cloning Issue: Error RC-50013 while running adcfgclone.pl dbTechStack

Cloning issue.

/clone/oracle/product/11.2.0/appsutil/clone/bin/../jre/bin/java -Xmx600M -DCONTEXT_VALIDATED=true -Doracle.installer.oui_loc=/clone/oracle/product/11.2.0/oui -classpath /clone/oracle/product/11.2.0/appsutil/clone/jlib/xmlparserv2.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/ojdbc5.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/java:/clone/oracle/product/11.2.0/appsutil/clone/jlib/oui/OraInstaller.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/oui/ewt3.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/oui/share.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/oui/srvm.jar:/clone/oracle/product/11.2.0/appsutil/clone/jlib/ojmisc.jar oracle.apps.ad.clone.ApplyDBTechStack -e /clone/oracle/product/11.2.0/appsutil/CLONE_ebso.xml -stage /clone/oracle/product/11.2.0/appsutil/clone -showProgress

APPS Password : Log file located at /clone/oracle/product/11.2.0/appsutil/log/CLONE_ebso/ApplyDBTechStack_05170000.log

\ 0% completed RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack

ERROR while running Apply…

Fri May 17 00:01:23 2013

ERROR: Failed to execute /clone/oracle/product/11.2.0/appsutil/clone/bin/adclone.pl

Please check logfile.

[orastg@pomodsdb01 bin]$

When checked in log file

.end std out.

Perl lib version (v5.8.8) doesn’t match executable version (v5.10.0) at /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/Config.pm line 46.

Compilation failed in require at /clone/oracle/product/11.2.0/appsutil/clone/ouicli.pl line 35.

BEGIN failed–compilation aborted at /clone/oracle/product/11.2.0/appsutil/clone/ouicli.pl line 35.

[AutoConfig Error Report]

The following report lists errors AutoConfig encountered during each

phase of its execution. Errors are grouped by directory and phase.

The report format is:

<filename> <phase> <return code where appropriate>

[APPLY PHASE]

AutoConfig could not successfully execute the following scripts:

Directory: /clone/oracle/product/11.2.0/perl/bin/perl -I /clone/oracle/product/11.2.0/perl/lib/5.8.3 -I /clone/oracle/product/11.2.0/perl/lib/site_perl/5.8.3 -I /clone/oracle/product/11.2.0/appsutil/perl /clone/oracle/product/11.2.0/appsutil/clone

ouicli.pl INSTE8_APPLY 255

AutoConfig is exiting with status 1

RC-50013: Fatal: Instantiate driver did not complete successfully.

/clone/oracle/product/11.2.0/appsutil/driver/regclone.drv

Solution

Edit ‘adxdbctx.tmp’ with correct perl version

To implement the solution please apply the following:

1. When cloning the file adlnkoh.sh will be instantiated, so modifying <OH>/appsutil/install/adlnkoh.sh will get overwritten when running adcfgclone reflected from the workaround below. The correct solution is to update the template DB_HOME/appsutil/template/adlnkoh.sh.

2. Retest the result once completed.

Workaround:

1. Do the following change in:

< OH>/appsutil/install/adlnkoh.sh

CHANGE
make -f ins_srvm.mk iodbagrp
TO
make -f ins_srvm.mk iosdbagrp

2. Do the following in :
$AD_TOP/admin/template/adlnkoh.sh

CHANGE
make -f ins_srvm.mk iodbagrp >> $LOGF 2>&1

TO
make -f ins_srvm.mk iosdbagrp >> $LOGF 2>&1

3. Run adcfgclone.pl dbTechStack again and check

Managers down – Status show “Target node/queue unavailable

Concurrent Managers Status shows ”Target node/queue unavailable” in Concurrent–>Manager–>Administer Screen form.

Solution:

Ensure Database is Running and Middle Tier Services are down.

Connect SQLPLUS as APPS user and run the following :

EXEC FND_CONC_CLONE.SETUP_CLEAN;

COMMIT;

EXIT;

Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtier to repopulate the required systemtables
Run the CMCLEAN.SQL script from the referenced note below (don’t forget to commit).
Note.134007.1 – ‘CMCLEAN.SQL – Non Destructive Script to Clean Concurrent Manager Tables‘
Start the middle tier services including your concurrent manager.
Retest the issue.

Managers down – Status “System Hold, Fix Manager”

Concurrent Managers Status shows “System Hold, Fix Manager” in Concurrent–>Manager–>Administer Screen form.

Solution:

• Ensure Concurrent :GSM Enabled profile is set to ‘Y’

• Run $FND_TOP/patch/115/sql/afdcm037.sql

• Go to $FND_TOP/bin

adrelink.sh force=y “fnd FNDLIBR”

adrelink.sh force=y “fnd FNDSM”

adrelink.sh force=y “fnd FNDFS”

adrelink.sh force=y “fnd FNDCRM”

• Run cmclean.sql

• Start Application Service (adstrtal.sh)

R12 Opp(output Post Processor) and Workflow Mailer is down

When i see the Status OPP Manger and Workflow Mailer from Concurrent–>Manager–>Administer Screen. I see below status

Solution :

• Ensure Concurrent:GSM Enabled profile is set to ‘Y’

• Verify Service Manager status in Administer Form.

• Verify Service Manager Definition.

• Ensure FNDSM Entries available in FND_CONCURRENT_QUEUES Table

• FNDSM entry should be correct in Tnsnames.ora file and tnsping FNDSM_hostname should work fine.

• Then Bounce the Services.

Ensure Concurrent:GSM Enabled profile is set to ‘Y’

ORA-06512: at “APPS.FND_CP_FNDSM”, line 29 Concurrent Manger not starting

When i checked concurrent manager log under $APPLCSF/log/<SID>.mgr

I see below error:

Cause: cleanup_node failed due to ORA-01427: single-row subquery returns more than one row

ORA-06512: at “APPS.FND_CP_FNDSM”, line 29
ORA-06512: at line 1.

The SQL statement being executed at the time of Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /dev/applmgr/R12/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your syst : 08-OCT-2013 00:30:51

Starting IEU_WL_CS Concurrent Manager : 08-OCT-2013 00:30:51

Could not initialize the Service Manager FNDSM_apps01_dev. Verify that apps01 has been registered for concurrent processing.
ORACLE error 1427 in cleanup_node

Cause: cleanup_node failed due to ORA-01427: single-row subquery returns more than one row
ORA-06512: at “APPS.FND_CP_FNDSM”, line 29
ORA-06512: at line 1.

The SQL statement being executed at the time of
Routine AFPEIM encountered an error while starting concurrent manager IEU_WL_CS with library /dev/applmgr/R12/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.

Solution

———-

sqlplus apps/apps

sql>exec fnd_conc_clone.setup_clean;

commit;

sql>@cmclean.sql

Started the concurrent manager on the application tier and it worked