Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Primary and Standby, RMAN errors 8137 and 8591

christian41936Jun 11 2012 — edited Jun 12 2012
Hello,

I have to resolve a serious problem of synchronization of two databases, one primary and one standby.

I receive on the RMAN scripts these two errors : RMAN 8137 and RMAN 8591. I well know what these errors mean. The archivelogs were not sent on the standby, and so they are still needed, and not deleted.

I have tried to follow the Oracle procedure of database synchronization (document 836986.1), but without success, as the archivelogs are still needed.

Here is (a part of) the debug trace when I send the delete input command on the primary:

DBGSQL: EXEC SQL AT TARGET begin dbms_rcvman . getRequiredSCN ( reqscn => :safescn:safescn_i , rlgscn => :reqrlgscn:reqrlgscn_i ) ; end ; [15:39:43.190]
DBGSQL: sqlcode=0 [15:39:44.174]
DBGSQL: :b1 = 1444336744
DBGSQL: :b3 = 380426159
DBGRCVMAN: ENTERING getRequiredSCN
DBGRCVMAN: this_cftype=CURRENT
DBGRCVMAN: ENTERING getAppliedSCN, alldest=0
DBGRCVMAN: ENTERING anyRemoteDestinations
DBGRCVMAN: no_target = 0
DBGRCVMAN: EXITING anyRemoteDestinations anyRemoteDestinations - target=
DBGRCVMAN: EXITING getAppliedSCN, alldest=0 getAppliedSCN - appscn=,rlgscn=
DBGRCVMAN: Got dest = 2, thread=1,sequence=16675,next_change=1206438636,applied=YES,resetlogs_change=380426159
DBGRCVMAN: gap_scn=,high_scn=,possible_gap=

BGRCVMAN: Got dest = 2, thread=1,sequence=20830,next_change=1430809158,applied=YES,resetlogs_change=380426159
DBGRCVMAN: gap_scn=,high_scn=,possible_gap=
DBGRCVMAN: Got dest = 2, thread=1,sequence=20852,next_change=1431558961,applied=NO,resetlogs_change=380426159
DBGRCVMAN: gap_scn=,high_scn=,possible_gap=

DBGRCVMAN: Got dest = 2, thread=1,sequence=21328,next_change=1454979735,applied=NO,resetlogs_change=380426159
DBGRCVMAN: gap_scn=,high_scn=,possible_gap=1444336744
DBGRCVMAN: Got dest = 11, thread=1,sequence=1,next_change=1,applied=,resetlogs_change=0
DBGRCVMAN: gap_scn=1444336744,high_scn=1454979735,possible_gap=
DBGRCVMAN: USE gap_scn:reqscn=1444336744,rlgscn=380426159
DBGRCVMAN: EXITING getRequiredSCN getRequiredSCN - reqscn=1444336744,rlgscn=380426159 ==> 444336744

Since sequence 20852, the archivelogs are not known on the standby.
The first archivelog on the primary that is still there is the sequence 21095.

Here is the rman configuration:
RMAN> show all;

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\S
NCFBDSIVOA.ORA'; # default

I have tried several times to do incremental backup on the primary, apply it on the standby, but it never worked, except for the current_scn which changed on the standby. The archivelogs are still needed on the primary, unfortunately.

What could I do next?
Starting a new incremental backup starting with sequence 20852?
Deleting by force all the archivelogs? And in that case what to do for the standby?
Starting a new incremental backup taking the current scn of the standby?

Edited by: Christian on Jun 10, 2012 11:46 PM
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 10 2012
Added on Jun 11 2012
16 comments
3,012 views