Oracle Audio Technologies B31679-01 manual Record of Upgrades

3.Use ttMigrate to migrate the data store from the old version to the new version. See “Moving between 32-bit and 64-bit data stores” on page 101 for an example of this procedure.

4.Start the new version of TimesTen Server, if you have not already. The client applications now have access to the upgraded data stores.

Note: Since both versions have TimesTen Server have been configured to listen on the same port in this procedure, if you wish to restart the old version you must first configure it to listen on a different port.

Client/Server online upgrade with continuous access to the data store

The migration of a data store using ttMigrate can be a long process if your data stores are very large. If it is critical that your client applications have nearly continuous access to the data store during the Client/Server online upgrade procedure, you may incorporate the procedure for performing an online upgrade with replication using the following steps:

1.Install the new version of TimesTen, making sure to configure TimesTen Server to listen on the same port as the old version. You will be asked whether you would like to start the new server, and must answer no.

2.Follow the steps in “Performing an online upgrade with replication” on page 104 to upgrade one copy of the data store. The client applications will remain connected to the other, non-upgraded copy of the data store.

3.Disconnect all clients from the old version of the data store.

4.Stop the old version of TimesTen Server.

5.Wait for all updates to finish replicating from the old version of the data store to the new version.

6.Start the new version of TimesTen Server. It will begin listening on the same port as the old version, and client applications may now connect to the new version of the data store with no change to their configurations.

Record of Upgrades

A new set of tables with the prefix ttrep_schema_version- is created each time that the ttMigrate -rcommand is used. These tables provide a history of the data store’s replication scheme from release to release.

Data Store Upgrades 117