Answer Posted / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, a nonconforming keyword such as
NOTFOUND, STOP, RAISE, or DO was used in the WHENEVER
statement. (Note that NOT FOUND is ANSI-compliant.) For
example, the offending code might look like: EXEC SQL
WHENEVER SQLERROR STOP; This informational message is issued
by the FIPS Flagger when FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, do not use the nonconforming keyword.

Please add more information about this Error

ORA-26084: direct path context already finished

1937

---

NZE-28890: Entrust Login Failed

1863

---

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

1934

---

In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.

2861

---

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

1926

---

IMG-02003: 2FF03 - incorrect color histogram feature specification

1695

---

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

1754

---

ORA-26028: index string.string initially in unusable state

3848

---

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

6733

---

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

2399

---

ORA-26076: cannot set or reset value after direct path structure is allocated

1950

---

ORA-26094: stream format error: input column overflow

2785

---

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

2140

---

IMP-00064: Definition of LOB was truncated by export

6395

---

invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity

3368

---