Checking the Status of Cache and Replication Agents

You can check the status of cache and replication agents.

Checking the Status of the Cache Agents in TimesTen Scaleout

In TimesTen Scaleout, you can use the ttGridAdmin dbStatus -all command to check whether the TimesTen cache agent processes are running.

See Monitoring the Status of the Cache Agent Processes in the Oracle TimesTen In-Memory Database Scaleout User's Guide.

The following example shows that the cache agent processes are stopped with the CA Status column.

% ttGridAdmin dbStatus -all
Database database1 summary status as of Mon Dec  7 09:36:43 PST 2020
 
created,loaded-complete,open
Completely created elements: 6 (of 6)
Completely loaded elements: 6 (of 6) 
Completely created replica sets: 3 (of 3) 
Completely loaded replica sets: 3 (of 3) 
 
Open elements: 6 (of 6) 
 
Database database1 element level status as of Mon Dec  7 09:36:43 PST 2020
 
Host  Instance  Elem Status CA Status Date/Time of Event  Message 
----- --------- ---- ------ --------- ------------------- ------- 
host3 instance1    1 opened stopped   2020-11-23 08:37:35         
host4 instance1    2 opened stopped   2020-11-23 08:37:35         
host5 instance1    3 opened stopped   2020-11-23 08:37:35         
host6 instance1    4 opened stopped   2020-11-23 08:37:35         
host7 instance1    5 opened stopped   2020-11-23 08:37:35         
host8 instance1    6 opened stopped   2020-11-23 08:37:35         
 
Database database1 Replica Set status as of Mon Dec  7 09:36:43 PST 2020
 
RS DS Elem Host  Instance  Status Date/Time of Event  Message 
-- -- ---- ----- --------- ------ ------------------- ------- 
 1  1    1 host3 instance1 opened 2020-11-23 08:37:35         
 1  2    2 host4 instance1 opened 2020-11-23 08:37:35         
 2  1    3 host5 instance1 opened 2020-11-23 08:37:35         
 2  2    4 host6 instance1 opened 2020-11-23 08:37:35         
 3  1    5 host7 instance1 opened 2020-11-23 08:37:35         
 3  2    6 host8 instance1 opened 2020-11-23 08:37:35         
 
Database database1 Data Space Group status as of Mon Dec  7 09:36:43 PST 2020
 
DS RS Elem Host  Instance  Status Date/Time of Event  Message 
-- -- ---- ----- --------- ------ ------------------- ------- 
 1  1    1 host3 instance1 opened 2020-11-23 08:37:35         
 1  2    3 host5 instance1 opened 2020-11-23 08:37:35         
 1  3    5 host7 instance1 opened 2020-11-23 08:37:35         
 2  1    2 host4 instance1 opened 2020-11-23 08:37:35         
 2  2    4 host6 instance1 opened 2020-11-23 08:37:35         
 2  3    6 host8 instance1 opened 2020-11-23 08:37:35 

Checking the Status of the Cache and Replication Agents in TimesTen Classic

In TimesTen Classic, you can use either the ttAdmin or ttStatus utility to check whether the cache agent and replication agent processes are running as well as determine each agent's start policy.

You can use a ttAdmin -query command to determine the status of the cache and replication agents, as well as the cache and replication agent start policies for a TimesTen database:

% ttAdmin -query cache1
RAM Residence Policy            : inUse
Replication Agent Policy        : manual
Replication Manually Started    : True
Cache Agent Policy              : always
Cache Agent Manually Started    : True

See ttAdmin in Oracle TimesTen In-Memory Database Reference.

Using the ttStatus utility without any commands shows all status information for cache and replication for all TimesTen instances:

% ttStatus
TimesTen status report as of Thu May  7 13:42:01 2009

Daemon pid 9818 port 4173 instance myinst
TimesTen server pid 9826 started on port 4175
------------------------------------------------------------------------
Data store /disk1/databases/database1
There are 38 connections to the data store
Shared Memory KEY 0x02011c82 ID 895844354
PL/SQL Memory KEY 0x03011c82 ID 895877123 Address 0x10000000
Type            PID     Context     Connection Name              ConnID
Cache Agent     1019    0x0828f840  Handler                           2
Cache Agent     1019    0x083a3d40  Timer                             3
Cache Agent     1019    0x0842d820  Aging                             4
Cache Agent     1019    0x08664fd8  Garbage Collector(-1580741728)    5
Cache Agent     1019    0x084d6ef8  Marker(-1580213344)               6
Cache Agent     1019    0xa5bb8058  DeadDsMonitor(-1579684960)        7
Replication     18051   0x08c3d900  RECEIVER                          8
Replication     18051   0x08b53298  REPHOLD                           9
Replication     18051   0x08af8138  REPLISTENER                      10
Replication     18051   0x08a82f20  LOGFORCE                         11
Replication     18051   0x08bce660  TRANSMITTER                      12
Subdaemon       9822    0x080a2180  Manager                        2032
Subdaemon       9822    0x080ff260  Rollback                       2033
Subdaemon       9822    0x08548c38  Flusher                        2034
Subdaemon       9822    0x085e3b00  Monitor                        2035
Subdaemon       9822    0x0828fc10  Deadlock Detector              2036
Subdaemon       9822    0x082ead70  Checkpoint                     2037
Subdaemon       9822    0x08345ed0  Aging                          2038
Subdaemon       9822    0x083a1030  Log Marker                     2039
Subdaemon       9822    0x083fc190  AsyncMV                        2040
Subdaemon       9822    0x084572f0  HistGC                         2041
Replication policy  : Manual
Replication agent is running.
Cache Agent policy  : Always
TimesTen's Cache agent is running for this data store
PL/SQL enabled.
------------------------------------------------------------------------

The information displayed by the ttStatus utility include the following that pertains to TimesTen for each TimesTen instance:

  • The names of the cache agent process threads that are connected to the TimesTen database

  • The names of the replication agent process threads that are connected to the TimesTen database

  • Status on whether the cache agent is running

  • Status on whether the replication agent is running

  • The cache agent start policy

  • The replication agent start policy

See ttStatus in Oracle TimesTen In-Memory Database Reference.