IBM PureData System for Analytics (Netezza) configuration choices that impact migration to Db2products
Some PureData® System for Analytics (Netezza®) configuration choices can result in compatibility issues when you migrate to a Db2® product.
Some of these choices are as follows:
- Multiple schemas
- If you configured your Netezza system to support
multiple schemas in multiple databases, migrate by using one of the following approaches. For each
approach, use the db_migrate command or Database Harmony Profile tool.
- If there are no conflicting schemas across the databases, drop the database identifiers, and then migrate to a single BLUDB database.
- If there are conflicting schemas across the databases, merge each database identifier and each schema into a single schema, and then migrate to a single BLUDB database.
- Case setting for identifiers
- In a Db2 system, lowercase identifiers, such as for table names, are converted to uppercase. This is also the default behavior in a Netezza system. However, if you used the nzinitsystem -lowercase or nzconvertsyscase command to force the Netezza system to use lowercase ...
- Time zone
- Netezza uses UTC by default, but you might have configured Netezza to use a different time zone. The Db2 products also use UTC by default. If you require time stamps, times, or dates to use a different time zone, use the TO_UTC_TIMESTAMP or TIMEZONE function.
- Encoding and collation
-
A Db2 system uses UTF-8 encoding with IDENTITY collation. A Netezza system uses Latin-9 encoding for single-byte characters and UTF-8 encoding for multibyte characters, with a default collation of BINARY. The differences between systems can result in data expansion when you load data and differences in how character data is ordered.