My pump process is down for so many days and when I tried to start the process it is getting ABENDED because it is trying to write in the remote trail file which is MISSING
GGSCI (oracleqa011.domain.com) 7> start PUMPQA
Sending START request to MANAGER ...
EXTRACT PUMPQA starting
GGSCI (oracleqa011.domain.com) 8> info PUMPQA
EXTRACT PUMPQA Last Started 2015-08-20 19:59 Status ABENDED
Checkpoint Lag 00:00:00 (updated 00:00:28 ago)
Log Read Checkpoint File ./dirdat/cb000011 --> This is source trail file
2015-08-20 19:59:30.000000 RBA 36679
GGSCI (oracleqa011.domain.com) 9> view report PUMPQA
2015-08-20 19:59:44 ERROR OGG-01496 Failed to open target trail file /u01/oracle/TARGET/cb000008, at RBA 8448365.
2015-08-20 19:59:44 ERROR OGG-01668 PROCESS ABENDING.
Here pump process is trying to write to the file “cb000008” where is has left before, since it’s been long ago this file doesn’t exist in the target location
Tried doing begin now command, but doesn’t work
GGSCI (oracleqa011.domain.com) 10> alter PUMPQA begin now
EXTRACT altered.
Still “ABENDED” --> because it will begin now but try to write to the same trail file
Solution:
Do “ETROLLOVER” for pump process, this will roll over to the next trail file in the sequence (here cb000009)
GGSCI (oracleqa011.domain.com) 10> ALTER EXTRACT PUMPQA ETROLLOVER
2015-08-20 20:02:22 INFO OGG-01520 Rollover performed. For each affected output trail of Version 10 or higher format, after starting the source extract, issue ALTER EXTSEQNO for that trail's reader (either pump EXTRACT or REPLICAT) to move the reader's scan to the new trail file; it will not happen automatically.
EXTRACT altered.
GGSCI (oracleqa011.domain.com) 11> start PUMPQA
Sending START request to MANAGER ...
EXTRACT PUMPQA starting
GGSCI (oracleqa011.domain.com) 12> info PUMPQA
EXTRACT PUMPQA Last Started 2015-08-20 20:02 Status RUNNING
Checkpoint Lag 00:03:09 (updated 00:00:08 ago)
Log Read Checkpoint File ./dirdat/cb000011
2015-08-20 19:59:30.000000 RBA 36679
In the target server I see “cb000009” has been created and writing into it.
0 comments:
Post a Comment