Forum Discussion
Error refreshing report on IBM DB2
Hi,
While refreshing a report which is built on IBM DB2 , I am getting the following error:Microsoft Db2 Client: Index was outside the bounds of the array. SQLSTATE=HY000 SQLCODE=-343.
Can anyone help out what this means and how to resolve it.
Regards,
Manisha.
Hi Anonymous ,
Generally speaking, the -343 error is due to The Microsoft ADO.NET Provider for DB2 and the underlying Microsoft DRDA Application Requester Client for DB2 do not process DB2 for z/OS V11 BLOB and CLOB data values that are longer than 1,048,576 bytes.
Please make sure that you download powerbi 64bit driver and install it. In addition, validate IBM Data Server Driver Package installation following the steps in below article.Validating IBM Data Server Driver Package (Windows) installation - IBM Documentation
You can also refer to a similar case: MSDB2 Client exception HY000 SQLCODE -343 (narkive.com)
If the problem is still not resolved, please provide detailed error information screenshoot and let me know immediately. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
Hi Anonymous ,
Generally speaking, the -343 error is due to The Microsoft ADO.NET Provider for DB2 and the underlying Microsoft DRDA Application Requester Client for DB2 do not process DB2 for z/OS V11 BLOB and CLOB data values that are longer than 1,048,576 bytes.
Please make sure that you download powerbi 64bit driver and install it. In addition, validate IBM Data Server Driver Package installation following the steps in below article.Validating IBM Data Server Driver Package (Windows) installation - IBM Documentation
You can also refer to a similar case: MSDB2 Client exception HY000 SQLCODE -343 (narkive.com)
If the problem is still not resolved, please provide detailed error information screenshoot and let me know immediately. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.In my particular case the issue was caused by the usage of SYSDATE in the SELECT statement:
SELECT ORDER, REPORTDATE,SYSDATE...
FROM SALESORDER
Replacing SYSDATE with CURRENT DATE solved the problem
SELECT ORDER, REPORTDATE,CURRENT DATE...FROM SALESORDER...
Interestingly usage of SYSDATE in the WHERE clause did not cause any issues
