Concurrent Managers Are Not Going Down Properly After Applying Patch 16735285 (Doc ID 2063862.1)

Last updated on OCTOBER 03, 2016

Applies to:

Oracle Concurrent Processing - Version 12.1.3 to 12.2.6 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Concurrent Manager Issues

Applied CPU Jan 2015 security patches in our 12.1.3 test environment.

After that, we have noticed "INV Remote Procedure Manager" die after the restart.

As per document "Upgrade 12.1.3: PO Document Approval Manager (POXCON), Receiving Transaction Manager (RCVOLTM) and INV Remote Procedure Manager (INCTM) Do Not Start / Die After Restart (Doc ID 1413393.1)", have applied the patch 16735285.

But after this patch , concurrent manager are not going down gracefully.
the following error occurs.

ERROR
-----------------------
Enable to contact Applications TNS Listener for FNDSM_<nodename> on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=<node name>)
CONC-SM CLIENT ERROR (ROUTINE=afpsmccs) (SM_NAME=<node name) (ERROR=144)

AFPPSPL-- 10-FEB-2015 09:50:27
  Call to PingProcess failed for FNDOPP

AFPPSPL-- 10-FEB-2015 09:50:27
  Node:<node name>, Service Manager:<node name> currently unreachable by TNS
Unable to contact Applications TNS Listener for FNDSM_<node name> on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=<node name>)
CONC-SM CLIENT ERROR (ROUTINE=afpsmckp) (SM_NAME=FNDSM_<node name) (ERROR=144)
10-FEB-2015 09:50:27 - Could not submit job to kill concurrent process 625026: Oracle error 100: ORA-01403: no data found has been detected in FND_CONC_RAC_UTILS.SUBMIT_MANAGER_KILL_SESSION.

  Adding Node:(PLUTO), Server Name:(FNDSM_<node name>) to unavailable list


Found dead process: spid=(1037), cpid=(625026), ORA pid=(57), manager=(0/4)
Unable to contact Applications TNS Listener for FNDSM_<node name> on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=<node name)
CONC


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Apply CPU Jan 2015 security patches.

Bring down concurrent managers.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Cannot start managers

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms