The result of ttSize does not match actual space utilisation (Doc ID 789515.1)

Last updated on SEPTEMBER 22, 2016

Applies to:

Oracle TimesTen In-Memory Database - Version 5.0.0 to 11.2.1.0.0 [Release 5.x to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 15-Jan-2014***

Goal

The question is often asked: why does the output from ttSize not match actual space utilisation for my structures? Frequently customers have created their table and indexes, loaded some rows, then compared the space utilisation reported by ttSize with the output from 'dssize' and been surprised by the discrepency.

The aim of this note is to explain why that discrepancy may exist at a high level.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms