0% found this document useful (0 votes)
4 views

Document 858852.1

Uploaded by

dinermi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views

Document 858852.1

Uploaded by

dinermi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

9/29/2020 Document 858852.

1
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

DBA_AUTOTASK_TASK and DBA_AUTOTASK_CLIENT Shows Different Status For Auto Optimizer


Stats Collection (Doc ID 858852.1)

In this Document

Symptoms
Changes
Cause
Solution
References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

SYMPTOMS

We are Trying to Disable the Auto Optimizer Stats Collection in 11G.


DBA_AUTOTASK_CLIENT shows that the 'auto optimizer stats collection' is disabled. But DBA_AUTOTASK_TASK shows that
the Task is Enabled.

BEGIN
DBMS_AUTO_TASK_ADMIN.DISABLE(
client_name => 'auto optimizer stats collection',
operation => NULL,
window_name => NULL);
END;
/

PL/SQL procedure successfully completed.

Checking the Status from DBA_AUTOTASK_TASK & DBA_AUTOTASK_CLIENT

SQL> select client_name,status from DBA_AUTOTASK_TASK;


.
CLIENT_NAME STATUS
---------------------------------------------------------------- --------
auto optimizer stats collection ENABLED <<===
auto space advisor ENABLED
sql tuning advisor ENABLED
.
SQL> select client_name,status from Dba_Autotask_Client;
.
CLIENT_NAME STATUS
---------------------------------------------------------------- --------
auto optimizer stats collection DISABLED <<===
auto space advisor ENABLED
sql tuning advisor ENABLED

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=14u4h7ujbz_636&id=858852.1 1/2
9/29/2020 Document 858852.1

CHANGES

CAUSE

This is expected Behavior.


The views assume that there is a one to many relationship between CLIENTS and TASKS.
Task can be used by different/multiple client. So even though if we disable the client, the DBA_AUTOTASK_TASK may still
show the status as enabled. In current version, the TASKS has only one CLIENT. But in future version of oracle , the TASKS
can have multiple CLIENTS so the status in DBA_AUTOTASK_TASK will show as ENABLED.
So the correct way to check the status is through DBA_AUTOTASK_CLIENT.

SOLUTION

Use DBA_AUTOTASK_CLIENT to check the status.

SQL> select client_name,status from Dba_Autotask_Client;

REFERENCES

BUG:8605352 - WRONG STATUS INFO IN DBA_AUTOTASK_TASK


NOTE:779596.1 - How Can We Find Out Status Of Task 'Auto Optimizer Stats Collection'
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=14u4h7ujbz_636&id=858852.1 2/2

You might also like