Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-32766: instr with negative offset: use varchar semantics
on LOBs
- 1 Answers
- 3264 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 |
QSM-02161: see the reason why REFRESH_FAST_AFTER_ONETAB_DML is disabled
ORA-30502: system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
ORA-14113: partitioned table cannot have column with LOB datatype
ORA-15198: operation string is not yet available
ORA-01157: cannot identify/lock data file string - see DBWR trace file
RMAN-06425: <datafile pathname not available>
DRG-13311: USER_LEXER stored procedure name contains a semicolon
ORA-13348: polygon boundary is not closed
NNL-00035: File string or nested IFILEs not found.
ORA-14405: partitioned index contains partitions in a different tablespace
ORA-28001: the password has expired
LPX-00254: invalid XML declaration
Oracle Errors 
