NonStop NS-Series Database Migration Guide

Migrating an Enscribe Database
HP Integrity NonStop NS-Series Database Migration Guide—540469-001
3-4
Moving Enscribe Files to the New System
Output source for DDL is closed.
Dictionary on subvol $DATA4.ENDICT is closed.
Dictionary on subvol $DATA4.ENDICT is purged.
Audited dictionary created on subvol $DATA4.ENDICT.
Dictionary opened on subvol $DATA4.ENDICT for update access.
In this example, the ?DDL TEMP command creates the file TEMP and uses it to store
DDL SOURCE definitions. The OUTPUT * command generates a DDL SOURCE
definition for every item in the original dictionary. Finally, the ?NODDL, DICT !,
COMMENTS, SOURCE TEMP command stream causes the old dictionary to be
purged, a new dictionary to be created, and all of the saved schema information from
TEMP to be compiled into the new dictionary.
The DDL compiler adds each item defined with TEMP to the newly-created dictionary.
For more information about DDL commands and DDL dictionaries, see the Data
Definition Language (DDL) Reference Manual.
Moving Enscribe Files to the New System
You can use these tools to move Enscribe files from a NonStop S-series system to an
Integrity NonStop NS-series system:
•
Steps for Moving an Enscribe Database Using RDF on page 3-4
•
Steps for Moving an Enscribe Database Using the BACKUP/RESTORE Utilities on
page 3-6
•
Steps for Moving an Enscribe Database Using SQLCI DUP on page 3-6
•
Steps for Moving an Enscribe Database Using FUP DUP on page 3-7
Steps for Moving an Enscribe Database Using RDF
1. Determine exactly which data from the Enscribe database on the NonStop S-series
system you want to replicate to the Integrity Nonstop NS-series system.
Caution. Migrating a database from a NonStop S-series system to an Integrity NonStop
NS-series system is a complex endeavor. These steps provide a general overview of how to
migrate an Enscribe database using RDF. For assistance in migrating your database, consult
HP migration services. For information about these services, see Using HP Migration Services
on page 1-1.
Note. This subsection contains a high-level overview of one method for migrating an Enscribe
database using RDF. For detailed instructions about using RDF for online synchronization of
Enscribe databases, see the NonStop RDF/IMP, IMPX, and ZLT System Management Manual.
Note. To replicate nonaudited files, first use AutoTMF to convert them to audited files. To
replicate files that cannot be made audited (for example, object, edit, and OSS files), use
AutoSYNC to move them.