RDF System Management Manual for H-Series and J-Series RVUs (RDF 1.9)

As described in “Creating a NonStop SQL/MX Backup Database From an Existing Primary
Database” (page 326), you can use the MXGNAMES utility to automatically generate the correct
LOCATION clauses, substituting the backup node name as needed. However, you must remap
any nonmatching volume names in these locations manually.
Comparing NonStop SQL/MX Tables
While the unsupported RDFCHEK utility program can be used to compare Enscribe files or
NonStop SQL/MP tables, it cannot be used to compare NonStop SQL/MX tables. If you need to
compare a NonStop SQL/MX table on your primary against a NonStop SQL/MX table on your
backup system, for example, one method of doing so is as follows:
1. Use the NonStop SQL/MX Select statement to select all rows in the primary table, and then
store them in an Enscribe entry-sequenced file.
2. Use the NonStop SQL/MX Select statement to select all rows in the backup table, and then
store them in another Enscribe entry-sequenced file.
3. Use RDFCHEK to compare the two entry-sequenced files.
Alternatively, you can use the unsupported utility MD5CHEK to compare NonStop SQL/MX
tables without using an intermediate entry-sequenced file. The online help for MD5CHEK, which
you can view by running MD5CHEK with no parameters, describes how to use MD5CHEK.
Comparing NonStop SQL/MX Tables 335