Answer / guest

Cause: The option UNSAFE_NULL=YES has been used with DBMS=V6
or DBMS=NATIVE (the default) or has been used with
MODE=ANSI/ANSI14/ANSI13.

Action: Either specify DBMS=V7 and MODE=ORACLE (the default)
when using UNSAFE_NULL=YES or do not use UNSAFE_NULL=YES.

Please add more information about this Error

ORA-23406: insufficient privileges on user "string"

1 Answers  

---

ORA-38483: invalid FUNCTION/PACKAGE/TYPE name: "string"

1 Answers  

---

ORA-29361: value string is outside valid range of 0 to 100

1 Answers  

---

ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

1 Answers  

---

ORA-01666: controlfile is for a standby database

1 Answers  

---

---

QSM-00507: no dimensions could be found

1 Answers  

---

PROC-00020: ORACLE_HOME environment not set

1 Answers  

---

TNS-12589: TNS:connection not bequeathable

1 Answers  

---

PLS-01708: In searched DELETE, UPDATE or INSERT, table must not appear in FROM clause of subqueries in search condition

1 Answers  

---

ORA-14045: only one partition may be modified

1 Answers  

---

QSM-02055: mv references a packed object table or view

1 Answers  

---

ORA-00822: MMAN process terminated with error

1 Answers  

---