SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

SQL/MX Objects Not Restored by BRCOM
You cannot use Backup and Restore 2 to restore these SQL/MX objects:
GRANT and REVOKE privileges
Referential integrity constraints
SPJs
Triggers
Views
However, except for GRANT and REVOKE privileges, you can capture the DDL for the CREATE
statements executed for these objects and use this information to manually re-create these objects
after a Restore operation. For more information, see the “Using the RESTORE SHOWDDL ON
Option to Re-Create Objects” (page 67). For more information, see the “Example: Recovering
Table Privileges” (page 242).
Other Restrictions on Backup and Restore 2 Operations
These Backup operations are not currently supported:
Parallel BACKUP
BACKCOPY or parallel BACKCOPY
It is important to distinguish between multiple backup jobs, which are supported, and parallel
BACKUP of the type where two identical tapes are written simultaneously, which is not supported.
To back up two copies of the data, use the BACKUP command twice rather than using the
BACKCOPY or parallel BACKUP commands. To back up three copies of the data, use the BACKUP
command three times. For more information, see the Backup and Restore 2 Manual.
Other restrictions include:
You cannot currently BACKUP or RESTORE SQL/MX, SQL/MP, or Enscribe objects to the
same tape set. However, you can issue a single command to back up all objects.
If a failure occurs, a BACKUP operation cannot be automatically restarted.
Currently, there is no support for media catalog.
Backing Up and Restoring OSS Program Files and SPJs
Backing Up and Restoring Program Executables and User Modules
Program executables and user modules in the SQL/MX environment are stored in OSS directories.
To back up these files, use OSS backup objects to specify their OSS directory locations:
BR> BACKUP $tape-drive, OSS (/usr/embedsqlprogs, /usr/embedsqlcbl,
/usr/javaclasses, /usr/tandem/sqlmx/USERMODULES);
To restore program executables and user modules, use OSS restore objects to specify the original
OSS directory locations and optional target locations under which the original directories are
restored:
BR> RESTORE $tape-drive, OSS (/usr/embedsqlprogs, TARGET /newdir),
(/usr/embedsqlcbl, TGT /newdir), /usr/javaclasses,
/usr/tandem/sqlmx/USERMODULES);
For more information about backing up and restoring OSS objects, see the Backup and Restore 2
Manual.
66 Planning Database Security and Recovery