Core Concurrent Processing - EBS (MOSC)

MOSC Banner

Concurrent manager log always has "Unable to contact Applications TNS Listener for... " after RPC4 p

edited Feb 9, 2017 3:50PM in Core Concurrent Processing - EBS (MOSC) 6 commentsAnswered

Hi,

OS: OEL 5.7

DB: 11.2.0.3

APP: 12.1.3

After applying RPC4 on R12.1.3 concurrent manager started giving following error on stopping cm with adstpall.sh

Unable to contact Applications TNS Listener for FNDSM_RECOPROD_PCHPROD on $NODE.  The Listener may be down or the TNS address is not properly configured for this name. (NODE=RECOPROD)
An error occured in client-side routine afpsmckp for Service Manager FNDSM_RECOPROD_PCHPROD.  The routine returned code 144. 


Check for preceding errors and as well as the service manager log file for further details."


21-JUL-2016 06:00:45 - Could not submit job to kill concurrent process 100209: Oracle error 100: ORA-01403: no data found has been detected in FND_CONC_RAC_UTILS.SUBMIT_MANAGER_KILL_SESSION.


  Adding Node:(RECOPROD), Server Name:(FNDSM_RECOPROD_PCHPROD) to unavailable list
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

EBS Concurrent Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center