Disabling one SQL PROFILE and its impact
Hello
We have inherited an 11g R2 database. It is a 2 node RAC on Linux
There is a query / batch report that we noticed thru SQL Monitoring which when run takes 5 plus hours to run. When we looked at the execution plan, we noticed that it is using a PROFILE
So it seems that previous DBAs handling this database came across this SQL and based on the SQL Tuning recommendation, chose to accept the SQL Profile. Since this PROFILE has been in place for a while now (it was created in 2016), we are wondering that perhaps at that time using the SQL Profile was a better option but it has been 4 years and perhaps by disabling that profile, we could now get a better execution plan as long as we make sure that the statistics on the underlying tables are up to date.