Connection to Auxilary using connect string failed with ORA-12528 [ID 419440.1]-优快云博客

Connection to Auxilary using connect string failed with ORA-12528 [ID 419440.1]

	Modified 15-FEB-2011Type PROBLEMStatus PUBLISHED

In this Document
Symptoms
Cause
Solution
References

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.1.0.6 - Release: 9.2 to 11.1
Information in this document applies to any platform.
***Checked for relevance on 15-Feb-2011***

Symptoms

During duplicate database creation, connection to the auxiliary database from target database server fails with ORA-12528: TNS:listener: all appropriate instances are blocking new connections.

E:/oracle/product/10.2.0/db_1/BIN>rman target / auxiliary sys/sys@duplicate

Recovery Manager: Release 10.2.0.1.0 - Production on Fri Mar 16 00:11:05 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: ORIGINAL (DBID=1451288337)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12528: TNS:listener: all appropri
ate instances are blocking new connections

When it fails , add manual entry for sidin listener.ora as per Note 301099.1

However, still youreceive the same error on connect in some cases.

Cause

Its because only the Auxiliary Instance is running .The instance registers with the listener by the PMON process. TO start the PMON process the database need to be in MOUNT status. Before there is nothing to register the database to the listerner so the instance is BLOCKED.

Solution

There are 2 options to solve this problem

Option 1

Connect to the auxiliary instance using OS authentication (as /) and use password file authentication for target database and connect via Listener.For example make below connection in RMAN from auxiliary database server

E:>rmantargetsys/sys@originalauxiliary/

RecoveryManager:Release10.2.0.1.0-ProductiononThuMar1523:57:082007

Copyright(c)1982,2005,Oracle.Allrightsreserved.

connectedtotargetdatabase:ORIGINAL(DBID=1451288337)
connectedtoauxiliarydatabase:DUPLICATE(notmounted)

Option 2

Create a static entry for the auxiliary database in the listener.ora file of the auxiliary database Oracle home and restart the listener. For example

Listener.ora
-------------

SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(GLOBAL_DBNAME=SAIRAM)
(ORACLE_HOME=G:/oracle/product/10.2.0/db_1)
(SID_NAME=SAIRAM)
)
)

Or

Use the Oracle10G feature. Make below entry in the tnsnames.ora file of the Oracle home from when RMAN is being executed.

tnsnames.ora
------------

SAIRAM=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)(HOST=apadhi-idc)(PORT=1521))
(CONNECT_DATA=
(SERVER=DEDICATED)
(SERVICE_NAME=SAIRAM)(UR=A)
)
)