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-00323: Current log of thread string not useable and all others need archiving

1 Answers  

---

ORA-01573: shutting down instance, no further change allowed

1 Answers  

---

LFI-00130: Input option specified on output only file.

1 Answers  

---

NNC-00050: message format error

1 Answers  

---

ORA-29966: The only binding of an operator cannot be dropped

1 Answers  

---

ORA-24015: cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist

1 Answers  

---

I've got a database (Oracle Database 10g Enterprise Edition Release 10.2.0.2.0) installed on a server. Via the network I try to connect to the database via a frontend DEVELOPER 2000 R 2.1 (SQL*Plus: Release 3.3.4.0.0 ) while connecting to database I've got the following error- message: ORA-12637: Packet receive failed

2 Answers  

---

ORA-23361: materialized view "string" does not exist at master site

1 Answers  

---

SQL*Loader-00103: Invalid log file name on command line

1 Answers  

---

ORA-29868: cannot issue DDL on a domain index marked as LOADING

1 Answers  

---

PCC-02205: Parser error at line number, column number, file string:

1 Answers  

---

ORA-30011: Error simulated: psite=string, ptype=string

1 Answers  

---