Migrating UDX, INZA, IFQ Functions, and SQL Extension Toolkit from IBM PureData System for Analytics
Learn about extra steps that you need to complete for seamless migration from a previous generation appliance.
Migrating INZA and SQL Extension Toolkit
- Uninstall INZA and SQL Extension Toolkit from the IBM®
PureData® System for Analytics appliance.
Make sure you have the
.cpp
files andnz_ddl
output of dependent objects before you drop them. You must recreate the items after you upgrade INZA and SQL Extension Toolkit.If you have dependent objects on the appliance, make sure you have copies of the
.cpp
files and their backups. Use the nz_ddl* tool to make the copies. - Run nz_migrate or take a backup and restore on Netezza Performance Server.
Do not migrate the old version of INZA and SQL Extension Toolkit. The SPU and host on the previous generation appliances are 32-bit and the SPU and host on Netezza Performance Server are 64-bit. You need to install the new SQL Extension Toolkit and INZA after the migration is completed.
Migrating IBM Fluid Query Functions after INZA installation to 11.2.X.X
- After you upgrade INZA to 11.2.X.X, reregister the
IFQAdmin
function:/nz/export/ae/products/fluidquery/fqRegister.sh --ifq-admin
- Reregister data connector/data movement functions with fqRegister.sh.
Migrating custom UDX from IBM PureData System for Analytics
After the migration is complete, you must recompile UDXs for them to work.
- Find all 32-bit UDXs (excluding INZA and SQL Extension Toolkit). Follow the steps that are described in Finding 32-bit UDX signature for Netezza Performance Server. This tool also indicates whether the correct INZA and SQL Extension toolkit is installed on system.
- After you identified the 32-bit host and 32-bit SPU code by running the nz_find_32bit_udx utility, recompile the code and reregister the UDXs in Netezza Performance Server. Follow the steps that are described in Recompiling 32-bit UDXs.