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-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined

1 Answers  

---

ORA-40221: maximum target cardinality exceeded

1 Answers  

---

QSM-02182: PCT is enabled through a join dependency

1 Answers  

---

ORA-33247: (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.

1 Answers  

---

ORA-12823: default degree of parallelism may not be specified here

1 Answers  

---

ORA-00030: User session ID does not exist.

1 Answers  

---

LPX-00231: invalid character ~1u ('~2c') found in a Name or Nmtoken

1 Answers  

---

PLS-00925: native compilation failed: Unable to create C file (string string)

1 Answers  

---

ORA-16219: This database is not preparing to switch over.

1 Answers  

---

ORA-01175: data dictionary has more than the string files allowed by the instance

1 Answers  

---

EXP-00034: error on rowid: file# number block# number slot# number

1 Answers  

---

ORA-30354: Query rewrite not allowed on SYS relations

1 Answers  

---