Sql patch creation impact in busy systems
From: GG <grzegorzof_at_interia.pl>
Date: Mon, 9 Nov 2020 19:07:21 +0100
Message-ID: <6d0c517f-773c-faca-6304-a5976fefaacd_at_interia.pl>
Date: Mon, 9 Nov 2020 19:07:21 +0100
Message-ID: <6d0c517f-773c-faca-6304-a5976fefaacd_at_interia.pl>
Hello,
got hit by some all_synonyms bug in PDB 12.1, quick solution seems to be add hint via
sys.dbms_sqldiag_internal.i_create_patch (for 3 sql_ids)
but is it safe in ExaCS environment running hundreds of sessions ?
Should we expect spike not only casued by hard parse for those sql_ids ?
Easy fallback via drop sql patch but same questions remain.
Have not find anything documented how this works .
Regards.
Greg
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Nov 09 2020 - 19:07:21 CET