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-04932: increment or adjust of sequence number failed

1 Answers  

---

ORA-26502: error resignal

1 Answers  

---

SQL*Loader-00111: Invalid number of rows for bind array or data saves

1 Answers  

---

ORA-00130: invalid listener address 'string'

2 Answers  

---

NNC-00051: message content error

1 Answers  

---

ORA-29382: validation of pending area failed

1 Answers  

---

KUP-04056: internal error: OCI error while fetching record: number

1 Answers  

---

ORA-19597: file string blocksize string does not match set blocksize of string

1 Answers  

---

PCB-00108: Unable to open list file "string"

1 Answers  

---

ORA-17613: Failed to initialize Oracle Disk Manager library: string

1 Answers  

---

ORA-14620: DEFAULT subpartition already exists

1 Answers  

---

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

1 Answers  

---