Concurrent Processing …

恼火的问题，重启多次并发服务一直无法启动，记录一下解决方法

 

 

 Concurrent Processing - The Concurrent Manager
Fails to Start on GSM Enabled Due to DBMS_LOCK.Request ResultCall
Failed to Establish ICM (文档 ID 245563.1) 转到底部 

--------------------------------------------------------------------------------

Checked for relevance on 04-JAN-2014

Application Install - 11.5.5 to 12.0.4

?fact: Oracle Application Object Library

?fact: Concurrent:GSM Enabled = Y

?symptom: The Concurrent Manager fails to start

?symptom: Routine &ROUTINE has attempted to start the
internal

concurrent manager.

?symptom: The ICM is already running.  Contact you
system administrator for

further assistance.

?symptom: a fpdlrq received an unsuccessful result from PL/SQL
procedure or

function FND_DCP.Request_Session_Lock.

?symptom: Routine FND_DCP.REQUEST_SESSION_LOCK received a result
code of 1

from the call to DBMS_LOCK.Request.

?symptom: Possible DBMS_LOCK.Request resultCall to establish_icm
failed

?symptom: The Internal Concurrent Manager has encountered an
error.

?change: Cloned Instance

?cause: Database Locking issue

 

fix:

1. Stop all services and concurrent managers

2. Stop and restart the database

3. Restart the services and concurrent managers

4. Verify if the issue remains

 

问题应该是出在这里：

 

How to Prevent The Concurrent Managers to Start When Launching the Apps Middle Tier Startup Script "adstrtal.sh" ? (文档 ID 417437.1)

转到底部

In this Document Goal Solution References Applies to: Oracle Applications DBA - Version 11.5.10.2 to 11.5.10.2 [Release 11.5.10] Oracle Concurrent Processing - Version 11.5.10.2 to 11.5.10.2 [Release 11.5] Information in this document applies to any platform. Goal  While configuring the PCP on two Apps tier nodes (example Node1 & Node2), only one ICM (Internal Concurrent Manager) should be running in an Apps 11i env  (e.g.  run only on Primay Node1). This note explains the way (modification in Apps XML file) to prevent the concurrent managers from starting on the second Node2 when launching the App start script "adstrtal.sh". Solution  The script adstrtal.sh calls the ServiceControl.java. This java class reads the service information in your context file under $APPL_TOP/admin. To prevent the concurrent managers from starting on your second node, you need to edit $APPL_TOP/admin/.xml and change:- s_concstatus">enabled<<BR>To s_concstatus">disabled<<BR> Please make this change after the service is already stopped, as this change will also affect adstpall.sh. There is no need to run AutoConfig, as ServiceControl.class reads the "s_status" variables directly from the XML file. References NOTE:373611.1 - Concurrent Processing - How To Move Concurrent Processing Server from One Node To Another Node NOTE:389516.1 - Adstrtal.Sh Does Not Initiate Adcmctl.Sh Process