Frequently asked questions about data migration

This FAQ provides you with answers to common questions regarding migrating data to on-premises systems.

General

How does Lift CLI migrate data to Db2 Warehouse on Cloud?

Migration from PureData System to Db2 Warehouse SaaS

Can the Lift CLI be installed directly on PureData System for Analytics?
What are the best practices for attaching and configuring additional storage for PureData System for Analytics?
On what part of my on-premises system should I install the Lift CLI if I'm using IBM PureData for Analytics sources?
Where should I install the Lift CLI for the best throughput if I’m using IBM PureData System for Analytics as my source?

Migration from Db2 to Db2 Warehouse SaaS

Where should I install the Lift CLI for the best throughput if I’m using IBM Db2 for Linux UNIX and Windows as my source?
What are the Db2 client requirements to extract my data from IBM Db2 for Linux UNIX and Windows with better performance?

How does Lift CLI migrate data to Db2 Warehouse on Cloud?

If you're migrating data from your IBM PureData System for Analytics (Netezza) database, you will first need to locally extract a database table to a CSV file using lift extract. Then, you will transfer your CSV data file to the IBM Db2 Warehouse as a Service landing zone using lift put. The IBM Db2 Warehouse as a Service landing zone is a pre-allocated volume used for data loading & scratch. Finally, you will load the uploaded CSV data file into the engine using lift load. Once the load is complete, you can delete the data file using lift rm.

If you're migrating a set of CSV files, you'll follow a similar set of steps to above. You'll start by transferring your CSV data files to the Db2 Warehouse SaaS landing zone using lift put. The Db2 Warehouse SaaS landing zone is a pre-allocated volume used for data loading & scratch. Finally, you will load the uploaded CSV data file into the engine using lift load. Once the load is complete, you can delete the data file using lift rm.

Can the Lift CLI be installed directly on PureData System for Analytics?

Yes, the Lift CLI can be installed on the PureData System for Analytics, but additional storage must be attached to provide the extracted data sufficient staging disk space.

What are the best practices for attaching and configuring additional storage for PureData System for Analytics?

The following tech notes provide steps to mount SAN/NFS systems on PureData Systems for Analytics. They also include best practices for attaching and configuring additional storage for PureData System for Analytics.

On what part of my on-premises system should I install the Lift CLI if I'm using IBM PureData for Analytics sources?

When you are installing the Lift CLI for PureData System for Analytics sources, install the Lift CLI on your "injection" system (the system that you use to stage data to load into the PureData System for Analytics database). That system will have good connectivity to the PureData System for Analytics and will have lots of disk space for staging data. However, if your injection system is already fully loaded, then install the Lift CLI on a similar system that is similarly connected and with significant staging disk space.

Where should I install the Lift CLI for the best throughput if I’m using IBM PureData System for Analytics as my source?

We strongly recommend that you install the Lift CLI on a Linux machine. When your Lift CLI is installed on a Linux machine, data extraction from PureData System for Analytics sources is done with high speed unload facilities. Install your Lift CLI on Linux for significantly better overall throughput when your source is PureData System for Analytics.

Where should I install the Lift CLI for the best throughput if I’m using IBM Db2 for Linux UNIX and Windows as my source?

We strongly recommend that you install the Lift CLI on a Linux machine with Db2 client installation. Installing Lift CLI on your Linux machine with Db2 client significantly improves overall throughput. When Lift CLI fails to detect Db2 client, different extract strategy is used and you may notice reduced extract throughput. A message on console "Lift is extracting data at sub-light speeds. You can improve extraction time by installing and configuring the Db2 client. For more information, visit "Installation methods for IBM data server clients", is printed when Db2 client is not available on your machine where Lift CLI is installed.

What are the Db2 client requirements to extract my data from IBM Db2 for Linux UNIX and Windows with better performance?

Prerequisites for Lift CLI to use Db2 client:

db2 (for Linux) or db2cmd (for Windows) command have to be available in PATH.
- Linux: <INSTANCE_OWNER_HOME>/sqllib/db2profile has to be applied to environment before executing LIFT CLI.
- Windows: The Db2 client has to be set as default instance.
The OS user has to be included in SYSADM group of the Db2 client instance if Lift CLI is run remotely from IBM Db2 for Linux UNIX and Windows server.
Version of the Db2 client has to be same or higher than version of IBM Db2 for Linux UNIX and Windows server.

Yes. Extracting hidden columns is supported by Lift CLI. By default, hidden columns are not included in the extracted CSV file. If you want to include hidden columns in the extracted data, explicitly specify all column names along with hidden column names by using column selection option. Refer lift extract --help for more information on column selection option.