TT0885: Invalid T-tree index

Question

After running for several days, our TimesTen 6.0.4 returns errors: TT0885: Invalid T-tree index
What is wrong? How can we fix this?
The error was first encountered when monitoring a table size:
/opt/TimesTen/myapp/bin/ttSize -tbl mydb.users -connstr "dsn=myDB;uid=***;pwd=***"
Rows = 1787180
Table in-line row bytes = 178192657
Indexes:
Can't get info on index FIRST_INDX.MYDB: TT0885: Invalid T-tree index -- file "index.c", lineno 8243, procedure "sb_ixInfo ()"
Can't get info on index SECOND_INDX.MYDB: TT0885: Invalid T-tree index -- file "index.c", lineno 8243, procedure "sb_ixInfo ()"
T-tree index MYDB.UID_INDX adds 36313369 bytes
Can't get info on index USER_INDX.MYDB: TT0885: Invalid T-tree index -- file "index.c", lineno 8243, procedure "sb_ixInfo ()"
Total index bytes = 36313369
Total = 214506026

Answer 1

Hi,
As I suspected. Using ttSize in this manner is not that useful since it does not measure./report on a tables actual space utilisation but rather it computes an 'estimated' utilisation based on the schema, indexes and rowcount. The calculations it use have to make certain assumptions about various things so the values returned may in some cases differ significantly from 'reality'. There is currently no exact way to determine the actual memory occupied by a specific table or index. However, there are accurate figures available about overall memory utiliation in the datastore. The SYS.MONITOR table includes fields such as PERM_ALLOCATED_SIZE, PERM_IN_USE_SIZE and PERM_IN_USE_HIGH_WATER plus equivalent fields for the TEMP region. Also, there is a useful built in procedure called ttBlockInfo.
I would strongly recommend that any routine space monitoring scheme be based on these rather than ttSize...
Chris