Re: Any way to capture spatial bind data?

From: Dominic Brooks <dombrooks_at_hotmail.com>
Date: Thu, 7 Dec 2023 14:48:31 +0000
Message-ID: <DBAPR02MB6470E3B9A7F02CC7543CE14AA18BA_at_DBAPR02MB6470.eurprd02.prod.outlook.com>



Is that a typo or did you mix up your events? 10046 - sql trace
10053 - optimizer trace



From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> on behalf of Osman DINC <dinch.osman_at_gmail.com> Sent: 07 December 2023 07:45
To: oracle-l_at_freelists.org <oracle-l_at_freelists.org> Subject: Any way to capture spatial bind data?

Hi all;

I am trying to troubleshoot an ORA-3137 [3146] error.

I have read Doc ID 31625618.8. In my case,it is a select statement not a dml. I guess, Most probably, it is a client driver issue but i want to diagnose more if possible. Client application is using an universal data access component (UniDAC for Delphi) and application does not have a detailed logging mechanism.

Problematic sql statement is working sometimes and for some bind values, it gets ORA-3137. We are using ASO(Advanced Security Option) and cursor_sharing is forced. Original statement is using literals.

Question is : I wonder if there is any way to capture spatial bind data? Its datatype is 121.

According to the v$sql_bind_capture documentation in Database Reference,

https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/V-SQL_BIND_CAPTURE.html#GUID-D353F4BE-5943-4F5B-A99B-BC9505E9579C

"Bind values are not always captured for this view. Bind values are displayed by this view only when the type of the bind variable is simple (this excludes LONG, LOB, and ADT data types) and when the bind variable is used in the WHERE or HAVING clauses of the SQL statement."

I traced with 10056,10043 and also tried errorstack for ORA-3137 and could not capture bind values in trace files.

Regards,

Osman DİNÇ

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Dec 07 2023 - 15:48:31 CET

Original text of this message