This content has been marked as final. Show 5 replies
Documentation (http://docs.oracle.com/cd/E21901_01/doc/timesten.1122/e21633/using.htm#BCGHAIBG) says:
"Oracle TimesTen manages database space using two separate memory partitions within a single contiguous memory space. One partition contains permanent data and the other contains temporary data.
- Permanent data includes the tables and indexes that make up a TimesTen database. When a database is loaded into memory, the contents of the permanent data partition are read from files stored on disk. The permanent data partition is written to disk during checkpoint operations.
- Temporary data includes locks, cursors, compiled commands, and other structures needed for command execution and query evaluation. The temporary data partition is created when a database is loaded into memory and is destroyed when it is unloaded.
The connection attributes that control the size of the database when it is in memory are PermSize and TempSize. The PermSize attribute specifies the size of the permanent data partition and the TempSize attribute specifies the size of the temporary data partition."
Additionally you can use the following command for getting the db size:
Command> dssize; PERM_ALLOCATED_SIZE: 32768 PERM_IN_USE_SIZE: 5867 PERM_IN_USE_HIGH_WATER: 5867 TEMP_ALLOCATED_SIZE: 32768 TEMP_IN_USE_SIZE: 6789 TEMP_IN_USE_HIGH_WATER: 7351 Command>
Thank you very much for your answer, it is very clear!
On Linux you can also minitor memory used by TimesTen using
Note that ipcs -m only tells you how large a shared memory segment TimesTen has allocated from the O/S and you can anyway know this as it is just PermSize+TempSize+LogBufMB+~20MB. It does not give you any insight into how much of that memory is actually used within TimesTen.
You are right.
We use this method to monitor memory on host. We create charts wat include all sorts of used memory.