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

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.............

2807

---

NZE-28890: Entrust Login Failed

1884

---

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

1959

---

ORA-16627: No standby databases support the overall protection mode.

3993

---

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

1711

---

ORA-16626: failed to enable specified object

2225

---

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

3865

---

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

2158

---

ORA-26095: unprocessed stream data exists

3583

---

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

2734

---

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

3386

---

ORA-16516: The current state is invalid for the attempted operation.

8824

---

IMP-00064: Definition of LOB was truncated by export

6418

---

IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier

3180

---

ORA-26032: index string.string loading aborted after string keys

2112

---