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

PLS-00253: Formal parameter string missing in the parameters clause

1 Answers  

---

ORA-01225: thread number string is greater than MAXINSTANCES string

1 Answers  

---

ORA-09829: pw_createPorts: server call pws_start_instance failed.

1 Answers  

---

PCC-02384: Missing array length specifier

1 Answers  

---

DRG-50913: first document requested string is not a positive number

1 Answers  

---

ORA-22160: element at index [string] does not exist

1 Answers   ICICI,

---

LPX-00105: element "~S" is not empty as required by the DTD

1 Answers  

---

ORA-31612: Allocation of process descriptor failed.

1 Answers  

---

NNL-00406: Canonical name: string

1 Answers  

---

ORA-31698: Error stack buffer size must be specified and must be greater than 0.

1 Answers  

---

ORA-24270: a row already exists in the string table for these parameters

1 Answers  

---

PLS-00997: no cursor return types allowed in this beta version

1 Answers  

---