Database Tuning (MOSC)

MOSC Banner

DBMS_STATS.CLEANUP_STATS_JOB_PROC caused deadlock when doing a partition exchange

edited Feb 27, 2012 10:31AM in Database Tuning (MOSC) 2 commentsAnswered ✓
Hi,
DB:11.2.0.2 (datewarehouse)

We did an partition exchange in our TEST db last nigth. The job had aborted due to an ORA-00060 Deadlock

The involved objects where:

DBMS_STATS.CLEANUP_STATS_JOB_PROC

and our own

ALTER INDEX LDW.MFT_STCKMRKT__CONT_ATTR_KEY REBUILD PARTITION MFT_MFTM_PR_W_200842

So, our job aborted. Our statsgathering is scheduled to day time because of the performance impact for the critical batch.

1. Why is DBMS_STATS.CLEANUP_STATS_JOB_PROC running at 00:00? What does it do?

We do some small partions exchanges during our nigthly batch, so this could, if we are unlucky, halt our PROD batch job.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center