Forum Stats

  • 3,875,203 Users
  • 2,266,862 Discussions


Extract is abended and looking 8 days old archive log.

user13471596 Member Posts: 12
edited Feb 28, 2011 1:43PM in GoldenGate
I was doing some maintenance and I stop all the extracts and replicats. Couple of my extracts are stopped and looking for 8 days old archive logs. Please tell me how can I recover from that situation. I dont have that archive any more we only keep 5days arch.

GGSCI (ggastdb01.infra.mms) 5> info e_it860t

EXTRACT E_IT860T Initialized 2011-02-08 16:04 Status STOPPED
Checkpoint Lag 00:10:05 (updated 04:34:30 ago)
Log Read Checkpoint Oracle Redo Logs
2011-02-24 09:53:04 Seqno 15721, RBA 103192

Report file Error:

2011-02-24 14:34:04 ERROR OGG-00446 Could not find archived log for sequence 15494 thread 1 under alternative or default destinations. SQL <SELECT name FROM v$archived_log WHERE sequence# = :ora_seq_no AND thread# = :ora_thread AND resetlogs_id = :ora_resetlog_id AND archived = 'YES' AND deleted = 'NO>. Last alternative log tried /u10/oradata/PPMTST10/arch/1_15494_721133148.arc, error retrieving redo file name for sequence 15494, archived = 1, use_alternate = 0Not able to establish initial position for sequence 15494, rba 68728848.

2011-02-24 14:34:04 ERROR OGG-01668 PROCESS ABENDING.


  • stevencallan
    stevencallan Member Posts: 3,459
    edited Feb 24, 2011 7:15PM
    If you don't have the log file(s) in question, then you need to:
    re-sync the databases/schema/tables, or
    advance the CSN to a point in time where you do have log files and deal with missing data separately

    Is an archived transaction log missing?
    ● Extract reads the archived logs when an online log is not available. If you started
    Extract after it was stopped for a long time, the records it needs to process might
    already be archived away.
    ● Restore the archive log that is specified in the error message in the report file, and also
    restore all subsequent logs.
    NOTE Extract should not be stopped for a long time. If you must stop Extract, make
    certain that archives are available all the way back to the time that you stopped
    Extract. If Extract remains stopped for an exceptionally long time, it might be more
    practical to resynchronize the table(s) rather than wait for Extract to go through the
    archives and catch up.
  • Make sense. Thanks for the help. I end up refreshing the target schema.
This discussion has been closed.