ORA-03106 exception when running a SELECT statement

[urban.tamas]

I had a very similar problem when TOAD threw an ORA-03106 exception when running a script if dbms output was enabled.

I am facing the same problem, but the difference is that I am running a query on a table that contains 2 XMLTYPE columns. I always get this Oracle exception for a "SELECT *" query. The only solution is to manually modify the XMLTYPE columns using the xmlserialize() method in the Editor.

I am using TOAD 2026R1 x64 version. The connection was established with TNS, Oracle 19c client, 64-bit version. The database character set is Latin-2.

[JohnDorlon]

Hi Tamas,

I am unable to reproduce this. I believe the problem is on Oracle's side, not Toad's.

You may have better luck using Toad in no-client mode, or with a newer client.

You can try turning on spool sql to see if that reveals anything.

If nothing else works, you can have Toad automatically add XMLSerialize for you with these settings. I would do this as a last resort though. It may not work right with complicated SQL.