Backup and Restore 2 Manual

BRCOM RESTORE Command
Backup and Restore 2 Manual—522696-019
7-7
Summary of Restoring SQL/MX or OSS Objects
Restoring OSS Objects
Restoring a directory includes all its subdirectories and files.
Restoring SQL/MX Objects

Restoring a catalog includes restoring all its subordinate objects in its object
hierarchy such as schemas, tables, and the subordinate objects of the tables.

Restoring a schema includes restoring all the subordinate tables.

Restoring a table includes:

Nondroppable constraints.

Droppable constraints unless you specify the CONSTRAINTS EXCLUDED job
option.

All the table data unless you specify the SQLDATA OFF job option.

Indexes and index partitions unless you specify the INDEXES EXCLUDED job
option.

SG_TABLE, if the table contains an IDENTITY column.

All partitions of an index are backed up with their parent index unless you specify
the INDEXES EXCLUDED job option. You cannot restore individual index partitions
by directly specifying an index partition in the RESTORE command. To restore
index partitions, you must restore the table that contains the index.

You cannot directly specify a constraint in a RESTORE command. To restore a
constraint, you must restore the table that contains the constraint. The constraints
that are restored vary depending on whether you specify CONSTRAINTS
INCLUDED or CONSTRAINTS EXCLUDED.

Restoring an index includes:

Restoring all the subordinate index partitions.

Target table needs to be explicitly defined with the help of “TARGET” keyword.
Restoring to the Restricted-Access Fileset
To restore to a restricted-access fileset, ensure that:

The user is a member of the SECURITY-OSS-ADMINISTRATOR security group.
Note. IDENTITY column feature is supported only in SQL/MX 3.1 versions and above.
Note. The super ID's access to the restricted-access fileset is limited to the file
permissions set on the restricted fileset. A super ID can restore only the files it owns in a
restricted-access fileset.