Check trace files:

The trace files in the alert log may be a little cryptic and more suitable for support, there are advanced topics in learning how to decipher the lines in the trace files.  The alert log will suffice for this issue.

PROD ALERT

Thu Jul 06 06:18:19 2016
Errors in file /u01/app/oracle/diag/rdbms/$lower_sid/$lower_sidc/trace/$lower_sid_tt00_9495.trc:
ORA-00270: error creating archive log
Thu Jul 06 06:18:19 2016
Errors in file /u01/app/oracle/diag/rdbms/$lower_sid/$lower_sid/trace/$lower_sid_tt00_9495.trc:
ORA-00270: error creating archive log
Thu Jul 06 06:18:19 2016
Errors in file /u01/app/oracle/diag/rdbms/$lower_sid/$lower_sid/trace/$lower_sid_tt00_9495.trc:
ORA-00270: error creating archive log
Thu Jul 06 06:23:19 2016

Standby Alert

Creating archive destination file : +ARCHIVE (30650368 blocks)
Thu Jul 06 06:18:25 2016
Errors in file /u01/app/oracle/diag/rdbms/$lower_sid/$lower_sid/trace/$lower_sid_ora_99824.trc  (incident=2088240):
Thu Jul 06 06:18:28 2016
Sweep [inc][2088240]: completed
Sweep [inc2][2088240]: completed
Thu Jul 06 06:23:20 2016

Steps to Resolve:

The error is pretty clear check space on the standby site.

  1. Check the meaning of the error in case it’s not as clear, Oracle support/some google searches will have a good description.
  2. Check the standby lag on both databases:
    1. standby value is xxxx.
    2. prod value yyyyy.
  3. BACKUP your archive logs on standby/primary if not automated:
  4. Setup automated deletion:
    1. CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON [ALL] STANDBY;
  5. Delete all logs not required if your standby is failing to do this automatically.
  6. Monitor the standby and primary logs.

PROD ALERT

Tail -f alert_SID.log
TT00: Creating remote archive destination LOG_ARCHIVE_DEST_3: ‘standby3’ (T-1.S-181120) (standbysid)
Thu Jul 06 06:23:19 2016
TT00: Transmitting activation ID 0x0
OCISessionBegin with PasswordVerifier succeeded
Client (PID:9495) attached to RFS (PID:100411) at remote instance number [1] at dest ‘standbysid’

Standby Alert

Network Resource Management enabled for Process  (pid 100411) for Exadata I/O
Primary database is in MAXIMUM PERFORMANCE mode
RFS[263]: Assigned to RFS process (PID:100411)
RFS[263]: No standby redo logfiles available for T-1
RFS[263]: Opened log for thread 1 sequence 181120 dbid 249804672 branch 791072871

Advertisements