| Can RMAN specifically delete obsolete archivelogs? [message #237033] |
Fri, 11 May 2007 12:22  |
clintonf
Messages: 82
Registered: May 2006
|
Member |
|
|
Hi all,
Is it possible, in RMAN, to delete only obsolete archivelogs?
`REPORT obsolete` returns obsolete .dbf files first and then a whole host of archivelogs.
Windows networking and my DB application makes copying .dbf files difficult (which is why they are obsolete). I can make regular archivelog backups and network copy them to my auxiliary DB with no problems.
Of course, with time the list of obsolete archivelogs is becoming rather bloated and slowing down DB backups and duplications so I would like to delete just the obsolete archivelogs. Thus far I have been guessing at the commands and reading up on the subject has not proven fruitful.
Is it possible to just delete the obsolete archivelogs?
Thanks!
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Can RMAN specifically delete obsolete archivelogs? [message #239624 is a reply to message #238679] |
Tue, 22 May 2007 15:15  |
clintonf
Messages: 82
Registered: May 2006
|
Member |
|
|
Hi there,
I want to retain obsolete .dbf's, not backups.
Currently I am using RMAN primarily to duplicate my production machine to a test machine. I can copy the archivelogs and backups across the network (with file copy)
In order to copy the .dbf's using RMAN I need to change the user that starts the Oracle service (Windows Server 2003). Unfortunately, doing so prevents users from accessing the database via the client applications.
The reason that I want to keep the obsolete .dbf's is so that I can still duplicate my database using the .dbf's with new backup files and archivelog files. At least, until I can determine how to allow access to the .dbf's across the network and Oracle.
As to retention policy, I don't have one (yet). I am still trying to determine the best parameters to use with RMAN (suggestions welcome!).
Is it possible to just delete the obsolete archivelogs?
Thanks!
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
