I got a few data corruptions in a test db when I performed a duplicate from a production db where a few tables have the nologging option.
Oracle support suggested to turn on the force logging option when perform a duplicate. I wish that i do not have to change the production settings in order to make a duplicate db in Test.
Any suggestions to prevent data block corruption in the target db from my next duplicate?
ORA-01110: data file 14: '+DATA/xxxxx/datafile/xxxxx01_02.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
Errors in file /xxxxx/app/oracle/diag/rdbms/xxxxx/xxxxx/trace/xxxxx_j000_67043338.trc (incident=1426036):
ORA-01578: ORACLE data block corrupted (file # 15, block # 27467)
ORA-01110: data file 15: '+DATA/xxxxx/datafile/xxxxx01_03.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
Errors in file /xxxxx/app/oracle/diag/rdbms/xxxxx/xxxxx/trace/xxxxx_j000_67043338.trc (incident=1426037):
ORA-01578: ORACLE data block corrupted (file # 15, block # 27019)
ORA-01110: data file 15: '+DATA/xxxxx/datafile/xxxxx01_03.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
Errors in file /xxxxx/app/oracle/diag/rdbms/xxxxx/xxxxx/trace/xxxxx_j000_67043338.trc (incident=1426038):
ORA-01578: ORACLE data block corrupted (file # 15, block # 27883)
ORA-01110: data file 15: '+DATA/xxxxx/datafile/xxxxx01_03.dbf'
Oracle enterprise version 11.2.0.3. Here is the rman script:
SPOOL LOG to '/home/oracle/scripts/REFRESH/target_db_duplicate.150601_1019.log'
run {
allocate channel D1 type sbt_tape;
allocate auxiliary channel T1 type sbt_tape
parms='ENV=(NB_ORA_CLIENT=server_name,NB_ORA_COPY_NUMBER=3)';
set until time="to_date('01-JUN-2015 02:00:00','DD-MON-YYYY HH24:MI:SS')";
duplicate target database to target_db
pfile=$ORACLE_HOME/dbs/inittarget_db.ora
nofilenamecheck;
}
SPOOL LOG OFF;
