RMAN DELETE EXPIRED

Does anybody could explain difference between DELETE OBSOLETE command and DELETE EXPIRED
The way I uderstand DELETE OBSOLETE would delete physical backupsets and catalog records for them if it beyond retention policy. But what is DELETE EXPIRED does? Does it delete physical backupset files or only catalog records?

http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1007.htm#sthref279
To quote the propaganda:
The term obsolete does not mean the same as expired. A backup is obsolete when REPORT OBSOLETE or DELETE OBSOLETE determines, based on the user-defined retention policy, that it is not needed for recovery. A backup is considered expired only when RMAN performs a crosscheck and cannot find the file. In short, obsolete means "not needed," whereas expired means "not found."

Similar Messages

Deleting expired backup not working.

Hi,
I am cleaning up the backup by deleting all the expired backups. My OS is RHEL 4 and DB is 10.2.0.3 and the backup is Veritas Netbackup using RMAN
Recovery Manager: Release 10.2.0.3.0 - Production on Mon Mar 28 12:51:16 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: WHSEPROD (DBID=2974933951)
connected to recovery catalog database
RMAN> delete expired backup;
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=136 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Veritas NetBackup for Oracle - Release 6.5 (2007072400)
allocated channel: ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_2: sid=145 devtype=SBT_TAPE
channel ORA_SBT_TAPE_2: Veritas NetBackup for Oracle - Release 6.5 (2007072400)
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=181 devtype=DISK
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
255513 255464 1   1   EXPIRED     SBT_TAPE    arch-s254-p1-t662126514
484866 484825 1   1   EXPIRED     SBT_TAPE    arch-s5711-p1-t680801187
1256712 1256637 1   1   EXPIRED     SBT_TAPE    arch-s257-p1-t724703694
1433633 1433540 1   1   EXPIRED     SBT_TAPE    arch-s5681-p1-t733340847
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=arch-s254-p1-t662126514 recid=254 stamp=662126515
deleted backup piece
backup piece handle=arch-s5711-p1-t680801187 recid=5674 stamp=680801188
deleted backup piece
backup piece handle=arch-s257-p1-t724703694 recid=254 stamp=724703695
deleted backup piece
backup piece handle=arch-s5681-p1-t733340847 recid=5674 stamp=733340848
Deleted 4 EXPIRED objects
RMAN> delete expired backup;
using channel ORA_SBT_TAPE_1
using channel ORA_SBT_TAPE_2
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
255513 255464 1   1   EXPIRED     SBT_TAPE    arch-s254-p1-t662126514
484866 484825 1   1   EXPIRED     SBT_TAPE    arch-s5711-p1-t680801187
1256712 1256637 1   1   EXPIRED     SBT_TAPE    arch-s257-p1-t724703694
1433633 1433540 1   1   EXPIRED     SBT_TAPE    arch-s5681-p1-t733340847
Do you really want to delete the above objects (enter YES or NO)?Even after it says it deleted 4 EXPIRED objects, why does it show those same four pieces? How can I get rid of it? Obviously, it is EXPIRED, so I don't need it. I ran crosscheck command too. That didn't worked. I ran the delete with force and obsolete options too. They also did not worked. Please help. What am I missing?

I tried that change command. But I am getting
RMAN> change backupset completed before '01-Jan-2011' uncatalog;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of uncatalog command at 04/06/2011 12:55:34
RMAN-06122: CHANGE .. UNCATALOG not supported for BACKUPSET
The action change suggested was to use
RMAN> change backupset .... delete;
This says deleted. But again when I list backup this shows.

Delete expired not working

Good Morning,
I have a 10g 2 database using flash recovery. I checked the flash recovery area and in there is listed arc log files from February. I had clicked the delete expired several times but it does not take affect.
Is this a known bug or am I not doing something right?
Your help in this matter would be appreciated.
thanks in advance.
al

CAN THIS IS A REASON!!!
RMAN WILL DELETE ARCHIVELOGS FROM DISK WHICH ARE OBSOLETE IF YOU ARE USING A CATALOG, HERE IS A SMALL TEST
FIRST I WILL RUN WITH CATALOG
RMAN> connect target /
RMAN> connect catalog rman/rman@rman
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
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; # 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 SNAPSHOT CONTROLFILE NAME TO '/opt1/app/oracle/product/ora92/dbs/snapcf_dgtest.f'; # default
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Tag
850279 B A A DISK 16-MAY-07 1 1 TAG20070516T145909
850302 B A A DISK 16-MAY-07 1 1 TAG20070516T145916
850326 B A A DISK 16-MAY-07 1 1 TAG20070516T145928
850351 B A A DISK 16-MAY-07 1 1 ARCH
850377 B A A DISK 16-MAY-07 1 1 ARCH
850405 B A A DISK 16-MAY-07 1 1 ARCH
850409 B 0 A DISK 16-MAY-07 1 1 TAG20070516T150205
850427 B A A DISK 16-MAY-07 1 1 TAG20070516T150239
850431 B 0 A DISK 16-MAY-07 1 1 TAG20070516T150250
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=22 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 850279 16-MAY-07
Backup Piece 850280 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1iihsf9t_1_1
Backup Set 850302 16-MAY-07
Backup Piece 850303 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1jihsfa4_1_1
Backup Set 850326 16-MAY-07
Backup Piece 850327 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1kihsfag_1_1
Backup Set 850351 16-MAY-07
Backup Piece 850352 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1lihsfce_1_1
Backup Set 850377 16-MAY-07
Backup Piece 850378 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1mihsfcl_1_1
Backup Set 850405 16-MAY-07
Backup Piece 850406 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1nihsfea_1_1
Backup Set 850409 16-MAY-07
Backup Piece 850410 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1oihsffd_1_1
Backup Set 850427 16-MAY-07
Backup Piece 850428 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1pihsfgf_1_1
Archive Log 850228 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_168.dbf
Archive Log 850229 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_169.dbf
Archive Log 850230 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_170.dbf
Archive Log 850231 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_171.dbf
Archive Log 850232 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_172.dbf
Archive Log 850233 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_173.dbf
Archive Log 850234 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_174.dbf
Archive Log 850235 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_175.dbf
Archive Log 850236 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_176.dbf
Archive Log 850237 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_177.dbf
Archive Log 850238 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_178.dbf
Archive Log 850239 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_179.dbf
Archive Log 850240 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_180.dbf
Archive Log 850241 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_181.dbf
Archive Log 850242 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_182.dbf
Archive Log 850243 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_183.dbf
Archive Log 850277 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_184.dbf
Archive Log 850300 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_185.dbf
Archive Log 850324 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_186.dbf
Archive Log 850349 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_187.dbf
Archive Log 850375 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_188.dbf
Archive Log 850403 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_189.dbf
Archive Log 850425 16-MAY-07 /data1/oradata/dgtest/archive/dgtest_1_190.dbf
Do you really want to delete the above objects (enter YES or NO)? NO
RMAN SHOWS ARCHIVES WHICH ITS GOING TO DELETE ALONG WITH BACKUPSETS
NOW SEE IT WITHOUT THE CATALOG
RMAN> quit
Recovery Manager complete.
$ rman
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN> connect target /
connected to target database: DGTEST (DBID=3559913552)
RMAN> delete obsolete;
using target database controlfile instead of recovery catalog
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=23 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 48 16-MAY-07
Backup Piece 48 16-MAY-07 /opt1/app/oracle/product/ora92/dbs/1oihsffd_1_1
Do you really want to delete the above objects (enter YES or NO)? no
RMAN> $ rman

Delete expired backup;

Hi expert,
i want delete expired backup of databae
CONFIGURE RETENTION POLICY TO REDUNDANCY 7
this is my RMAN Database setting
how can delete RMAN backup ,
i have take backup of every day.
delete backup 'sysdate -2';
but how can delete it?

I think you are confusing the things.
If you set a policy of REDUNDANCY = 7, then you want to keep 7 copies of the files in the backups.
And that is excluded with DELETE OBSOLETE clause and not to DELETE EXPIRED clause.
And also, if you define REDUNDANCY = 7, you may not use a DELETE SYSDATE-2, because there may be a file that was not backuped 7 times.

I want to delete expired backups

Hey, I had manually deleted some backups, I didn't know about the "delete obsolete" command at the time. So when I do a "report obsolete" the expired backups are still showing and when I do a delete expired, it wont delete them since they were already deleted, but they are still showing up when i do a crosscheck and report obsolete.
So, my question is, is there anyway to tell rman that they have already been deleted? So they wont show up anymore?

Can you tell the output of CROSSCHECK and DELETE EXPIRED statements. RMAN marks backups and copies as expired when you run a CROSSCHECK command and the files are absent or inaccessible.

Will RMAN delete archive log files on a Standby server?

Environment:
Oracle 11.2.0.3 EE on Solaris 10.5
I am currently NOT using an RMAN repository (coming soon).
I have a Primary database sending log files to a Standby.
My Retention Policy is set to 'RECOVERY WINDOW OF 8 DAYS'.
Question: Will RMAN delete the archive log files on the Standby server after they become obsolete based on the Retention Policy or do I need to remove them manually via O/S command?
Does the fact that I'm NOT using an RMAN Repository at the moment make a difference?
Couldn't find the answer in the docs.
Thanks very much!!
-gary

Hello again Gary;
Sorry for the delay.
Why is what you suggested better?
No, its not better, but I prefer to manage the archive. This method works, period.
Does that fact (running a backup every 4 hours) make my archivelog deletion policy irrelevant?
No. The policy is important.
Having the Primary set to :
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBYBut set to "NONE" on the Standby.
Means the worst thing that can happen is RMAN will bark when you try to delete something. ( this is a good thing )
How do I prevent the archive backup process from backing up an archive log file before it gets shipped to the standby?
Should be a non-issue, the archive does not move, the REDO is transported and applied. There's SQL to monitor both ( Transport and Apply )
For Data Guard I would consider getting a copy of
"Oracle Data Guard 11g Handbook" - Larry Carpenter (AKA Dr. Paranoid ) ISBN 978-0-07-162111-2
Best Oracle book I've read in 10 years. Covers a ton of ground clearly.
Also Data Guard forum here :
Data Guard
Best Regards
mseberg
Edited by: mseberg on Apr 10, 2012 4:39 PM

RMAN Delete Obsolete job fails due to Error Allocating Device

Experts, I need help, please.
This is 10.2.0.1 on Windows
RMAN> DELETE NOPROMPT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=130 devtype=DISK
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/15/2012 14:10:17
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
I ran RMAN> configure device type 'SBT_TAPE' clear;
but I still get the same error.
I backup to Disk, not tape
Notice the reference to SBT_TAPE:
RMAN configuration parameters are:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
What do I need to do to be able to run DELETE OBSOLETE; ?
Thanks, John

as anand mention ,you've to reset this parameter to default value.
and clear cmd with configure will remove it from configuration parameter
see below
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
*CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;*
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE 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/db/dbs/snapcf_GG1.f'; # default
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/16/2012 12:04:34
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2
RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' clear;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
RMAN configuration parameters are successfully reset to default value
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
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 2 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 ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1591 instance=GG1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=1627 instance=GG1 devtype=DISK
no obsolete backups found

Delete expired data guard

Hi,
I got a question regarding the primary db and the data guard db. I had to reduce the amount of files retained due to space limitations on the primary. When I clicked on the delete expired button and the job is run the files that are deleted on the primary are they also deleted on the data guard db? If not will this cause a problem if when a fail over or switch over is needed?
Thanks in advance for your help.
al

Good Morning Kam Singh
I just have one additional question that occurred to me last night at home. There was an issue with hard parsing that my ADDM advised increasing my SGA by 2.5 gigs. Someone on the forum here was kind enough to give me the view V$sgainfo to find out how much free memory was available in my system. Well when I interrogated this view it came up with a big fat zero availability. Now from what I understood from my readings was that 10g sga was dynamic. That the memory processes are adjusted to need from information taken from the AWR. At the page where the ADDM listed a button to implement the change (increase) I hesitated until I found out how much free was available. Right now I am glad that I did. My question is If I did click on that implementation button would have the oem tool taken the memory not being used from some other location and allocate it to this spot or would it have returned an error of some kind?
You may have more experience with this and may have come across this situation than I. Do you recall what you did?
Does anyone else recall what they did in this situation?
Please give advise.
Regards to all,
al

RMAN Delete pbsolete ERROR

Dear Friend,
In our production server , we use IBM - Tivoli Storage Manager - Software for our RMAN backup purpose . The backup data backup piece are stored on a Storage Library . It works fine but the problem is when I am going to delete "obsolete backup" then it shows the following error :
RMAN> Delete pbsolete;
Backup Set 870 06-OCT-08
Backup Piece 870 06-OCT-08 c-1077970889-20081006-00
Backup Set 871 07-OCT-08
Backup Piece 871 07-OCT-08 rfjsj6d8_1_1
Backup Set 872 07-OCT-08
Backup Piece 872 07-OCT-08 rgjsj6n1_1_1
Backup Set 873 07-OCT-08
Backup Piece 873 07-OCT-08 c-1077970889-20081007-00
Backup Set 875 08-OCT-08
Backup Piece 875 08-OCT-08 rjjslh0e_1_1
Backup Set 876 08-OCT-08
Backup Piece 876 08-OCT-08 c-1077970889-20081008-00
Backup Set 878 11-OCT-08
Backup Piece 878 11-OCT-08 rmjsstps_1_1
Backup Set 879 11-OCT-08
Backup Piece 879 11-OCT-08 c-1077970889-20081011-00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 10/14/2008 19:14:20
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
Anybody has idea about the above error ?
Plz inform .. ..

See Note:567555.1 Encountered RMAN-03002 and RMAN-06091 when Deleting Obsolete Backups
The problem is a tape channel had not being allocated when attempt to delete obsolete backup on tape.
HTH
Enrique

Should i delete expired certificates in the keychain on my iMac

Since installing Yosemite Facetime & iMessage will not accept my apple password. message states I should contact apple with customer code 4397-0036-7181. On looking in my keychain a lot of certificates have expired. Should I delete them?

You should delete expired certificates, but that alone won't solve your problem.
If you're trying to sign in to FaceTime, try to sign in to iMessage in the Messages application, or vice versa.
Otherwise, do as the alert directs. According to reports, you won't be charged for the support call if you select "Apple ID"—not the hardware model—as the product you're asking about, and cite the "customer code" in the alert as the "validation code" when you speak to the Apple representative. I can't confirm.

Deleting Expired certificates from IOS CA

I have been looking at how to delete expired certificates from an IOS CA. I have seen the command "crypto pki server trim" but this command appears to only apply to certificates in the CRL list. Does anyone know if there is a similar command to just delete expired certificates rather than ones that have been revoked first? It would be a hassle to have to manually go through each one.

Hi Yerko,
Yes you can. Please have a look at the below link:
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_pki/configuration/15-mt/sec-pki-15-mt-book/sec-cert-enroll-pki.html
Please visit the below section.
Configuring Cut-and-Paste Certificate Enrollment
SUMMARY STEPS
1.    enable
2.    configure terminal
3.    crypto pki trustpoint name
4.    enrollment terminal pem
5.    fingerprint ca-fingerprint
6.    exit
7.    crypto pki authenticate name
8.    crypto pki enroll name
9.    crypto pki import name certificate
10.    exit
11.    show crypto pki certificates
Regards,
Kanwal
Note: Please mark answers if they are helpful.

Deleting Expired Roles

Hi,
can delete expired profiles with PFCG_TIME_DEPENDENCY, but what can I do for roles with no valid date range in the user master dat
Thanks,
Sreekar.

Hi,
You may want to review notes 312943, 504412, and 313587 to see if there is any helpful information. Below is some documentation that may be helpful for others. We are going from 40B to 47 and had a few issues with role deletion.
First, the report PFCG_TIME_DEPENDENCY is functioning as designed. It was not designed to remove activity groups.
Second, in transaction SU10 you must have the "Valid From" and "Valid To" fields filled in with the actual dates (04/08/2002) in order to remove the invalid activity group. You need to be sure that the "Remove User" radio button is set in the role tab. In the profile tab, the "Add User" radio button is selected by default. What you have to do is go to the profile tab and select the "Remove User" radio button. You have to make sure both role and profile have the same radio button selected (i.e. remove from users). Only then when you click save, will it allow you to delete the role from user. In transaction SU10, you need to complete the following steps:
1. Click on the Authorization data button.
2. Entry the users name, latimerc.
3. Click on the execute button.
4. Put a check in front of the users name.
5. Click on the transfer button.
6. Now highlight the user.
7. Click on the pencil button.
8. Click on the Activity Groups tab.
9. Enter the profile name (PM_NOTIFICATION_PROCESSOR).
10. Enter the valid from and valid to dates (04/08/2002).
11. Change the radio buttons to remove user from both the Activity Group and Profile Tabs.
12. Click on the trash can.
In another customer message the following was provided by developement:
There is no regular functionality for mass deletion of roles. But, if you want to avoid the deletion by hand or with an own created report, I would suggest the following:
The report ZDELETE_RY_T_AGRS can delete all roles with names like 'T_....' or 'RY....'. The report gives you a list of all these roles and then deletes the selected ones. You can modify the report to get all your roles in the selection list. Therefore, you have to change the following:
SELECT * FROM AGR_FLAGS INTO TABLE L_AGR_FLAGS
WHERE FLAG_TYPE = 'COLL_AGR'
AND FLAG_VALUE = 'X'.
SORT L_AGR_FLAGS BY AGR_NAME.
LOOP AT SINGLE_ACTGROUPS WHERE AGR_NAME+11 <> SPACE AND <<< delete
( AGR_NAME(2) = 'T_' OR AGR_NAME(2) = 'RY' ). <<< delete
LOOP AT SINGLE_ACTGROUPS WHERE AGR_NAME+11 <> SPACE. <<< insert
READ TABLE L_AGR_FLAGS WITH KEY AGR_NAME = SINGLE_ACTGROUPS-AGR_NAME
BINARY SEARCH.
Text from an additional customer message offers further help:
1. Go on role tab.
2. Select remove from user.
3. Enter ZR.PRD.GENERIC and date : 06/04/2002 12/31/9999.
4. Go to profile tab.
5. Select remove from user.
6. Save.
7. Do the same for ZR:HR:ESS from 01/01/2002 to 12/31/9999 and worked from date for testid was 01/01/2002 and testid2 02/01/2002. In this case, the two assignements were deleted, and the roles were also removed from the two UMR.
Reward points if found helpfull..
Cheers,
Chandra Sekhar.

Automatic delete expired w/RMAN

I'm looking for some rman scripts to delete
obsolete bacuppieces from disk.
We make incremental level 1 backups every day, and incremental level 0 every sat.
We are backing up files to disk.
I want to delete obsolete backuppieces from disk, and i need rman to do it.
I can do a CHANGE BACKUPPIECE FOR DELETE'
but, i need to know the obsolete backuppieces names first.
The problem is, i don't want to remove those
files manually in order to CROSSCHEKING afterwards.
I would be nice to implement
some new rman command like
'delete obsolete completed before...'
wouldn't it?
RDBMS 8.1.6.3
and RMAN 8.1.6.3
Thank you.

Take a look at the script rman1.sh. It usually can be found at $ORACLE_HOME/rdbms/demo directory.
You may be able to copy this and modify it to remove the backups that are obsolete.
Make sure to test this out and it works as you expect.
null

RMAN "delete noprompt obsolete" not deleted

OS: AIX 5.3L; Oracle 10g R2
I have "delete noppropt obsolete" in my RMAN backup script as {
delete noprompt obsolete;
crosscheck backupset;
crosscheck archivelog all;
delete noprompt expired backup;
delete noprompt expired archivelog all;
backup as compressed backupset incremental level 1 cumulative device type disk tag 'Baan_bkup$LEVEL1' database plus archivelog delete input; }
but the incremental level 1 cumulative backupsets, outside my 7 days window, did not been deleted as prompted, even they are under the obsolete list. Why?
Message was edited by:
user508054

I also observed that with "REPORT OBSOLETE", only partial of the backupset piece of backup were "OBSOLETE". For example, after this morning LEVEL 1 incremental backup, my last Sunday, Mar 4 level 0 backup has 12 backup pieces (including controlfile and archivelog), but only two have been on the obsolete list. The two are controlfile and archivelog, and other 10 datafaile backupsets are still there in the list. Really confused! Are they supposed to be treated as a bunch?

RMAN delete noprompt obsolete

Hi,
I'm keen to know what does this comand mean in RMAN backup. "delete noprompt obsolete;" .Can I apply this comand for no catalog too or it's just meant for rman catalog.
Thanks
M.Kaur

Hi,
I'm trying to do house keeping on RMAN backups,following is my script,but this does not remove hte last year's backups on the tape,thou the tape is mounted to the lib.Must I add in another command? but yes the last year's backup is not even shown in the rman backup list,but it's still in the sbt_tape,how do I remove it from there.
Note: RMAN no catalog running on oracle 9i 9.2.0.7
allocate channel for delete type disk;
allocate channel for delete type 'sbt_tape'
PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
report obsolete orphan;
report obsolete;
crosscheck backup;
crosscheck copy;
crosscheck backup of controlfile;
delete noprompt expired backup;
delete noprompt expired archivelog all;
delete noprompt expired backup of controlfile;
delete force noprompt expired copy;
delete force noprompt obsolete orphan;
delete force noprompt obsolete;
release channel;
Thanks

RMAN DELETE EXPIRED

Similar Messages

Maybe you are looking for