RE: [EXTERNAL] Question on sql plan management
From: Beckstrom, Jeffrey <jbeckstrom_at_gcrta.org>
Date: Thu, 1 Sep 2022 11:33:27 +0000
Message-ID: <DM6PR09MB4677366C06DAFA22F902B60EDF7B9_at_DM6PR09MB4677.namprd09.prod.outlook.com>
Date: Thu, 1 Sep 2022 11:33:27 +0000
Message-ID: <DM6PR09MB4677366C06DAFA22F902B60EDF7B9_at_DM6PR09MB4677.namprd09.prod.outlook.com>
Now as I understand this above baselines will work as a shield for the plan regression issue. As because , even with the 19C optimizer feature, the queries are going to follow the captured 12.1 baseline path which is in the accepted state. But my question was , as 19C has a lot of enhancement done in the optimizer and those may actually benefit many or some of the existing queries, so what is the suggested way to get those new or better plans added safely to the existing sql queries or accepted baselines? Or should we rely on the oracle given the auto evolve task(SYS_AUTO_SPM_EVOLVE_TASK) to do this for us? And will the captured baselines cause issues for heavy hard parse queries?
Regards
Yudhi
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Sep 01 2022 - 13:33:27 CEST