Table-level restore

Deployment options: Netezza Performance Server for Cloud Pak for Data System Netezza Performance Server for Cloud Pak for Data

When you request a table-level restore, the system restores individual tables from an existing full-database backup to a specific database. Table-level restore does not drop the target database or affect objects in that database other than those objects that you are explicitly restoring.

Table-level restore does the following:
  • Restores regular tables, not external or temp tables, views, sequences, users, or groups.
  • Replaces tables with the same name if they exist (and you use the -droptables option).
    Note: While doing a table-level restore of an existing table with -droptables, it cannot drop the table if any objects (like procedure or function) has dependency on it, and the restore fails. For example:
    Error: NZ-01103/01104: DB SQL 'DROP TABLE "ADMIN"."NZ_PROC1_REF";' failed - DB error - ERROR:  Can't delete NZ_PROC1_REF - procedure PROC1(CHARACTER VARYING) depends on it.
  • Includes the permissions that directly reference the restored tables.
  • Restores any foreign keys that are on or reference the tables.
  • Returns all materialized views to their original state. (Leaves previously active mviews that is suspended if you used the -suspendmviews option.)
Table-level restore has the following restrictions:
  • You cannot rename tables during the restoration.
  • You cannot append to an existing table.
  • You cannot create users and groups during the restoration. If the owner of the table does not exist, the admin user becomes the new owner. Permission grants fail for any users or groups that do not exist during the restore.
  • You are responsible for ensuring database integrity. However, if you have foreign keys, the system warns you of potential inconsistencies.