ORA-12537 TNS-12518 Process m000 died

The recent customer email description failed to connect to the database from the client with the error code ORA-12537: TNS: connection closed, and the connection was closed. Directly through tnsping, there is no problem. The TNS-12518: TNS: listener cocould not hand off client connection appears in the listener log. That is, Listener cannot distribute client connections. The following describes the specific error information, analysis and solution processes.

 

1. Front-end error information

C:\Program Files\VMware\VMware vSphere CLI>sqlplus robinson@sywgmrSQL*Plus: Release 10.2.0.1.0 - Production on Thu Mar 27 10:49:00 2014Copyright (c) 1982, 2005, Oracle.  All rights reserved.Enter password:ERROR:ORA-12537: TNS:connection closed

2. Fault Analysis

Oracle @ SZDB:/users/oracle/OraHome10g/network/log> tail listener_sywgmr.log TNS-12547: TNS: lost contact TNS-12560: TNS: protocol adapter error TNS-00517: Lost contact Linux Error: 32: broken pipe27-MAR-2014 11:02:38 * (CONNECT_DATA = (SID = SYWGMR) (CID = (PROGRAM =) (HOST =__ jdbc _) (USER = ))) * (ADDRESS = (PROTOCOL = tcp) (HOST = 127.0.0.1) (PORT = 63561) * establish * SYWGMR * 12518TNS-12518: TNS: listener cocould not ha Nd off client connection TNS-12547: TNS: lost contact TNS-12560: TNS: protocol adapter error TNS-00517: Lost contact Linux Error: 32: Broken pipeoracle @ SZDB: ~> Oerr ora 1253712537,000 00, "TNS: connection closed" // * Cause: "End of file" condition has been reached; partner has disconnected. // * Action: None needed; this is an information message. oracle @ SZDB: ~> Oerr ora 1251812518,000 00, "TNS: listener cocould not hand off client connection" // * Cause: The process of handing off a client connection to another process // failed. // * Action: Turn on listener tracing and re-execute the operation. verify // that the listener and database instance are properly configured for // direct handoff. if problem persists, call Oracle Support. // * Comment: The problem can be Worked around und by grouping dispatcher (s) // to specifically handle the desired presentation (s), and connecting // directly to the dispatcher, bypassing the listener. # according to the above 2 error no, did not get too much useful information # ora-12518 is recommended for a trace. its comment description can be solved by configuring disaptcher. Currently, our database uses the dedicate method. # For details about how to configure the listener trace, refer to listener, fault still # view alert log below # day below Note: The m000 process cannot be created. The m000 process is the slave process of the smon process. oracle @ SZDB: /users/oracle> tail/u02/database/SYWGMR/bdump/alert_SYWGMR.logThu Mar 27 11:00:28 2014 ksvcreate: Process (m000) creation failedThu Mar 27 11:01:29 2014 Process m000 died, see its trace fileThu Mar 27 11:01:29 2014 ksvcreate: Process (m000) creation failedThu Mar 27 11:02:30 2014 Process m000 died, see its trace fileThu Mar 27 11:02:30 2014 ksvcreate: Process (M000) creation failed # An Error occurred at 06:19:02 2014 and the job slave Process Thu Mar 27 06:19:02 2014 Process J000 died could not be derived. see its trace fileThu Mar 27 06:19:02 2014kkjcre1p: unable to spawn jobq slave processThu Mar 27 06:19:02 2014 Errors in file/u02/database/SYWGMR/bdump/sywgmr_cjq0_7780.trc: # From the alert log, we can see that the instance cannot create new process, probably because the maximum number of processes set by the instance is exceeded. oracle @ SZDB: ~> Export ORACLE_SID = SYWGMRoracle @ SZDB: ~> Sqlplus/as sysdbaSQL * Plus: Release 11.2.0.3.0 Production on Thu Mar 27 10:56:27 2014 Copyright (c) 1982,201 1, Oracle. all rights reserved. connected to: Oracle Database 10g Release 10.2.0.3.0-64bit Production -- Author: Leshami -- Blog: http://blog.csdn.net/leshamiSQL> col RESOURCE_NAME for a20SQL> col LIMIT_VALUE for a20SQL> select resource_name, MAX_UTILIZATION, LIMIT_VALUE from v $ resource_limit where resource_name in ('processs', 'session'); RESOURCE_NAME MAX_UTILIZATION LIMIT_VALUE ------------------ ------------- your processes 1000 1000 sessions 1004 # The above query result is true.

3. troubleshooting

# Find the cause of the fault and handle it. The following is a description of processes: PROCESSES specifies the maximum number of operating system user processes that can simultaneously connect to Oracle. its value shoshould allow for all background processes such as locks, job queue processes, and parallel execution processes. the default values of the SESSIONS and TRANSACTIONS parameters are derived from this parameter. therefore, if you change the value of PROCESSES, yo U shoshould evaluate whether to adjust the values of those derived parameters. # modify the processes parameter of an instance, as shown below. memory modification is not supported. Therefore, scopesys> alter system set processes = 1500; alter system set processes = 1500 * ERROR at line 1 must be added: ORA-02095: specified initialization parameter cannot be modifiedsys> alter system set processes = 1500 scope = spfile; System altered. # The following is the result after modification and restart. If you are using the pfile parameter, you can directly modify the processes value in pfile and then restart it. Sys> show parameter processesNAME type value =------------- ------------------------------ processes integer 1500sys> show parameter session; name type value =----------- ---------------------------- sessions integer 1655

More references

For more information about Oracle RAC, see
Use crs_setperm to modify the resource owner and permissions of RAC.
Use crs_profile to manage RAC resource configuration files
RAC database startup and Shutdown
Oracle RAC services
Services in Oracle Database 10g
Migrate datbase from single instance to Oracle RAC
Connect Oracle RAC to a specified instance
Oracle RAC load balancing test (combined with server and client)
Oracle RAC server connection Load Balance)
Load Balance)
Non-Default port listening configuration in oracle rac (listener. ora tnsnames. ora)
Oracle rac listener Configuration (listener. ora tnsnames. ora)
Configure RAC load balancing and Failover
CRS-1006, CRS-0215 fault case
Installing Oracle 10g RAC Based on Linux (RHEL 5.5)
Use runcluvfy to verify the Oracle RAC installation environment

For more information about the basics and concepts of Oracle network configuration, see:
Configure dynamic service registration for non-default ports
Configure sqlnet. ora to restrict IP Access to Oracle
Configure and manage Oracle listener logs
Set the Oracle LISTENER password (LISTENER)
Configure the ORACLE client to connect to the database

For more information about user-managed backup and recovery, see
Oracle cold backup
Oracle Hot Backup
Concept of Oracle backup recovery
Oracle instance recovery
Oracle recovery based on user management
SYSTEM tablespace management and Backup Recovery
SYSAUX tablespace management and recovery
Oracle backup control file recovery (unsing backup controlfile)

For information on RMAN backup recovery and management, see
RMAN overview and architecture
RMAN configuration, Monitoring and Management
Detailed description of RMAN backup
RMAN restoration and recovery
Create and use RMAN catalog
Create RMAN storage script based on catalog
Catalog-based RMAN backup and recovery
RMAN backup path confusion
Use RMAN for recovery from different machine backups (WIN platform)
Use RMAN to migrate a file system database to ASM
Linux RMAN backup shell script
Use RMAN to migrate the database to a different machine

For the ORACLE architecture, see
Oracle tablespace and data files
Oracle Password File
Oracle parameter file
Oracle ONLINE redo LOG FILE)
Oracle Control File)
Oracle archiving logs
Oracle ROLLBACK and UNDO)
Oracle database instance startup and Shutdown Process
Automated Management of Oracle 10g SGA
Oracle instances and Oracle databases (Oracle Architecture)