Core Concurrent Processing - EBS (MOSC)

MOSC Banner

EBS v12.2.4 Cloned system: Internal Concurrent Manager (ICM) is Not Active and can't start

edited Aug 12, 2015 4:35AM in Core Concurrent Processing - EBS (MOSC) 3 commentsAnswered

Our system is EBS v12.2.4, we cloned the system, the database and other application is OK.

But the Internal Concurrent Manager (ICM) is Not Active and can't start.

We use the script that under /jit/jit13/fs1/inst/apps/JIT13_fxsljit04/admin/scripts/adcmctl.sh to start the ICM. But it is failed.

Below is results for adcmctl.sh status apps/password:

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

You are running adcmctl.sh version 120.19.12020000.3

Internal Concurrent Manager is Not Active at this time.

adcmctl.sh: exiting with status 0

adcmctl.sh: check the logfile /jit/jit13/fs1/inst/apps/JIT13_fxsljit04/logs/appl/admin/log/adcmctl.txt for more information ...

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS Concurrent Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center