Data Store Upgrades
89
the same as the character set specified for the Oracle database that
the TimesTen data store connects to.
• Replication is not possible between data stores with different
character sets. Because data stores created with versions of TimesTen
prior to 7.0 do not have a data store character set specified, a special
data store character set, TIMESTEN8, has been created, which
allows replication compatibility between data stores created by
TimesTen 7.0 and those created by earlier releases. If you plan to
perform the data store upgrade as an online upgrade with replication
(see
“Performing an online upgrade with replication” on page 104
),
then you must specify a
DatabaseCharacterSet
of TIMESTEN8 in
your TimesTen 7.0 DSN.
• If you use TimesTen Client/Server and intend to connect to the
upgraded data store with an application linked to a Client ODBC
library from a version prior to TimesTen 7.0, you must specify a
DatabaseCharacterSet
of TIMESTEN8 in your TimesTen 7.0 DSN
in order to ensure compatibility. See
“Performing a Client/Server
online upgrade from a TimesTen version prior to 6.0” on page 113
or
“Performing a Client/Server online upgrade from TimesTen version
6.0 and above” on page 116
.
Note:
The TIMESTEN8 data store character set is intended for use
only when transitioning from a version of TimesTen prior to 7.0. When
you no longer need your data store to replicate to a pre-7.0 version of
TimesTen, or to connect to a pre-7.0 client application, you should use
ttMigrate
to convert your data store to a data store character set other
than TIMESTEN8. See
“Data store character set conversion” on page
91
for details.
Data type conversion
When performing an upgrade from a version prior to TimesTen 7.0, you
must choose whether to preserve the data types in your data store as
TimesTen data types, or whether to convert them to Oracle data types.
Your planned use for the data store and your preferred upgrade method
will have an impact on this decision.
