How to Avoid or Prevent "Process 0x%p appears to be hung in Auto SQL Tuning task" Messages
(Doc ID 1344499.1)
Last updated on MARCH 28, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database - Standard Edition - Version 18.104.22.168 and later
Oracle Database - Personal Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Occasionally, when running the "SYS_AUTO_SQL_TUNING_TASK" warning messages such as the following may appear in the alert log:
"Current time = %u, process death time = %u"
"Attempting to kill process 0x%p with OS pid = %s"
"OSD kill skipped for process %p"
"OSD kill succeeded for process %p"
"OSD kill failed for process %p"
These messages indicate that an auto kill of a "hung"/long running tuning task has taken place. This is a protective measure purely to avoid the task from over-running its time limit because of a single task and protects a the system from harm caused by such over-running.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document