This post applies to 12c and 19c as well, it introduced two popular ways for creating a standby database: RMAN DUPLICATE and from primary database backup
This post demonstrates how to build an Oracle 18c physical standby database managed by data guard. The method should also apply to 12c and 19c as well.
Read more of this content when you subscribe today.
Read more of this content when you subscribe today.
Read more of this content when you subscribe today.
In 11g, duplicate a standby database from active database with “RMAN-05001” error:
RMAN> run {
duplicate target database for standby from active database;
}
RMAN-05001: auxiliary file name /u02/oradata/TESTDBSTY/sysaux01.dbf
conflicts with a file used by the target database
The issue is a bug, it seems the file system for both primary and standby database are the same, though “db_file_name_convert” and “log_file_name_convert” are configured already.
Add “NOFILENAMECHECK” option into duplicate RMAN command:
RMAN> run
{
duplicate target database for standby
from active database nofilenamecheck;
}
This issue does not happen on 12c, so it seems a bug for 11g.
While run RMAN “duplicate target database for standby from active database nofilenamecheck” in 11g database, then got below errors:
... .. . set newname for datafile 3 to "/u02/oradata/TESTDBSTY/undotbs01.dbf"; ... .. . channel ORA_DISK_1: starting datafile copy input datafile file number=00003 name=/u02/oradata/TESTDB/undotbs01.dbf RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/15/2019 15:53:17 ORA-17628: Oracle error 19505 returned by remote Oracle server continuing other job steps, job failed will not be re-run ... .. .
Read more of this content when you subscribe today.
Make DBA Life Easy 