RDF/IMP and IMPX System Management Manual (RDF 1.4+)

Online Database Synchronization
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
7-6
Considerations When Synchronizing Entire
Databases
As a precaution, if RDFCOM encounters a Stop-RDF-Updater record during its
backward search of the MAT, it issues a warning message to that effect asking if you
want to proceed with initialization. If the extractor encounters such a record while
operating in database synchronization mode, it abends.
TMF Shutdown Records
TMF shutdown records in the MAT do not cause a problem, except that RDF shuts
down and you must then restart it.
CREATE/LOAD Issues
The LOAD command only works on tables and files that are nonaudited. If you create
the empty duplicate tables and files as audited entities, you must then use FUP ALTER
commands to turn off their audit attributes before you can load them.
For information about the SQLCI LOAD or FUP LOAD commands, refer to the HP
NonStop SQL 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.