Modify First Connection Attributes

If you have not modified the db.ini file, proceed to the Manually Edit the db.ini File section. You must now delete the standby Pod and then delete the active Pod. When you delete a Pod that contains a container running TimesTen, the Operator creates a new Pod to replace the deleted Pod. This new Pod contains a new sys.odbc.ini file which is created from the contents of the db.ini file located in the /ttconfig directory.

Perform these steps to delete the standby Pod.

1. Use the kubectl get command to determine which Pod is the standby Pod for the sample TimesTenClassic object. The active Pod is the Pod represented in the ACTIVE column. The standby Pod is the other Pod (not represented in the ACTIVE column). Therefore, for the sample TimesTenClassic object, the active Pod is sample-0, (represented in bold) and the standby Pod is sample-1.

   % kubectl get ttc sample
   NAME     STATE    ACTIVE     AGE
   sample   Normal   sample-0   47h
   

2. Delete the standby Pod (sample-1, in this example). This results in the Operator creating a new standby Pod to replace the deleted Pod. When the new standby Pod is created, it will use the newly modified sample ConfigMap. (You modified this ConfigMap in the Manually Edit the db.ini File section.)

   % kubectl delete pod sample-1
   pod "sample-1" deleted
   

3. Use the kubectl get command to verify the standby Pod is up and running and the state is Normal.

   Note that the state is StandbyDown (represented in bold).

   % kubectl get ttc sample
   NAME     STATE         ACTIVE     AGE
   sample   StandbyDown   sample-0   47h
   

   Wait a few minutes, then run the command again. Note that the state has changed to Normal (represented in bold).

   % kubectl get ttc sample
   NAME     STATE    ACTIVE     AGE
   sample   Normal   sample-0   47h
   

4. Use the kubectl exec -it command to invoke the shell in the standby Pod (sample-1, in this example). Then, run the ttIsql utility to connect to the sample database. Note the new PermSize value of 600 and the new TempSize value of 300 in the connection output (represented in bold).

   % kubectl exec -it sample-1 -c tt -- /bin/bash
   % ttIsql sample 
   Copyright (c) 1996, 2025, Oracle and/or its affiliates. All rights reserved. 
   Type ? or "help" for help, type "exit" to quit ttIsql. 
   connect "DSN=sample"; 
   Connection successful:  
   DSN=sample;UID=timesten;DataStore=/tt/home/timesten/datastore/sample;
   DatabaseCharacterSet=AL32UTF8;ConnectionCharacterSet=AL32UTF8;
   AutoCreate=0;PermSize=600;TempSize=300;DDLReplicationLevel=3;
   ForceDisconnectEnabled=1; 
   (Default setting AutoCommit=1)
   

5. Fail over from the active Pod to the standby Pod. See "Fail Over" for details of the fail over process. Before you begin this step, ensure you quiesce your applications and you use the ttRepAdmin -wait command to wait until replication is caught up, such that all transactions that were executed on the active database have been replicated to the standby database. Once the standby is caught up, fail over from the active database to the standby by deleting the active Pod. When you delete the active Pod, the Operator automatically detects the failure and promotes the standby database to be the active.

   Delete the active Pod (sample-0, in this example).

   % kubectl delete pod sample-0
   pod "sample-0" deleted
   

6. Wait a few minutes, then use the kubectl get command to verify the active Pod is now sample-1 for the sample TimesTenClassic object and the state is Normal (represented in bold).

   % kubectl get ttc sample
   NAME     STATE    ACTIVE     AGE
   sample   Normal   sample-1   47h
   

7. Use the kubectl exec -it command to invoke the shell in the active Pod (sample-1, in this example). Then, run the ttIsql utility to connect to the sample database. Note the new PermSize value of 600 and the new TempSize value of 300 in the connection output (represented in bold).

   % kubectl exec -it sample-1 -c tt -- /bin/bash
   Last login: Thu Jan 16 15:50:29 UTC 2025 on pts/0
   [timesten@sample-1 ~]$ ttIsql sample
    
   Copyright (c) 1996, 2025, Oracle and/or its affiliates. All rights reserved.
   Type ? or "help" for help, type "exit" to quit ttIsql.
    
    
    
   connect "DSN=sample";
   Connection successful: 
   DSN=sample;UID=timesten;DataStore=/tt/home/timesten/datastore/sample;
   DatabaseCharacterSet=AL32UTF8;ConnectionCharacterSet=AL32UTF8;
   AutoCreate=0;PermSize=600;TempSize=300;DDLReplicationLevel=3;
   ForceDisconnectEnabled=1;
   (Default setting AutoCommit=1)
   

8. Use the kubectl exec -it command to invoke the shell in the standby Pod (sample-0, in this example). Then, run the ttIsql utility to connect to the sample database. Note the new PermSize value of 600 and the new TempSize value of 300 in the connection output (represented in bold).

   % kubectl exec -it sample-0 -c tt -- /bin/bash
   % ttIsql sample
    
   Copyright (c) 1996, 2025, Oracle and/or its affiliates. All rights reserved.
   Type ? or "help" for help, type "exit" to quit ttIsql.
    
    
    
   connect "DSN=sample";
   Connection successful: 
   DSN=sample;UID=timesten;DataStore=/tt/home/timesten/datastore/sample;
   DatabaseCharacterSet=AL32UTF8;ConnectionCharacterSet=AL32UTF8;
   AutoCreate=0;PermSize=600;TempSize=300;DDLReplicationLevel=3;
   ForceDisconnectEnabled=1;
   (Default setting AutoCommit=1)

You have successfully modified the PermSize and the TempSize first connection attributes.