SQL Profile exists but was ignored during the tuning process
I get this kind of message on the Automated SQL Tuning Advisor. Also, last week, a sql that had a sql profile on it, started running slow. When I analyzed It, I got the same message: SQL Profile "SYS_SQLPROF_013e32bf03180058" exists for this statement and was ignored.
What is causing the sql profile to be ignored? How can we ensure that once in place, it is used every time we run the sql.
Thanks!
What is causing the sql profile to be ignored? How can we ensure that once in place, it is used every time we run the sql.
Thanks!
0