Seeing Flood Of Trace Files With Entries Like This: KtsmgCursorScan: Exit For Non-directpath
(Doc ID 2920887.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.12.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
Database producing trace files with following text over and over.
ktsmgCursorScan: Exit for non-directpath Select in CURBOUND: (ext_sql_id: aaaaaaaaa, int_sql_id: '12346', hash: 3411294691) elapsed: 16731 fetchtm: 0 curtime: 1673187324 sttm: 0 QRY_EXPRN_TIME(secs): 1800 max_query_mql: 0 opcode: 3 curstate: 3 is_dirpath_datapump: 0
ktsmgCursorScan: Exit for non-directpath Select in CURBOUND: (ext_sql_id: bbbbbbbbb, int_sql_id: '4165', hash: 3072231849) elapsed: 167318 fetchtm: 0 curtime: 1673187324 sttm: 0 QRY_EXPRN_TIME(secs): 1800 max_query_mql: 0 opcode: 3 curstate: 3 is_dirpath_datapump: 0
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |