My Oracle Support Banner

DB Clients Cannot Connect to the SMF DB After a Cluster Failover to the Other Node Resulting in a "ORA-12505" Error (Doc ID 1297933.1)

Last updated on MAY 18, 2021

Applies to:

Oracle Communications Network Charging and Control - Version 3.1.0 and later
Information in this document applies to any platform.

Symptoms

If one node of a Solaris Clustered Service Management System (SMS) goes offline, some of the configured Resource Groups will failover to the other clustered SMS node(s), resulting in database (DB) clients' not being able to connect to the Database anymore.  A client is any process that connects to the database either locally or remotely.

The client process will produce an Oracle database error message when this occurs, similar to the following example:


A net service name alias of connect descriptor can be defined using the Oracle tnsnames.ora and listerner.ora files (found in $ORACLE_HOME/network/admin) of the database server.  An example of a SMS tnsnames.ora file is attached to this document as a reference.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 Some SMS Cluster Background Information
Changes
Cause
 Cluster Resource Group Configuration
 lh-ora1-rg
 lh-ora2-rg
 ora-lsnr1-rg
 ora-lsnr2-rg
 LISTENER1:
 LISTENER2:
 LISTENER2:
Solution
 To Conclude


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.