Answer Posted / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, a nonconforming SQL statement such as
PREPARE was used. For example, the offending code might look
like: EXEC SQL PREPARE SQL-STMT FROM :HV END-EXEC. 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 statement.

Please add more information about this Error

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

8824

---

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

3389

---

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

3993

---

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

1626

---

ORA-26084: direct path context already finished

1954

---

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

2160

---

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

1771

---

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

2112

---

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

2736

---

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

1960

---

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

6752

---

ORA-26095: unprocessed stream data exists

3585

---

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

1973

---

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

3867

---

IMP-00064: Definition of LOB was truncated by export

6420

---