Answer / guest

Cause: The destination was defined in the INIT.ORA file with
wrong syntax. The Data Guard broker failed to update the
destination when the log transport was turned on.

Action: Check the Data Guard broker log to see which
database has the problem. Fix the syntax error in the
INIT.ORA file or remove the entry from the INIT.ORA file.
Check if the syntax of the log transport related properties
are correct.

Please add more information about this Error

ORA-12925: tablespace string is not in force logging mode

1 Answers  

---

ORA-37121: AW Spreadsheet invalidated

1 Answers  

---

SQL*Loader-00459: error fetching numeric value for sequence on column (string)

1 Answers  

---

ORA-32106: array fetch not allowed without setBuffer on all columns

1 Answers   Oracle,

---

ORA-13035: Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object

1 Answers  

---

PCB-00241: A host variable is required here

1 Answers  

---

ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA

1 Answers  

---

RMAN-12020: error on step filtered for normal output string

1 Answers  

---

ORA-14407: partitioned table contains subpartitions in a different tablespace

1 Answers  

---

ORA-14086: a partitioned index may not be rebuilt as a whole

1 Answers  

---

PCC-02428: Buffer type is incompatible with LOB type

1 Answers  

---

ORA-15012: ASM file 'string' does not exist

1 Answers  

---