Why is Detector not capturing SQL errors in IDAA (IBM® DB2® Analytics Accelerator)?

book

Article ID: 193664

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA Database Management for DB2 for z/OS - Performance Suite CA Database Management for DB2 for z/OS - SQL Performance Suite CA Detector for DB2 for z/OS CA-Insight Performance Monitor for DB2 UDB for z/OS

Issue/Introduction

IDAA (IBM® DB2® Analytics Accelerator) fails to run some SQL queries.  In IBM Accelerator Studio we can see the queries failing with State 22003. We determined that a SQLCODE -413 was being returned to DB2 for a DECFLOAT conversion.  However, Detector had no record of these -413 errors.

Is there some configuration that we need to do for Detector to capture SQL errors from queries that run in IDAA?

 

Environment

Release : 19.0

Component : CA Detector for DB2 for z/OS

Resolution

Detector did not collect the -413 SQL errors because DB2 did not update the SQLCA with the -413 error information during the execution of the failing OPEN statement. Since DB2 is not updating the SQLCA on the z/OS system with the -413 error information, it's unlikely that any z/OS based application could detect the error and report it.