About replication and aging

Question

System environment：Oracle 10.2.0.5, TimesTen 11.2.1
Size of datastore: PerSize=2000, TempSize=400
Create all cachegroup with:
Aging use recvtime LIFETIME 20 minutes cycle 5 minutes ON;
Our application runs normally at first, then PerSize reaches maximum value for a couple of times and the program is stopped.
We checked Persize with command dssize:
PERM_ALLOCATED_SIZE:204800
PERM_IN_USE_SIZE:2047588
PERM_IN_USE_HIGH_WATER:2047588
We confirmed that the data in the table has been written to tables in Oracle, but the space for tables in TimesTen was not
released. Seems that the Aging policy has no effect. I am wondering why is this happening and how do we find out where the
problem is?
Thank you.

Answer 1

Some thoughts..
Can you verify that the AWT bookmark is moving forward, indicating that transactions are being sent to Oracle. Use "call ttlogholds" from ttIsql while your app is running. Aging won't occur on rows that have not been propagated to Oracle.
The only other thing I can think of is that if the aging thread encounters a row lock error, it will ignore this row and move on to the next. If it encounters table lock errors, there is nothing it can do for that table. This would probably show up as Warnings in the ttmesg.log files.
You could also try tracing aging from ttIsql:
call tttrace('level aging 4');
call tttrace('outfile /tmp/ttaging.out');
Now run your app. When the Perm section is full so:
call tttrace('level aging 0');
to turn tracing off, and then check what's in the trace output file /tmp/ttaging.out . You should see a sample entry like this:
09:42:23.272 473 AGING 2L 2044C 3382P Entering sbAgingOneTable(): curTime=87, ltblid= 637076
09:42:23.272 474 AGING 3L 2044C 3382P curTime=87, 6 deleted, 0 remaining, tbl = TT.OCGF
09:42:23.272 475 AGING 2L 2044C 3382P Exiting sbAgingOneTable(): curTime=87, reason = 'no more rows', 6 deleted, 0 remaining, tbl = TT.OCGF
09:42:23.272 476 AGING 1L 2044C 3382P Exiting sbAgingTB(): curTime
which'll give you an idea of how many rows it was able to delete.