RDF System Management Manual

Maintaining the Databases
HP NonStop RDF System Management Manual—524388-003
6-5
NonStop SQL/MP or NonStop SQL/MX Databases
Catalog Changes
RDF views NonStop SQL/MP and NonStop SQL/MX DDL operations as updates to
catalogs. NonStop SQL/MP and NonStop SQL/MX catalogs themselves are audited
tables, even on the backup system. NonStop SQL/MP and NonStop SQL/MX 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 736, citing file system error 11, and the updater retries until the file is created
by the user.
DDL Operations
Every NonStop SQL/MP or NonStop SQL/MX DDL operation performed on the primary
system must also be performed on the backup system by NonStop SQL/MP or
NonStop SQL/MX if any of the tables or catalogs reside on volumes protected by RDF.
DDL Operations Guidelines
The following guidelines apply to NonStop SQL/MP and NonStop SQL/MX DDL
operations:
•
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 nonaudited, 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.
3. Issue an ALTER TABLE table-name AUDIT statement for the table.