Inactive no manager after cloning....

We got an INACTIVE NO MANAGER after cloning an 11i with ATG.RUP.5.

The concurrent manager log, appeared with the following error:

Could not initialize the Service Manager FNDSM_[SERVER_NAME]_[ENV_NAME]. Verify that [SERVER_NAME] has been registered for concurrent processing. Routine AFPEIM encountered an error while starting concurrent manager.

We got a solution, while browsing through the net.
at

No comments:

Post a Comment

Kindly make your valuable and progressive comments here.
Junks will be deleted without notice :-)

Subscribe to: Post Comments (Atom)

  Find below few useful scripts for  Performance  Management:: # Important MOS notes for TRACING: There are several ways to trace a particul...

  • adapcctl.sh: exiting with status 204
    On a new VIS R12.1 installation, the OHS (oracle http server) failed to start and give status 204. Upon querying the status of opmn manage...
  • Ever Hit with ORA-46981 in Oracle EBS Environment ?
    Recently when I was tasked to do a cloning of my production Oracle Apps instance to a target single-node server,  I hit a dead-end with the ...
  • (no title)
    A nice story about RMAN.           The story begins,  when one of my associate DBAs did an RMAN restoration & recovery 2 days back...