Core Concurrent Processing - EBS (MOSC)

MOSC Banner

After Cloning concurrent managers are down

edited Sep 6, 2011 12:55AM in Core Concurrent Processing - EBS (MOSC) 6 commentsAnswered
After cloning environment TEST (with rapid clone) into a new server (different hostname) , clone process ended successfully
,everything it seems ok, but concurrent manager doesn´t work fine , only start one concurrent manager:

[applbsd@ldbsasvofi0 bin]$ ps -ef |grep FNDLIBR
applbsd  30103 30097  0 10:21 ?        00:00:00 FNDLIBR                                                                     
applbsd  32665  1353  0 11:12 pts/1    00:00:00 grep FNDLIBR
[applbsd@ldbsasvofi0 bin]$

Restart application and database several times but doesn´t work.

Attached log concurrent managers == > TEST_0823.mgr


We applied the next  workarounds , based on metalink notes:
ID 736024.1 / 305986.1 / etc...
Autoconfig , cmclea, run..

 I applied the procedure :

Concurrent Processing  - After Cloning All the Concurrent Managers Do Not Start for the Clone [Article ID 555081.1]  ( content part of your indications )

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center