Primary Remote log shipping failing with ORA-16057 - Server not in Data Guard configuration
(Doc ID 1570928.1)
Last updated on JANUARY 13, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
------------Primary Alert log-----------------
Thu Jul 11 16:28:16 2013
ALTER SYSTEM SET log_archive_dest_2='service=<SERVICENAME> async valid_for=(all_logfiles,primary_role) db_unique_name=<DB_UNIQUE_NAME>'
SCOPE=BOTH;
Thu Jul 11 16:28:17 2013
PING[ARC1]: Heartbeat failed to connect to standby '<SERVICENAME>'. Error is 16057..'
..
.
Error 16057 for archive log file 1 to '<SERVICENAME>'
Thu Jul 11 16:28:19 2013
<PATH>/trace/<SID>_tt01_6296.trc:
ORA-16057: server not in Data Guard configuration
@primary,
SQL> col error for a30
SQL> select dest_id,error,status,log_sequence,applied_scn from v$archive_dest where dest_id=2;
DEST_ID ERROR STATUS LOG_SEQUENCE APPLIED_SCN
---------- ------------------------------ --------- ------------ -----------
2 ORA-16057: server not in Data ERROR 61 0
Guard configuration
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |