SR 3-2743352731: TNS-12500: TNS:listener failed to start a dedicated server process === ODM Action Plan === The RDA

uploaded is for a Hyperion Database, it has no DBA information whatsoever. To avoid further back and forth, please refer to below note, it has solutions and checks to this kind of errors. ORA-00610 And/Or "unable to spawn jobq slave process " And/Or "Process(<>) creation failed" In The A(Doc ID 416244.1) ORA-00610 And/Or "unable to spawn jobq slave process " And/Or "Process(<>) creation failed" In The Alert Log And/Or TNS-12518/ TNS-12500 In Listener Log

Applies to:
Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.2.0.2 - Release: 8.1.7 to 11.2 Information in this document applies to any platform. Oracle Server Enterprise Edition - Version: 10.1.0.2 to 11.1.0.7

Symptoms
Getting ORA-00610: Internal error code in the alert log. You can see the following in alert log : Errors in file /oracle/app/oracle/admin/icdiuat/bdump/icdiuat_ora_508118.trc: ORA-00610: Internal error code Thu Feb 1 14:53:43 2007 Process J000 died, see its trace file Thu Feb 1 14:53:43 2007 kkjcre1p: unable to spawn jobq slave process ksvcreate: Process(q002) creation failed Alert log is in different directory in 11g than in earlier versions. Listener connections could also be failing with the following errors : TNS-12518: TNS:listener could not hand off client connection TNS-12547: TNS:lost contact TNS-12560: TNS:protocol adapter error TNS-00517: Lost contact Linux Error: 32: Broken pipe TNS-12518 is usually an indication of a resource problem. Below error can also be an indication of the same problem. ORA 12500 "TNS:listener failed to start a dedicated server process"

Cause
This is usually a resource problem. i.e. lack of resources at the OS level.

Solution
You can try the following as solutions : 1. Increase the paramater JOB_QUEUE_PROCESSES. 2. Make sure Swap is correctly configured and increase it if necessary. 4 ~ 8 GBs of RAM, set Swap to at least double RAM size. 8~16 GBs of RAM, set Swap to double RAM. 16~32 GBs of RAM or more, set Swap at a rate of 0.75xRAM. 3. Make sure all the Kernel parameters are correctly configured above minimum requirements, especially maximum number of processes per non-root user. 4. Use the HCVE to check that all the minimum requirements are met. Note.250262.1 RDA 4 - Health Check / Validation Engine Guide 5. Check the ulimits and preferably set all to Unlimited. 6. Check the system log at the same time of the messages for errors/any indication of resource problem. 7. Check your SGA and PGA settings, make sure they are not set too low or too high. Preferably PGA_AGGREGATE_TARGET is set at a rate of 2 MBs per process defined by the PROCESSES parameter. An over allocation of resources could also cause the same. One of the above solutions will most likely fix your problem but if none does, please log an SR with Oracle Support to assist you. Hints: You can monitor the PROCESSES usage at the database level using the V$RESOURCE_LIMIT view. Also, if you monitor the database and see a lot of INACTIVE sessions, then you need to resolve that first before addressing the suggestions above, these sessions are lying idle eating up resources, and causing limitations, so the users need to make sure to exit their sessions gracefully, these sessions should be cleaned up regularly and perhaps consider using DCD and KeepAlive (Windows only). Note.226202.1 How to Set Keepalive on Windows NT/2000 Note.151972.1 Dead Connection Detection (DCD) Explained