RE: Rman Locking
- From: "Hallas, John, Tech Dev" <John.Hallas@xxxxxxxxxxxxxxxxx>
- To: <Paula_Stankus@xxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 11 Nov 2004 13:52:58 -0000
Yes it would help.
After every backup we run 2 scripts, one to delete expired backups and =
the other to restore a controlfile to /tmp to prove the validity of the =
backup.
-----Original Message-----
From: Paula_Stankus@xxxxxxxxxxxxxxx
[mailto:Paula_Stankus@xxxxxxxxxxxxxxx]
Sent: Thursday, November 11, 2004 12:48 PM
To: Hallas, John, Tech Dev; oracle-l@xxxxxxxxxxxxx
Subject: RE: Rman Locking
In this case, wouldn't it also help to delete any "expired" backups?=20
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Hallas, John, Tech
Dev
Sent: Wednesday, November 10, 2004 3:58 AM
To: Oracle-L (E-mail)
Subject: RE: Rman Locking
We run into this problem quite a lot.
The issue seems to be that during a RMAN backup it takes an enqueue lock
=3D (seems to be of type CHPT) against the RMAN catalogue.
This is held whilst it searches for obsolete/redundant rows to delete.
As you will be aware there is quite a lot of referential integrity =3D
within the catalogue and some of the full table scans can be quite =3D
intensive on a very large catalogue.
The process then exaggerates as another backup is kicked off from a =3D
different target database.
The end result is the need to kill of the locked processes and restart.
Solutions can be to reduce the number of concurrent rman backups from =
=3D
seperate servers and to increase the number of catalogues in use.
We have a RMAN recovery database with a number of schemas which we back
=3D various versions of Oracle software into and we can also split into =
=3D
schemas for application types (i.e. rman8i, rmman9i, rmancust etc)
HTH
John
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Spears, Brian
Sent: Tuesday, November 09, 2004 4:35 PM
To: Oracle-L (E-mail)
Subject: Rman Locking
Anybody ever run into a resync catalog while backing up archive logs =3D
causing problems. It is happening once a week randomly. What happens
is =3D deadlock on chp table and of course all other Rman stuff is held
up. It seems to =3D be this one small rarely used database. The way we
solve it is to go out =3D and kill the process on unix and everything is
freed up.
I would like to say that the network is burping or something and
disconnecting the process ..but its on the same database all the time.
Brian
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
NOTE: This message was auto-learned as non-spam. If this is wrong,
please correct the training as soon as possible.
Teach CanIt if this mail (ID 15353270) is spam:
Spam:
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Ds&i=3D15353270&m=3Da3e5=
cf3f5
252
Not spam:
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Dn&i=3D15353270&m=3Da3e5=
cf3f5
252
Forget vote:
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Df&i=3D15353270&m=3Da3e5=
cf3f5
252
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS
--
//www.freelists.org/webpage/oracle-l
Other related posts:
