These days I’ve been trying Goldengate 21 for DB2 on z/OS (Extract). And still surprises!
Last year, with Goldengate 21.6, it would simply corrupt trailfiles if the extract abended.
This year, with Goldengate 21.10, After adding a new extract,the extract abends without any error or explanation. The report file would remain with this:
2023-06-21 15:11:31 INFO OGG-25184
Using DB2 subsystem DBZOS.
Only in the /var/log/messages one could see:
Jun 21 15:11:31 oraclevm1 kernel: extract: segfault at 0 ip 00007f1c5cca609f sp 00007ffcabd65c28 error 4 in libc-2.17.so[7f1c5cc0b000+1c4000]
SR open and Oracle says, it is fixed with Goldengate 21.11, which is released in two weeks. Well… almost. With Goldengate 21.11 the extract still crashes but only about five minutes after the start command. And the error on /var/log/messages is little different:
Aug 28 13:29:50 oraclevm1 kernel: extract: segfault at 170 ip 00005569d4916a82 sp 00007ffe69d1e600 error 4 in extract[5569d4415000+aaa000]
Oracle says – yes, sorry. Please try the workaround to create the extract with:
ADD EXTRACT e_ab, TRANLOG, EOF
When I check the Goldengate 21 documentation for “ADD EXTRACT” , this option is not valid for DB2 for z/OS, but ok. I try and it works.
Checking with Oracle, the information is that when doing:
ADD EXTRACT e_ab, TRANLOG, BEGIN NOW
It stores the time we run the command and, when we start the extract, it will scan the DB2 log to find the LSN (Log Sequence Number or the CSN from DB2) corresponding to that time. In this scan operation is the bug that makes the segmentation fault. Using EOF, it will always use the end of the Transaction Log at the time we start the Extract.
The Goldengate documentation will be updated soon to add that EOF is also valid for DB2 for z/OS.