OraFAQ Forum: Data Guard » RMAN and Dataguard

Home » Server Options » Data Guard » RMAN and Dataguard (Oracle 11.2.0.3.0, RHEL 5.8)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

RMAN and Dataguard [message #670440]

Wed, 04 July 2018 11:58

dirish
Messages: 232
Registered: November 2006

Senior Member

on both primary and standby sites - i have in RMAN > CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

but archivelogs are not being deleted on the primary site

when i try to delete from RMAN
RMAN> delete noprompt archivelog until time 'SYSDATE-5';

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=2836 device type=DISK
RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
archived log file name=/ilarch1/archive/CI/CI2_37118_826186736.arc thread=2 sequence=37118

SQL> select max(sequence#) from v$archived_log where applied='YES';

MAX(SEQUENCE#)
--------------
37154

SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /ilarch1/archive/CI/CI
Oldest online log sequence 37153
Next log sequence to archive 37155
Current log sequence 37155

please help

Report message to a moderator

Re: RMAN and Dataguard [message #670441 is a reply to message #670440]

Wed, 04 July 2018 12:01

John Watson
Messages: 8976
Registered: January 2010
Location: Global Village

Senior Member

rm the file, then crosscheck and delete expired archivelog.

Report message to a moderator

Re: RMAN and Dataguard [message #670442 is a reply to message #670440]

Wed, 04 July 2018 12:05

dirish
Messages: 232
Registered: November 2006

Senior Member

INST_ID PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
---------- --------- ------------ ---------- ---------- ---------- ----------
1 ARCH CLOSING 2 37147 497664 991
1 ARCH CLOSING 2 37148 157696 261
1 ARCH CLOSING 2 37149 4620288 1891
1 ARCH CLOSING 2 37150 172032 766
1 ARCH CLOSING 2 37151 67584 1147
1 ARCH CLOSING 2 37141 131072 2048
1 ARCH CLOSING 2 37152 1638400 960
1 ARCH CLOSING 2 37153 1 74
1 MRP0 WAIT_FOR_LOG 2 37155 0 0
1 RFS IDLE 0 0 0 0
1 RFS IDLE 2 37155 802763 1

INST_ID PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
---------- --------- ------------ ---------- ---------- ---------- ----------
1 RFS IDLE 0 0 0 0

Report message to a moderator

Re: RMAN and Dataguard [message #670443 is a reply to message #670441]

Wed, 04 July 2018 12:06

dirish
Messages: 232
Registered: November 2006

Senior Member

you mean to manually delete the applied archives and do the crosscheck, etc?

Report message to a moderator

Re: RMAN and Dataguard [message #670444 is a reply to message #670443]

Wed, 04 July 2018 12:11

dirish
Messages: 232
Registered: November 2006

Senior Member

RMAN> delete noprompt expired archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=5652 device type=DISK
specification does not match any archived log in the repository

Report message to a moderator

Re: RMAN and Dataguard [message #670445 is a reply to message #670444]

Wed, 04 July 2018 12:12

dirish
Messages: 232
Registered: November 2006

Senior Member

From PRIMARY

RMAN> show all;

RMAN configuration parameters for database with db_unique_name CI are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oldbackup/rmanbkup/comptel/CI2/%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/products/11.2.0/dbs/snapcf_CI2.f'; # default

Report message to a moderator

Re: RMAN and Dataguard [message #670446 is a reply to message #670445]

Wed, 04 July 2018 12:13

dirish
Messages: 232
Registered: November 2006

Senior Member

From STANDBY

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name CISTBY are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
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 '/oldbackup/rmanbkup/comptel/CI2/%F';
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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/products/11.2.0_2/11.2.0/dbs/snapcf_CISTBY.f'; # default

Report message to a moderator

Re: RMAN and Dataguard [message #670447 is a reply to message #670444]

Wed, 04 July 2018 12:48

John Watson
Messages: 8976
Registered: January 2010
Location: Global Village

Senior Member

dirish wrote on Wed, 04 July 2018 18:11

RMAN> delete noprompt expired archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=5652 device type=DISK
specification does not match any archived log in the repository

I've already told you what to do. You have missed out the first two steps.

Report message to a moderator

Re: RMAN and Dataguard [message #670448 is a reply to message #670440]

Wed, 04 July 2018 12:54

Michel Cadot
Messages: 68757
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Please read How to use [code] tags and make your code easier to read.

Report message to a moderator

Re: RMAN and Dataguard [message #670449 is a reply to message #670448]

Wed, 04 July 2018 13:06

dirish
Messages: 232
Registered: November 2006

Senior Member

Thanks, John, i have manually deleted all the applied applied archives, crosscheck and delete expired.

I will monitor and give you feedback. Thanks

Report message to a moderator

Re: RMAN and Dataguard [message #670450 is a reply to message #670449]

Wed, 04 July 2018 13:11

John Watson
Messages: 8976
Registered: January 2010
Location: Global Village

Senior Member

Oh dear. Did I say to delete all the applied archivelogs? No. I said to delete the file that was not applied. Well, your database will survive. As for you in your present job, that remains to be seen.

Report message to a moderator

Re: RMAN and Dataguard [message #670451 is a reply to message #670450]

Wed, 04 July 2018 13:14

dirish
Messages: 232
Registered: November 2006

Senior Member

In fact, i only moved the archives to a new directory.

Report message to a moderator

Previous Topic:	Impact and risk during data guard implementation
Next Topic:	RAC - DG

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 03 18:44:55 CDT 2025