OGG OGG-01496 OGG-01028

今天由于没有正常的先关闭源端的PUMP进程而直接关闭了备库的replicat和MGR进程。
导致PUMP进程启动不了报错如下：
OGG-01496  Oracle GoldenGate Capture for Oracle, py169.prm:  Failed to open target trail file ./dirdat/tb000183, at RBA 4434691.

我对PUMP提示使用下一个trail文件
alter extract py169, ETROLLOVER


然后重新启动报错如下：


2014-07-07 14:20:05  INFO    OGG-01478  Oracle GoldenGate Capture for Oracle, py169.prm:  Output file ./dirdat/tb is using format RELEASE 11.2.
2014-07-07 14:20:05  INFO    OGG-01026  Oracle GoldenGate Capture for Oracle, py169.prm:  Rolling over remote file ./dirdat/tb000184.
2014-07-07 14:20:26  ERROR   OGG-01028  Oracle GoldenGate Capture for Oracle, py169.prm:  Incompatible record (101) in ./dirdat/sb000182, rba 48681981 (getting header)
同时我记录了replicat进程的最后SCN
Current Checkpoint Detail:


Read Checkpoint #1


  GGS Log Trail


  Startup Checkpoint (starting position in the data source):
    Sequence #: 182
    RBA: 48681981
    Timestamp: 2014-07-07 10:33:08.815143
    Extract Trail: ./dirdat/tb


  Current Checkpoint (position of last record read in the data source):
    Sequence #: 182
    RBA: 48681981
    Timestamp: Not Available
    Extract Trail: ./dirdat/tb


CSN state information:
  CRC: 7B-3D-9C-FA
  Latest CSN: 1019744288
  Latest TXN: 15.4.220038
  Latest CSN of finished TXNs: 1019744288
  Completed TXNs: 15.4.220038
  
  
可以发现应该是sb000182出现的问题，然后进行metalink




METALINK文档如下：
ADD EXTRACT py169, EXTTRAILSOURCE ./dirdat/sb
add  rmttrail ./dirdat/tb,extract py169
ALTER EXTRACT py169, EXTSEQNO 182, EXTRBA 48681981


ALTER EXTRACT py169, EXTSEQNO 182, EXTRBA 48681710 


If a trail is not corrupt, a pump or replicat can be restarted by noting the point of failure (trail number and RBA) indicated in the report and discard file. Please do not attempt this if you are not familiar with reading these reports.


This should be done on transaction boundaries or with RESTARTCOLLISIONS enabled. If you do not understand this, do not do this yourself; please have support assist you.


 


>logdump
logdump> log to mycase.txt
logdump> open (/ggtrail/GGODSCF/dirdat/cf000325)  << logdump> ghdr on
logdump> pos (RBA 19018)                                      << logdump> n
  this will give you a bad header message


logdump> sfh prev
  this gives you the header of the previous record start,write down the RBA value   <<

logdump> count
  if this finishes Ok and gives you a count of tables and records, the trail is OK and you can use the RBA we saved for the alter later
  the trail is known to be undamaged
  if this does not finish with the count, you have a bad trail and must use another recovery method, contact support.
logdump> exit


You now have a history of what you did in file mycase.txt and a written record of the RBA to use to ALTER the extract data pump or replicat


ggsci> alter , extseqno < the existing sequence number>, extrba
ggsci> start


可以发现实际METALINK建议PUMP进程如果在不是真正的损坏的情况下可以从上一个HEADER进程重新读取，这样就能恢复，
如果这样还有问题，需要删除备份端的REPLICAT进程，然后重建，如果删除了REPLICAT进程就把REMOTE TRAIL
file 删除，然后重建。
1、删除备份端的REPLICAT进程
2、删除备份端的REMOTE TRAIL文件
3、更改PUMP提取的位置重新提取
4、建立REPLICAT进程
5、使用start rt01 aftercsn 1019744288（这里就是前面记录的SCN） 来启动


我由于没有注意最后一步，导致数据丢失，最后只能重新从主库导出，重建了。
同时提醒大家如果要关闭备份端的MGR进程一定要先关闭源端的PUMP进程，不至于
ABEND掉，出现未知的错误。

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/7728585/viewspace-1211548/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/7728585/viewspace-1211548/