Symptom
- When collect DB2 data, the SDCCN log of SAP EarlyWatch Alert shows error:
"DB6_HIST_DB: An exception has occurred that was not caught." - The following dump can be found in ST22:
Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_SY_STRUCT_COMP_NAME
ABAP Program /SDF/CL_DB6_MON===============CP
Application Component SV-SMG-SDD
Error analysis:
The exception is assigned to class 'CX_SY_STRUCT_COMP_NAME' and was not caught in procedure "GET_DB_PERF_HISTORY" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated this exception, the current program was terminated.
The reason for the exception is:
Component Name 'LOG_EXTRACTION_CUR_COMMIT_READS' of the Component 65 Too Long
Read more...
Environment
- SAP NetWeaver Application Server for ABAP
- ST-PI 740 with support package lower than SP16
- ST-PI 2008_1_7* with support package lower than SP26
Product
SAP NetWeaver Application Server for ABAP all versions
Keywords
UNCAUGHT_EXCEPTION, /SDF/CL_DB6_MON, EWA, data collection, db2, st-pi, get_db_perf_history, SDCCN , KBA , SV-SMG-SDD , Service Data Download , Problem
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.
SAP Knowledge Base Article - Preview