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

PCB-00557: USING clause can only be used on a PREPAREd dynamic statement

1 Answers  

---

NZE-29106: Cannot import PKCS #12 wallet.

1 Answers  

---

ORA-16164: LGWR network server host detach error

1 Answers  

---

ORA-32150: Cannot perform operation on a null timestamp

1 Answers  

---

ORA-15029: disk 'string' is already mounted by this instance

1 Answers  

---

ORA-25144: invalid option for CREATE TABLESPACE with TEMPORARY contents

1 Answers  

---

ORA-00025: failed to allocate string

1 Answers  

---

SQL*Loader-00421: error converting data

1 Answers  

---

NNL-00545: Displays query request statistics

1 Answers  

---

ORA-31151: Cyclic definition encountered for string: "string"

1 Answers   FBCH,

---

PCC-02405: Variable is of undefined type

1 Answers  

---

RMAN-08046: channel string: starting compressed full datafile backupset

1 Answers  

---