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-31019: Recursive deletion snapshot too old for string/string
ORA-06578: output parameter cannot be a duplicate bind
ORA-07453: requested resource manager plan schema does not contain OTHER_GROUPS
RMAN-08016: channel string: starting datafile backupset restore
KUP-11003: bad data encountered while reading from file string
ORA-02308: invalid option string for object type column
ORA-13051: failed to initialize spatial object
ORA-39752: redundent column in partitioning and join columns is not allowed
ORA-24779: detach not allowed with open remote cursor
DRG-11441: gist numParagraphs string is invalid
EXP-00027: failed to calculate ORACLE block size
NNL-00345: Save_config_on_stop is currently OFF