NaturalOracle DataGaurd tutorial Series Coming Soon!! Natural
For Any queries, please mail us at support@funoracleapps.com

Internal Concurrent Manager status could not be determined.

No comments
There can a scenario where while running

adcmctl status apps/apps_password

The output is:

$ adcmctl.sh status apps/apps_password

You are running adcmctl.sh version 115.28

Internal Concurrent Manager status could not be determined.

adcmctl.sh: exiting with status 0



Solution:

1. We can run cmclean.sql script.
    As suggested by (Oracle Note: 134007.1 - CMCLEAN.SQL - Non Destructive Script to 
    Clean Concurrent Manager Tables). Shutdown the CM, run the script (make sure you issue 
    commit once the script is  done), start the CM and check for the issue.

2. If after running the the cmclean.sql the issue still persists then take down the application tier
    services and run autoconfig. This will relink the binaries of the adcmctl.sh. After autoconfig is 
    successful then take up  the application services and and check the issue.

  
 
There may be another senario where ,if the Oracle Application version is R12.1 and higher, then there might be case that managers are running fine but when we try to check the status for the ICM through adcmctl.sh then it will return as status could not be determined.
 
adcmctl.sh status apps/apps_passwd
You are running adcmctl.sh version 120.17.12010000.5
Internal Concurrent Manager status could not be determined.
adcmctl.sh: exiting with status 0
This is a bug As per Oracle Note(Adcmctl.Sh Script Is Unable To Determine The ICM Status (Doc ID 1320217.1)).
Oracle suggest to apply one patch to resolve the issue.( Patch 12410716: FNDSVCRG STATUS COULD NOT BE DETERMINED AFTER RHEL5 SECURITY PATCH UPDATES)
 
 

No comments :

Post a Comment