Answer / guest

Cause: This situation occurs when the database resource
guard attempts to set database configuration property values
into the database by issuing "ALTER SYSTEM" or "ALTER
DATABASE" command. Typical causes of this error are: a) The
values of log transport related properties have syntax
errors; b) The Value of LogArchiveTrace is out of range; c)
Database initialization parameter STANDBY_FILE_MANAGEMENT
cannot be set to AUTO because the database compatability is
not set to 9.0.0.0.0 or higher.

Action: Check the Data Guard broker log to see which
property has the problem and reset the property correctly.

Please add more information about this Error

ORA-02304: invalid object identifier literal

1 Answers  

---

ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists

1 Answers  

---

ORA-24776: cannot start a new transaction

1 Answers  

---

NID-00121: Database should not be open

1 Answers  

---

PLS-01405: Under ANSI's grammar, numeric data represented in exponent notationmust use an uppercase E

1 Answers  

---

---

ORA-01520: number of data files to add (string) exceeds limit of string

1 Answers  

---

QSM-02138: agg(expr) requires correspondng agg(expr*expr) function

1 Answers  

---

ORA-09791: slembdf: translation error, unable to translate error file name.

1 Answers  

---

LPX-00314: an internal failure occurred

1 Answers  

---

RMAN-10034: unhandled exception during execution of job step number, error unknown

1 Answers  

---

IMP-00053: Import mode incompatible with Export dump file

1 Answers  

---

TNS-12206: TNS:received a TNS error during navigation

1 Answers  

---