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

PCC-02104: Unable to connect to Oracle

1 Answers  

---

ORA-30942: XML Schema Evolution error for schema 'string' table string column 'string'

1 Answers  

---

ORA-31671: Worker process string had an unhandled exception.

1 Answers  

---

RMAN-06462: no backupsets found on device DISK that match specification

1 Answers  

---

ORA-16403: shutdown in progress - remote connection is not permitted

1 Answers  

---

ORA-01189: file is from a different RESETLOGS than previous files

1 Answers  

---

ORA-19905: log_archive_format must contain %%s, %%t and %%r

2 Answers  

---

TNS-00270: %s: Terminal Error string

1 Answers  

---

ORA-02190: keyword TABLES expected

1 Answers  

---

ORA-37117: olapi history retention has been disabled

1 Answers  

---

ORA-32739: Hang analysis aborted due to failed heap re-grow

1 Answers  

---

IMG-00510: %s

1 Answers  

---