Answer / guest

Cause: An Oracle extension to the ANSI/ISO standard was
used. Specifically, aa pointer or nonconforming datatype
such as VARCHAR was used. For example, the offending code
might look like: EXEC SQL BEGIN DECLARE SECTION END-EXEC. 01
USERNAME PIC X(10) VARYING. EXEC SQL END DECLARE SECTION
END-EXEC. This informational message is issued by the FIPS
Flagger when FIPS=YES.

Action: none

Please add more information about this Error

ORA-32591: connect string too long

1 Answers  

---

LPX-00657: Invalid output PI '~S'.

1 Answers  

---

ORA-01273: STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher

1 Answers  

---

ORA-00232: snapshot controlfile is nonexistent, corrupt, or unreadable

1 Answers  

---

PCC-01515: FIPS warning: Undeclared host variable "string" at line number in file string

1 Answers  

---

ORA-16569: Data Guard configuration is not enabled.

1 Answers  

---

PCC-02040: CMD-LINE: Option selected, but no value provided

1 Answers  

---

ORA-28163: GRANT already specified

1 Answers  

---

ORA-12040: master rollback segment option not support by master site string

1 Answers  

---

PLS-00717: method 'string' does not have matching signature among existing methods

1 Answers  

---

LPX-00017: ~1sNodeName: <~2S>

1 Answers  

---

SQL*Loader-00515: Error getting CPU time

1 Answers  

---