Bind Values Misordered After Loading Large PL/SQL Unit Without Carriage Returns
(Doc ID 1386413.1)
Last updated on DECEMBER 16, 2019
PL/SQL - Version 10.2.0.1 to 126.96.36.199 [Release 10.2 to 11.2] Information in this document applies to any platform.
When loading a large PL/SQL program unit (package, procedure, function, or trigger) that does not contain any line feeds or carriage returns using SQL*Developer or some other API or tool besides SQL*Plus, the PL/SQL code contains SQL queries that returns wrong results or DML statements that are either failing with strange errors such as ORA-01722 or end up affecting the wrong rows. When looking closer using a SQL trace, the bind values appear to be out of order or corrupt.
Stripped line feeds or carriage returns or perhaps the code has been modified and now exceeds 64K characters or causes a SQL statement with binds to span both sides of the 64K boundary.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!