Streams Propagation Fails with ORA-12514 after Remote Database Global Database Name Change

(Doc ID 1503612.1)

Last updated on MAY 15, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.4 [Release 11.1 to 11.2]
Information in this document applies to any platform.

Symptoms

Streams Propagation encountering ora-12154

Remote database is a RAC database using SCAN listener

Propagation is configured using queue_to_queue=>TRUE

The global database name is of the remote database has been changed from
CDB to CDB2. Other than that there have been not other changes. The tnsnames.ora
file still refers to the remote database as CDB. There is still a service CDB reported by
the remote listener.

Listener Services on the remote database show : 

On the remote side at the listener, you have :
Service "CDB" has 3 instance(s).
 Instance "CDB_1", status READY, has 1 handler(s) for this service...
 Instance "CDB_2", status READY, has 1 handler(s) for this service...
 Instance "CDB_3", status READY, has 1 handler(s) for this service...
...
The services connected with the Streams Apply queue is :

Service "SYS$STRMADMIN.A_Q_F_CDBP.CDB2" has 1 instance(s).
 Instance "CDB_1", status READY, has 1 handler(s) for this service...
...

Tracing the sqlnet requests from the local side using sqlnet.ora/trace_level_server=16 shows that the
error is being caused by a mismatch in the requested service name for the Streams queue.

The local side is attempting to access the Streams queue using : SYS$STRMADMIN.A_Q_F_CDBP.CDB
when in fact that Streams queue is registered with the listener as service :  SYS$STRMADMIN.A_Q_F_CDBP.CDB2

Changes

The global database name of the remote database has been changed.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms