Symptom
After table reorg by DB6CONV index size increasing is found.
Log info like following could be found in DB6CONV log:
Before reorg:
20170311 084642 >>> Total Size [KB]: 68162848 --> this is the size of both table and indexes before reorg
20170311 084642 >>> Data Size [KB] : 27972160 --> this is the size of table before reorg
20170311 084642 >>> Long Size [KB] : 0
20170311 084642 >>> LOB Size [KB] : 0
20170311 084642 >>> XML Size [KB] : 0
20170311 084642 >>> COL Size [KB] : 0
20170311 084642 >>> Index Size [KB]: 40190688 --> this is the size of indexes before reorg
After reorg:
20170312 112051 >>> Total Size [KB]: 74353728 --> this is the size of both table and indexes after reorg
20170312 112051 >>> Data Size [KB] : 16767552 --> this is the size of table after reorg
20170312 112051 >>> Long Size [KB] : 0
20170312 112051 >>> LOB Size [KB] : 0
20170312 112051 >>> XML Size [KB] : 0
20170312 112051 >>> COL Size [KB] : 0
20170312 112051 >>> Index Size [KB]: 57586176 --> this is the size of indexes after reorg (Increased)
Read more...
Environment
SAP on IBM DB2 for Linux, UNIX, and Windows
Keywords
Table reorg, DB6CONV, table size, index size, DB6 , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , 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.