jlandzpa
作者jlandzpa·2014-11-28 14:53
系统运维工程师·广州华南资讯科技有限公司

2014.11.28 SQL2650N An invalid parameter "poLogBuffer"

字数 2289阅读 7392评论 0赞 0
SQL2650N An invalid parameter "poLogBuffer" was passed to the "db2ReadLog" read log API
 
ogg的抽取报错:
014-11-25 16:53:31  ERROR   OGG-00001  Oracle GoldenGate Capture for DB2, ex_03.prm:  Execution cannot continue - Program Terminating.
2014-11-25 16:53:31  ERROR   OGG-00816  Oracle GoldenGate Capture for DB2, ex_03.prm:  db2ReadLog error [SC=-2650:SQL2650N  An invalid parameter "poLogBuffer" was passed to the "db2ReadLog" read log API.  Reason Code = "8"] [The buffer is not of sufficient size to store a log record].
2014-11-25 16:53:31  ERROR   OGG-01668  Oracle GoldenGate Capture for DB2, ex_03.prm:  PROCESS ABENDING.


解决方法:
在ogg上增加了个参数。
tranlogoptions bufsize 20971520

另外:如果是使用cdc做db2的同步触发这个错误的话,就需要设置 加大 log_read_api_buffer_size_kb (缺省是200).
http://www-01.ibm.com/support/docview.wss?uid=swg21659431

Technote (troubleshooting)

Problem(Abstract)

Subscription failed to start mirroring after getting log reader error -2650 rc 8

Symptom

Subscription cannot start and failed with the error below, in the source event log :

"SQL2650N An invalid parameter "poLogBuffer" was passed to the
"db2ReadLog" read log API. Reason Code = "8". ".


Cause

By default log_read_api_buffer_size_kb=200 , so If log records is bigger than 200k in DB2 transaction log then CDC Subscription fails with SQL2650N RC 8 error

Environment

CDC for DB2 LUW database on source

Diagnosing the problem

Issue DB2 ? SQL2650N command on DB2 Server installed machine to get more detail about the error

SQL2650N An invalid parameter "<parameter_name>" was passed to the
"<API-name>" read log API. Reason Code = "<reason-code>".

Explanation:

An invalid parameter was passed to a read log API. The possible reason
codes are as follows:

08

The buffer is not of sufficient size to store a log record.

User response:

Based on the reason code, follow the instructions given:

08

Increase the size of the allocated buffer.

Resolving the problem

Follow the steps :

- Increase the system paremeter log_read_api_buffer_size_kb value to higher in source DB2 LUW datastore. (4000 kb should be sufficient )

- bounce the source DB2 LUW instance

- restart the failing subscription.  

如果觉得我的文章对您有用,请点赞。您的支持将鼓励我继续创作!

0

添加新评论0 条评论

Ctrl+Enter 发表

作者其他文章

相关文章

相关问题

相关资料

X社区推广