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-12454: label string does not exist for policy string

1 Answers  

---

DRG-12407: invalid CTX REPEAT tag attribute (string)

1 Answers  

---

SQL*Loader-00127: Invalid maximum record size

1 Answers  

---

LSX-00151: invalid combination of attributes "ref" and "name"

1 Answers  

---

RMAN-00574: rman aborting due to errors read/writing dbms_pipe

1 Answers  

---

ORA-16081: insufficient number of processes for APPLY

1 Answers  

---

ORA-01693: max # extents (string) reached in lob segment string.string

1 Answers  

---

ORA-15041: diskgroup space exhausted

1 Answers  

---

ORA-09264: sptpa: error flagging process

1 Answers  

---

ORA-17500: ODM err:string

1 Answers  

---

PLS-00485: in exception handler, 'string' must be an exception name

1 Answers  

---

DRG-12513: valid stop classes are: string

1 Answers  

---