Answer Posted / guest

Cause: When MODE={ANSI | ANSI14}, an attempt was made to use
the WHENEVER SQLWARNING statement without declaring the
SQLCA. When MODE={ANSI | ANSI14}, declaring the SQLCA is
optional, but to use the WHENEVER SQLWARNING statement, the
SQLCA must be declared.

Action: Remove all WHENEVER SQLWARNING statements from the
program or declare the SQLCA by hardcoding it or copying it
into the program with the INCLUDE statement.

Please add more information about this Error

How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?

2719

---

When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............

2797

---

when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly

2225

---

IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1616

---

ORA-26084: direct path context already finished

1945

---

ORA-07497: sdpri: cannot create trace file 'string'; errno = string.

2795

---

ORA-16626: failed to enable specified object

2210

---

ORA-26029: index string.string partition string initially in unusable state

2151

---

ORA-26079: file "string" is not part of table string.string

1954

---

if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires

2692

---

ORA-26027: unique index string.string partition string initially in unusable state

6741

---

IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2727

---

ORA-26030: index string.string had string partitions made unusable due to:

1937

---

ORA-26082: load of overlapping segments on table string.string is not allowed

1765

---

RMAN-05017: no copy of datafile number found to recover

2410

---