OGG-01389错误

环境介绍：

生产端：ogg 11.2

容灾端: ogg 11.1
部署OGG后，容灾端replicat进程abend,信息如下：

 

2012-08-07 23:56:21  INFO    OGG-01669  Oracle GoldenGate Collector:  Opening ./dirdat/aa000000 (byte -1, current EOF 0).
2012-08-08 00:00:25  ERROR   OGG-01389  Oracle GoldenGate Delivery for Oracle, REP.prm:  File header failed to parse tokens. File ./dirdat/aa000000, last offset 810, data: 0x     32A: 000000013A00000200003B000004000000013C000014000000101414141414141414141414141114141433000070300000070005455854444131000002000332000002000B3300000200023400000200013500000200003600000200013700003D003B56657273696F6E2031312E322E312E302E31204F4747434F52455F3131.
2012-08-08 00:00:25  ERROR   OGG-01668  Oracle GoldenGate Delivery for Oracle, REP.prm:  PROCESS ABENDING.

 

错误分析：

The source GoldenGate environment in my case was 11.2.1.0.0 and the target GoldenGate environment was 11.1.1.1，So it looks like the extract file generated by GG version 11.2.1.0 was not compatible with the 11.1.1 replicat process which is reading the trail file.
To overcome this problem we had to use the parameter FORMAT RELEASE in the extract parameter file.
Quoting the documentation  :
FORMAT RELEASE <major>.<minor>

具体参见：http://gavinsoorma.com/2012/06/using-the-format-release-parameter-to-handle-goldengate-version-differences/

 

问题解决：

Change the format of the trail file to the (lower) GoldenGate version of the target environment.
In the extract parameter file we have to add in this case the line:
rmttrail /u01/app/goldengate/dirdat/yy, format release 11.1

 

GGSCI> alter extract ext, etrollover

2012-06-21 04:32:40  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.

 

On the Target side, we want the Replicat process to read the new trail file when it starts up and not the one with the higher 11.2 version it was reading initially when it abended
GGSCI > alter replicat rep  extseqno 1
REPLICAT altered.

We now start the Replicat process and see that it is running fine and reading the next sequence in the trail file which is aa000001