ORA-00001: unique constraint (SYS.WRH$_MUTEX_SLEEP_PK) violated

From: Marko Sutic <marko.sutic_at_gmail.com>
Date: Sun, 9 Dec 2012 10:38:55 +0100
Message-ID: <CAMD6WPdGHyh0ohihVaXcqdW3yAhweQZN5hc5xtH4FjGbUwSDFg_at_mail.gmail.com>



Hi all,
with every AWR snapshot I get "ORA-00001: unique constraint (SYS.WRH$_MUTEX_SLEEP_PK) violated" which generates trace file and core dump.

I' aware that this error is not dangerous but in 3 days I have 3.5G of trace files with snapshot taking every 15 mins. Tracing ORA-00001 errors is not enabled by default but I have to enable this because I want to trace ORA-00001 errors for prod application.

I've dropped all historical snapshots using DBMS_WORKLOAD_REPOSITORY.DROP_SNAPSHOT_RANGE but this error again appears with every new AWR snapshot.

There is Metalink document related to this error: ORA-00001: Unique Constraint (SYS.WRH$_MUTEX_SLEEP_PK) Violated [ID 1498713.1]

Solution
Apply 11.2.0.4 patchset when avaialable
or
Check if a patch is available for your version of Oracle and operating system: Patch 10122454

Currently I cannot upgrade database to 11.2.0.4 and cannot download patch as I don't have download access (extended support).

Is there any workaround for this problem?

DB - 11.1.0.7 on Linux 64bit

  • Error Stack Dump ----- ORA-00001: unique constraint (SYS.WRH$_MUTEX_SLEEP_PK) violated
  • Current SQL Statement for this session (sql_id=gj6uc50hpnr1p) ----- insert into WRH$_MUTEX_SLEEP (snap_id, dbid, instance_number, mutex_type, location, sleeps, wait_time) select :snap_id, :dbid, :instance_number, mutex_type, location, sleeps, wait_time from v$mutex_sleep where sleeps > 0 order by mutex_type, location
  • PL/SQL Stack -----
  • PL/SQL Call Stack ----- object line object handle number name 0x2d83e8a60 14 package body SYS.DBMS_WORKLOAD_REPOSITORY 0x2d83e8a60 37 package body SYS.DBMS_WORKLOAD_REPOSITORY 0x2d9366e88 2 anonymous block

Thank you all for your valuable answers.

Regards,
Marko

--
http://www.freelists.org/webpage/oracle-l
Received on Sun Dec 09 2012 - 10:38:55 CET

Original text of this message