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

ORA-31490: could not attach to LogMiner session

1 Answers  

---

DRG-10579: must provide text query criteria

1 Answers  

---

SQL*Loader-00943: incorrect datafile string specified for table string partition string

1 Answers  

---

PCB-00635: This attribute is only valid for Internal LOB types

1 Answers  

---

ORA-09789: sllfsk: unable to read file.

1 Answers  

---

IMG-00579: extra quantize argument

1 Answers  

---

ORA-13355: SDO_ORDINATE_ARRAY not grouped by number of dimensions specified

1 Answers  

---

TNS-00072: * start - start up process_name

1 Answers  

---

ORA-22283: filename contains characters that refer to parent directory

1 Answers  

---

ORA-36704: (XSRELTBL06) workspace object should be dimensioned by workspace object.

1 Answers  

---

LSX-00232: invalid unsigned long "~S"

1 Answers  

---

TNS-00519: Operating system resource quota exceeded

2 Answers  

---