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

NNL-00300: Cancelled server cache dump

1 Answers  

---

ORA-39012: Client detached before the job started.

1 Answers  

---

NNL-00537: set|show server [<server_name>] : set|show the currently managed server

1 Answers  

---

ORA-13514: Metric Capture too close to last capture, group string

1 Answers  

---

ORA-30376: prevent sharing of a parsed query of an explain rewrite session

1 Answers  

---

NNL-00512: Shows or sets the server's auto-refresh expiration period

1 Answers  

---

AMD-00118: output file "string" already exists

1 Answers  

---

PLS-01415: Use of aggregate value here

1 Answers  

---

ORA-29386: plan or consumer group string is mandatory and cannot be deleted or modified

1 Answers  

---

ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents

2 Answers   Wipro,

---

PCC-01301: Your Pro*PL/I authorization is about to expire

1 Answers  

---

ORA-31011: XML parsing failed

1 Answers  

---