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

DGM-16943: You must connect to instance "string" and issue the command again.

1 Answers  

---

ORA-09700: sclin: maximum number of latches exceeded

1 Answers  

---

ORA-09718: osnsui: cannot set up user interrupt handler.

1 Answers  

---

ORA-24274: no row exists in the string table for these parameters

1 Answers  

---

SQL*Loader-00431: illegal NULLIF or DEFAULTIF clause specified for nested table column string

1 Answers  

---

---

NNL-00227: Request-processing delay is currently disabled

1 Answers  

---

ORA-23410: materialized view "string"."string" is already in a refresh group

1 Answers  

---

ORA-24325: this OCI operation is not currently allowed

1 Answers  

---

ORA-30087: Adding two datetime values is not allowed

1 Answers   Oracle,

---

AMD-00140: internal error: [string] [string] [string] [string] [string]

1 Answers  

---

ORA-02736: osnfpm: illegal default shared memory address

1 Answers  

---

NNL-00418: Attributes Mapped: number

1 Answers  

---