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

NNO-00272: line string; invalid DIT/DN

1 Answers  

---

ORA-00263: there are no logs that need archiving for thread string

1 Answers  

---

ORA-32639: Aggregate functions on reference MODELs are not allowed

1 Answers  

---

ORA-12541: TNS:no listener

1 Answers  

---

ORA-26514: object 'string.string' not found

1 Answers  

---

PCB-00581: "string" used as both host variable and indicator

1 Answers  

---

SQL*Loader-00516: Control file (string) has no contents

1 Answers  

---

RMAN-06499: skipping archive log file string; already backed up string time(s)

1 Answers  

---

ORA-09291: sksachk: invalid device specified for archive destination

1 Answers  

---

ORA-16070: parameter string contains an invalid REGISTER attribute value

1 Answers  

---

TNS-12597: TNS:connect descriptor already in use

1 Answers  

---

LFI-01503: Max filename size exceeded generating filename.

1 Answers  

---