ORA-12537错误处理一例

一。问题

   用SQLPLUS连接新搭建的RAC时，报如下错误：

SQL*Plus: Release 11.2.0.1.0 Production on Tue Nov 14 00:32:50 2017

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

ERROR:
ORA-12537: TNS:connection closed

二。分析

1.检查scan listener和本地listener都有启动，已有启动

2.用netstat检查端口是否存在，已有存在

3.检查iptables是关闭的

4.在其它机器上telnet port是通的

5.检查crs服务是正常 的

6.本机sqlplus连接数据库是正常的

三。解决

cd $ORACLE_HOME/bin

ls -l|grep oracle

 -rwxr-s--x 1 cplmst dba 239820050 Nov  7 16:21 oracle

chmod u+s oracle
改为
-rwsr-s--x 1 cplmst dba 239820050 Nov  7 16:21 oracle
即可。 

参考文档：

Applies to:

Oracle Database Configuration Assistant - Version: 11.2.0.1 and later   [Release: 11.2 and later ]
Information in this document applies to any platform.

Symptoms

In environment where listener home (including SCAN listener which resides in Grid Infrastructure/ASM home) and database home are owned by different OS user, ORA-12537 could happen when connecting through listener, when creating database through DBCA, or when installing database software and creating a database in runInstaller. Job Role Separation is a typical example as SCAN and local grid home listener is owned differently than database.

• Error detail

12537, 00000, "TNS:connection closed"
// *Cause: "End of file" condition has been reached; partner has disconnected.
// *Action: None needed; this is an information message.

Before the error is reported, connection could hang for a while, and a core file may also be generated.

• Screen output:

SQL> conn system/xxx@OSES
ERROR:
ORA-12537: TNS:connection closed

OR

PRCR-1079 : Failed to start resource ora.db11.db
CRS-5011: Check of resource db11 failed: details at ..
CRS-2674: Start of ora.db11.db on racnode1 failed
ORA-12546: TNS:permission denied

 

• listener_scann.log or listener.log

TNS-12518: TNS:listener could not hand off client connection
TNS-12546: TNS:permission denied
 TNS-12560: TNS:protocol adapter error
  TNS-00516: Permission denied
   Linux Error: 13: Permission denied

OR

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

 

• runInstaller error if installing

INFO: Starting Output Reader Threads for process /ocw/grid/bin/kfod
INFO: Parsing KFOD-00300: OCI error [-1] [OCI error] [ORA-12547: TNS:lost contact
INFO: Parsing ] [12547]
INFO: Parsing
INFO: The process /ocw/grid/bin/kfod exited with code 1
..
SEVERE: [FATAL] [INS-30502] No ASM disk group found.
   CAUSE: There were no disk groups managed by the ASM instance +ASM1.

 

Cause

1. Listener owner (including SCAN listener) can not access oracle binary in database home:

As listener owner:

$ ls -l $RDBMS_HOME/bin/oracle
ls: /home/oracle/app/oracle/product/11.2/db/bin/oracle: Permission denied

2. Oracle binary in database home has wrong permission:

ls -l $RDBMS_HOME/bin/oracle
-rwxr-x--x 1 oracle asmadmin 184286251 Aug  9 16:25 /home/oracle/app/oracle/product/11.2/db/bin/oracle

The permission "-rwxr-x--x" is wrong as it's missing suid bit, oracle binary should have permission of 6751:

-rwsr-s--x 1 oracle asmadmin 184286251 Aug  9 16:25 /home/oracle/app/oracle/product/11.2/db/bin/oracle

Note: If Job Role Separation is in place, the group will be , otherwise it will be 


3. File System for database home does not support setuid/suid or has nosetuid/nosuid set:

mount| grep 
/home/oracle on /dev/dsk/diskoracle read/write/nosuid..

 

Solution

Solution is to make sure file system for database home has setuid/suid set, database binary($RDBMS_HOME/bin/oracle) has correct ownership and permission, and listener owner is able to access database oracle binary (as listener owner, "ls -l $RDBMS_HOME/bin/oracle" will tell)

If its Job Role Separation environment, please refer to the following document:

Oracle® Grid Infrastructure 
Installation Guide
11g Release 2 (11.2)

Oracle ASM Job Role Separation Option with SYSASM

References

NOTE:970619.1 - ORA-12545 or ORA-12537 Reported while Connecting to RAC through SCAN name
NOTE:975457.1 - How to Troubleshoot Connectivity Issue with 11gR2 SCAN Name