Upgrade the Standby Database

Perform these steps to upgrade the standby database.

Note:

Even though you are upgrading the standby database, depending on your replication configuration, this may result in disruption on your active database. This may impact your applications. Perform the upgrade at the appropriate time.

Determine which Pod is the standby.
```
kubectl get ttc manrepsample
```
The output is similar to the following.
```
NAME           STATE    ACTIVE           AGE
manrepsample   Normal   manrepsample-0   160m
```
Since the manrepsample-0 Pod is the active, the manrepsample-1 Pod is the standby.
Delete the standby Pod.
```
kubectl delete pod manrepsample-1
```
The output is the following.
```
pod "manrepsample-1" deleted
```
Kubernetes automatically creates a new manrepsample-1 Pod to replace the deleted Pod. The TimesTen Operator configures the new manresample-1 Pod as the standby Pod. This new Pod runs the upgraded TimesTen image.

Monitor the progress of the upgrade by observing the state transitions.

 kubectl get events -w

The output is similar to the following:

LAST SEEN   TYPE      REASON                   OBJECT                         MESSAGE
...              
2m51s       Warning   StateChange              timestenclassic/manrepsample   TimesTenClassic was Normal, now ActiveTakeover
2m50s       Normal    StateChange              timestenclassic/manrepsample   TimesTenClassic was ActiveTakeover, now StandbyDown
50s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 Agent Up
50s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 Instance Exists
50s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 Daemon Down
50s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 Daemon Up
50s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 Database Unloaded
43s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 Database None
22s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 Database Loaded
22s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 RepAgent Not Running
22s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 RepScheme Exists
22s         Normal    StateChange              timestenclassic/manrepsample   Pod manrepsample-1 RepState IDLE
16s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 Database Loaded
16s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 RepAgent Running
16s         Normal    Info                     timestenclassic/manrepsample   Pod manrepsample-1 RepScheme Exists
16s         Normal    StateChange              timestenclassic/manrepsample   Pod manrepsample-1 RepState STANDBY
16s         Normal    StateChange              timestenclassic/manrepsample   Pod manrepsample-1 is Ready
16s         Normal    StateChange              timestenclassic/manrepsample   TimesTenClassic was StandbyDown, now Normal

The TimesTen Operator successfully upgraded the standby database.

You are now ready to fail over from the active database to the standby.