Concurrent Manager Node is in Lowercase Causing Adgendbc.sh to Fail
Last updated on OCTOBER 04, 2016
Applies to:Oracle Concurrent Processing - Version 188.8.131.52 to 184.108.40.206 [Release 11.5]
Information in this document applies to any platform.
Upgraded database to 220.127.116.11, 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:
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:
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.
CPU Patches Applied:
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