Concurrent Manager(CM) Trouble shooting :
For Concurrent manager(CM) trouble shooting
1. First check the CM is up or not by using below any one procedure.
i. ps –ef|grep FNDLIBR
ii. adcmctl.sh status apps/<appsPWD>
iii. Login as system administrator responsibilities go to the below navigation Concurrent -> manager -> Administer -> see the Actual and target for all the managers
2. If CM in down check the internal manager Logfile in $APPLCSF/APPLLOG location for errors.
3. If any errors related to FNDFS then check the Application listener STATUS , if it is not running start it.
4. If CM is up/running then log file and output file are not able see the user from the front end then check the Application listener is status if it is not running then start it.
5. If any user is complained some request is running long time then
i. First check the CM status and ICM status.
ii. Check any Locks on DB particularly related to that program.
iii. Check any INVALID objects related to that program.
iv. Check any incompatible requests/programs are running for that program.
Login as system administrator responsibility and query the long running request /program. Navigate to concurrent program define query that long running request in the same form select incompatible requests .
If any incompatible request is running then find the user name who is running that program inform them regarding the incompatibilities.
For Concurrent manager(CM) trouble shooting
1. First check the CM is up or not by using below any one procedure.
i. ps –ef|grep FNDLIBR
ii. adcmctl.sh status apps/<appsPWD>
iii. Login as system administrator responsibilities go to the below navigation Concurrent -> manager -> Administer -> see the Actual and target for all the managers
2. If CM in down check the internal manager Logfile in $APPLCSF/APPLLOG location for errors.
3. If any errors related to FNDFS then check the Application listener STATUS , if it is not running start it.
4. If CM is up/running then log file and output file are not able see the user from the front end then check the Application listener is status if it is not running then start it.
5. If any user is complained some request is running long time then
i. First check the CM status and ICM status.
ii. Check any Locks on DB particularly related to that program.
iii. Check any INVALID objects related to that program.
iv. Check any incompatible requests/programs are running for that program.
Login as system administrator responsibility and query the long running request /program. Navigate to concurrent program define query that long running request in the same form select incompatible requests .
If any incompatible request is running then find the user name who is running that program inform them regarding the incompatibilities.
0 comments:
Post a Comment