Is Service Manager up & running ???

Is Service Manager up & running ???

select CONCURRENT_QUEUE_NAME, ENABLED_FLAG,
MAX_PROCESSES, RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME like 'FNDSM%';

- ps -ef | grep FNDSM
- U'll get PPID of FNDSM
- ps -ef | grep PPID

The FNDSM PPID will be the parent process of the other concurrent manager services in the environment


UR's Key Run ;-) 

How to create FNDSM ??????

Some time after cloning Service Mgr "FNDSM" might be missing.

In that case, create FNDSM as below

as applmgr user

Run @$FND_TOP/patch/115/sql/afdcm037.sql - Creates necessary libs for FNDSM and Mgr for pre existing nodes.

Note : FNDSM can not be created from Conc -> Mgr -> Define form

UR's Key Run ;-) 

Identify Request Trace file

Get Ur Conc Req Trace File as below :

sql>select value from v$parameter where name='user_dump_dest';

Run the following sql:--

prompt
accept request prompt 'Please enter the concurrent request id for the appropriate concurrent program:'
prompt

column traceid format a8
column tracename format a80
column user_concurrent_program_name format a40
column execname format a15
column enable_trace format a12
set lines 80
set pages 22
set head off

SELECT 'Request id: '||request_id ,
'Trace id: '||oracle_Process_id,
'Trace Flag: '||req.enable_trace,
'Trace Name:
'||dest.value||'/'||lower(dbnm.value)||'_ora_'||oracle_process_id||'.trc',
'Prog. Name: '||prog.user_concurrent_program_name,
'File Name: '||execname.execution_file_name|| execname.subroutine_name ,
'Status : '||decode(phase_code,'R','Running')
||'-'||decode(status_code,'R','Normal'),
'SID Serial: '||ses.sid||','|| ses.serial#,
'Module : '||ses.module
from fnd_concurrent_requests req, v$session ses, v$process proc,
v$parameter dest, v$parameter dbnm, fnd_concurrent_programs_vl prog,
fnd_executables execname
where req.request_id = &request
and req.oracle_process_id=proc.spid(+)
and proc.addr = ses.paddr(+)
and dest.name='user_dump_dest'
and dbnm.name='db_name'
and req.concurrent_program_id = prog.concurrent_program_id
and req.program_application_id = prog.application_id
and prog.application_id = execname.application_id
and prog.executable_id=execname.executable_id;

select oracle_id from fnd_concurrent_requests where request_id = &req_id;


UR's Key Run ;-) 

Could not start Service Manager FNDSM_

CM.... Wake Up... Wake Up...

Issue: CM not cmg up after JDK upgrade to 1.6.0_18. Got the below err in Log

Starting STANDARD Concurrent Manager               : 25-OCT-2010 10:29:42

Could not start Service Manager FNDSM_APPSDBAEXPERTS_TEST1. The TNS alias could not be located, the listener process on APPSDBAEXPERTS could not be contacted, or the listener failed to spawn the Service Manager process.

Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /test1/applmgr/11510/fnd/11.5.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 25-OCT-2010 10:29:42

                     Process monitor session ended : 25-OCT-2010 10:29:42

Sol:

-- From the error we thought its issue with tnsfiles. Found some differences ( as we ran autoconfig ), so restored the backup files and retried bringing up the CM.

   But still CM is not happy to come Up :-)

-- Then we thought of relinking FND executables will solve the issue. But..still CM is said NO..

-- We found Note 470100.1 with exact error ( But this note mostly appeals post clone issue where fnd_nodes table contains non-existent nodes info ).

   Note says:
  1. Execute FND_CONC_CLONE.SETUP_CLEAN

  2.  Run AutoConfig on DB.

  3.  Run AutoConfig on MT

  4.  Retest CM

   -- Tried this...thinking may b it will work.... CM said.. Wat U think I am...? I am not gng to get convinced doing something or the other...

-- Finally.....

   We got the Exact Hit...

   Note 423170.1

   As per this note the issue is bec of FNDSM coredump issue.

   try,

   $ cd $FND_TOP/bin

   $ FNDSM

   Segmenation Fault

   -- In gen.. we should not get any o/p at all if tht is good.

   -- It's exactly the same issue in our case.

   Action Plan:-

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

   1. Apply patch 3830807: " PATCH 3293983 NEEDS TO INCLUDE ALL THE MAKEFILES UNDER THE 8.0.6 ORACLE_HOME".

   2. Relink all executables using adadmin.

   3. Retest CM.

   Note: The Concurrent Manager should start without any errors. There should be no errors in the 8.0.6 listener log file.

--- Finally, Our CM is very much Happy 2 come Up... nd It Came Up......... :-)

--- Actually this issue has been fixed by my frd..nd collegue Srini :-) bef him.. lot of trail nd errors done for many hrs..bt he fixed..in a fly... :-)

Bye..Guys..

K I R A N...

Register concurrent program with request group.

Most of us came across a situation where
after defining(promoting) a concurrent program ,to make other users be able to
run the program we need to add the program to a request group(which we used to
do by navigation through security->responsibility->Request).
The same can be achieved by running package FND_PROGRAM as foloows.

DECLARE
BEGIN
FND_PROGRAM.add_to_group
(
PROGRAM_SHORT_NAME =>'XX_XXXXXX'
,PROGRAM_APPLICATION =>'AR'
,REQUEST_GROUP =>'Receivables All'
,GROUP_APPLICATION =>'AR'
) ;
commit;
exception
when others then
dbms_output.put_line('Object already exists');
END ;
/