Answer / guest

Cause: The Data Guard broker detected that the log transport
setting for some database regarding its AlternateLocation
property value is incorrect. The incorrect setting could be
one of the following: (1) the AlternateLocation property is
empty but the log transport to the standby has an ALTERNATE
setting; (2) the AlternateLocation property is not empty but
the log transport to the standby has no ALTERNATE setting;
(3) the AlternateLocation property does not match the
ALTERNATE setting in the log transport. The mismatch may
includes service string, directory specification of the
alternate location, or SP_NAME attribute; (4) the
log_archive_dest_state_n parameter corresponding to the
alternate location is not set to ALTERNATE; (5) the flash
recovery area is being used by the standby for archived
logs, but the log transport to the standby still has an
ALTERNATE setting for the AlternateLocation. Data Guard
broker logs provide further details on which of the above
cases causes the error.

Action: Re-enable the primary database to clear the error.

Please add more information about this Error

DRG-12206: tag string already exists in section group string

1 Answers  

---

ORA-40252: no target values were found

1 Answers  

---

ORA-25244: dequeue index key not found, QUEUE string, rowid string

1 Answers  

---

ORA-14010: this physical attribute may not be specified for an index partition

1 Answers  

---

ORA-00088: command cannot be executed by shared server

1 Answers  

---

---

NID-00335: The following datafiles are not consistent:

1 Answers  

---

ORA-12468: max write level does not equal max read level

1 Answers  

---

ORA-27064: cannot perform async I/O to file

1 Answers  

---

ORA-23498: repgroups specified must have the same masters

1 Answers  

---

ORA-31014: Attempted to delete the root container

1 Answers  

---

LSX-00250: invalid normalizedString "~S"

1 Answers  

---

DRG-11832: Request Entity Too Large

1 Answers  

---