How to Solve :
Oracle database error code ORA-32766 – instr with negative offset: use varchar semantics on LOBs
Oracle Database Error Code ORA-32766 Description :
instr with negative offset: use varchar semantics on LOBs
Error Cause:
The current varchar behavior is different. e.g. instr(abcd, cd, -2, 1) returns 3, whereas instr(to_clob(abcd), cd, -2, 1) returns 0, (i.e. no match), because the reverse search starts from offset -2, which points to c and moving backward, i.e. d is ignored. This is symmetric to instr(dcba,dc,2,1), which returns 0.
How to Solve :
ORACLE uses the same varchar semantics on LOBs (instr). Using the same example, instr(to_clob(abcd), cd, -2, 1) will return 3 as in the varchar case.
Filed under: How to Solve, Oracle 10g, Oracle 11g, Oracle 9i, Oracle Error Codes Etiketler: ora - 32766, 32766, about oracle ORA-32766 error, help ORA-32766 about, instr with negative offset: use varchar semantics on LOBs, ORA-32766 error code, ORA-32766 problem, Oracle 9i 10g 11g, Oracle Database Server Error Messages, Oracle Error Codes, oracle number 32766 error code, oracle ORA-32766 example
No Comment Yet
No Comment Yet
Recent Entries
- Oracle database error code ORA-29959 – error in the execution of the string routine for one or more of the index partitions
- Oracle database error code ORA-31601 – Function string cannot be called now that fetch has begun.
- Oracle database error code ORA-29958 – fatal error occurred in the execution of ODCIINDEXCREATE routine
- Oracle database error code ORA-31600 – invalid input value string for parameter string in function string
- Oracle database error code ORA-29957 – cannot create a function-based domain index on a string table
- Oracle database error code ORA-31604 – invalid string parameter “string” for object type string in function string
- Oracle database error code ORA-29961 – too many warnings occurred in the execution of ODCIIndex DDL routine
Search Oracle Error Codes and Descriptions:
Be The First To Comment
Similar Errors
Please Leave Your Comments Below