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

Maintaining the Databases
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
6-5
SQL/MP Databases
Catalog Changes
RDF views SQL/MP DDL operations as updates to catalogs. SQL/MP catalogs
themselves are audited tables, even on the backup system. SQL/MP DDL operations are
not replicated by RDF; therefore, RDF does not apply updates to catalogs.
The following guidelines apply to creating catalogs:
•
If a catalog exists on a volume protected by RDF, this catalog should also be present
on the corresponding volume on the backup system.
•
To avoid errors, create a catalog on the backup system before creating it on the
primary system. If audit data is generated for a primary catalog before the
corresponding backup catalog exists, every audit record for the catalog causes a file
open error.
Updater processes check for catalog tables, which have a file code in the range 550
through 590 and 859 (ODBC catalogs). An updater does not apply any changes to a
table that has a catalog file code.
An update operation to a table that does not exist causes RDF to log an RDF error
message 705 (file open failure), citing file system error 11, for each audit record
corresponding to that table.
DDL Operations
Every SQL/MP DDL operation performed on the primary system must also be
performed on the backup system by SQL/MP if any of the tables or catalogs reside on
volumes protected by RDF.
DDL Operations Guidelines
The following guidelines apply to SQL/MP DDL operations:
•
If a table on the backup system is nonaudited, an index created for the table is
nonaudited.
•
If a table and index on the backup system are audited, turn off TMF auditing for
both the table and its dependent indexes before any applications on the primary
system update the index.
•
Creating an index or loading data into an added table partition does not interfere
with RDF protection. Although a CREATE INDEX or ALTER TABLE MOVE
FROM FIRST KEY UP TO KEY operation seems to create an audited index or
partition within a transaction, only the updates to the catalog and file labels are
audited. The index or partition is created unaudited, and audit is not turned on until
after the operation is complete. Performing either of these DDL operations on the
backup system for a corresponding DDL operation on the primary system does not
cause problems because the operation on the primary system proceeds internally as
follows:
1. Create a nonaudited table (index or partition).
2. Move the data without logging by TMF.