Changes

Deployment options: IBM Netezza ApplianceIBM Netezza ApplianceNetezza Performance Server for Cloud Pak for Data as a Service

Backup and restore changes

  1. Incremental backup (differential or cumulative) does not report Backing up <name> for a table that has not been modified since the last backup, when TRACK CHANGES is ON for the database.
  2. Backup (full or incremental) does not report Backing up <name> for a table that has BACKUP OFF or BACKUP DATA OFF.
  3. When you are backing up a BACKUP DATA OFF table, backup does report a warning Forcing empty backup of table <name> as it has been excluded from backup. Forcing an empty backup (with no rows) ensures that restore empties the specific table regardless of its previous contents (which might have been based on a different value of the table's BACKUP setting).
  4. For a table with BACKUP OFF, restore of views or synonyms that reference the table fail s with a nonfatal error message.
  5. When a table is Altered from BACKUP [DATA] OFF to BACKUP [DATA] ON, the next incremental backup displays the warning message Forcing full backup of table '<name>' which has been groomed, truncated or added to backup since last backup.. This expanded warning message also appears when a table is groomed or truncated between backups.
  6. When a database is Altered from TRACK CHANGES OFF to TRACK CHANGES ON, the next incremental backup queries all BACKUP ON tables for inserted and deleted rows. The same as the existing incremental backup.
  7. The new TRACK CHANGES and BACKUP settings, for databases and tables, are backed up and restored.
  8. The backup and restore changes are both backward- and forward-compatible. For an older release that restores from a newer backup, some nonfatal errors might appear during the restore. The errors do not prevent the restore transaction from committing. (For example, Restore of increment <number> from backupset <backupset> to database '<db_name>' committed.).

System view changes

  1. A new dbtrackchanges column (value 0 when OFF, 1 when ON) is added to the _v_database view.
  2. A new dontbackup column (0 = BACKUP [DATA] ON, 1 = BACKUP DATA OFF, 2 = BACKUP OFF) is added to _v_table, _v_table_storage_stat, _v_table_only_storage_stat, _v_obj_relation, _v_object_data, and _v_objects.

nzsql changes

  1. \d <table> shows Backup Data Off or Backup Off when that is the case. The latter is always the case for a temporary table. No additional text is displayed when the table has BACKUP [DATA] ON, which is the default.

    · \l+ (list databases with extra detail) shows an extra TRACKCHANGES column. The value that is displayed is blank if TRACK CHANGES is off (the default), or ON if on.

Netezza Performance Server Replication changes

  1. Replication does not treat tables with BACKUP DATA OFF or BACKUP OFF specially. These are always backed up (definition and data) by nzreplbackup and restored by nzreplrestore. Do not use nzbackup or nzrestore directly to initialize or recover a replication node.

  2. The SQL syntax (TRACK CHANGES on CREATE/ALTER DATABASE, and BACKUP on CREATE / ALTER TABLE) is replicated when used with a replicated database on a master node.

  3. \l+ (list all databases with extra detail) always shows REPLICATION_SET and TRACKCHANGES, whether any databases are replicated. The special replicated database _GLOBAL, which is not a real database but, which appears in views such as _v_replicated_database and _v_replication_state, does not appear in the output of \l+ (as before).