OGG-01423 No valid default archive log destination directory found for thread :EXTRACT ABENDED

OGG-01423 No valid default archive log destination directory found for thread  :EXTRACT ABENDED

If any of the archive log thread is missing are not Readable by the Golden gate the warning message will be in the extract report file and the extract will move in to the Abended state 

Step 1

check the extract status ..in the ggsci command prompt

GGSCI (db) > info TRANE

EXTRACT    TRANE     Last Started 2012-07-19 01:05   Status ABENDED

Checkpoint Lag       00:00:00 (updated 134:26:36 ago)

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-20 09:10:37  Thread 1, Seqno 71824, RBA 14858240

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-20 09:10:42  Thread 2, Seqno 83766, RBA 93465600

Note the sequence number of the Redo log and make sure that all the redo logs are available and the redo log destination is reachable by the GG

GGSCI (db) > send TRANE status

2012-07-25 23:38:56  INFO    OGG-00987  GGSCI command (prod): send TRANE status.

ERROR: EXTRACT TRANE not currently running.

Step 2

View the report file and Check for the warning and the error messages the rpt file is located under dirrpt in the gg root directory

2012-07-25 21:24:26  WARNING OGG-01423  No valid default archive log destination directory found for thread 1.

Maximum supported ASM read buffer size is 28 KB

2012-07-25 21:24:26  WARNING OGG-01423  No valid default archive log destination directory found for thread 2.

2012-07-25 21:24:26  INFO    OGG-00546  Default thread stack size: 262144.

2012-07-25 21:24:26  INFO    OGG-01513  Positioning to (Thread 1) Sequence 71796, RBA 35363856, SCN 3.2783180541.

If youa re getting this kind of warning messages better check the archive log  sequence which is mentioned  in the error and if the particular archive log is not available restore it to the archive log destination from that point of archive log the golden will proceed to read the data from it to till now so check all the archive log up to date

In case if you don't have the archive log then  also we can start the gg  by altering the extract checkpoint to the lease archive log which is available,,,  in are omitting some archive log there will be data loss during that time period

for example if you're extract had stopped at Sunday and   you are trying to start on Wednesday but if you don't have the archive log  for  Monday then we can alter the gg checkpoint o the Tuesday and we can proceed from Tuesday to until present ... but the monday's data will be loss and you have to think for alter arrangement to move the data for that day

Step3

Alter the extract to the least available the archive-log

and if you are using the GG in the Rac environment then you have to alter all the threads according to the archive log available 

 GGSCI (db) > alter ext trane, thread 1, extseqno71831 , extrba 0

2012-07-25 23:39:50  INFO    OGG-00987  GGSCI command (oraprod): alter ext trane  thread 1, extseqno 71831, extrba 0.

EXTRACT altered.

GGSCI (db) > alter ext trane, thread 2, extseqno 83777, extrba 0

2012-07-25 23:40:34  INFO    OGG-00987  GGSCI command (oraprod): alter ext trane  thread 2, extseqno 83777, extrba 0.

EXTRACT altered.

In this situation we have archive log's starting from the 71831,and 83777 as we are  in the two node RAC environment  

Step 4

Alter the extract for the io checkpoint also

alter extract trane ,thread 1, ioextseqno 71831 ,ioextrba 0

2012-07-25 23:40:11  INFO    OGG-00988  WARNING: Unsupported operation. This might cause transactional inconsistency. Modifying input checkpoint #1, Oracle thread #1 of EXTRACT: ioseq = 71831 iorba = 0.

Are you sure you want to continue? Y

EXTRACT altered.

alter extract trane ,thread 2,ioextseqno 8377 ,ioextrba 0

2012-07-25 23:40:57  INFO    OGG-00988  WARNING: Unsupported operation. This might cause transactional inconsistency. Modifying input checkpoint #2, Oracle thread #2 of EXTRACT: ioseq = 83777 iorba = 0.

Are you sure you want to continue? Y

EXTRACT altered.

Step 5

start the extract and check the status 

GGSCI (db) > start TRANE

GGSCI (db) > info TRANE

EXTRACT    TRANE     Last Started 2012-07-25 23:41   Status RUNNING

Checkpoint Lag       134:30:52 (updated 00:00:00 ago)

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-20 09:10:37  Thread 1, Seqno 71831, RBA 0

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-20 09:10:42  Thread 2, Seqno 83777, RBA 0

Step 6

Check the lag point and wait until all the lag's are processed and it becomes zero

GGSCI (db) > info all

Program               Status              Group       Lag           Time Since Chkpt

MANAGER     RUNNING

EXTRACT     RUNNING     TRANE       134:30:52     00:00:09

EXTRACT     RUNNING     TRANE       121:40:09     00:00:07

GGSCI (db) > info all

Program              Status              Group       Lag           Time Since Chkpt

MANAGER     RUNNING

EXTRACT     RUNNING     TRANE       42:11:29      00:00:08

EXTRACT     RUNNING     TRANP       00:00:00      00:00:01

REPLICAT    RUNNING     SETUPR      00:00:00      00:00:07

REPLICAT    RUNNING     TRANR       00:00:00      00:00:02

GGSCI (db01) 38> info all

Program             Status              Group        Lag           Time Since Chkpt

MANAGER     RUNNING

EXTRACT     RUNNING     TRANE       00:00:00      00:00:01

EXTRACT     RUNNING     TRANP       00:00:00      00:00:06

REPLICAT    RUNNING     SETUPR      00:00:00      00:00:05

REPLICAT    RUNNING     TRANR       00:00:00      00:00:01

Wait until the Lag becomes zero .. once it is zero then it will proceed  Normally ....