Concurrent Request stays with 'Inactive No Manager'

[Guest_imported]

Hi ,

We are installing Oracle Apps 11.0.3 on Compaq Tru64 Unix on Alpha ES40. I have used the 1 hour Install. The Installation has

completed without any error. And I am able to start all the managers and access Apps from Client machine. But when a Concurrent

request is submitted, we are getting an 'Inactive : No Manager' status. I have tried a lot of actions to solve this problem, but it has not

been rectified.

Has anybody faced this problem ?

Is this a bug in apps 11.0.3 for Tru64 unix ? Does it require a patch ?

Pl. get back with your idea about this and how we can solve this problem.

Regards,
Arun

The contents of the log file is as follows :


========================================================================
Starting TST internal concurrent manager -- shell process ID 31316

logfile=/d01/app/appltst/1103/fnd/11.0.28/log/TST.mgr
PRINTER=
mailto=appltst
restart=N
diag=N
sleep=60 (default)
pmon=20 (default)
quesiz=1 (default)


+---------------------------------------------------------------------------+
Application Object Library: Concurrent Processing version 11.0

Copyright (c) Oracle Corporation 1979, 1992, 1997. All rights reserved.

Internal Concurrent Manager started : 06-MAR-2001 18:25:49

+---------------------------------------------------------------------------+

Process monitor session started : 06-MAR-2001 18:25:50
ping: unknown host
Process monitor session ended : 06-MAR-2001 18:25:52

Process monitor session started : 06-MAR-2001 18:45:52
ping: unknown host
Process monitor session ended : 06-MAR-2001 18:45:54
06-MAR-2001 18:56:54
Request : 493
Priority : 0
Program : 0/5
State : Q

Process monitor session started : 06-MAR-2001 18:58:09
Process monitor session ended : 06-MAR-2001 18:58:09
06-MAR-2001 18:58:09
Request : 493
Priority : 0
Program : 0/5
State : Q

Shutting down Internal Concurrent Manager : 06-MAR-2001 18:58:09
The TST@TST internal concurrent manager has terminated successfully - exiting.
z=1 (default)

Call to establish_icm failed
The Internal Concurrent Manager has encountered an error.

Review concurrent manager log file for more detailed information. : 06-MAR-2001 18:57:11 -


Shutting down Internal Concurrent Manager : 06-MAR-2001 18:57:11

List of errors encountered:
.............................................................................

_ 1 _
AFPSMG cannot find concurrent manager with process ID 25

Cause: AFPSMG found no rows while selecting concurrent manager 25
from FND_CONCURRENT_PROCESSES for update.

Action: Contact your support representative.

_ 2 _
Routine AFPCSQ encountered an ORACLE error. .

Review your error messages for the cause of the error. (=<POINTER>)
.............................................................................


CONC-ICM ALREADY RUNNING

List of errors encountered:
.............................................................................

_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR

Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
.............................................................................

The TST@TST internal concurrent manager has terminated with status 1 - giving up.

========================================================================

 

[cgswong]

It appears as though your concurrent manager can not start. The log indicates that it tries to start, but keeps shutting down without actually starting, so runnning any concurrent request would fail (give the error you got).

There can be any number of reasons why this error occurs so your best and quickest route is to log an iTAR at Oracle MetaLink.

Hope this helps.

- Stuart

 

[jezzerwebb]

From the extract from the log file, it would seem that when you start up your concurrent managers it thinks that there should be existing processes running, which there are not. This is a &quot;feature&quot; of Oracle Applications, in that the development team did not clear out the concurrent process tables before they packaged it up.

To resolve this, do the following steps.

1. Make sure that there are no concurrent processes still running. ps -ef | grep FNDLIBR
2. Use sqlplus, login as APPLSYS
3. delete * from fnd_concurrent_processes;
Don't panic if it deletes a lot of rows this table holds a lot of useless history information, and should be cleaned up every so often.
4. update fnd_concurrent_queues set running_processes=0;

Now restart your concurrent managers, which should startup without any errors in the log file at all.
Then see if the requests go through OK.

If you have any problems with concurrent managers, the above steps are a good starting point, and you will probably be advised of them first when you contact Oracle.

Good luck.