Optim High Performance Unload configuration for unsupported locales

Optim™ High Performance Unload uses the Internationalization Components for Unicode, (ICU) (http://www.ibm.com/icu), for implementing its internationalization and globalization support.

By default, Optim High Performance Unload, determines which ICU converter to use from the current locale for converting text data extracted from Db2® tables to the unloaded files.

Normally, Optim High Performance Unload can determine the correct converter from the locale string by using internal tables or the shipped version of the db2hpu.locale file. However, sometimes you might need to quickly handle some situations independently, without waiting for a fix or code change from IBM®. For example, you might upgrade your operating system to a new level that uses a new and currently undefined locale. In other cases, you might need to extract a table from a backup that exists on a foreign system. Moreover, if you are performing a cross-system unload, you might need to map the locale of the source system to the locale of the destination system.