ORA-32766: instr with negative offset: use varchar semantics
on LOBs
Answer / guest
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.
Action: 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.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 0 No |
ORA-31202: DBMS_LDAP: LDAP client/server error: string
ORA-16605: unable to delete template, template is in use
ORA-00484: LMS* process terminated with error
ORA-15173: entry 'string' does not exist in directory 'string'
ORA-06814: TLI Driver: the SPX device file could not be opened
QSM-01065: materialized view, string, cannot compute measure, string, in the query
ORA-13637: Executing or modifying task string is disallowed until the task is reset to its initial state.
NNL-00835: Average delete processing time: string
RMAN-06116: cannot crosscheck unavailable object
ORA-38762: thread string redo log with scn string could not be found
DRG-11610: URL store: unable to read local file specified by string
ORA-12341: maximum number of open mounts exceeded