Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Extract is abended and looking 8 days old archive log.

user13471596
Member Posts: 12
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.
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.
Answers
-
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.