Data Guard :: RMAN Refuses To Delete Old Archivelog
Apr 10, 2013
We have two Windows 2008 VMs with Oracle 11G configured as primary and standby.This configuration has been defined by a partner who is no longer working for us.We have broken the correct application of the redo log on the standby when we have not correctly restored some snapshots on those two VMs.I would like to create a new Oracle server that will become the new standby. For that, I need too :
- Display the full dataguard configuration to reproduce it on the new server
- Stop (delete ?) the configuration on the primary server.
We also have the current problem that RMAN refuses to delete old archivelog since they have not been applied to the standby.
How to make the automatic deletion of all the archivelogs when it is applied successfully on the standby database? We have 1 primary database and 1 standby database using oracle physical dataguard.
In the primary database, we have daily backup job so that the applied archivelogs are deleted automatically, no problem
But in the standby database ( physical standby) I have to go there and delete manually because I don't issue backup on this database. Is there any solution for this problem.
I have a standby database in which I am backing up my database from. I also backup my archivelogs on my primary site as well as the control file. My issue is that I cannot find the correct RMAN command that will allow me to delete the actual backupsets from disk after say 7 days.
I know how to delete automatically the actual archivelog files, but not how to only have 7 days of archivelog backupsets available at any one given time.
Oracle 10gR2 on 64-bit RHEL.Backup Strategy:There will be a level-0 backup of the database every Sunday and level-1 every weekday.Archivelogs will be backed up up every 30 minutes.
Q: How can I delete ALL the archivelog backups that were taken that day (every 30 minutes) right after successful completion of level-0 or level-1 backup?
I want to delete them because they may not be of any use after the level-0 or level-1 backup (am I right)?
If I want to take Rman archive log backup with delete input command , how the archive logs will be copied to standby database
For eg
I am taking archive backup as
RMAN>backup archivelog all delete input;
here consider few archives are not copied to standby database (due to nw issue) then how standby will receives these missing archives as those are deleted by rman backup at primary side.
I am not getting any document related to above query.
the data guard configuration is left as it is, i.e.
cta: physical standby ctastd: primary
I discover the following findings in the alertcta.log, i.e. in cta database,
Primary database is in MAXIMUM PERFORMANCE mode RFS[8]: Successfully opened standby log 4: 'D:ORA102CTAREDO04.LOG' Thu Sep 01 10:38:08 2011 Errors in file d:ora102ctaudumpcta_rfs_536.trc: ORA-16401: archivelog rejected by RFS
Quote:
ORA-16401: archivelog rejected by RFS
Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.
Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.
it seems to be that there are multiple primary database, but it is not based on the information from v$database.Right now the physical standby database cannot received any archive logs from the primary.I've checked the database_role in both servers, they are as they are designated.
from the physical standby database
SYS@cta>select db_unique_name, database_role, switchover_status from v$database; DB_UNIQUE_NAME DATABASE_ROLE SWITCHOVER_STATUS ------------------------------ ---------------- -------------------- CTA PHYSICAL STANDBY NOT ALLOWED SYS@cta>alter database recover managed standby database disconnect from session
[code]....
the standby is always busy, i.e. SESSIONS ACTIVE. i.e make sure the archived logs are shipped and apply over to physical standby.
I created a standby database yesterday and everything is working correctly. I need to make some tweaks, however, and one of those is the directory that the standby database expects the archivelogs to be.
I found that the archivelogs were being shipped to $ORACLE_HOME/dbs and named arch*.arc. Interestingly a log switch ships the archivelog minus the "arch" at the front and all archivelogs now do not have that format. I moved the archivelogs to the correct location and renamed them. I have been able to set the correct location using standby_archive_dest and can see that the archivelogs are shipped to there.
Also, v$archived_log shows the correct path and filename. The problem I have is that when I come to apply the archivelogs it still seems to think that they should be in $ORACLE_HOME/dbs and named with "arch" at the front. what parameter I need to change to tell oracle the correct path and filename to use when applying the archivelogs?
I have a DR setup with the following configuration
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; 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; 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 STANDBY
I dont want to backup the STDBY DB but I want the ARC files to be removed when applied so my flash area does not fill up. Is there some command(rman or not) that can fire off this policy?
I am creating physical standby database through Rman duplicate command from 2 node rac cluster. rman do all its work. now am try to start the mrp process on physical standby database. I am getting following errors
------------------------------------------------------------ Check that the primary and standby are using a password file and remote_login_passwordfile is set to SHARED or EXCLUSIVE, and that the SYS password is same in the password files. returning error ORA-16191 ------------------------------------------------------------ ORA-16191: Primary log shipping client not logged on standby ------------------------------------------------------------
I copied the same pass file from primary to standby and many times verify the same but i got the same error.
We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
On next month i will have plan to delete history data on my Primary database, but i still want to keep them in logical standby as the data warehouse. So, how can i skip delete statement from primary database apply to logical standby.
Oracle SQL apply only support for Skip DML but not for keep delete statement
(on 10g and 11g)SQL>exec dbms_logstdby.skip(statement => 'DELETE',schema_name => 'SCOTT', object_name => 'DEPT');BEGIN dbms_logstdby.skip(statement => 'DELETE',schema_name => 'SCOTT', object_name => 'DEPT'); END; *ERROR at line 1:ORA-06550: line 1, column 7:PLS-00306: wrong number or types of arguments in call to 'SKIP'ORA-06550: line 1, column 7:PL/SQL:
I have been trying to do a once off backup of an oracle database. I have followed instructions to do standard backups and when actually running the RMAN backup I got a ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode.
No problem: I read that you need to execute the following commands in RMAN to ensure a clean shutdown/startup of the database to get past this problem: run {shutdown immediate;startup mount, etc } ...problem is - this code shuts down the database and then I cannot restart it using startup mount as it starts with this TNS listener errors. So I have restart through services but then I get the NOARCHIVELOG error cropping up again.
I'm getting quite frustrated with this. I don't need an archive/redo log - I just need the current state (snapshot) of the database with all the datafiles / procedures/functions in it...a once off - but I can't seem to get this working.
i have changed the log_archive_dest_1 to another drive (suppose D ) than Oracle installed disk
created tables in scott , alter system switch logfile;
so archive log was der in the new destination i delete that archivelog from D and pasted to drive E ( cut paste ) start rman , crosschecked archivelogs Now , i want to tell Rman that recover that archivelog from E and then recover
I am trying to create the Standby database using RMAN.
I have first created an auxiliary instance followed by the password file for the instance and the registering it it listener.
Below are the parameters of the pfile of the standby database and followed by the command issued at the RMAN prompt.
PFILE parameters [STANDBY] orcl.__db_cache_size=293601280 orcl.__java_pool_size=8388608 orcl.__large_pool_size=8388608 orcl.__oracle_base='F:appdsharma'#ORACLE_BASE set from environment
Can i setup physical standby without RMAN? I want to create a fresh single physical standby without RMAN .. If i copy all files in another system and take the controlfile from primary as alter database create controlfile for standby ... and fill all the gaps with archives.. Should it work ? i am on 10G Rhel 4 linux.. and both machines would have same config
We have EM (Cloud 12c) initiated scheduled backup jobs that perform (all below are online backups, obviously archivelog mode)
- level 0 Incremental 3AM on Sunday - with options backup all archive logs, delete input, delete obsolete
- level 1 Incremental (non cumulative) 3AM every other day - same options
Recovery window is set to 3 days, other options below:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 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 BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
[code]....
Everything appears to be working normally (archive logs are being backed up and once they are the archive logs themselves are being deleted from the FRA), but I'm having some trouble understanding the behavior of the delete obsolete.
With a recovery window of 3 days, on Monday at 11AM my expectation would be that I would find in backups the following:
- level 0s from day before (Sunday) and the previous Sunday (8 days prior)
- all level 1s from previous Sunday on (so Mon-Sat and this morning)
- archivelog backups from Friday until this morning
What I'm not understanding is that I'm seeing archivelog backups from last Monday, Tuesday, etc. - i would have thought these would have gone obsolete based on my recovery window, yet when I run report obsolete in RMAN nothing is showing up.
Here we have a dataguard environment with db1 as primary and db2 as physical standby database. We configured dataguard in 10g environments and we are not using grid control. What are the steps for configuring rman for incremental backups in this environment?
We want to schedule the backups to be taken in standby db, (that is applicable in case of switchover too). In the case of switchover to db2 what all do we need to do in rman manually to resume backups in db1?
I have One Production and one logical standby database . Due to tape problem we are unable to take backups of primary . And due to business , we cannot take back up on disk in hot period(Bank database ) .
If i take logical standby database backup(level 0 ) using RMAN , then will i be able to restore it on production dtbs (In case Production down) ? . Logical standby is in sync with primary .
Got Active DataGuard on a primary database, quite nicely sending its archive logs to its secondary. I can quite happily use the Broker and switchover between them.
Now if I take RMAN backups of the primary database, if I have to failover to the secondary, I'm gonna loose all those backups.
Well, I can restore the whole database to the backup, cos I can restore the control file, from the backuip and therefore I can restore the whole db.
But if I want to restore to a tablespace, I wont be able to , cos the db_unique_names names are different, and the DB ID's will be different.
Same goes if I use a recovery catalog....
so how do I failover/switchover without loosing my previous rman backups ??
RMAN-03009: failure of backup command on t1 channel at 12/15/2012 06:15:11 RMAN-10015: error compiling PL/SQL program RMAN-10033: error during compilation of job step 2: ORA-00603: ORACLE server session terminated by fatal error ORA-04030: out of process memory when trying to allocate 400 bytes (PL/SQL DIANA,LISIMA: Add cells)
We received the above error message after the following event:
rman failed to backup because archivelog destination was out of space
We moved SOME of the archivelog file manually using operating system command mv to another location so that our application can run first.When the engineers restarted the rman to backup, we receive the above error.
I'm on a Windows server 2003 R2 64 bit, database is 11.1.0.7. From RMAN connected to the target and the catalog, this is a show all;
RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:oracleadmin
[code]....
I'm running incremental backups, a level 0 on sunday and a level 1 the other days of the week, this is the ctl file:
LEVEL 0: connect target /@ORCL connect catalog rman/rmanpw@rmancat RUN {
[code]....
The level 0 does delete the archive logs (because of the delete input). Each backupset has two copies of the archive logs (which is what I want), and I expected the logs to be deleted after being backed up 2 days (each day is twice, 2 days = 4 times). But it's not deleting the logs, even after 6 runs.
am trying to run rman backup plus archivelog TO tape disk my rman configuration settings are as seen below
RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 2; CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; [code].....
get the following error when i do this, RMAN-03009: failure of backup command on C3 channel at 01/03/2013 11:33:45 ORA-00600: internal error code, arguments: [ksfdfetch1], [], [], [], [], [], [],
creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0) Operating System:Linux 5 Error: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52 RMAN-03015: error occurred in stored script Memory Script RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor [code]....
provide any work arounds to proceed further in creating the standby database.
