My Oracle Support Banner

TNS-12514,TNS-12523,TNS-12528,J000 died kkjcre1p: unable to spawn jobq slave process (Doc ID 756389.1)

Last updated on MARCH 08, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 10-Oct-2016***


Symptoms


Error below appears on the database

TNS-12514: TNS:listener does not currently know of service requested in connect descriptor,
TNS-12523: TNS:listener could not find instance appropriate for the client connection,
TNS-12502: TNS:listener received no CONNECT_DATA from client,
TNS-12520: TNS:listener could not find available handler for requested type of server,
TNS-12528: TNS:listener: all appropriate instances are blocking new connections

Investigating the alert at the same time find the errors below:-

Process J000 died, see its trace file
Sun Nov 23 06:00:19 2008
kkjcre1p: unable to spawn jobq slave process
Sun Nov 23 06:00:19 2008
Errors in file d:\oracle\admin\fm01\bdump\fm01_cjq0_3780.trc:


Process J000 died, see its trace file
Sun Nov 23 06:00:20 2008
kkjcre1p: unable to spawn jobq slave process
Sun Nov 23 06:00:20 2008
Errors in file d:\oracle\admin\fm01\bdump\fm01_cjq0_3780.trc:

The location of the alert log file and bdump is different in 11g from the pre 11g. The locations in 11g are:

Alert log is ”{ADR_HOME}/alert/”
BDUMP is ”{ADR_HOME}/trace/”
Refer to Note 438148.1- Finding alert.log file in 11g 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.