ORA-16815: incorrect log transport setting for
AlternateLocation of standby "string"
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
Is This Answer Correct ? | 0 Yes | 0 No |
ORA-06601: LU6.2 Driver: Invalid database ID string
DRG-13307: 'off'=string and 'len'=string references character past end-of-file of string character document, at line string
ORA-25015: cannot perform DML on this nested table view column
ORA-26054: Direct Path Context prepared for a different mode than operation requested.
ORA-24304: datatype not allowed for this call
DRG-11525: invalid commitafter parameter of string specified
ORA-14036: partition bound value too large for column
ORA-19905: log_archive_format must contain %%s, %%t and %%r
ORA-01295: DB_ID mismatch between dictionary string and logfiles
DRG-10017: you must be string to do this: string
PLS-00700: PRAGMA EXCEPTION_INIT of string must follow declaration of its exception in the same declarative part
ORA-32337: cannot alter materialized view with pending changes refresh on commit