Oracle Audio Technologies B31679-01 - Manual (Page 103)

Data Store Upgrades 95
a Client/Server online upgrade from a TimesTen version prior to 6.0”
on page 113
.
• If you are upgrading from a version of TimesTen that is 6.0 or above,
the process is much easier. Starting with 7.0, TimesTen Server is able
to talk directly to all versions of TimesTen Client from 6.0 onward.
There is no need to keep the old installation of TimesTen Server
when upgrading to the new version in this case. See
“Performing a
Client/Server online upgrade from TimesTen version 6.0 and above”
on page 116
.
The simple Client/Server online upgrade process minimizes, but does
not eliminate, the interruption of client application access to the data
store being upgraded. To maintain nearly continuous availability of a
data store to all clients, you may use the approach outlined in
“Online
upgrades with replication” on page 94 to keep an identical copy of the
data store available to the old version of TimesTen Server while you
upgrade the first copy to the new version. Once the upgraded copy of
the data store is available to the new version of TimesTen Server, you
may stop the old version and start the new version, listening on the same
port. The only interruption in availability using this method will be the
very brief period during which the old server is stopped and the new
server is started.
On Windows, more than one version of TimesTen cannot be installed at
the same time. Therefore, it is not possible to perform online upgrades
with Client/Server on Windows if you are upgrading from a version of
TimesTen prior to 6.0. It is also not possible to combine the Client/
Server online upgrade procedure with that for performing an online
upgrade with replication unless you use two different machines, one for
each version of the data store that you are upgrading.
Performing an in-place data store upgrade
To upgrade an existing data store without exporting the data store to an
external format, you can perform an in-place upgrade. This requires that
all applications disconnect from the data store and that the data store be
unloaded from shared memory.
Unloading a data store
TimesTen data stores remain loaded in shared memory as long as any
applications or TimesTen agents (such as the cache or replication
agents) are connected to them. Data stores may also be kept in shared
memory, even when no applications or agents are connected, if the
RAM policy of the data store has been modified using the
ttAdmin