This content has been marked as final. Show 24 replies
Thanks for your input.
I'm thinking I will just take out the 'delete input' clause from the backup script and have a separate job that will delete the archivelogs (well after the backups have completed and after verification that the archivelogs were indeed successfully backed up). How does that sound?
Since you are not keeping Archive around very long the database might be holding the lock on the archivelog file you are trying to delete.That wouldn't be the case. Once an Archivelog has been created, the database doesn't "hold a lock on it". Furthermore, RMAN will not backup an Archivelog that hasn't been completed (i.e. is still in the progress of being written out). Then, the DELETE INPUT will only delete an Archivelog that has been backed up.
Therefore, the operations should be clean. There must be some other reason for the "hold up".
Hemant K Chitale
Thanks for you input. I'm thinking the file has to be created, then it has to be written which takes a moment. If during that brief moment RMAN tries to delete it there would be a conflict which could cause a hang.
If you know of other conflicts that would better explain then please post them.
I'm pretty sure I saw an Oracle note which offers some support to my theory. If I find it I will post here.
Cannot find the note but...
Does not matter since the GolderGate has been shook out. Yes that would explain, you cannot delete Archive that is still needed for that. Thanks Hemant!!
Edited by: mseberg on Jan 24, 2013 9:15 PM
Will depend upon the Oracle version :
You need to :
Configure archivelog deletion policy.
I believe this short document will cover it :
Usage of RMAN in Streams Environment [ID 421176.1]
Reporte Obsolete Does not Report Archivelog Backup [ID 803635.1]
OERR:RMAN 8137 WARNING: archived log not deleted, needed for standby or upstream capture process [ID 1365394.1]
Edited by: mseberg on Jan 25, 2013 7:58 AM