Answer / guest

Cause: A proscribed function was used in a SQL statement.
Certain functions such as SQLCODE and SQLERRM can be used
only in procedural statements.

Action: Remove the function call from the SQL statement. Or,
replace the function call with a local variable. For
example, the following statement is illegal: INSERT INTO
errors VALUES (SQLCODE, SQLERRM); However, you can assign
the values of SQLCODE and SQLERRM to local variables, then
use the variables in the SQL statement, as follows: err_num
:= SQLCODE; err_msg := SQLERRM; INSERT INTO errors VALUES
(err_num, err_msg);

Please add more information about this Error

ORA-16755: failed to set initialization parameter

1 Answers  

---

LPX-00115: element "~1S" is missing required attribute "~2S"

1 Answers  

---

ORA-22862: specified object identifier doesn't match existing object identifier

1 Answers  

---

TNS-00108: TNS_ADMIN not defined

1 Answers  

---

ORA-32108: max column or parameter size not specified

1 Answers  

---

NID-00350: string (number) string

1 Answers  

---

PLS-00536: Navigation through REF variables is not supported in PL/SQL.

1 Answers  

---

ORA-09909: Malloc of scratch buffer failed.

1 Answers  

---

RMAN-06161: error when inspecting auxiliary filename: string

1 Answers  

---

ORA-00449: background process 'string' unexpectedly terminated with error string

1 Answers  

---

SQL*Loader-00119: Invalid parallel file (data file) name on command line

1 Answers  

---

DRG-11104: Oracle Text error:

1 Answers  

---