RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

CREATE SCHEMA BCAT.SCH LOCATION ZSDXYZ3A;
You must use the LOCATION clause. If you specified the LOCATION clause when creating
the primary system's schema, you must use the same subvolume here. If you did not specify
the LOCATION clause when creating the primary system's schema or if you do not know the
name of the subvolume used for the schema on the primary system, then you must query the
primary system to obtain the Guardian subvolume name, and you must use the Guardian
subvolume name with the LOCATION clause here. See “Creating NonStop SQL/MX Primary
and Backup Databases” (page 307).
3. If you want each catalog to be seen from both systems, register your primary and backup
catalogs. See “Creating NonStop SQL/MX Primary and Backup Databases” (page 307) for
instructions and examples.
4. Use the MXGNAMES utility to generate the LOCATION clauses for the RESTORE utility. To
generate a location clause for a single table on the primary node called CAT.SCH.TAB1, use
this command:
MXGNAMES CAT.SCH.TAB1 -BR2 -node=\bnode -output=TAB1MAP
See the SQL/MX Installation and Management Guide for more information about the
MXGNAMES utility. This command generates the necessary location clause to restore this
table on the backup node, without changing the volume names, and saves the output to a
Guardian EDIT file called TAB1MAP. If necessary, you can remap the volume names manually
by editing this file.
LOCATION
(
\PNODE.$DATA01.ZSDABCDEF.FILE100 TO \BNODE.$DATA0A.ZSDABCDEF.FILE100,
\PNODE.$DATA02.ZSDABCDEF.FILE100 TO \BNODE.$DATA0B.ZSDABCDEF.FILE100,
\PNODE.$DATA03.ZSDABCDEF.FILE100 TO \BNODE.$DATA0C.ZSDABCDEF.FILE100
)
You can generate one such location file for each table, or a single file in one MXGNAMES
command by providing an input list of NonStop SQL/MX names. The input list must be a
Guardian EDIT file consisting of one fully-qualified ANSI SQL table name per line, such as:
CAT.SCH.T1
CAT.SCH.T123
CAT.SCH.ABC
Assuming this EDIT file is called BR2INPUT, you can use the this command to generate a single
output file call LOCMAP2, containing the necessary LOCATION clause to back up all three
tables:
MXGNAMES -sqlnames=BR2INPUT -BR2 -node=\bnode -output=LOCMAP2
See the SQL/MX Installation and Management Guide for information about how to generate
input table name lists from your database and more complete information on the MXGNAMES
utility.
5. Use the BACKUP utility to store your primary database objects on tape, using their ANSI
names. The application must be stopped, and the database inactive, while the backup is being
performed.
Creating a NonStop SQL/MX Backup Database From an Existing Primary Database 311