Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-32766: instr with negative offset: use varchar semantics
on LOBs
- 1 Answers
- 3162 Views
- I also Faced
- E-Mail Answers
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-29803: missing ANCILLARY keyword
ORA-40004: penalty must be negative for BLAST-N
NNL-00973: Query state: number
ORA-22974: missing WITH OBJECT OID clause
ORA-06423: NETCMN: Error in receiving data
ORA-16546: missing or invalid piece
ORA-02716: osnpgetdatmsg: message from host had incorrect message type
ORA-25321: enqueue failed, user property specified but queue string.string is not an 8.1 style queue
ORA-19592: wrong string conversation type
NZE-29153: RSA self-test failure
ORA-31696: unable to export/import string using client specified string method
ORA-09706: slsget: get_process_stats error.
Oracle Errors 
