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 |
DRG-10583: TRUNCATE INDEX failed: string
ORA-09273: szrfc: error verifying role name
ORA-14280: all rows in table do not qualify for specified subpartition
LPX-00608: Repeated declaration of '~1S' in element '~2S'.
ORA-28138: Error in Policy Predicate
ORA-09772: osnpmetbrkmsg: message from host had incorrect message type
ORA-30118: syntax error at 'string' at the end of input
O2F-00333: An unexpected token appeared where a keyword was expected in the INTYPE file
ORA-22627: tc [string] must be that of object/varray/nested table
RMAN-03037: Spooling started in log file: string
ORA-02205: only SELECT and ALTER privileges are valid for sequences
ORA-30129: invalid function argument received