The following sections contain the compatibility matrix, upgrade notes, and general notes for Netezza Analytics Version 3.x
Database compatibility with NPS
- Netezza Analytics Version 184.108.40.206 requires that your Netezza systems run NPS Release 220.127.116.11 or later.
- Netezza Analytics Version 18.104.22.168 requires that your Netezza systems run NPS Release 22.214.171.124 or later.
- Netezza Analytics Version 126.96.36.199 requires that your Netezza systems run NPS Release 188.8.131.52 or later.
- Netezza Analytics Version 184.108.40.206 requires that your Netezza systems run NPS Release 220.127.116.11 or later.
- Netezza Analytics Version 18.104.22.168 and Version 3.0 require that your Netezza systems run NPS Release 7.0.4 P1 or later.
- Depending on the version which you are upgrading from and other factors, you might also need to recompile and reregister your Analytic Executable (AE) applications to run them in the corresponding NPS environment. See the section Upgrade notes for further details on this subject.
Compatibility with R
- Netezza Analytics Version 22.214.171.124, Version 126.96.36.199 and Netezza Analytics Version 188.8.131.52 are compatible with R 3.0.2 up to R 3.1.1.
- Netezza Analytics Version 184.108.40.206 and Netezza Analytics Version 220.127.116.11 are compatible with R 3.0.2.
Compatibility with Revolution R Enterprise for IBM Netezza
- Netezza Analytics V18.104.22.168, V22.214.171.124, V126.96.36.199, V188.8.131.52, and V184.108.40.206 do not work with Revolution R Enterprise.
- Netezza Analytics V3.0 requires Revolution R Enterprise for IBM Netezza release 6.2.
Compatibility matrix for Netezza Analytics V2.0.5 and later and NPS 6.0.5 and later
|Netezza Analytics Version||NPS Version|
|2.0.5||6.0.5 P5 or later, but 6.0.5 P10 is recommended|
|2.0.6||220.127.116.11 or the NPS versions that are supported for Netezza Analytics 2.0.5.
18.104.22.168 does not support any Netezza Analytics versions before Netezza Analytics Version 2.0.6.
|2.5.0||7.0 or later|
|2.5.1||7.0 or later|
|2.5.2||7.0 or later|
|2.5.3||7.0 or later|
|2.5.4||7.0 or later
If NPS Release 7.0.3 is used, 7.0.3 P2 or later is recommended.
|3.0||7.0.4 P1 or later|
|22.214.171.124||7.0.4 P1 or later
To install Netezza Analytics Version 126.96.36.199 in an existing replication environment, NPS 188.8.131.52 is required.
|184.108.40.206||220.127.116.11 or later
To install Netezza Analytics Version 18.104.22.168 in an existing replication environment, NPS 22.214.171.124 or later is required.
|126.96.36.199||188.8.131.52 or later|
|184.108.40.206||220.127.116.11 or later|
|18.104.22.168||22.214.171.124 or later|
Local nzspatial database on subordinate nodes is not upgraded automatically
To manually update the local nzspatial databases, run the following command:
Backup of databases that are enabled for Netezza Analytics V2.5.x before migrating to V3.0.x
After you migrate the databases that are enabled for Netezza Analytics V2.5.x to Netezza Analytics V3.0 or later, you cannot revert the migration. Therefore, make a backup of all databases that are enabled for Netezza Analytics V2.5 before you start the migration. Otherwise, you cannot work with these databases if you revert your Netezza Analytics V3.0 or later to Netezza Analytics V2.5.x.
Upgrade from Netezza Analytics V2.x
If you are upgrading from Netezza Analytics V2.x, you must recompile and reregister the Analytics Executable (AE) applications to run them in the V3.0 or later environment as follows:
- Recompile the C AE applications, C++ AE applications, and Fortran AE applications. Other languages do not require this step because they are either interpreted or do not use shared library linking in the same way.
- Reregister all AE applications.
- When you recompile and reregister, you must ensure that all statements of register_ae and compile_ae use --version 3 instead of --version 2. If you still use --version 2 instead of --version 3 after the upgrade, the error ERROR: AE UDX-Adapter Build Mismatch will occur if you upgraded from V2.0.x and might occur if you upgraded V2.5.4.
- When you register or reregister the AE applications, you must also specify the appropriate replication value to register_ae. For more information about the replication values, see the section Upgrade from Netezza Analytics V126.96.36.199 or V3.0. Note that the only relevant portion from this section is about specifying the values and not whether or not you need to reregister.
- All new AEs must also use --version 3.
- If you downgrade from INZA 3.0 to INZA 2.x, you must use --version 2 instead of --version 3.
Upgrade from Netezza Analytics V188.8.131.52 or V3.0
When you upgrade your NPS version to NPS 184.108.40.206 or later, the default values for the UDX replication behavior are chosen, that is REPLICATE BY SQL or REPLICATE BY VALUE. For more information about how the default is chosen, see the NPS documentation.
- If these default values are correct, reregistering the AE applications is not required.
- If these default values are not correct, you must reregister the AE applications. You must also specify the correct value that is to be used by giving the appropriate argument to register_ae.
NPS Upgrade might require a rebuild of database views
When you upgrade to NPS version 7.0.4 P1 or later, re-enable all databases that are enabled for Netezza Analytics because a re-build of the views in these databases might be necessary.
Re-enable the databases during the installation of Netezza Analytics. When the installation is completed, you are asked if you want to re-enable all databases that are enabled for Netezza Analytics.
- If you specify yes, all the databases that are enabled for Netezza Analytics are automatically re-enabled, and all database views are rebuilt. Further actions are not required.
- If you specify no, you get the following message:
The databases that are enabled for Netezza Analytics are not re-enabled at this time.
You can run the script for re-enabling databases at any time by using the following command at a shell prompt:
After you run this command, all the databases that are enabled for Netezza Analytics are re-enabled, and all database views are rebuilt.
- If you do neither of these actions, you might have to recreate database views that were created by Netezza Analytics.
The problem occurs because when a database is enabled for Netezza Analytics by using the script create_inza_db.sh, the script creates some views in the database, for example, V_NZA_MODELS, to access the model metadata. These views are based on particular system views. When a newer NPS version is installed, the new version might update these system views. If that occurs, all views that use those system views become invalid. To make the views valid again, you must rebuild them.
If a rebuild is required, an error message that is similar to the following error message is displayed.
Base table/view '_V_SYS_PRIV' attr 'OBJECTTYPE' has changed (name); rebuild view 'V_NZA_MODELS'
When you receive such an error message, you can run the following script:
Alternately, you can take the following manual steps to rebuild the views to make them valid again:
1. Log in to your database as administrator.
2. Drop the affected views by running the following command:
DROP VIEW V_NZA_MODELS, V_NZA_COMPONENTS, V_NZA_PARAMS, V_NZA_COLPROPS;
3. Re-initialize the database by running the following command:
Note that these steps are needed for each Netezza Analytics-enabled database.
Upgrade removes objects from Netezza Analytics system databases
Upgrading causes permanent removal of database objects. If a previous installation of Netezza Analytics is found on the appliance, the installation process removes the earlier version before installing the new packages. The inza, nza, nzm, and nzr databases are then dropped and all objects in those databases, including objects that were created by users. are permanently removed.
Note that it is not recommended to make such changes in these databases because they are intended for storing the Netezza Analytics code only, but if you have done so, follow these directions to save your data:
- To save the analytic models, create a new database and enable it for IBM Netezza Analytics by running the appropriate script(s) -- create_inza_db.sh, create_inza_db_admin.sh, create_inza_db_developer.sh, and create_inza_db_user.sh. Then, use the COPY_MODEL command to copy the wanted model or models into the new database. Do not copy these objects back to the original database because the original database is always deleted when you upgrade your Netezza Analytics version.
Note: From Netezza Analytics V3, you can no longer enable the inza, nza, nzm, or nzr database for Netezza Analytics. Therefore, you cannot copy the models back to these databases.
- For all other database objects, you can copy them manually to another database by using the appropriate SQL commands. Alternatively, you can use the backup command to save a whole database and then restore it to a different name. In that case, you can also copy the database objects back to the original database after the upgrade. Be certain to adjust user and group privileges when you copy database objects. With this procedure, however, analytics models are not saved because restoring to a different database is not supported for databases that are enabled for Netezza Analytics versions previous to Netezza Analytics V3. You must use the procedure that is outlined in the first bullet.
Appliance workload impact
The functionality of Netezza Analytics is broad and powerful, and it uses various resources on the appliance. Sometimes, the resources that are required to do specific analytic operations might be substantial, for example, large matrix calculations. Although safeguards ensure continued performance of the overall appliance, complex operations might impact other regular system-related activity.
If you experience performance differences on your regular systems, find out if analytic operations are done simultaneously. To solve performance problems and to avoid that the analytic operations affect critical system operations, you can run the analytic operations at a different time. You can also adjust the settings to run the analytic operations with a lower priority.
Was this topic helpful?
17 October 2019