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-15186: ASMLIB error function = [string], error = [string], mesg = [string]

1 Answers  

---

ORA-37113: OLAP API initialization error: (string)

1 Answers  

---

NMP-00010: memory exhausted

1 Answers  

---

ORA-09762: sNeXT_instanceName: translation error.

1 Answers  

---

NZE-28807: Cannot update the data source.

1 Answers  

---

ORA-31019: Recursive deletion snapshot too old for string/string

1 Answers  

---

ORA-04935: unable to get/convert SCN recovery lock

1 Answers  

---

ORA-13339: LRS polygon clipping across multiple rings

1 Answers  

---

PLS-00655: only functions can be declared as PIPELINED

1 Answers  

---

ORA-29322: SCN string size too long -- maximum size 58 bytes/characters

1 Answers  

---

ORA-39021: Database compatibility version string is not supported.

1 Answers  

---

ORA-06954: Illegal file name

1 Answers  

---