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

RMAN-06187: controlfile copy string not found or out of sync with catalog

1 Answers  

---

RMAN-06542: file string is excluded from whole database backup

1 Answers  

---

ORA-00274: illegal recovery option string

1 Answers  

---

ORA-19734: wrong creation SCN - control file expects converted plugged-in datafile

1 Answers  

---

ORA-07636: smsdbp: $MGBLSC failure

1 Answers  

---

ORA-01954: DEFAULT ROLE clause not valid for CREATE USER

1 Answers  

---

ORA-34350: (MXDSS06) string is an open analytic workspace.

1 Answers  

---

DRG-11127: inconsistent index policy with trained rule

1 Answers  

---

ORA-14046: a partition may be split into exactly two new partitions

1 Answers  

---

ORA-25140: %s space policy cannot be specified for the string extent management

1 Answers  

---

TNS-01172: Listener has shut down since all listen addresses have been deallocated

1 Answers  

---

RMAN-06197: Total System Global Area string bytes

1 Answers  

---