When a REPLICAT process ABEND’s it can be dificult to pinpoint why, and trying to get over the error and allow the REPLICAT to continue can be tricky.
In this example, my source is an Oracle Linux 12c machine running EXTRACT, my target is a Windows Server 2016 machine running MSSQL/REPLICAT.
In this example, we are presented with the following errors in the REPLCIAT report after it has ABENDED
2019-08-15 18:21:20 WARNING OGG-03014 Source column COLUMN_NAME has more characters than target column COLUMN_NAME can hold. Some source characters will not be mapped during conversion from source character set UTF-8 to target character set UTF-16. 2019-08-16 09:28:56 ERROR OGG-01163 Bad column length (357) specified for column COLUMN_NAME in table TABLE.X, maximum allowable length is 255.
From the same report, we need to garner what RBA the fault occured at, you can see this here:
Last log location read: FILE: C:GoldenGatedirdat/1p000003921 SEQNO: 3921 RBA: 4982061 TIMESTAMP: 2019-08-16 09:28:53.053432 EOF: NO READERR: 0
With this information, open LogDump, prepare the application, and move to your RBA:
Logdump 1 > open C:GoldenGatedirdat/1p000003921 (use your filename here) Logdump 2 > ghdr on logdump 3 > detail on logdump 4 > detail data logdump 5 > ggstoken on logdump 6 > ggstoken detail logdump 7 > pos 4982061 (use your RBA here)