Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1300504.1
Update Date:2012-08-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  1300504.1 :   Intermittent ORA-12514 on Exadata RAC Database Server 11.2  


Related Items
  • Exadata X3-2 Hardware
  •  
  • Exadata Database Machine X2-8
  •  
  • Exadata Database Machine X2-2 Full Rack
  •  
  • Exadata Database Machine X2-2 Half Rack
  •  
  • Exadata Database Machine X2-2 Qtr Rack
  •  
  • Exadata Database Machine X2-2 Hardware
  •  
  • Exadata X3-2 Half Rack
  •  
  • Exadata X3-2 Full Rack
  •  
  • Oracle Exadata Storage Server Software
  •  
  • Exadata Database Machine V2
  •  
  • Exadata X3-8 Hardware
  •  
  • Exadata X3-2 Eighth Rack
  •  
  • Oracle Exadata Hardware
  •  
  • Exadata X3-2 Quarter Rack
  •  
Related Categories
  • PLA-Support>Database Technology>Engineered Systems>Oracle Exadata>DB: Exadata_EST
  •  




Created from <SR 3-1888565281>

Applies to:

Oracle Exadata Storage Server Software - Version 11.2.1.2.0 and later
Oracle Exadata Hardware - Version 11.2.0.1 and later
Exadata Database Machine V2 - Version Not Applicable and later
Exadata Database Machine X2-2 Full Rack - Version Not Applicable and later
Exadata Database Machine X2-2 Half Rack - Version Not Applicable and later
Information in this document applies to any platform.
***Checked for relevance on 22-Aug-2012***

Symptoms


2 Node RAC Cluster
Connections via the listener occasionally fail to connect to the DB Node.

Service we are trying to connect to ->

Service "ntxdvn"
& this has 2 instance -> Instance "ntxdvn1", & "ntxdvn2"

Fails with ->

ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

Changes

None.  Relatively new deployment of Exadata machine.

Cause


One of the SCAN listeners was not registering all database services

[oracle@dm01db01 bin]$ ./lsnrctl status LISTENER_SCAN1

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 02-JUL-2010 16:12:00

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

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1)))
STATUS of the LISTENER
------------------------
Alias LISTENER_SCAN1
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 02-JUL-2010 12:01:00
Uptime 0 days 4 hr. 10 min. 59 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/11.2.0/grid/network/admin/listener.ora
Listener Log File /u01/app/11.2.0/grid/log/diag/tnslsnr/dm01db01/listener_scan1/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER_SCAN1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=167.113.153.236)(PORT=1521)))
The listener supports no services
The command completed successfully

Also
====


[oracle@dm01db02 bin]$ ./srvctl config service -d ntxdvn -s ntxdvn -a
PRCR-1001 : Resource ora.ntxdvn.ntxdvn.svc does not exist

167.113.153.235 (LISTENER_SCAN2) has service ntxdvn for instance ntxdvn2. Connection is successful.
167.113.153.237 (LISTENER_SCAN3) has service ntxdvn for instance ntxdvn1. Connection is successful.
167.113.153.236 (LISTENER_SCAN1) has no service for ntxdvn. Connection failed.

Solution


This behavior has not been confirmed to be a defect, nevertheless we are seeing it here when the server's public name (IP address) is configured on eth0 device.

You can easily workaround this problem by defining the REMOTE_LISTENER in the database.

Re-define the REMOTE_LISTENER parameter as follows:

Old remote_listener parameter:
remote_listener=dm01-scan:1521

New remote_listener parameter:
remote_listener=listeners_dm01

Added tnsnames.ora entry for listeners_dm01on both DBM's in the RDBMS Oracle Home.
listeners_dm01 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST=dm01scan-vip1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST=dm01scan-vip2)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST=dm01scan-vip3)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST=dm0101-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST=dm0101-vip)(PORT = 1521))
)
)

replacing each hostname with the proper IP address.

We have logged the <BUG:9884238> to track any future occurrences of this behavior and documented the work-around and desired behavior.

References

@ <BUG:9884238> - EXADATA V2 : LISTENER ENDPOINT INCLUDES CISCO MANAGEMENT NETWORK

Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback