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...