Archive

Posts Tagged ‘Standby Database’

ORA-00308: cannot open archived log ‘+SG_DG’

July 5, 2011 Leave a comment

I create standby database in ASM diskhgroup. Once I start recovering the standby database, the message below reported.

SQL>  recover standby database;
ORA-00279: change 5585696618 generated at 07/05/2011 17:11:24 needed for thread 1
ORA-00289: suggestion : +SG_DG
ORA-00280: change 5585696618 for thread 1 is in sequence #41151
ORA-00308: cannot open archived log ‘+SG_DG’
ORA-17503: ksfdopn:2 Failed to open file +SG_DG
ORA-15045: ASM file name ‘+SG_DG’ is not in reference form

Check with oracle support ,  the note (ID 341591.1) shows that it was caused in-correct initial parameter settings.

RMAN-06136 On Duplicate Database for Standby with OMF and ASM [ID 341591.1]

Parameters not set correctly.

To perform the duplicate with OMF and ASM, you must have the following parameters:
db_file_name_convert – if appropriate
db_unique_name – must be set to a name different from primary db_unique_name.
standby_file_management – must set to AUTO
db_create_file_dest – must be set

Finally I found that the parameter standby_file_management was not set. I set it again. The problem was fixed.

SQL> alter system set standby_file_management=auto;

System altered.

SQL> recover standby database;
ORA-00279: change 5585696618 generated at 07/05/2011 17:11:24 needed for thread 1
ORA-00289: suggestion :
+SG_DG/vstbqa/archivelog/2011_07_05/thread_1_seq_41151.1474.755718357
ORA-00280: change 5585696618 for thread 1 is in sequence #41151

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

ORA-00279: change 5585699383 generated at 07/05/2011 17:50:53 needed for thread 1
ORA-00289: suggestion : +SG_DG
ORA-00280: change 5585699383 for thread 1 is in sequence #41152
ORA-00278: log file
‘+SG_DG/vstbqa/archivelog/2011_07_05/thread_1_seq_41151.1474.755718357’ no
longer needed for this recovery