Symptom
When performing a "Single Table Analysis" in DBA Cockpit for a specific table, an Internal Server Error 500 occurs stating "******* not being interpreted as a number".
- The issue is accompanied by a stack trace (dump) starting with:
Category: ABAP programming error
Runtime Errors: CONVT_NO_NUMBER
ABAP Program: CL_IXML=======================CP
Application Component: BC-ABA-XML - Optdiag for the target table shows huge Weight on a column statistics:
Histogram for column: "col1"
Column datatype: varbinary(16)
Requested step count: 800
Actual step count: 40000
Sampling Percent: 0
Tuning Factor: 50
Out of range Histogram Adjustment is DEFAULT.
Low Domain Hashing.
Step Weight Value
1 6955618650492923300000000000000000.00000000 <= 0x000b8e5238195575e1000000041c1234
2 0.00000387 < 0x00278a48758f0a62e1000000041c0666
3 0.00005130 = 0x00278a48758f0a62e1000000041c0666
Read more...
Environment
Business Suite on Adaptive Server Enterprise (ASE) 16.0
Product
SAP Adaptive Server Enterprise 16.0
Keywords
Single Table Analysis, Internal Server Error 500, CONVT_NO_NUMBER, ABAP programming error, Weight, column statistics , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.