ISSUE:
Not able to determine the status of Internal Concurrent Manager using the script 'adcmctl.sh'.
Installation of E-Business Suite R12 on Oracle Linux 5.6, all post-install steps were completed successfully, no errors. Application startup was fine, ICM was also working and requests were being served properly. Attempting to check the status of Internal Concurrent Manager using the script 'adcmctl.sh', responded with error.
Running the following:
./adcmctl status apps/<appspwd>
'Internal Concurrent Manager status cannot be determined'
Running the following:
$FND_TOP/bin/FNDSVCRG STATUS
received:
'Internal Concurrent Manager status could not be determined'
FINDINGS:
This issue is documented in the following bug:
Bug 12353506 - ADCMCTL.SH SCRIPT IS UNABLE TO DETERMINE THE ICM STATUS
Modify a minor parameter used to execute a sql statement in afpsrg.o which is a main routine for an executable, FNDSVCRG. It's been like this for many years but apparently, database 11g has more stringent checking on the parameter. Plus, using adcmctl.sh with "status" as a parameter is a rarely used functionality.
Parameters to afuexec(use_curs, 1, 0, NOHOLD), parameter will need to be 1, 1 rather than 1, 0.
Files modified or created
fnd src/process afpsrg.oc 120.0.12010000.2
Fix summary: bug 12353506 - changed a parameter to afuexec to avoid error
when FNDSVCRG is called with STATUS.
Forced checkin of dual maintained file from revision 115.10
SOLUTION:
For 12.1 test the following steps in a development instance and then migrate accordingly:
1. Download and review the readme of Patch 12410716
2. Apply the patch in a test instance and verify the fix prior to application to other instances.
Note:For apps 12.0 the following patch will fix the issue:
Patch 14093847:R12.FND.A
The patch provides: afpsrg.oc: 120.0.12000000.4 :
Patch detail:
1OFF:12410716:FNDSVCRG STATUS COULD NOT BE DETERMINED AFTER RHEL5
For 12.2 test the following steps in a development instance and then migrate accordingly:
$FND_TOP/bin/FNDSVCRG STATUS
Internal Concurrent Manager status could not be determined
1. Check the value for $GWYUID, and confirm it is either not set or invalid.
2. SQL> select USERNAME,ACCOUNT_STATUS,PROFILE from dba_users where USERNAME like 'APP%'
USERNAME ACCOUNT_STATUS
APPLSYSPUB EXPIRED(GRACE)
3. Ensure APPLSYSPUB status is OPEN. After resetting the password of APPLSYSPUB , you should able to connect using sqlplus.
REFERENCE:
Adcmctl.Sh Script Is Unable To Determine The ICM Status (Doc ID 1320217.1)
Not able to determine the status of Internal Concurrent Manager using the script 'adcmctl.sh'.
Installation of E-Business Suite R12 on Oracle Linux 5.6, all post-install steps were completed successfully, no errors. Application startup was fine, ICM was also working and requests were being served properly. Attempting to check the status of Internal Concurrent Manager using the script 'adcmctl.sh', responded with error.
Running the following:
./adcmctl status apps/<appspwd>
'Internal Concurrent Manager status cannot be determined'
Running the following:
$FND_TOP/bin/FNDSVCRG STATUS
received:
'Internal Concurrent Manager status could not be determined'
FINDINGS:
This issue is documented in the following bug:
Bug 12353506 - ADCMCTL.SH SCRIPT IS UNABLE TO DETERMINE THE ICM STATUS
Modify a minor parameter used to execute a sql statement in afpsrg.o which is a main routine for an executable, FNDSVCRG. It's been like this for many years but apparently, database 11g has more stringent checking on the parameter. Plus, using adcmctl.sh with "status" as a parameter is a rarely used functionality.
Parameters to afuexec(use_curs, 1, 0, NOHOLD), parameter will need to be 1, 1 rather than 1, 0.
Files modified or created
fnd src/process afpsrg.oc 120.0.12010000.2
Fix summary: bug 12353506 - changed a parameter to afuexec to avoid error
when FNDSVCRG is called with STATUS.
Forced checkin of dual maintained file from revision 115.10
SOLUTION:
For 12.1 test the following steps in a development instance and then migrate accordingly:
1. Download and review the readme of Patch 12410716
2. Apply the patch in a test instance and verify the fix prior to application to other instances.
Note:For apps 12.0 the following patch will fix the issue:
Patch 14093847:R12.FND.A
The patch provides: afpsrg.oc: 120.0.12000000.4 :
Patch detail:
1OFF:12410716:FNDSVCRG STATUS COULD NOT BE DETERMINED AFTER RHEL5
For 12.2 test the following steps in a development instance and then migrate accordingly:
$FND_TOP/bin/FNDSVCRG STATUS
Internal Concurrent Manager status could not be determined
1. Check the value for $GWYUID, and confirm it is either not set or invalid.
2. SQL> select USERNAME,ACCOUNT_STATUS,PROFILE from dba_users where USERNAME like 'APP%'
USERNAME ACCOUNT_STATUS
APPLSYSPUB EXPIRED(GRACE)
3. Ensure APPLSYSPUB status is OPEN. After resetting the password of APPLSYSPUB , you should able to connect using sqlplus.
REFERENCE:
Adcmctl.Sh Script Is Unable To Determine The ICM Status (Doc ID 1320217.1)