Report Obsolete And Delete Obsolete Commands In RMAN
Sep 9, 2012
I am getting the below error while executing "report obsolete" and "delete obsolete " commands in RMAN. except these two all the RMAN commands are working fine like "list backup summary" "list backup" .....
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 08/28/2012 11:03:04
RMAN-06004: ORACLE error from recovery catalog database: ORA-01403: no data found
OS: IBM AIX
Oracle Version: 9.2.0.8
I am working on Oracle 10g Rel 2. I am unable to delete the OBSOLETE from rman
previously my senior use to take backup on remote m/c.
While giving the command
rman>delete obsolete
RMAN-06207: WARNING: 228 objects could not be deleted for DISK channel(s) due RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status RMAN-06210: List of Mismatched objects RMAN-06211: ========================== RMAN-06212: Object Type Filename/Handle RMAN-06213: --------------- --------------------------------------------------- RMAN-06214: Backup Piece \192.168.1.162BACKUPFINPRODDB_T619092194_S12_P1 RMAN-06214: Backup Piece \192.168.1.162BACKUPFINPRODDB_T619093015_S13_P1
I've created a small script witch delete the obsolete and expired backups of RMAN.
The problem is: the "delete obsolete" and the "delete expired backup" command needs a confirmation with YES. I don't need to confirm the command and he deletes the backups directly?
Here is my little script:
#!/bin/ksh export ORACLE_SID=dbtest2 export ORACLE_HOME=/home/oracle/srv/ora/product/11.2.0/dbtest_2 export ORACLE_BIN=/home/oracle/srv/ora/product/11.2.0/dbtest_2/bin alias RMAN=$ORACLE_BIN/rman
I have a problem in running delete obsolete or report obsolete using rman. Although the retention policy is set to "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS;", when running delete obsolete or report obsolete it deletes or returns all the backupsets till sysdate. What should I do to solve this issue?
I am trying to delete the backupset using Delete Obsolete command, but i am unable to get the success. As per the oracle Doc after completion of Retention Period oracle automatically deletes the backupset. I have set the retention period of 8 days.
Environment: 2 Node Oracle(10.2.0.4.0) RAC on Aix 6.1.
Backups using RMAN utility.Our system is configured to take backups on Tape library using TSM server.
We take incremental level 1 backup on all days and Level 0 backup on Wednesday.We would like to keep the RMAN retention period of 14 days.I delete the backups that are 7 days old from the disk to save space and 14 days older backup from Tape.
I am getting below error in my RMAN backup logfiles.Also attached
RMAN-06207: WARNING: 147 objects could not be deleted for DISK channel(s) due RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status RMAN-06210: List of Mismatched objects RMAN-06211: ========================== RMAN-06212: Object Type Filename/Handle RMAN-06213: --------------- ---------------------------------------------------
The configuration of RMAN is:
RMAN> show all; RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS; CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; CONFIGURE CONTROLFILE AUTOBACKUP ON;
[code].....
How to avoid this error ? Can we set "Retention period" as 14 days in RMAN level and delete the backups in disk which is older than 7 days?Should the deletion of tape backup be handled in TSM level ?
We observed that our RMAN backup was taking more time to complete. CROSSCHECK is the main culprit as because of having data in the catalog for more than 3 years.
So in the part of script we added delte obsolete recovery windoe of 14 days. (Redundancey 1).
Here the problem is we are getting error as
RMAN-03002 - failure of delete command RMAN-06091 - NO channel allocated for maintenance (of an appropriate type).
Reason: Till 2 years back the backup was stored in tape and after that it got changed to disk. So allocating channel disk to delete obsolet is not working. How we can over come this.
We tried like allocating channel tape sbt_type. It got failed as no media manager information configured. We dont have that information.
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.
- level 1 for datafile not backed up since 'sysdate-1' then another policy makes:
- level 0 when the datafiles become read only
The recovery windows is set to 1 day.
In the following situation:
RMAN> list backup of datafile 394;
List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 12721 Incr 0 13.25M SBT_TAPE 00:01:13 25-MAY-11 BP Key: 12777 Status: AVAILABLE Compressed: NO Tag: ST_TRONLINE_FB20110525 Handle: bk_13201_1_752082473 Media: A00003
[code]....
I expect that the first L0 backup is going to become obsolete, but even if I run crosscheck, it never become obsolete.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options ******************************************************************************** SYS AS SYSDBA in MyDB....> startup ******************************************************************************** ORA-32004: obsolete and/or deprecated parameter(s) specified ORACLE instance started.
Total System Global Area 612368384 bytes Fixed Size 1250428 bytes Variable Size 121637764 bytes Database Buffers 482344960 bytes Redo Buffers 7135232 bytes Database mounted. Database opened.
SYS AS SYSDBA in MyDB....> ******************************************************************************** PFILE.ORA ******************************************************************************** *.db_name='MYDB' *.db_unique_name='MYDB'
note in our database we changed RMAN backup to redundancy 7.
RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 7; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default 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 NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_mscmada.f'; # default
Also we have scheduled in our dailly backup to delete obsolete backup means to delete backup which completed more that 7 times, but when we check our backup still in our disk for 1 Month.Note we have scheduled to delete obsolete backup dailly.
I have set the RETENTION POLICY TO RECOVERY WINDOW Values to 2 days,but my backup sets which backuped before 2 days(30-NOV-11),and the backup set is avaliable also,i think it must be expired or obsolete,why?
RMAN> show all; RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
I have a RUN file within a script to duplicate a database. As part of this RUN file I also run the command configure controlfile autobackup off; as part of this RUN file. However, this command has turned off backup of the control file on the AUXILLARY database (i.e. production) as well as the TARGET database (test). Is this supposed to happen?
My run file is:
rman TARGET sys/XXXX@${DB}-SOURCE AUXILIARY / RUN { allocate AUXILIARY channel a1 type disk; allocate AUXILIARY channel a2 type disk; allocate AUXILIARY channel a3 type disk; allocate AUXILIARY channel a4 type disk;
if I run below rman command lines in 10g and 11g RMAN, it works well, but NOT in RMAN (Release 8.1.7.4.0), so which commandlines I should use to get to the same pursposes in RMAN 8.1.7.4?
run { ALLOCATE CHANNEL c1 TYPE 'sbt_tape'; ALLOCATE CHANNEL c2 TYPE 'sbt_tape'; ALLOCATE CHANNEL c3 TYPE 'sbt_tape';
I am trying to remove archive log file on my standby site but I am getting the following message. There are lots of archive logs are present on the storage but rman is unable to displaying that.
RMAN> list archivelog all;
specification does not match any archived log in the repositoryRMAN>
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.
I deleted all my RMAN backup with delete backup command .but when i run query on v$rman_backup_job_details, show information, i don't know that v$rman_backup_job_details read data from where? and how to delete complete that v$rman_backup_job_details don't show any thing?
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)?
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.
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.
I am not familiar with form with report in APEX. I have a lot of forms with reports that was created before, but they have only create buttons. Now I need to add edit and delete buttons. I wish I do not have to recreate forms with reports. But when I tried to add delete function by comparing a form with delete button created by APEX, but it does not work. the delete button does not react at all.
setting is as follows:
button style: template based button button template: Button button type: normal action: redirect to URL execute validation: NO URL target: javascript:apex.confirm(htmldb_delete_message,'DELETE'); database action: SQL delete action condition type: value of item / column in expression1 is not null expression1: P2172_ALIAS_ID
I also enable the delete in the process of :"Process Row of SOR_ALIAS"
If I set action of delete button as submit page, I can delete the row, but no standard popup warning,
We run rman backups every night (level 0 on weekend, level 1 other 6 days). Backups are running fine. The problem I'm having is we also have a OEM report that runs morning to report on the status of those backups. For some reason, the status of the OEM database is always "RUNNING", everything else is "COMPLETED". This is the sql that is being run:
SELECT DB_NAME, STATUS, START_TIME, END_TIME FROM RMAN.RC_RMAN_STATUS where start_time between sysdate - 1 and sysdate and operation = 'RMAN' order by db_name, start_time desc;
The status reports runs at 7AM and all the backups run between noon and midnight, this is the output from the sql:
