Upgrade a Grid to a Patch-Compatible Release

Upgrading a grid to a patch-compatible release consists of ensuring that every instance uses for its operations the installation files provided by a different patch set (or patch) release of TimesTen, for example, upgrading the installation from a 22.1.x to a 22.1.y release. To make all instances operate with installations of a target TimesTen release, you need to perform three main tasks:

Create an installation of the target release on each host in the model.
Modify each management instance to use with the new installation and then restart the instance.
Modify each data instance to use with the new installation and then restart the instance.

As with any other aspect of administering a grid, all the aforementioned tasks are performed through the ttGridAdmin utility. The grid topology (number of management instances, K-safety value, and the number of replica sets) and if the upgrade supports to keep at least one full copy of every database available for applications to connect determines which ttGridAdmin commands need to be run, in which order, and at what time.

To keep things as simple and as straightforward as possible, TimesTen provides the ttGridAdmin gridUpgrade command. The ttGridAdmin gridUpgrade command studies the grid and, if possible, runs all the necessary commands to perform either of the aforementioned tasks without further input from the instance administrator. Alternatively, you can perform any and all of the main tasks for an upgrade at your own pace by providing each individual ttGridAdmin command that the ttGridAdmin gridUpgrade command would otherwise run in the background.

The next topics describe the release compatibility metadata, the prerequisites for upgrading a grid to a patch-compatible release and how to perform such upgrade either with or without the ttGridAdmin gridUpgrade command.

Release Compatibility Metadata

Every TimesTen release includes metadata regarding whether the release can be upgraded from or to a previous TimesTen release. The release compatibility metadata includes similar information concerning previous TimesTen releases.

In TimesTen Scaleout, the ttGridAdmin gridUpgrade command uses this metadata to determine if and what type of upgrade instances of the current release support towards the target release.

Upgrade Prerequisites

Upgrades to a patch-compatible release have these prerequisites:

The current version of the model matches the latest version of the model. In other words, there have not been any changes to the model since the latest changes were applied.
Including the target release, the grid is running under no more than two different releases. One or more instances operating under a different but compatible release to the rest of the instances is expected. For example, a grid may continue to successfully operate during an upgrade or even after the upgrade is interrupted or one of the operations performed during the upgrade fails; in such cases, you may make a second attempt to complete the upgrade after resolving the issue. However, you should not attempt an upgrade when a previous upgrade with a different target release has yet to be completed.

Upgrading a Grid with the ttGridAdmin gridUpgrade Command

To upgrade a grid to a patch-compatible release with the ttGridAdmin gridUpgrade command, complete these tasks:

Create Installations of the Target Release

Before you can upgrade a grid to a patch-compatible release, all hosts in the model must have access to an installation of the target release. The -createInstallations option of the ttGridAdmin gridUpgrade command creates, for each host, an installation of the provided TimesTen distribution or from an existing TimesTen installation.

Create an installation of the target release on every host defined in the model.
Note:
Ensure that you download a TimesTen distribution of the target release to a location reachable by the active management instance.
```
% ttGridAdmin gridUpgrade -createInstallations -source host1:/mydir/timesten2211190.server.linux8664.zip 
Checking for existing installations of TimesTen 22.1.1.19.0............OK
Creating missing installation objects.................................OK
Applying model to create new installations............................OK
```
TimesTen performs these tasks while the ttGridAdmin gridUpgrade -createInstallations command is in operation:
1. Checks for installations of the target release already defined in the model. If TimesTen finds any such installations, it will note which hosts are associated with them so it does not create another target release installation for them later on.
2. Runs the ttGridAdmin installationCreate command for each host in the model (excluding the hosts noted above) to create an installation object of the target release.
  
  Note:
  
  TimesTen uses the location used to create the current installation and the default installation name as the location for the installation of the target release. For example, if the location used to create the current installation for the host1 host is /grid, then TimesTen uses /grid/installation1 to create the target installation. If installation1 is already in use as an installation name, TimesTen uses installation2 and so on. If you want to customize the locations and installation names used, create the installations without using the ttGridAdmin gridUpgrade command, as described in Create Installations of the Target Release.
3. Runs the ttGridAdmin modelApply command to apply the changes made to the model, which creates the new installations.

Now that every host in the grid has an installation of the target release, you can proceed to upgrade the management and data instances.

For more information on the ttGridAdmin gridUpgrade command, see Upgrade a Grid (gridUpgrade) in Oracle TimesTen In-Memory Database Reference.

Upgrade the Management Instances

Use the -type mgmt option of the ttGridAdmin gridUpgrade command to upgrade the management instances to the target release.

Upgrade the management instances to the target release.
```
% ttGridAdmin gridUpgrade -type mgmt -to 22.1.1.19.0
Checking prerequisites................................................OK
Checking for existing installations of TimesTen 22.1.1.19.0............OK
Verify that upgrade is known to be supported..........................OK
Verify that instances are running the expected releases...............OK
Determining management instance state.................................OK
Modify instance host2.instance1.......................................OK
Apply change..........................................................OK
Stop standby management instance host2.instance1......................OK
Start standby management instance host2.instance1.....................OK
Fail over to management instance host2.instance1......................OK
Start standby management instance host1.instance1.....................OK
Modify instance host1.instance1.......................................OK
Apply change..........................................................OK
Stop standby management instance host1.instance1......................OK
Start standby management instance host1.instance1.....................OK
Fail over to management instance host1.instance1......................OK
Start standby management instance host2.instance1.....................OK
```
TimesTen performs these tasks while the ttGridAdmin gridUpgrade -type mgmt command is in operation:
1. Checks that the grid meets all the prerequisites required for an upgrade operation.
2. Checks that each host is associated with an installation of the target release.
3. Verifies that the current release supports an upgrade to the target release.
4. Verifies that the management instances are running the releases indicated in the model.
5. Determines if the grid is using either an active standby or single management instance configuration.
  
  Note:
  
  The tasks to follow vary depending of the configuration detected and which management instances, if any, need to be upgraded. Next are the tasks for when neither management instance in an active standby configuration has been upgraded to the target release.
6. Runs the ttGridAdmin instanceModify command to change the installation used by the standby management instance to the installation of the target release.
7. Runs the ttGridAdmin modelApply command to apply the change made to the model.
8. Runs the ttGridAdmin mgmtStandbyStop command to stop the standby management instance.
9. Runs the ttGridAdmin mgmtStandbyStart command to restart the standby management instance. The instance now uses the installation files provided by the target release to operate.
  
  Note:
  
  For a single management instance configuration, TimesTen would only need to perform tasks 1 through 9, where tasks 6 through 9 are performed on the active management instance. In such case, after stopping the instance, no other management operations can be performed on the grid until the instance is once more operational.
10. Runs the ttGridAdmin mgmtActiveSwitch command to stop the active management instance and fail over to the standby management instance. Now, the active management instance is the instance using the installation of the target release.
11. Runs the ttGridAdmin mgmtStandbyStart command to restart the standby management instance, which has yet to be upgraded.
12. Runs the ttGridAdmin instanceModify command to change the installation used by the standby management instance to the installation of the target release.
13. Runs the ttGridAdmin modelApply command to apply the change made to the model.
14. Runs the ttGridAdmin mgmtStandbyStop command to stop the standby management instance.
15. Runs the ttGridAdmin mgmtStandbyStart command to restart the standby management instance. The instance now uses the installation files provided by the target release to operate.
16. Runs the ttGridAdmin mgmtActiveSwitch command to stop the active management instance and fail over to the standby management instance. Now, the active management instance is the same instance as in the beginning of the operation.
17. Runs the ttGridAdmin mgmtStandbyStart command to restart the standby management instance.

Now that you have successfully upgraded the management instances to the target release, you can proceed to upgrading the data instances.

For more information on the ttGridAdmin gridUpgrade command, see Upgrade a Grid (gridUpgrade) in Oracle TimesTen In-Memory Database Reference.

Upgrade the Data Instances

TimesTen supports both online and offline upgrades of data instances between patch-compatible releases on a case by case basis. The metadata TimesTen uses to determine if a grid is patch compatible to another and if either or both type of upgrades are possible is included in every TimesTen installation.

An online upgrade consists on upgrading the data instances in such a manner that there is always at least one copy of the database available for applications to connect. This means that TimesTen only supports online upgrades for grids with k set to 2 or greater and with at least one loaded database.

An offline upgrade consists of upgrading the data instances while all databases are unloaded from memory. TimesTen supports offline upgrades for all values of K-safety.

These topics describe how to perform an online or offline upgrade of data instances:

Online Upgrade of Data Instances

Use the -type data -online options of the ttGridAdmin gridUpgrade command to perform an online upgrade of the data instances to the target release.

Upgrade the data instances to the target release.

% ttGridAdmin gridUpgrade -type data -to 22.1.1.19.0 -online
Checking prerequisites................................................OK
Checking for existing installations of TimesTen 22.1.1.19.0............OK
Verify that upgrade is known to be supported..........................OK
Verify that instances are running the expected releases...............OK
Modify instance host3.instance1.......................................OK
Apply model...........................................................OK
Stop host3.instance1..................................................OK
Start host3.instance1.................................................OK
Waiting for host3.instance1 database database1 to reload..............OK     
Modify instance host6.instance1.......................................OK
Apply model...........................................................OK
Stop host6.instance1..................................................OK
Start host6.instance1.................................................OK
Waiting for host6.instance1 database database1 to reload..............OK     
Modify instance host4.instance1.......................................OK
Apply model...........................................................OK
Stop host4.instance1..................................................OK
Start host4.instance1.................................................OK
Waiting for host4.instance1 database database1 to reload..............OK     
Modify instance host7.instance1.......................................OK
Apply model...........................................................OK
Stop host7.instance1..................................................OK
Start host7.instance1.................................................OK
Waiting for host7.instance1 database database1 to reload..............OK     
Modify instance host5.instance1.......................................OK
Apply model...........................................................OK
Stop host5.instance1..................................................OK
Start host5.instance1.................................................OK
Waiting for host5.instance1 database database1 to reload..............OK     
Modify instance host8.instance1.......................................OK
Apply model...........................................................OK
Stop host8.instance1..................................................OK
Start host8.instance1.................................................OK
Waiting for host8.instance1 database database1 to reload..............OK

TimesTen performs these tasks while the ttGridAdmin gridUpgrade -type data -online command is in operation:

Checks that the grid meets all the prerequisites required for an upgrade operation.
Checks that each host in the grid has an installation of the target release associated with it.
Verifies that the current release supports an online upgrade to the target release.
Verifies that the data instances are running the releases indicated in the model.
Runs the ttGridAdmin instanceModify command to change the installation used by a non-upgraded data instance to the installation of the target release.
Runs the ttGridAdmin modelApply command to apply the change made to the model.
Runs the ttGridAdmin instanceExec -only host.instance ttDaemonAdmin -stop command to stop the data instance from task 5.
Runs thettGridAdmin instanceExec -only host.instance ttDaemonAdmin -start command restart the data instance from the previous task. The instance now uses the installation files provided by the target release to operate.
Waits for the data instance from the previous task to reload the local element of each loaded database before proceeding to the next data instance to upgrade.
Repeats tasks 5 through 9 until all data instances have been upgraded.

Now you have successfully upgraded your grid to the target release.

For more information on the ttGridAdmin gridUpgrade command, see Upgrade a Grid (gridUpgrade) in Oracle TimesTen In-Memory Database Reference.

Offline Upgrade of Data Instances

Use the -type data -offline options of the ttGridAdmin gridUpgrade command to perform an online upgrade of the data instances to the target release.

Upgrade the data instances to the target release.
```
% ttGridAdmin gridUpgrade -type data -to 22.1.1.19.0 -offline
Checking prerequisites................................................OK
Checking for existing installations of TimesTen 22.1.1.19.0............OK
Verify that upgrade is known to be supported..........................OK
Verify that instances are running the expected releases...............OK
Determining data instance state.......................................OK
Modify instance host3.instance1.......................................OK
Modify instance host4.instance1.......................................OK
Modify instance host5.instance1.......................................OK
Modify instance host6.instance1.......................................OK
Modify instance host7.instance1.......................................OK
Modify instance host8.instance1.......................................OK
Apply changes.........................................................OK
Stop data instances...................................................OK
Start data instances..................................................OK
```
TimesTen performs these tasks while the ttGridAdmin gridUpgrade -type data -offline command is in operation:
1. Checks that the grid meets all the prerequisites required for an upgrade operation.
2. Checks that each host in the grid has an installation of the target release associated with it.
3. Verifies that the current release supports an offline upgrade to the target release.
4. Verifies that the data instances are running the releases indicated in the model.
5. Runs the ttGridAdmin instanceModify command to change the installation used by a non-upgraded data instance to the installation of the target release. TimesTen repeats this task until all data instances use an installation of the target release.
6. Runs the ttGridAdmin modelApply command to apply the changes made to the model.
7. Runs the ttGridAdmin instanceExec -type data ttDaemonAdmin -stop to stop all data instances.
8. Runs the ttGridAdmin instanceExec -type data ttDaemonAdmin -start command restart all data instances. The data instances now use the installation files provided by the target release to operate.

Now you have successfully upgraded your grid to the target release.

For more information on the ttGridAdmin gridUpgrade command, see Upgrade a Grid (gridUpgrade) in Oracle TimesTen In-Memory Database Reference.

Upgrading a Grid Without the ttGridAdmin gridUpgrade Command

To upgrade a grid to a patch-compatible release without the ttGridAdmin gridUpgrade command, complete these tasks:

Create Installations of the Target Release

You may use the ttGridAdmin installationList command to determine the hosts that need to be upgraded and the location of the current installations, as shown next.

% ttGridAdmin installationList
Host  Install       Location                     Comment
----- ------------- ---------------------------- -------
host1 installation1 /grid/tt22.1.1.18.0
host2 installation1 /grid/tt22.1.1.18.0
host3 installation1 /grid/tt22.1.1.18.0
host4 installation1 /grid/tt22.1.1.18.0
host5 installation1 /grid/tt22.1.1.18.0
host6 installation1 /grid/tt22.1.1.18.0
host7 installation1 /grid/tt22.1.1.18.0
host8 installation1 /grid/tt22.1.1.18.0

Create an installation from the new TimesTen release on every host defined in the model.

Note:

If the default name for installations, installation1, is already in use, you need to provide a name for the new installation. The example uses installation2 as the name for the new installation on every host of the grid.

% ttGridAdmin installationCreate host1.installation2 -location /grid -source host1:/mydir/timesten2211190.server.linux8664.zip
Installation installation2 on Host host1 created in Model

% ttGridAdmin installationCreate host2.installation2 -location /grid -source host1:/mydir/timesten2211190.server.linux8664.zip
Installation installation2 on Host host2 created in Model

% ttGridAdmin installationCreate host3.installation2 -location /grid -source host1:/mydir/timesten2211190.server.linux8664.zip
Installation installation2 on Host host3 created in Model

% ttGridAdmin installationCreate host4.installation2 -location /grid -source host1:/mydir/timesten2211190.server.linux8664.zip
Installation installation2 on Host host4 created in Model

% ttGridAdmin installationCreate host5.installation2 -location /grid -source host1:/mydir/timesten2211190.server.linux8664.zip
Installation installation2 on Host host5 created in Model

% ttGridAdmin installationCreate host6.installation2 -location /grid -source host1:/mydir/timesten2211190.server.linux8664.zip
Installation installation2 on Host host6 created in Model

% ttGridAdmin installationCreate host7.installation2 -location /grid -source host1:/mydir/timesten2211190.server.linux8664.zip
Installation installation2 on Host host7 created in Model

% ttGridAdmin installationCreate host8.installation2 -location /grid -source host1:/mydir/timesten2211190.server.linux8664.zip
Installation installation2 on Host host8 created in Model

Apply the changes made to the latest version of the model. TimesTen copies the installation files to the location specified for each host.
```
% ttGridAdmin modelApply
```

For more information on the ttGridAdmin installationList or ttGridAdmin installationCreate command, see List Installations (installationList) or Create an Installation (installationCreate), respectively, in Oracle TimesTen In-Memory Database Reference.

For more information on the ttGridAdmin modelApply command, see Applying the Changes Made to the Model and Model Operations in Oracle TimesTen In-Memory Database Reference.

Upgrade the Management Instances

How to upgrade the management instances depends on whether there is one or two management instances configured in the grid. Follow the procedure that better applies to your configuration:

Active Standby Configuration

When you have an active standby configuration for your management instances, you can upgrade each management instance separately without any interruption of service by ensuring that an active management instance is always up.

Stop the standby management instance.

% ttGridAdmin mgmtStandbyStop
Standby management instance host2.instance1 stopped

Modify the standby management instance to use the new installation.

% ttGridAdmin instanceModify host2.instance1 -installation installation2
Instance instance1 on Host host2 modified in Model

Apply the changes made to the latest version of the model.
```
% ttGridAdmin modelApply
```
Start the standby management instance by running the ttGridAdmin mgmtStandbyStart command on the standby management instance.
```
% ttGridAdmin mgmtStandbyStart
Standby management instance started
```
Verify that the standby management instance is operational and synchronized with the active management instance with the ttGridAdmin mgmtStatus command.
```
% ttGridAdmin mgmtStatus
Host Instance Reachable RepRole(Self) Role(Active) Role(Self) Seq RepAgent RepActive
------------------------------------------------------------------------------ 
host1 instance1 Yes     Active        Unknown      Active     445 Up       Yes
host2 instance1 Yes     Standby       Unknown      Standby    445 Up       No
```
Note:

Ensure that the sequence number matches in both instances to ensure that both instances are communicating properly and synchronized. If the sequence number does not match, run the ttGridAdmin mgmtExamine command for instructions on how to proceed. See Examine Management Instances (mgmtExamine) in Oracle TimesTen In-Memory Database Reference.
On the standby management instance, switch the active and standby management instances.
```
% ttGridAdmin mgmtActiveSwitch
This is now the active management instance
```
TimesTen Scaleout stops the active management instance and promotes the standby management instance to active.

On the new active management instance, modify the installation of the old active management instance.

% ttGridAdmin instanceModify host1.instance1 -installation installation2
Instance instance1 on Host host1 modified in Model

Apply the changes made to the latest version of the model.
```
% ttGridAdmin modelApply
```
On the old active management instance, start the instance as a standby management instance.
```
% ttGridAdmin mgmtStandbyStart
Standby management instance started
```
Verify that the standby management instance is operational and synchronized with the active management instance.
```
% ttGridAdmin mgmtStatus
Host Instance Reachable RepRole(Self) Role(Active) Role(Self) Seq RepAgent RepActive
------------------------------------------------------------------------------ 
host1 instance1 Yes     Standby       Unknown      Standby    451 Up       No
host2 instance1 Yes     Active        Unknown      Active     451 Up       Yes
```
Note:

Ensure that the sequence number matches in both instances to ensure that both instances are communicating properly and synchronized. If the sequence number does not match, run the ttGridAdmin mgmtExamine command for instructions on how to proceed. See Examine Management Instances (mgmtExamine) in Oracle TimesTen In-Memory Database Reference.

For more information on the ttGridAdmin mgmtStandbyStop, ttGridAdmin mgmtStandbyStart, and ttGridAdmin mgmtStatus commands, see Management Instance Operations in Oracle TimesTen In-Memory Database Reference.

For more information on the ttGridAdmin instanceModify command, see Modify an Instance (instanceModify) in Oracle TimesTen In-Memory Database Reference.

For more information on the ttGridAdmin mgmtActiveSwitch command, see Starting, Stopping and Switching Management Instances in this document and Switch the Active Management Instance (mgmtActiveSwitch) in Oracle TimesTen In-Memory Database Reference.

For more information on the ttGridAdmin modelApply command, see Applying the Changes Made to the Model and Model Operations in Oracle TimesTen In-Memory Database Reference.

Upgrading a Single Management Instance

In a single management instance configuration, you need to restart the active management instance for the new installation to take effect, as shown next:

Modify the active management instance to use the new installation.

% ttGridAdmin instanceModify host1.instance1 -installation installation2
Instance instance1 on Host host1 modified in Model

Apply the changes made to the latest version of the model.
```
% ttGridAdmin modelApply
```

Stop the active management instance.

% ttGridAdmin mgmtActiveStop
Active management instance stopped

Restart the active management instance.

% ttGridAdmin mgmtActiveStart
This management instance is now the active

For more information on the ttGridAdmin instanceModify command, see Modify an Instance (instanceModify) in Oracle TimesTen In-Memory Database Reference.

For more information on the ttGridAdmin modelApply command, see Applying the Changes Made to the Model and Model Operations in Oracle TimesTen In-Memory Database Reference.

For more information on the ttGridAdmin mgmtActiveStop and ttGridAdmin mgmtActiveStart, see Management Instance Operations in Oracle TimesTen In-Memory Database Reference.

Upgrade the Data Instances

Before you can restart a data instance so that the new installation takes effect, you need to unload all databases:

Unload all databases as shown in Unloading a Database from Memory.

Stop all data instances.

% ttGridAdmin instanceExec -type data ttDaemonAdmin -stop
Overall return code: 0
Commands executed on:
  host3.instance1 rc 0
  host4.instance1 rc 0
  host5.instance1 rc 0
  host6.instance1 rc 0
  host7.instance1 rc 0
  host8.instance1 rc 0
Return code from host3.instance1: 0
Output from host3.instance1:
TimesTen Daemon (PID: 4498, port: 6624) stopped.
Return code from host4.instance1: 0
Output from host4.instance1:
TimesTen Daemon (PID: 4536, port: 6624) stopped.
Return code from host5.instance1: 0
Output from host5.instance1:
TimesTen Daemon (PID: 4492, port: 6624) stopped.
Return code from host6.instance1: 0
Output from host6.instance1:
TimesTen Daemon (PID: 4510, port: 6624) stopped.
Return code from host7.instance1: 0
Output from host7.instance1:
TimesTen Daemon (PID: 4539, port: 6624) stopped.
Return code from host8.instance1: 0
Output from host8.instance1:
TimesTen Daemon (PID: 4533, port: 6624) stopped.

Modify all the data instances to use the new installations.

Note:

You can perform this step before unloading the databases or stopping the data instances if you want to reduce the down time the databases incur during the upgrading operation.

% ttGridAdmin instanceModify host3.instance1 -installation installation2
Instance instance1 on Host host3 modified in Model

% ttGridAdmin instanceModify host4.instance1 -installation installation2
Instance instance1 on Host host3 modified in Model

% ttGridAdmin instanceModify host5.instance1 -installation installation2
Instance instance1 on Host host3 modified in Model

% ttGridAdmin instanceModify host6.instance1 -installation installation2
Instance instance1 on Host host3 modified in Model

% ttGridAdmin instanceModify host7.instance1 -installation installation2
Instance instance1 on Host host3 modified in Model

% ttGridAdmin instanceModify host8.instance1 -installation installation2
Instance instance1 on Host host3 modified in Model

Apply the changes made to the latest version of the model.
```
% ttGridAdmin modelApply
```

Restart all data instances.

% ttGridAdmin instanceExec -type data ttDaemonAdmin -start
Overall return code: 0
Commands executed on:
  host3.instance1 rc 0
  host4.instance1 rc 0
  host5.instance1 rc 0
  host6.instance1 rc 0
  host7.instance1 rc 0
  host8.instance1 rc 0
Return code from host3.instance1: 0
Output from host3.instance1:
TimesTen Daemon (PID: 19072, port: 6624) startup OK.
Return code from host4.instance1: 0
Output from host4.instance1:
TimesTen Daemon (PID: 19144, port: 6624) startup OK.
Return code from host5.instance1: 0
Output from host5.instance1:
TimesTen Daemon (PID: 19210, port: 6624) startup OK.
Return code from host6.instance1: 0
Output from host6.instance1:
TimesTen Daemon (PID: 19247, port: 6624) startup OK.
Return code from host7.instance1: 0
Output from host7.instance1:
TimesTen Daemon (PID: 19284, port: 6624) startup OK.
Return code from host8.instance1: 0
Output from host8.instance1:
TimesTen Daemon (PID: 19315, port: 6624) startup OK.

Restart all databases as shown in Reloading a Database into Memory.

For more information on the ttGridAdmin instanceExec or ttGridAdmin instanceModify command, see Execute a Command or Script on Grid Instances (instanceExec) or Modify an Instance (instanceModify), respectively, in Oracle TimesTen In-Memory Database Reference.

For more information on the ttGridAdmin modelApply command, see Applying the Changes Made to the Model and Model Operations in Oracle TimesTen In-Memory Database Reference.

Optional: Delete the Installations of the Previous Release

To avoid assigning the wrong installation to new instances, it is recommended that you delete the installations of the previous release from your grid.

Delete the installation objects of the previous model in the model.

% ttGridAdmin installationDelete host1.installation1
Installation installation1 on Host host1 deleted from Model

% ttGridAdmin installationDelete host2.installation1
Installation installation1 on Host host2 deleted from Model

% ttGridAdmin installationDelete host3.installation1
Installation installation1 on Host host3 deleted from Model

% ttGridAdmin installationDelete host4.installation1
Installation installation1 on Host host4 deleted from Model

% ttGridAdmin installationDelete host5.installation1
Installation installation1 on Host host5 deleted from Model

% ttGridAdmin installationDelete host6.installation1
Installation installation1 on Host host6 deleted from Model

% ttGridAdmin installationDelete host7.installation1
Installation installation1 on Host host7 deleted from Model

% ttGridAdmin installationDelete host8.installation1
Installation installation1 on Host host8 deleted from Model

Apply the changes made to the latest version of the model.
```
% ttGridAdmin modelApply
```
If the installation files associated with the installation model objects you just deleted are not in use by any other installation object in this or any other grid, then delete the files on every host. Ensure that you change the permissions of the directory so that you can delete all files.
```
% cd /grid
% chmod -R 750 tt22.1.1.18.0/
% rm -rf tt22.1.1.18.0/
```

For more information on the ttGridAdmin installationDelete command, see Delete an Installation (installationDelete) in Oracle TimesTen In-Memory Database Reference.