Using the ttStatus Utility
Use the ttStatus utility to check the status of the TimesTen daemon and the state of all TimesTen connections.
In this example, the output from ttStatus indicates that no TimesTen daemon is running. If the daemon has stopped unexpectedly, see No Response from TimesTen Daemon or Subdaemon for troubleshooting information.
% ttStatus ttStatus: Could not connect to the TimesTen daemon. If the TimesTen daemon is not running, please start it by running "ttDaemonAdmin -start".
In this example, the output from ttStatus indicates that the TimesTen daemon is running. There is one database named database1.
The first line indicates that the TimesTen daemon is running as process 26251 on port 6624 for the instance1 TimesTen instance. The second line indicates the TimesTen Server is running as process 26258 on port 6625.
There are currently 14 connections to the database: one user and 13 subdaemon connections.
The restart policies for the cache agent and the replication agent in the database are set to manual.
% ttStatus TimesTen status report as of Tue Mar 19 10:16:07 2021 Daemon pid 26251 port 6624 instance instance1 TimesTen server pid 26258 started on port 6625 ------------------------------------------------------------------------ ------------------------------------------------------------------------ Data store /scratch/testuser/database1 Daemon pid 26251 port 6624 instance instance1 TimesTen server pid 26258 started on port 6625 There are 14 connections to the data store Shared Memory KEY 0x021001b9 ID 10813443 PL/SQL Memory KEY 0x031001b9 ID 10846212 Address 0x5000000000 Type PID Context Connection Name ConnID Process 26291 0x00007f5975c07010 database1 1 Subdaemon 26256 0x00007fe2000008c0 Deadlock Detector 2043 Subdaemon 26256 0x00007fe2040008c0 Checkpoint 2041 Subdaemon 26256 0x00007fe2080008c0 Monitor 2045 Subdaemon 26256 0x00007fe2280008c0 Flusher 2044 Subdaemon 26256 0x00007fe230eb1010 Garbage Collector 2037 Subdaemon 26256 0x00007fe2312ce010 XactId Rollback 2038 Subdaemon 26256 0x00007fe2317ec010 IndexGC 2035 Subdaemon 26256 0x00007fe231d0a010 HistGC 2039 Subdaemon 26256 0x00007fe232228010 AsyncMV 2040 Subdaemon 26256 0x00007fe232746010 Log Marker 2036 Subdaemon 26256 0x00007fe232c64010 Aging 2042 Subdaemon 26256 0x00007fe238170010 Rollback 2046 Subdaemon 26256 0x00007fe23858d010 Manager 2047 Replication policy : Manual Cache Agent policy : Manual PL/SQL enabled. ------------------------------------------------------------------------ Accessible by group g900 End of report
This example shows a connection to an old instance of a database. This can occur when a database is invalidated, but some users have not disconnected from the invalidated copy of the database still in memory. After all users disconnect, the memory is automatically freed.
% ttStatus TimesTen status report as of Mon Aug 6 22:03:04 2021 Daemon pid 5088 port 17000 instance instance1 TimesTen server pid 4344 started on port 17002 ----------------------------------------------------------------- Data store c:\temp\sample There are no connections to the data store Obsolete or not yet active connection(s): Process 4696 context 0xd08800 name sample connid 1, obsolete connection, shmKey 'Global\DBI45b94c6f.3.SHM.4' Replication policy : Manual Cache agent policy : Manual ----------------------------------------------------------------- End of report