Notes when using RMAN to copy a physical standby Database

When using RMAN to copy a physical standby database, it is prone to errors and the error is very strange.
The author summarizes the following points.

1. RMAN-04006 ORA-12528

Start the slave database to nomount

SQL> startup nomount & nbsp;
The Oracle routine has been started.

Total System Global Area 751595520 bytes
Fixed Size 2292912 bytes
Variable Size 557843280 bytes
Database Buffers 188743680 bytes
Redo Buffers 2715648 bytes

Connect to the master database

Oracle @ Sol_ORA:/oracle/12.1/network/admin $ rman target sys/test @ TESTM auxiliary sys/test @ TESTS

Recovery MANAGER: Release 12.1.0.1.0-Production on Thursday November 7 09:53:18 2013

Copyright (c) 1982,201 3, Oracle and/or its affiliates. All rights reserved.

Connected to the target database: TESTM (DBID = 1234105814)
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-00554: Internal recovery manager package initialization failed
RMAN-04006: Error from secondary Database: ORA-12528: TNS: Listener: no new connection is allowed for all applicable routines

Cause Analysis of the above situation: Because the standby database instance is in the nomount status, if the listener is dynamically registered, the listener will not be registered in the nomount status, so you need to configure static registration.

Solution: Configure static listening. The tnsnames. ora of the master database is as follows:

# Connection string pointing to the slave Database
TESTS =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = 188.188.3.20) (PORT = 1521 ))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = TESTM)
)
)

Add:

# Add static registration for the standby Database
SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = TESTM) (ORACLE_HOME =/oracle/product/12.1.0 )))
$ Lsnrctl reload & nbsp; // reload listener. ora
$ Lsnrctl status // view the status

Oracle @ Sol_ORA:/oracle/12.1/network/admin $ rman target sys/test @ TESTM auxiliary sys/test @ TESTS // troubleshooting of master database connection

Recovery MANAGER: Release 12.1.0.1.0-Production on Thursday November 7 10:00:02 2013

Copyright (c) 1982,201 3, Oracle and/or its affiliates. All rights reserved.

Connected to the target database: TESTM (DBID = 1234105814)
Connected to the secondary Database: TESTM (not loaded)
2. RMAN-06136: ORACLE error from secondary Database: ORA-19847: unable to read control file headers from remote site
Cause: Unknown

Solution: disconnect all standby databases outside the RMAN of the master database

3. RMAN-06136: ORACLE error from the secondary Database: ORA-01013: user request to cancel the current operation, because duplicate on the standby database there is a user login, after logging out error resolution

Cause: Unknown

Solution: disconnect all standby databases outside the RMAN of the master database

Recommended reading:

Basic Oracle tutorial-copying a database through RMAN

Reference for RMAN backup policy formulation

RMAN backup learning notes

Oracle Database Backup encryption RMAN Encryption