Monday, July 15, 2019

How to fix ORA-01745: invalid host/bind variable name ORA-600[qcscbndv1]

Cause: A colon in a bind variable or INTO specification was followed by an inappropriate name, perhaps a reserved word.
Action: Change the variable name and retry the operation.
-----------------------

As per note "ORA-600[qcscbndv1], [65535, ORA-600[Kghssgfr2], ORA-600[17112] Instance Failure ( Doc ID 1311230.1 ) "

The number of bind variables on a SQL statement is limited to 65536, and any number greater than 65536 will cause the error. 

This can affect any version of Oracle.

CHANGES
This SQL statement with the many bind variables will never have run successfully before.
It will be new development, or newly generated SQL.

CAUSE
This ORA-600[qcscbndv1] error is due to exceeding the limit of the number of bind variables allowed on a SQL statement. When the limit is reached, the ORA-600[qcscbndv1] is raised, the process is terminated, and the cleanup is initiated. The cleanup itself is affected and results in the secondary memory corruption errors that accompanies this problem.

SOLUTION
This is an application design issue. The number of bind variables on a SQL statement is limited to 65536, and any number greater than 65536 will cause the error.

This can affect any version of Oracle.
Prior to 11.2 (or 10.2.0.5), this error would be reported as ORA-7445[opiaba].
If patch 6614936 was applied to these earlier releases, the error would be ORA-600[qcscbndv1].

To resolve this problem, please modify the application to limit the number of bind variables on the SQL statement to 65535 or less.

No comments:

Post a Comment