Bug of rain and Oracle GoldenGate in Jinan, oraclegoldengate

Bug of rain and Oracle GoldenGate in Jinan, oraclegoldengate


Jinan is raining now (am). However, my mood is best described by Qi Qin's Song-"relentless rain, gently wake me up and make my tears ice like rain"

I have just confirmed a bug of ogg in the production environment (this bug is related to ddl). The ogg version with the bug is:

Oracle GoldenGate Capture for Oracle Version 11.2.1.0.25 19181440 19358139 AIX 5L, ppc, 64bit (optimized), Oracle 11g on Sep 3 2014 13:34:20 --------------> pay attention to this time

Ogg media with bugs comes from: p19509714_1121025_AIX64-5L.zip
In the PDF file of this zip file, the bug fix for this ogg version is described as follows:

Version 11.2.1.0.25 BLR 19358139–1 September 2014  19358139 - GoldenGate parsing multiple times.Cache the prepare update statement to checkpoint table.

The ogg version tested on my own virtual machine is:

Oracle GoldenGate Capture for Oracle Version 11.2.1.0.25 19181440 19517566_FBO Linux, x64, 64bit (optimized), Oracle 11g on Sep 4 2014 15:53:25 --------------> pay attention to this time

This Version 11.2.1.0.25 19181440 19517566_FBO is the following media:
P19551348_1121025_Linux-x86-64.zip
In the PDF file of this zip file, the bug fix for this ogg version is described as follows:

Version 11.2.1.0.25  BLR19517566 –5 September 201419517566 - IE EXTRACT ABEND WITH OGG 01161 BAD COLUMN INDEX .Fixed a problem with STARTSCN greater than 8 bytes number.

Comparing the Compilation Time of the two ogg programs, we can see that the difference is only one day, but the bug fix is different...
This can also be explained: Why can't I reproduce the problems in the customer's production environment on my own virtual machine ....

Search on mos with the keyword "19517566". The following articles can be found:

Extract will not replicate the newly added columns in the table (Document ID 1944004.1) EXTRACT misparses DDL metadata causing extract/replicat errors when processing DML after a DDL change (Document ID 1923448.1)

In the above two articles, we recommend that you upgrade ogg to the latest version ---- 11.2.1.0.27

And "19517566" is also the bug that the oracle sr engineer located in this production environment's ogg problem. It seems that ogg is inevitably upgraded...