[SOLVED] Re: Deadlock on CDC_ALTER_CTABLE_BEFORE
- From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
- To: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxx>
- Date: Mon, 15 Jun 2009 13:51:39 -0300
Aw, come on, it's a test DB, no need of resignation. Backups are taken daily
so there was no data loss (not that it would matter on test db). Actually,
the problem started with a script to drop tables for a data refresh, so data
was not useful anyway.
Restoring the DB worked great, I had hope there was another way, however I
tried running catalog (even with the db without any users on) and it still
failed.
I appreciate everyone's imput on this.
Mark, I saw that note just a few minutes too late. I thought of disabling
triggers, but I thought it would introduce inconsistency into de DB.
thanks!
Alan Bort
Oracle Certified Professional
On Mon, Jun 15, 2009 at 9:54 AM, Bobak, Mark <Mark.Bobak@xxxxxxxxxxxx>wrote:
> Hi Alan,
>
>
>
> Take a deep breath….now let it out slowly. It’s not the end of the world.
> If you have MetaLink access, see DOC ID *360509.1.*
>
>
>
> This appears to be a known problem w/ an easy fix.
>
>
>
> -Mark
>
>
>
>
>
> *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
> oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Guillermo Alan Bort
> *Sent:* Monday, June 15, 2009 8:15 AM
> *To:* oracle-l-freelists
> *Subject:* Deadlock on CDC_ALTER_CTABLE_BEFORE
>
>
>
> After a newbie mistake I get a few errors from the data dictionary (dba_*
> views not working, synonyms brokent, etc). Obviously the data dictionary is
> broken. When I try to re-create it using catalog.sql I get these errors:
>
>
> ERROR at line 1:
> ORA-04020: deadlock detected while trying to lock object
> SYS.CDC_ALTER_CTABLE_BEFORE
>
>
> I opened the database in restricted mode.
>
> Any ideas?
>
>
> Alan Bort
> Oracle Certified Professional
>
Other related posts:
