RDF System Management Manual for H-Series RVUs (RDF 1.8)

For information about the SQLCI LOAD or FUP LOAD commands, refer to the SQL/MP Reference
Manual or the File Utility Program (FUP) Reference Manual, respectively. The following information
is general in nature and is not intended as a substitute for the information contained in those
two manuals.
General Considerations for Enscribe Files
• Key-sequenced files. To improve the performance of the load operations, specify the SORTED
option.
• Relative files. To ensure complete consistency with the source files, specify the NO
COMPACT option.
• Entry-sequenced and unstructured files. Currently there is no reliable mechanism to
synchronize these file types online. Entry-sequenced and unstructured files should be
synchronized offline.
• Partitioned files (key-sequenced or relative). For partitioned files, you can initiate the load
operation with a single command by executing the LOAD command against the primary
partition.
• Alternate key files (key-sequenced or relative). You should execute LOAD commands
against all alternate key files.
Special Consideration for Enscribe Files
If you create empty Enscribe files on your primary system, you should create them with the audit
attribute set off. This is particularly important if you create them on volumes protected by RDF.
If you create them as audited files on database volumes that are being protected by RDF, the
updaters also create them on the backup system. You then must purge the files on your backup
system before copying the loaded files from the primary system.
General Considerations for NonStop SQL/MP Tables
• Key-sequenced tables without SYSKEY. To improve the performance of the load operations
significantly, specify the SORTED option.
• Key-sequenced tables with SYSKEY. Because the SQLCI LOAD operation generates new
SYSKEY values, key-sequenced tables containing SYSKEYs cannot be synchronized online.
• Relative tables. To ensure complete consistency with the source files, specify the NO
COMPACT option.
• Entry-sequenced tables. Currently there is no reliable mechanism to synchronize
entry-sequenced tables online. These tables should be synchronized offline.
• Partitioned tables. You can initiate the load operation with a single command by executing
the LOAD command against the primary partition.
• Index tables. With regard to index tables, there are several considerations for relative and
key-sequenced tables. Regardless of base table type, you cannot load an index table by itself.
Index tables can only be loaded when the associated relative or key-sequenced table is
loaded.
If you want the associated index tables loaded when you load a relative or key-sequenced
table, you must create empty index tables first, before issuing the LOAD command. When
you load the base table, the index tables are loaded automatically.
Alternatively, you can load your base tables without index tables. Then you can create and
populate your index tables with the NonStop SQL/MP product before you start the RDF
updaters.
If you fail to create the index tables before issuing the START UPDATE command, the
affected updater reports a file-system error 11 (File not found) when trying to apply an
update to an index table, and it continues to retry the update. In this situation, the updater
does not make forward progress until you create the index on your backup system.
Synchronizing Entire Databases Online 159