4/28/23, 4:11 PM 3322619 - Oracle SBP 202302 (19.
202302 (19.18DBRU) Query Performance Issue Occurs with high "Direct Path Read" on Non-Exadata
SAP Note
3322619 - Oracle SBP 202302 (19.18DBRU) Query
Performance Issue Occurs with high "Direct Path Read" on
Non-Exadata
Component: BC-DB-ORA (Oracle), Version: 3, Released On: 12.04.2023
Symptom
After patching database with SBP 202302 (19.18DBRU), high "direct path read" is observed for SQL statements which previously used buffer cache
reads.
SQL statements which may have same execution plan after patching database to 19.18 (SBP 202302), but all executions are doing "direct path read"
leading to overall high Physical/disk Reads then, you are affected by this Bug.
Remark: This SAP Hotnews is relevant for Non-Exadata Storage Environments only!
Other Terms
SBP 202302, 19.18DBRU, Performance, Direct Patch Read, MOS Doc ID 2940472.1
Reason and Prerequisites
There was a patch (31626438) introduced in SBP 202105 (19.11DBRU) as disabled by default, but it is then enabled in 19.18 by default. It is causing
"direct path read" for objects that otherwise could be cached in the buffer cache and use the cache reads for subsequent executions.
To check if that _FIX_CONTROL is enabled, execute the following:
SELECT BUGNO, VALUE FROM GV$SYSTEM_FIX_CONTROL WHERE BUGNO=31626438;
BUGNO VALUE
---------- -------
31626438 1 <<<<<< "1" means it is enabled
This bug fix lowers the object threshold triggering "table access full" operations to make use of "direct path read" into PGA (private memory) instead
of "db file scattered read" into SGA (shared memory).
Because it goes into PGA, this means all subsequent executions cannot leverage any buffer access via SGA for common buffers.
You will likely see the same execution plan, but more physical IO per SQL ID for such operations due to blocks going to PGA over and over again
causing high Physical Reads in the database.
If you obtain 10046 trace of the problem SQL. From tkprof output of the 10046 trace, you will observe difference in "direct path read" behaviour before
and after 19.18 Patching.
Example:
SBP 202302 (19.18DBRU):
Event waited on Times Max. Wait Total Waited
------------------------------- Waited ---------- --------------
SQL*Net message to client 2 0.00 0.00
Disk file operations I/O 1 0.00 0.00
db file sequential read 3 0.00 0.00
PGA memory operation 2 0.00 0.00
ASM IO for non-blocking poll 122 0.00 0.00
direct path read 45 0.00 0.09 <<<<<<<<<<< Direct Path Reads
db file scattered read 1 0.00 0.00
SQL*Net message from client 2 0.12 0.13
Before SBP 202302 (19.18DBRU):
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited <<<<<<<<<< No "direct path read" Observed below
------------------------------- Waited ---------- --------------
SQL*Net message to client 2 0.00 0.00
Disk file operations I/O 1 0.00 0.00
db file sequential read 3 0.00 0.00
db file scattered read 98 0.00 0.16
SQL*Net message from client 2 0.12 0.13
https://userapps.support.sap.com/sap/support/sfm/notes/print/0003322619?language=E&token=7255D72971E9954F9CFFD349FC7AF97D 1/2
4/28/23, 4:11 PM 3322619 - Oracle SBP 202302 (19.18DBRU) Query Performance Issue Occurs with high "Direct Path Read" on Non-Exadata
Solution
Workaround:
If your database is patched with SBP 202302 (19.18DBRU) on Non-Exadata Storage Environment, it is strongly advised to disable Fix 31626438.
Therefore we need to add "_FIX_CONTROL"="31626438:OFF" to the "_FIX_CONTROL" statement available in the Oracle SBP 202302 READMEs.
So in total the final statement is:
ALTER SYSTEM SET "_FIX_CONTROL"=
'5099019:ON','6055658:OFF','6120483:OFF','6399597:ON','6430500:ON','6972291:ON',
'7324224:OFF','7658097:ON','8932139:ON','8937971:ON','9196440:ON','9495669:ON',
'13627489:ON','13699643:OFF','14255600:ON','14595273:ON','18405517:2','20355502:10',
'20636003:OFF','22387320:ON','22540411:ON','23738304:OFF','24561942:ON','25643889:ON',
'26536320:ON','27321179:ON','27466597:ON','28173995:ON','28234255:3','28414968:3',
'28498976:ON','28558645:ON','28602253:ON','28708585:ON','28835937:ON','28999046:ON',
'29302565:ON','29304314:ON','29385774:ON','29450812:ON','29487407:ON','29687220:ON',
'29867728:ON','29930457:ON','30008456:ON','30018126:ON','30142527:ON','30195773:ON',
'30231086:ON','30235691:ON','30249927:ON','30470947:ON','30483217:ON','30537403:ON',
'30776676:ON','30786641:ON','30887435:ON','31009032:ON','31082719:ON','31143146:ON',
'31266779:ON','31444353:1','31487332:ON','31496840:ON','31579233:ON','31626438:OFF',
'31821701:ON','31961578:ON','31988833:ON','32014520:ON','32107621:ON','32205825:ON',
'32212062:ON','32302470:ON','32396085:ON','32408640:ON','32578113:ON','32614157:ON',
'32851615:ON','32874571:ON','33297275:ON','33303725:ON','33369863:ON','33547527:ON'
COMMENT='SAP_191800230117_202302 RECOMMENDED SETTINGS + SAP Hotnews 3322619'
SCOPE=BOTH;
Database restart is not required for above mentioned workaround if you already have restarted your database after setting the SBP 202302
"_FIX_CONTROL".
(The no-need to restart the database is an exception here to the normal "_FIX_CONTROL" update after a SBP installation as just this special
"_FIX_CONTROL" is added.)
This issue has been resolved via Patch for bug 35246710 even if "FIX_CONTROL" 31626438 is still enabled (=1) and it is scheduled for inclusionsion
into SBP 202305 (19.19DBRU).
Manual Activities
This document is referenced by
SAP Note/KBA Title
2799930 Patches for 19c: Grid Infrastructure (/sap/support/notes/2799930 )
2799920 Patches for 19c: Database (/sap/support/notes/2799920 )
https://userapps.support.sap.com/sap/support/sfm/notes/print/0003322619?language=E&token=7255D72971E9954F9CFFD349FC7AF97D 2/2
