Monday, March 14, 2011

Lsnrctl Services Displays "status UNKNOWN"

Environment
11gR2 2 nodes Oracle Database on OEL 5.5 platformt

Problem
There are two Metalink notes explaining this issue:
1 Lsnrctl Services Displays "status UNKNOWN", MODOSE, And Multiple Handlers [ID 151223.1]
Listener Control Services Shows Status Unknown for a Database [ID 301877.1]
Issues Affecting Automatic Service Registration [ID 235562.1]

I have a 2-nodes 11gR2 RAC database with 11gR1 Grid Contrl Agent installed on both servers, the database was configured with conventional listener service rather than the new "Single Client Access Name (SCAN)", so the database should use the listener.ora parameter file found under $ORACLE_HOME, which is:
/u02/oracle/product/11.2.0/dbhome_1/network/admin,
However, when I did "lsnrctl" to check listener status, I got the following:

[oracle@node1~]$ lsnrctl


LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 14-MAR-2011 12:05:19


Copyright (c) 1991, 2009, Oracle.  All rights reserved.


Welcome to LSNRCTL, type "help" for information.


LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=node1.host.com)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.2.0 - Production
Start Date                18-JAN-2011 16:54:26
Uptime                    54 days 18 hr. 10 min. 53 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/11.2.0.2/grid/network/admin/listener.ora
Listener Log File         /u02/oracle/diag/tnslsnr/cash/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.100.130)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.100.211)(PORT=1521)))
Services Summary...
Service "node1.host.com" has 1 instance(s).
  Instance "node1", status READY, has 1 handler(s) for this service...
Service "nodeoXDB.wealthengine.com" has 1 instance(s).
  Instance "node1", status READY, has 1 handler(s) for this service...
The command completed successfully

As seen in the above highlighted text, the database is actually using a listener.ora file out of /u01/11.2.02/grid/network/admin, rather than the one from $ORACLE_HOME (/u02).  So I checked the listener.ora file under /u01, here it's:

[oracle@node1 admin]$ more /u01/11.2.0.2/grid/network/admin/listener.ora
LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER))))            # line added by Agent
LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1))))                # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON                # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON              # line added by Agent


So according to the comments found above, it seems that Grid Control Agent made the above changes and forced the database to use the listener.ora file under /u01.  The two nodes do have Grid Control Agent installed. 


Awaiting for Oracle Support for instructions.




References

  1. NOTE:460982.1 - How To Configure Server Side Transparent Application Failover
  2. How to Setup SCAN Listener and Client for TAF and Load Balancing [Video] [ID 1188736.1]
  3. NOTE:887522.1 - 11gR2 Grid Infrastructure Single Client Access Name (SCAN) Explained
  4. NOTE:972500.1 - How to Modify SCAN Setting after Installation
  5.  NOTE:887522.1 - 11gR2 Grid Infrastructure Single Client Access Name (SCAN) Explained
  6. Setting Environment Variables Through Srvctl [ID 733567.1]
  7. LISTENER_SCAN Fails to Start Using SRVCTL [ID 1050953.1]
  8. 11.2 Scan and Node TNS Listener Setup Examples [ID 1070607.1]
  9. http://www.oracle.com/technetwork/database/clustering/overview/scan-129069.pdf

Labels: , ,

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home