WARNING OGG-00869 Aborting BATCHSQL transaction_batchsql resumed-优快云博客

本文链接：https://blog.youkuaiyun.com/huoshuyinhua/article/details/73176602

本文记录了处理Oracle GoldenGate中出现的OGG-00869警告的过程及解决方案，涉及异常批处理SQL交易导致的数据应用不一致问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

由于处理ogg-01031

找到目标端的复制进程后，stop该进程，报等待超时的错误。检查report

2017-06-13 11:06:51  INFO    OGG-01139  BATCHSQL resumed, recovered from error.


2017-06-13 11:14:02  WARNING OGG-00869  Aborting BATCHSQL transaction. Detected inconsistent result: executed 2 operations in batch, resulting in 0 affected rows.


2017-06-13 11:14:02  WARNING OGG-01137  BATCHSQL suspended, continuing in normal mode.


2017-06-13 11:14:02  WARNING OGG-01003  Repositioning to rba 758544243 in seqno 12.

根据该问题，查找mos发现文档1604824.1

How to Resolve: "WARNING OGG-00869 Aborting BATCHSQL transaction. Detected inconsistent result: executed <nn> operations in batch, resulting in <nn> affected rows." (文档 ID 1604824.1)

APPLIES TO:

Oracle GoldenGate - Version 11.2.0.0.0 and later
Information in this document applies to any platform.

GOAL

WARNING OGG-00869 Aborting BATCHSQL transaction. Detected inconsistent result: executed 16 operations in batch, resulting in 0 affected rows.

Does not occur in initial loads.

SOLUTION

The issue you are seeing is caused by the array processing of data resulting in consolidated statements that result in data being applied in a consolidated manner to the target.
This is not a problem if it occurs every few seconds over a period of minutes.
Because Replicat returns to operating in normal mode when this issue occurs, no data is lost or corrupted.
This message is generated by Teradata, not OGG, and the user is advised to open a ticket with Teradata for any specifics.

Note that all Aborting BATCHSQL messages for any database is normal. Please search "Aborting BATCHSQL transaction" in MOS for other like messages

看到这篇文档我就放心了

使用命令

send repxx forcestop

未果，

ps -ef | grep repxx

kill -9 xxxxx

杀掉了该进程，重启了下。正常了（强制关、杀进程都要确定复制进程恢复所需的trail文件是否存在）