New Sql profiles
From: Pap <oracle.developer35_at_gmail.com>
Date: Mon, 13 Sep 2021 02:04:49 +0530
Message-ID: <CAEjw_fiEKH6sgpVgkP7yKLvBvQpvuc+1treeOF8hwmedVEq-Fg_at_mail.gmail.com>
Hello Listers, We are seeing a few sqls running longer post 19c migration and when looking into the details , we found the new plan which it opting are having some sql profiles created/attached(having name SYS_SQLPROF****) and forcing the plan to go for a suboptimal ones. Want To understand how those are created for so many(around ~10) sqls. In DBa_sql_profiles they are having TYPE as 'AUTO' and STATUs as ENABLED having a specific TASK_EXEC_NAME. So wanted to understand if any automatic job caused this which should have been turned off during this migration or somebody must have created those by manually running some task , which seems unlikely?
Date: Mon, 13 Sep 2021 02:04:49 +0530
Message-ID: <CAEjw_fiEKH6sgpVgkP7yKLvBvQpvuc+1treeOF8hwmedVEq-Fg_at_mail.gmail.com>
Hello Listers, We are seeing a few sqls running longer post 19c migration and when looking into the details , we found the new plan which it opting are having some sql profiles created/attached(having name SYS_SQLPROF****) and forcing the plan to go for a suboptimal ones. Want To understand how those are created for so many(around ~10) sqls. In DBa_sql_profiles they are having TYPE as 'AUTO' and STATUs as ENABLED having a specific TASK_EXEC_NAME. So wanted to understand if any automatic job caused this which should have been turned off during this migration or somebody must have created those by manually running some task , which seems unlikely?
Regards
Pap
-- http://www.freelists.org/webpage/oracle-lReceived on Sun Sep 12 2021 - 22:34:49 CEST