Home » RDBMS Server » Backup & Recovery » RMAN Backup - Applying Retention Policy takes very long (Oracle Database 9.2.0.6 Sun Solaris 8)
RMAN Backup - Applying Retention Policy takes very long [message #292593] Wed, 09 January 2008 05:35 Go to next message
hardeys
Messages: 4
Registered: May 2007
Location: India
Junior Member
Hi All,

I am using RMAN to backup my Apps 11i Database. When RMAN applies the Retention Policy which is set to redundacy 1, its takes more than one hour. So the Whole backup takes 1 hour 30 mins.

If i apply the same script on the test environment, the backup finishes within 30 mins. What can be the reasons.
Re: RMAN Backup - Applying Retention Policy takes very long [message #292601 is a reply to message #292593] Wed, 09 January 2008 05:55 Go to previous messageGo to next message
Frank Naude
Messages: 4587
Registered: April 1998
Senior Member
Enable debugging and try to find the step that's so slow. I's most likely a query against the catalog database.

RMAN> DEBUG ON;
Re: RMAN Backup - Applying Retention Policy takes very long [message #292604 is a reply to message #292601] Wed, 09 January 2008 06:03 Go to previous messageGo to next message
hardeys
Messages: 4
Registered: May 2007
Location: India
Junior Member
I am using controlfile as catalog... Will setting Debug=on consume more time..
Re: RMAN Backup - Applying Retention Policy takes very long [message #292609 is a reply to message #292593] Wed, 09 January 2008 06:23 Go to previous messageGo to next message
Michel Cadot
Messages: 68728
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator
There is no relation between retention policy and rman backup duration.
Search other things.

Regards
Michel

Re: RMAN Backup - Applying Retention Policy takes very long [message #292663 is a reply to message #292604] Wed, 09 January 2008 09:45 Go to previous message
Frank Naude
Messages: 4587
Registered: April 1998
Senior Member
It may take slightly longer, but will write out a LOT of extra information. Look at the "elapsed time" of each call and compare it to the debug output on the faster system.
Previous Topic: Duplicate Database Doubt
Next Topic: Restore and Recovery using non-default archivelog destination
Goto Forum:
  


Current Time: Tue Dec 24 10:54:16 CST 2024