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-32152: Cannot perform operation on a null number

1 Answers  

---

ORA-09812: Unable to get user clearance from connection

1 Answers  

---

PLS-00607: SQLJ Object Types can have only SQLJ Types as its supertype or subtype

1 Answers  

---

ORA-18004: outline already exists

1 Answers  

---

ORA-19697: standby controlfile not found in backup set

1 Answers  

---

NID-00321: Proceeding with operation

1 Answers  

---

ORA-36634: (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.

1 Answers  

---

ORA-39019: invalid operation type string

1 Answers  

---

ORA-14644: table is not subpartitioned by Hash method

1 Answers  

---

RMAN-06103: duplicate qualifier found in REPORT command: string

1 Answers  

---

ORA-14132: table cannot be used in EXCHANGE

1 Answers  

---

ORA-19590: conversation already active

1 Answers  

---