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

COLUMN 88, OFFSET 300, LENGTH 15, ASC.
COLUMN 87, OFFSET 285, LENGTH 15, ASC.
NOT UNIQUE )
AUDIT
BUFFERED
AUDITCOMPRESS
SECURITY (RWEP); NCNC
MODIF: 27 Dec 1997, 20:01
CREATION DATE: 02 Dec 1997, 12:37
REDEFINITION DATE: 10 Jan 1998, 14:46
LAST OPEN: 10 Jan 1998, 14:46
EOF 466944 (2.2% USED)
EXTENTS ALLOCATED: 160
INDEX LEVELS: 1
PARTITION ARRAY STANDARD
Partition Key Changes
If you change a key for any partition on the primary system, you must also change the key for
the corresponding partition on the backup system.
Table Purges
If you use the SQLCI PURGE command to purge a protected table from the primary system, you
must also purge the corresponding table from the backup system. You should not purge a table
on the backup system until you are sure RDF has completed all processing on the table. The
processing is complete when the RTD time is zero for the updater process associated with the
table’s volume. To check the RTD time, issue a STATUS RDF command.
If you purge a table on the primary system, you must not re-create it on the primary system until
you are certain that the updaters have caught up, and you have purged and re-created the table
on the backup system.
For NonStop SQL/MP and NonStop SQL/MX databases, RDF replicates the following file-label
modification:
PURGEDATA
Enscribe Databases
For Enscribe databases, RDF replicates the following file-label modifications:
Only when creating an audited fileCREATE
Only when increasing the number of extents of an audited
file
ALTER MAXEXTENTS
Enscribe files only (if REPLICATEPURGE is enabled)PURGE
Only when purging data from an audited filePURGEDATA
RDF does not replicate the following operations on files. If you perform any of these operations
on the primary system, you also need to perform the operation on the backup system:
• File-label modifications not in the preceding list
• Partition key changes
• Alternate-key file changes
To perform operations on Enscribe files that RDF does not replicate, follow these procedures:
1. Stop application processing on the primary system.
2. Stop TMF on the primary system; wait for RDF to read the STOP TMF message in the audit
trail and stop itself.
3. Start TMF on the primary system so the operations on audited Enscribe files can be performed.
4. Start RDF so that no audit trails are lost, but do not resume application processing.
152 Maintaining the Databases