| RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process archiv [message #646937] |
Fri, 15 January 2016 01:27  |
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
|
Senior Member |
|
|
Dear All,
we have below script for taking archivelog backup, format is mentioned on the disk location.
run {
allocate channel c1 type disk;
allocate channel c2 type disk;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup as compressed backupset archivelog all delete input format '/backup/RMAN/testdb/testdb_Archbkp0_%U_%t_%T.arc' ;
release channel c1;
release channel c2;
}
while executing this script, we are getting below error -
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/log/arch/TESTDB/1_60622_886260234.dbf thread=1 sequence=60622
Below are the configuration done at pfile.
*.log_archive_config='DG_CONFIG=(MAGMADB,MAGMADBSTDBY)'
*.log_archive_dest_1='LOCATION=/log/arch/MAGMADB VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MAGMADB'
*.log_archive_dest_2='SERVICE=MAGMADBSTDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MAGMADBSTDBY'
*.log_archive_dest_state_2='DEFER'
This production database was configure with standby but recently parameter for standby service is marked as defer.
Still, standby db_config is configured.
Please let us know how to rectify the issue. It was working fine before the configuration done.
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name TESTDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 5 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED;
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 NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/database/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_TESTDB.f'; # default
Regards,
Ashish Kumar Mahanta
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process archiv [message #647016 is a reply to message #647001] |
Mon, 18 January 2016 05:59  |
 |
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
Again,
OP has asked for it by using "defer" option.
quoting docs
Quote:
defer
Specifies that valid destination information and attributes are preserved, but the destination is excluded from archiving operations until re-enabled.
Quote:The archived redo log deletion policy is configured to NONE by default. In this case, RMAN considers archived redo log files in the recovery area as eligible for deletion if they meet both of the following conditions:
The archived redo logs, whether in the flash recovery area or outside of it, have been transferred to the required remote destinations specified by LOG_ARCHIVE_DEST_n.
The archived redo logs have been backed up at least once to disk or SBT or the logs are obsolete according to the backup retention policy.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
