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

ORA-01304: subordinate process error. Check alert and trace logs

1 Answers  

---

ORA-39034: Table string does not exist.

1 Answers  

---

ORA-06318: IPA: Local maximum number of connections exceeded

1 Answers  

---

ORA-29385: cannot create plan directive from string to string

1 Answers  

---

ORA-01932: ADMIN option not granted for role 'string'

1 Answers  

---

ORA-30392: the checksum analysis for the rewrite equivalence failed

1 Answers  

---

ORA-25231: cannot dequeue because CONSUMER_NAME not specified

1 Answers  

---

ORA-00215: must be at least one controlfile

1 Answers  

---

ORA-02277: invalid sequence name

1 Answers  

---

NNL-00254: Server-generated requests currently do not request forwarding

1 Answers  

---

RMAN-08589: channel string: starting datafile conversion

1 Answers  

---

RMAN-20211: FROM TIME is before RESETLOGS time

1 Answers  

---