The client cannot connect to oracle normally, and the listening status is & quot; Not All Endpoints Registered &

Source: Internet
Author: User

The client cannot connect to oracle normally, and the listening status is "Not All Endpoints Registered" solution 1. symptom Description: The application response is Not normal.

[grid@sdcmpdb1 ~]$ lsnrctl statusLSNRCTL for Linux: Version 11.2.0.3.0 - Production on 01-JUL-2013 16:39:49Copyright (c) 1991, 2011, Oracle.  All rights reserved.Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))STATUS of the LISTENER------------------------Alias                     LISTENERVersion                   TNSLSNR for Linux: Version 11.2.0.3.0 - ProductionStart Date                01-JUL-2013 15:47:57Uptime                    0 days 0 hr. 51 min. 52 secTrace Level               offSecurity                  ON: Local OS AuthenticationSNMP                      OFFListener Parameter File   /oracle/11.2.0/grid/network/admin/listener.oraListener Log File         /oracle/app/oracle/diag/tnslsnr/sdcmpdb1/listener/alert/log.xmlListening Endpoints Summary...  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))The listener supports no servicesThe command completed successfully[grid@sdcmpdb1 ~]$ crsctl status res -t--------------------------------------------------------------------------------NAME           TARGET  STATE        SERVER                   STATE_DETAILS       --------------------------------------------------------------------------------Local Resources--------------------------------------------------------------------------------ora.ARCHDG.dg               ONLINE  ONLINE       sdcmpdb1                                                    ONLINE  ONLINE       sdcmpdb2                                     ora.DATA.dg               ONLINE  ONLINE       sdcmpdb1                                                    ONLINE  ONLINE       sdcmpdb2                                     ora.LISTENER.lsnr               ONLINE  INTERMEDIATE sdcmpdb1                 Not All Endpoints R                                                              egistered                          ONLINE  ONLINE       sdcmpdb2                
2. After query, the reason is as follows: the database has two listener, one oracle user and one grid user. Normally, only the grid user
[grid@sdcmpdb1 ~]$  ps -ef|grep LISTENERoracle    8317     1  0 15:41 ?        00:00:01 /oracle/app/oracle/product/11.2.0/db_1/bin/tnslsnr LISTENER -inheritgrid     14518     1  0 15:47 ?        00:00:00 /oracle/11.2.0/grid/bin/tnslsnr LISTENER -inheritgrid     21614 21346  0 16:45 pts/0    00:00:00 grep LISTENER

 

3. After one stop, it should be back to normal.
[grid@sdcmpdb1 ~]$ ps -ef|grep LISTENERgrid     14518     1  0 15:47 ?        00:00:00 /oracle/11.2.0/grid/bin/tnslsnr LISTENER -inheritgrid     21895 21724  0 16:49 pts/0    00:00:00 grep LISTENER

 

4. This error is also reported on metailink, mainly because The listener port is occupied and cannot be properly started. As a result, Cause The problem is caused by another listener defined statically in listener. ora, using the same port and IP is running from the RDBMS ORACLE_HOME, started manually causing the default listener starting from GRID_HOME can not register its endpoint. hence the error reported in dbca. ps-ef | grep tns:
grid   7222 1 0 Apr26 ? 00:00:13 /u01/app/11.2.0/grid/bin/tnslsnr LISTENER_SCAN1 -inheritgrid   7237 1 0 Apr26 ? 00:00:13 /u01/app/11.2.0/grid/bin/tnslsnr LISTENER -inheritoracle 7354 1 0 Apr26 ? 00:00:01 /u02/app/oracle/product/11.2.0/db/bin/tnslsnr LISTENER -inherit  Another possible cause is the listener or scan listener being defined manually in listener.ora, for example:LISTENER_SCAN3 =                           (DESCRIPTION =   (ADDRESS = (PROTOCOL = TCP)(HOST = racnode1)(PORT = 1523)) )LISTENER_SCAN1 =                             (DESCRIPTION =   (ADDRESS = (PROTOCOL = TCP)(HOST = racnode1)(PORT = 1521))SolutionFrom 11.2 onwards, all listeners should be runing from GRID_HOME, listener and listener_scan<n> entry should be added automatically into listener.ora, no manual editing is required for TCP definition.1. Stop the listener running from RDBMS ORACLE_HOME$<RDBMS ORACLE_HOME>/bin/lsnrctl stop LISTENER2. stop the listener from GRID_HOME$<GRID_HOME>/bin/srvctl stop listener -n <node name>$<GRID_HOME>/bin/srvctl stop scan_listener -i <scan#>eg:$<GRID_HOME>/bin/srvctl stop listener -n racnode1$<GRID_HOME>/bin/srvctl stop scan_listener -i 1If above command fails to stop the tnslsnr process, please use "kill -9 <pid of tnslsnr>" to stop the LISTENER and LISTENER_SCAN1 process.3. remove any manually added LISTENER definition from listener.ora if it exists4. restart the LISTENER and LISTENER_SCAN1  from GRID_HOME$<GRID_HOME>/bin/srvctl start listener -n <node name>$<GRID_HOME>/bin/srvctl start scan_listener -i <scan#>5. check crsctl stat res -t output, they both should show ONLINE status now.

 

 

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.