Answer / guest

Cause: The Data Guard broker detected that the log transport
setting for the standby 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-13801: invalid value for SQLTUNE_CATEGORY parameter

1 Answers  

---

ORA-16160: Cannot change protected standby database configuration

1 Answers  

---

ORA-31428: no publication contains all the specified columns

1 Answers  

---

TNS-04073: Passwords do not match.

1 Answers  

---

ORA-27485: argument string already exists at a different position

1 Answers  

---

ORA-40004: penalty must be negative for BLAST-N

1 Answers  

---

ORA-32741: Hang analysis already going on

1 Answers  

---

ORA-01526: error in opening file 'string'

1 Answers  

---

ORA-32611: incorrect use of MODEL CV operator

1 Answers  

---

RMAN-20217: datafile not part of the database

1 Answers  

---

SQL*Loader-00465: %s directive expects number arguments, number found.

1 Answers  

---

KUP-01006: error signalled during parse of access parameters

1 Answers  

---