Symptom
From within DBAcockpit you navigate to 'Space > SAP system overview > Details' and the following error is reported back:
ADBC SQL Error occurred
[IBM] [CLI Driver] [DB2] PART_RANGE_ALERT IS NOT VALID IN THE CONTEXT WHERE IT IS USED
The developer trace shows the full query with Db2 SQLCODE -206 reported:
C Fri Mar 1 13:21:22 2019
C *** ERROR => DB2 Call 'SQLExecute' Error: conHdl = 00 SQLCODE = -206 : [IBM][CLI Driver][DB2] PART_RANGE_ALERT IS NOT VALID IN THE CONTEXT WHERE IT IS USED
[dbdb2cli.c 6403]
C {root-id=0200020000551EE98F8A98D40497910E}_{conn-id=00000000000000000000000000000000}_0
C DB2Trc: Select MAX(TS_SIZE_ALERT), MAX(IX_SIZE_ALERT), MAX(NUM_PART_ALERT), MAX(PART_RANGE_ALERT) from DB2QD\
C DB2Trc: B02_SCHEMA where COLDATE = '20190301' AND SCHEMA = 'SAPR3';
B ***LOG BY2=> sql error -206 performing OPC [dbds 398]
B ***LOG BY0=> [IBM][CLI Driver][DB2] PART_RANGE_ALERT IS NOT VALID IN THE CONTEXT WHERE IT IS USED [dbds 398]
B ***LOG BY1=> sql error -206 [dbacds 1843]
Read more...
Environment
- Db2 z/OS
- Netweaver AS ABAP
- SAPCL patch#11 or earlier
Product
Keywords
SQL0206N kernel collector , KBA , BC-DB-DB2 , DB2 for z/OS , BC-DB-DB2-SYS , DB2 for z/OS - Database interface , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.