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

In each case, the quotes delimiting the identifier are removed. For example, if the table
CAT.”S&C%H”.”T*A*B?01” is dropped at 12:57:15 am on April 24, 2011, the saved DDL file
would be:
/usr/tandem/sqlmx/ddl/CAT.S_C_H.T_A_B_01-20110424-215715.ddl
If the three-part ANSI name exceeds the maximum OSS file name length of 248, it is truncated to
248 characters.
Files with similar names can be distinguished by:
• The trailing timestamp portion of the name.
• The contents of the file, which always indicates the full ANSI name of the table.
NOTE: NonStop SQL/MX does not remove these files. You must remove unwanted files from this
location.
Using Backup and Restore 2 for SQL/MX Database Recovery
Use Backup and Restore 2 to back up to tape and restore to disk SQL/MX objects, OSS program
files, and other components, as required to properly recover your database.
Backup and Restore 2 uses BRCOM, the command-line user interface from which you enter and
manage BACKUP and RESTORE commands for SQL/MX and OSS objects. For more information
about the BRCOM command syntax, see the Backup and Restore 2 Manual.
To back up and restore SQL/MP tables or other SQL/MP objects, you must use the T9074 BACKUP
and RESTORE utilities. For more information, see the SQL/MP Installation and Management Guide,
the SQL/MP Reference Manual, and the Guardian Disk and Tape Utilities Reference Manual.
NOTE: The backup recovery method provided through Backup and Restore 2 is different from
the recovery methods provided through the TMF subsystem. The Backup and Restore 2 method is
normally used as a secondary recovery scheme. Also, remember that an SQL/MX object recovered
by TMF might not be consistent with the current metadata description of the object.
This subsection contains general guidelines for using Backup and Restore 2 for SQL/MX objects,
including:
• “Frequency of Backups” (page 63)
• “Backup Objects Hierarchy” (page 64)
• “SQL/MX Objects Backed Up Explicitly” (page 64)
• “SQL/MX Objects Backed Up Implicitly” (page 65)
• “SQL/MX Objects Not Restored by BRCOM” (page 66)
• “Other Restrictions on Backup and Restore 2 Operations” (page 66)
• “Backing Up and Restoring OSS Program Files and SPJs” (page 66)
• “Using the RESTORE SHOWDDL ON Option to Re-Create Objects” (page 67)
Table 5 (page 62) describes how SQL/MX and OSS objects are managed by Backup and Restore
2. For more information, see the Backup and Restore 2 Manual.
Using Backup and Restore 2 for SQL/MX Database Recovery 61