Backup and Restore 2 Manual

Backup and Restore 2 Overview
Backup and Restore 2 Manual—522696-019
1-13
Relationship between Backup Restore and Backup
Restore 2
Restore of Views, Stored Procedures, Triggers, and
Referential Integrity Constraints
With SQL/MX release 3.2, HP introduces the OBEYDDL option to restore the objects in
Table 1-1. For more information, see the OBEYDDL Job Option on page 7-51.
In the earlier versions, after the restore operation was complete, you had to create the
objects manually, using the DDL information, which was captured during the backup
operation.
Manually Creating SQL/MX Objects
To manually create triggers, views, referential integrity constraints, and stored
procedures from the DDL information:
1. Use the RESTORE SHOWDDL ON option to generate one or more OSS edit files
containing data definition language (DDL) information for each of these objects.
For more information, see the SHOWDDL Job Option on page 7-50
2. Use the DDL information in the OSS edit files as MXCI command files to
regenerate these SQL/MX objects that cannot be restored.
Automatically Creating SQL/MX Objects During Restore
You can use the OBEYDDL option introduced in SQL/MX release 3.2 to automatically
restore the objects in Table 1-1.
Relationship between Backup Restore and
Backup Restore 2
Backup Restore (T9074) and Backup Restore 2 (T0744) are both backup and restore
utilities running on Non-Stop platform and they co-exist. The BRCOM interface serves
Table 1-1. Restore of Views, Stored Procedures, Triggers, and Referential
Integrity Constraints
SQL/MX
Object Description
Referential
integrity
constraints
Constraints that specify that a column or set of columns in the table can only
contain values matching those in a column or set of columns in the
referenced table.
Stored
procedures
A type of user-defined routine (UDR) in Java (SPJ) that operates within a
database server. A stored procedure does not return a value to the caller.
Triggers A mechanism that resides in the database and specifies that when a
particular action—an insert, delete, or update—occurs on a particular table,
SQL/MX should automatically perform one or more additional actions.
Views A table that has a logical definition and a file label but contains no data.