Concurrent Manager Node is in Lowercase Causing Adgendbc.sh to Fail (Doc ID 1539713.1)

Last updated on OCTOBER 04, 2016

Applies to:

Oracle Concurrent Processing - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.

Symptoms

Upgraded database to 11.2.0.3, ran the interoperability patches and the CPU patches for April 2012. Now autoconfig.sh makes the node names in fnd_nodes to be lowercase causing adgendbc.sh to fail and the .dbc files to be invalid.

Similar issue to that recorded in Note 954165.1. Error is:

java.sql.SQLException: ORA-01403: no data found
ORA-06512: at "APPS.FND_APP_SERVER_PKG", line 298
ORA-06512: at line 1

 
Applied Patch 9171650, which replaced 7164202 referenced in Note 954165.1, it did not address/fix the problem.  The node name in FND_NODES are still lower case.

Manually updating the FND_NODES and set node_name to uppercase allows adgendbc.sh to run successfully. This also allows to start all application process and login.

The concurrent managers will not start. The managers display the following error:

Starting PODAMGR Concurrent Manager : 18-MAR-2013 09:30:20
Could not initialize the Service Manager FNDSM_VMLIN04A_OFFDEV. Verify that VMLIN04A has been registered for concurrent processing.
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /usr2/offappl/po/11.5.0/bin/POXCON.

 

Changes

 Upgraded to database 11.2.0.3 with Document:881505.1 - Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms