How can I skip the current transaction after the GoldenGate process fails?

After the GoldenGate process fails, how can we skip the current transaction during the OGG operation? Generally, the disaster recovery REPLICAT process is ABENDED due to various reasons. At this time, we need to analyze ggserr. log, DISCARDFILE, replicat report, and use Logdump and other tools to locate errors. In specific application scenarios, through analysis and troubleshooting, some transactions can be applied without the disaster recovery end. The following example shows a problem encountered in configuring OGG in production today. Www.2cto.com: During the synchronization process, a transaction is created for a table under the OGG user in the queue passed from the master database. As a result, the REPLICAT process is ABENDED. After analysis, this table is used for DDL replication in the master database and does not need to be applied in the slave database. It is decided to skip the next transaction without affecting data consistency: 1, locate the current REPLICAT process in the queue File and RBA: GGSCI (sv890n01) 46> info rads_1 REPLICAT RADS_1 Last Started 2012-12-08 02:23:36 29 Status ABENDEDCheckpoint Lag 00:01:38 (updated ago) Log Read Checkpoint File. /dirdat/pa1_02 14:05:51. 970013 RBA 77698825 2, because the RBA of two adjacent transactions in the queue is not This is a simple + 1 link, so you need to locate the rba of the next transaction. here you need to use the logdump tool. Open the queue file: Logdump 10> open. /dirdat/pa000002Current LogTrail is/u01/app/oracle/oradata/ogg/dirdat/pa1_02 locate the specified RBA location: logdump 11> pos 77698825 Reading forward from RBA 77698825 view the details of the current transaction. Here, you can see the DDL/DML operation type, RBA, Object Name, and other related information: logdump 12> n2012/12/08 14:05:52. 970.013 DDLOP Len 1221 RBA 77698825 Name: After Image: Partition 0G s2c43 353d 2735 3730 3727 2c2c 4237 3d27 3537 3037 |, C5 = '000000', B7 = '5707272c 2c42 323d 2735 3631 3330 2c2c 3027 3d27 | ', B2 = '000000', B3 = '4f47 4233 2c2c 561300 3d27 4727 4d53 5f54 4234 434f | ogg ',, b4 = 'dbms _ TABCO4d50 5f54 454d 505f 554e 434d 5027 2c2c 4331 323d | MP_TEMP_UNCMP ', C12 = 2727 2c2c 4331 333d 2727 2c2c 4235 3d27 5441 rjc | '',, c13 = '', B5 = 'tabl4527 2c2c 4236 3d27 4452 4f50 272c 2c42 383d 274f | E ', B6 = 'drop ',, b8 = 'o4747 2e47 4753 5f44 444c 5f48 4953 5427 2c2c 4239 | GG. GGS_DDL_HIST ', and B9 check the information of the next transaction: www.2cto.com Logdump 13> n2012/12/08 14:05:52. 970.013 Insert Len 370 RBA 77700210 Name: duplicate ate. TB_DOWNLOAD_LOGAfter Image: Partition 4G s0000 0009 0000 0005 7274 7231 3100 0100 0900 | ........ rtr11 ....... 0531 3036 3034 0002 001d 0000 0019 5943 3159 3037 |. 10604 ........ YC1Y07315f 3132 3939 3537 3833 3534 3932 342e 786d 6c00 | 20171299578354924.xml0000300 0300 0030 0004 00bf 0000 00bb 6874 7470 3a2f | ..... 0 ........ http:/2f64 6174 6167 6174 652e 6368 696e 6162 6f6e 642e |/Reset ate. chinabond.636f 6d2e 636e 2f64 6174 6167 6174 652f 6469 7370 | com.cn/datagate/disp6174 6368 3f66 756e 635f 6964 3d32 3031 3126 7374 | atch? Func_id = 2011 & st has now located the rba of the next transaction. 3. In GGSCI, you can re-specify the current rba of the replicat process to skip the current transaction GGSCI (sv890n01) 47> alter replicat rads_1, extrba 77700210 REPLICAT altered. GGSCI (sv890n01) 48> start rads_1Sending START request to MANAGER... REPLICAT RADS_1 starting