When tuning a SQL that very long statement ( OGL system ). An error at the state of GET PLAN was returned:
"ORA-06550: line 2, column 22"
"PLS-00172: string literal too long"
Invalid SQL statement.
Possible causes of this error include:
- The schema for the SQL statement is not selected.
- You are using PL/SQL code or more than one SQL statement.
The Tuning Lab only processes a single .
SELECT/INSERT/DELETE/UPDATE. For multiple SQL statements .
or PL/SQL code, first use the SQL Scanner module to .
extract the SQL statements.
- The parameter from the SQL Scanner - Local Variable
Conversion was not replaced in the SQL statement.==
This problems occurs when handling long invalid SQL.
WORKAROUND:
None,
STATUS:
Waiting for fix in a future release Quest SQL Optmizer for Oracle.
N:B
Note that this only happens when have a very long string (longer than 32767 characters) and your SQL is not recognized by the SQL Optimizer. If you
have a SQL that SQL Optimizer supports, you will not experience this error even if your SQL is longer than 32767.
