Altibase

Altibase

When migrating Altibase version 5.1.5 or lower, the characters are broken.

Cause

Altibase version 5.1.5 or lower does not support globalization, so JDBC does not know how to handle the character set of the database.

Solution

You must include the character set value (for example, KSC5601) set in the destination database in the encoding option of the corresponding database connection information in the Migration Center. Here's how to check the Altibase character set.

• Version 4.3.9 ~ 5.1.5:
  

  SELECT VALUE1 FROM V$PROPERTY WHERE NAME = 'NLS_USE';
  

• Version 5.3.3 or later:
  

  SELECT NLS_CHARACTERSET FROM V$NLS_PARAMETERS;
  

In the Reconcile step, "Tablespace to Tablespace Mapping" does not show a specific tablespace.

Cause

The user in the connection information at the Migration Center does not have privilege to access to the tablespace.

Solution

Grant the Altibase user access to the tablespace.

When migrating Altibase version 4.5.1.0 or earlier, it fails to retrieve information of a column whose data type is BLOB, byte, or nibble.

Cause

The Altibase JDBC driver of the corresponding version cannot return the BLOB, byte, or nibble data type to UNKOWN to know the column data type.

Solution

Tables with BLOB, byte, and nibble data types are migrated using aexport and iLoader.

Some data of bit, varbit, and nibble data types migrated from Altibase 6.1.1 and earlier versions do not match the original database.

Cause

When the Altibase 6.1.1 or lower JDBC driver inserts bit, varbit, or nibble type data in batch execution, it fails to migrate some data normally.

Solution

Open the project, click the menu Migration-Migration Option, select 'No' for Batch Execution, and perform data migration.