Re: Troubleshooting ORA-12704 errors
Date: Thu, 03 Oct 2019 21:27:44 +0100
Message-ID: <DE3DD14B-E53B-4D31-ACD4-AA70A3561CF6_at_dunbar-it.co.uk>
Hi Chris,
Your columns and binds are looking like they use different and incompatible charactersets. Some charactersets cannot be compared - resulting in what you are seeing here. When you changed from varchar2 to nvarchar2 you were using the same characterset in the two sides of the comparison.
In a eord, or two, you are now comparing apples, before it was apples and oranges. You see this in the csid values in the two ora-12704 lines in your original post.
I might be wrong but usually, binds appear before the exec in the trace. From the look of things your sql is parsed then the error is detected, but it doesn't appear as a parse error line, then the cursor is closed - hard closed - so no exec and that's possiblt why the binds are missing.
Most of the ora-12704 lines are the same as the binds would be, the just have different names.
HTH
Chees,
Norm.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Oct 03 2019 - 22:27:44 CEST