Home > problem-cause-solution > hung in Auto SQL Tuning task, critical alert in GC

hung in Auto SQL Tuning task, critical alert in GC


Problem

Critical alert comes as:

mydb01 : -K- mydb1:Operational error () detected in /u01/app/oracle/diag/rdbms/mydb/mydb/alert/log.xml at time/line number: Tue Apr 20 00:10:51 2010/36623. : 00:15 20/04/10

Cause

I had opened an SR and the result is: It is a bug.
Bug 8636312: HUNG IN AUTO SQL TUNING TASK which is based on the Oracle base bug Billy gave above.
No workaround is provided, and the bug is not patched or solved in newer version.
Acknowledging this alert from the GC, solved my need of stopping the anoyingly coming of this alert.
You can acknowledge the alert by clicking the alert link, which brings details of it, containing “acknowlege” button.

This alert is related with the Metric: “Generic Operational Error”

Workaorund

Meantime you can drop auto sql tuning job as follows:

Check the AUTO SQL TUNING TASK exist:

SELECT   TASK_NAME, STATUS FROM   DBA_ADVISOR_TASKS

WHERE   task_name LIKE ‘%SYS_AUTO_SQL_TUNING_TASK%';

TASK_NAME STATUS
SYS_AUTO_SQL_TUNING_TASK FATAL ERROR

Drop it with command:

exec DBMS_SQLTUNE.DROP_TUNING_TASK(‘SYS_AUTO_SQL_TUNING_TASK’);

Solution

Waiting for the patch.

About these ads
  1. January 19, 2011 at 10:35 pm

    Interesting enough and informative subject

  2. November 22, 2012 at 8:57 pm

    Thank you for sharing! Your post helped me today.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 36 other followers

%d bloggers like this: