Answer / guest

Cause: The user attempted to change the control program's
local trace level, and the program encountered an error
while changing the level. Usually the problem is that
tracing was enabled for the first time (by changing the
trace level from OFF to something else) and the trace file
is not writeable by the control program.

Action: Check to see that the trace file is writeable. Your
documentation will tell you the name of the trace file.

Please add more information about this Error

ORA-02141: invalid OFFLINE option

1 Answers  

---

DRG-12302: invalid column list

1 Answers  

---

ORA-26571: %s.string.string: number of arguments (string) does not match replication catalog

1 Answers  

---

DRG-50916: last document string is less than first document

1 Answers  

---

ORA-23303: application raised generic exception during deferred RPC

1 Answers  

---

ORA-30387: invalid rewrite mode for REWRITE_EQUIVALENCE API

1 Answers  

---

TNS-12549: TNS:operating system resource quota exceeded

1 Answers  

---

DRG-50946: Invalid unary operator for theme index

1 Answers  

---

ORA-01234: cannot end backup of file string - file is in use or recovery

1 Answers  

---

ORA-39059: dump file set is incomplete

1 Answers  

---

PCC-02132: CMD-LINE: Could not allocate memory

1 Answers  

---

RMAN-06103: duplicate qualifier found in REPORT command: string

1 Answers  

---