Database Memory & 4030/4031 (MOSC)

MOSC Banner

Why do we see 300+ entries in v$sql_shared_cursor reasons: Insert Direct Load mismatch for same SQL

edited Oct 20, 2021 1:29PM in Database Memory & 4030/4031 (MOSC) 1 commentAnswered

Why are we seeing 300+ entries in v$sql_shared_cursor with reasons of:
"...Insert Direct Load mismatch(...)..." for the same SQL

Oracle Version : 12.1.0.2
(I believe this was an issue in 12.1.0.1 
Bug 9380377 - INSERT / MERGE child cursor leak due to INST_DRTLD_MISMATCH - superceded (Doc ID 9380377.8))

SQL:

MERGE INTO X LCT 
USING 
( SELECT LC.ROWID RID 
FROM Y LS 
INNER JOIN X LC ON LC.STRUCTUREID = LS.ID 
WHERE LS.MASTERID = :B1 ) SRC ON 
(LCT.ROWID = SRC.RID) 
WHEN MATCHED THEN 
UPDATE 
SET LCT.LOT = :B6, LCT.APPSOURCE = SUBSTR(TRIM(:B5 ), 0, 255), LCT.APPVERSION = SUBSTR(TRIM(:B4 ), 0, 30), LCT.UPDATEDBY = SUBSTR(TRIM(:B3 ), 0, 10), LCT.CLIENTDEVICE = SUBSTR(TRIM(:B2 ), 0, 30), LCT.UPDATEDON = SYSTIMESTAMP

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center