RE: RMAN hangs after 10.2 upgrade
- From: "Orysia Husak" <Orysia.Husak@xxxxxxxxxxxxx>
- To: <oramail@xxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 2 Mar 2007 09:28:34 -0700
When we upgraded from 10.2.0.1 to 10.2.0.2 our rman backups started
taking significantly longer. We were seeing control file sequential read
waits. Once we recreated the control files, the rman backups speeded up
again. On databases that we created at 10.2.0.2, we didn't see this
bizarre behavior in the rman backups.
Orysia
Orysia Husak
Sr. Oracle DBA - Classroom Applications Hosting
University of Phoenix/ Apollo Group, Inc.
Office: 602-546-6934
Mobile: 602-377-8586
orysia.husak@xxxxxxxxxxxxx
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Rich Holland
[oramail]
Sent: Friday, March 02, 2007 8:16 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RMAN hangs after 10.2 upgrade
We recently upgraded a dozen or so databases from 9.2.0.(6|7) to
10.2.0.2 + patch 10 on Win32. Now when we execute a 'connect target' in
RMAN, it runs very slow - a 'show all' command takes a couple minutes to
complete. 'exit' takes ~5 minutes. We're not using a recovery catalog,
and our control files are around 15M. If we don't connect to the
database, RMAN starts & stops very fast, as expected - it just seems to
be trodding through molasses whenever it's connected to the database.
Here's a 'show all' in one of the systems:
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 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
'\\backupserver\orab
kup\DEV\dev_ctrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 3 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
'E:\ORACLE\DEV\102\DATABASE\SNCFBWP.ORA';
# default
Has anyone else seen similar problems with 10.2? We poked around in
metalink but didn't see anything....
Thanks!
Rich
Other related posts: