Showing results for 
Search instead for 
Did you mean: 
Level 9

DPA monitor DB2

Hi Everyone,

anybody can help, why this happen when trying to add DB2 monitored by DPA

Date: 1/9/20, 5:03:31 PM


org.quartz.JobExecutionException: DatabaseMonitorStartJob failed [See nested exception: org.springframework.dao.DataIntegrityViolationException: QuickPoll; SQL [SELECT auth_id igniteex, stmt_start, stmt_type, ai.db_name, CAST(stmt_text AS BLOB) sql_text, creator, package_name, section_number, stmt_partition_number, (CASE ai.appl_status WHEN 3 THEN stmt_operation * 1000 ELSE ai.appl_status END) waitevent, ai.agent_id, ai.appl_name FROM table(snapshot_appl_info(CAST(NULL as VARCHAR(1)), -2)) AS ai INNER JOIN TABLE(snapshot_statement(CAST(NULL as VARCHAR(1)), -2)) AS s ON s.agent_id = ai.agent_id INNER JOIN TABLE(snap_get_appl_info_v95(CAST(NULL as VARCHAR(1)), -2)) ai95 ON s.agent_id = ai95.agent_id AND ai.agent_id = ai95.agent_id WHERE s.agent_id = ai.agent_id AND s.stmt_type <> 'STMT_TYPE_UNKNOWN' AND stmt_stop IS NULL AND ai.appl_id <> APPLICATION_ID() AND is_system_appl = 0 AND ai95.agent_id = ai.agent_id AND ai95.agent_id = s.agent_id  AND ai.appl_status NOT IN (0, 2, 4) ORDER BY agent_id, stmt_start DESC, stmt_type]; DB2 SQL Error: SQLCODE=-420, SQLSTATE=22018, SQLERRMC=DECFLOAT, DRIVER=3.64.114; nested exception is DB2 SQL Error: SQLCODE=-420, SQLSTATE=22018, SQLERRMC=DECFLOAT, DRIVER=3.64.114]

at com.confio.idc.database.job.DatabaseMonitorStartJob.execute(SourceFile:145)

at com.confio.idc.database.job.DatabaseMonitorStartJob.execute(SourceFile:153)

at com.confio.idc.database.DatabaseMonitor.startScheduler(SourceFile:755)

at com.confio.idc.database.DatabaseMonitor.startSchedulers(SourceFile:738)

at com.confio.idc.database.DatabaseMonitor.start(SourceFile:529)

at com.confio.idc.database.job.DatabaseMonitorLifecycleJob.execute(SourceFile:84)

at org.quartz.core.JobRunS

thank you

Tags (2)
0 Kudos
1 Reply
cpriddy Product Manager
Product Manager

Re: DPA monitor DB2

I suggest you call Solarwinds support as this looks likely to be defect vs. a configuration issue.

0 Kudos