Beruflich Dokumente
Kultur Dokumente
6
Oracle Corporate Support
Problem Repository
Problem ID : 1011248.6
Affected Platforms : Generic: not platform specific
Affected Products : Oracle Application Object Library
Affected Components : FOUNDATION V10.XX
Affected Oracle Vsn : Generic
Summary:
WHAT ARE THE COMMON CONCURRENT MANAGER ISSUES?
+=+
Problem Description:
====================
What are the common concurrent manager issue in applications release 10?
Key words: DIAGNOSIS EXAMPLE ORACLE USDSOP PERMISSIONS LOG OUT APPLCSF CHILD
PROCESS AFPEOT REP_PATH APPLPLS APPLSYS.ENV ORACLE_SID GWYUID FNDNAM TWO_TASK
AFPCAL CPMGR AFPCSQ AFPGCP SYS SYSTEM DUAL AFPGMG PMON LOCK
FND_CONCURRENT_REQUESTS STARTMGR AFPCMT AFPSMG AFPGSR V$PROCESS V$SESSION
V$PARAMETER DBMS_LOCK DBMS_PIPE STANDARD FND_V$PROCESS FND_CONCURRENT
AFPFPROS.PLS AFPFPROB.PLS AFCPDCPS.PLS AFCPDCPB.PLS AFCPUTLS.PLS AFCPUTLB.PLS
FNDCPMGR APPLDCP AFPPRT FDXLNG NLS_LANGUAGE
+==+
Solution ID : 2059281.6
For Problem : 1011248.6
Affected Platforms : Generic: not platform specific
Affected Products : Oracle Application Object Library
Affected Components : FOUNDATION V10.XX
Affected Oracle Vsn : Generic
Summary:
MOST COMMON CONCURRENT MANAGER ISSUES BULLETIN
+=+
Solution Description:
C:/…/1011248.6 1/10
4/21/2011 1011248.6
=====================
1. Make certain that the OS login for the user trying to start
the concurrent manager is the owner of the applications code, or
has been given the appropriate permission to run startmgr and
batchmgr. This can be done by a) making the startmgr script
setuid for applmgr, b) changing the group permissions on the
scripts and placing users any users in that group who should be
able to bring up the concurrent manager.
You will still see the above message for any managers not
C:/…/1011248.6 2/10
4/21/2011 1011248.6
activated and, although listed in the logfile, it is not a
critical error. Exiting with status 0 is an indication that a
program exited cleanly. See chapter 8 of the System
Administration manual for more information.
C:/…/1011248.6 3/10
4/21/2011 1011248.6
iv. Check the pmon method being used, and try using the
LOCK pmon method instead.
select count(*)
from fnd_concurrent_requests
where status_code='T';
update fnd_concurrent_requests
set status_code='X', phase_code='C'
where status_code='T';
C:/…/1011248.6 4/10
4/21/2011 1011248.6
APP-01227 AFPGSR encountered an ORACLE error. ORA-03113:
end-of-file on communication channel
AFPFPROS.pls
AFPFPROB.pls
C:/…/1011248.6 5/10
4/21/2011 1011248.6
AFCPDCPS.pls
AFCPDCPB.pls
AFCPUTLS.pls
AFCPUTLB.pls
select count(*)
from fnd_concurrent_requests
where status_code='T';
OR
update fnd_concurrent_requests
set status_code='X', phase_code='C'
where status_code='T';
Oracle Errors
-------------
C:/…/1011248.6 6/10
4/21/2011 1011248.6
Update Fnd_Concurrent_Requests
Set Nls_Language = Substr(Userenv('Language'),1,
Instr(Userenv('LANGUAGE'),'_')-1),
Nls_Territory = Substr(Userenv('Language'),
Instr(Userenv('LANGUAGE'),'_')+1,
Instr(Userenv('LANGUAGE'),'.')-
Instr(Userenv('LANGUAGE'),'_')-1)
Where Nls_Language is null
or Nls_Territory is NULL;
ORA-942 Table or view does not exist (when starting up the ICM)
2. Check that the view FND_V$PROCESS exists, and that the applsys
user has access to V$PROCESS, V$SESSION, DBMS_LOCK, DBMS_PIPE,
STANDARD, and, if using distributed concurrent processing,
V$THREAD.
Generic Issues
--------------
2. The concurrent manager starts from the command line, but not from
the Administer Concurrent Manager screen.
AFPFPROS.pls
AFPFPROB.pls
C:/…/1011248.6 7/10
4/21/2011 1011248.6
AFCPDCPS.pls
AFCPDCPB.pls
AFCPUTLS.pls
AFCPUTLB.pls
Try relinking FNDLIBR, if that does not check to see if there are
pending requests. If possible, make certain there aren't any
jobs in pending status, and then try to bring the manager up.
This is especially true if there are a high number of requests
with a status of pending because the concurrent manager reads in
all pending requests on startup.
4. The specialization rules that were just recently defined are not
taking effect.
Try bouncing the CM to make sure that all the current rules are
being implemented.
This is most likely due to base bug 246213. Make certain this
patch has been applied. It is actually a 7.1.3 RDBMS bug which
affects complicated views.
8. All the concurrent managers are running, and the concurrent manager
has been successfully bounced several time, but all the requests have
a status of 'Inactive' and 'No Manager'.
C:/…/1011248.6 8/10
4/21/2011 1011248.6
none of the managers could run it. Any requests that follow this
request will then be unable to run until the original request
completes.
------------------------------------------------
When in doubt....
If you are encountering errors with the concurrent managers some steps
that can be safely executed include:
C:/…/1011248.6 9/10
4/21/2011 1011248.6
to those directories. If $APPLCSF is set, so that all the log
and out files get written to a common directory, the $APPLLOG
directories still must exist. Also, even with $APPLCSF set, the
internal concurrent manager log files will always be written to
$FND_TOP/$APPLLOG.
select count(*)
from fnd_concurrent_requests
where status_code='T';
If there are any such rows then delete them from the table, or
modify them so they have status of 'Terminated':
OR
update fnd_concurrent_requests
set status_code='X', phase_code='C'
where status_code='T';
+==+
References:
C:/…/1011248.6 10/10