Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

6.3 RDAREAs to be backed up together

The HiRDB administrator must back up not only RDAREAs that have been processed, but also RDAREAs that have been updated as a result of that processing. The following table lists the RDAREAs to be backed up together.

Table 6-3 RDAREAs to be backed up together

Processing executed since previous backup Type of RDAREA to be backed up
MST DIR DIC DIC LOB USR USR LOB LOB indx LOB data RG RG LOB
ALTER INDEX Y Y Y -- Y -- Y#37 -- -- --
ALTER
PROCEDURE
-- -- Y Y -- -- -- -- -- --
ALTER
ROUTINE
-- -- Y Y -- -- -- -- -- --
ALTER
TABLE
Y#1 Y#1 Y -- Y -- -- -- -- --
ALTER
TRIGGER
-- -- Y Y -- -- -- -- -- --
CREATE
CONNECTION
SECURITY
-- -- Y -- -- -- -- -- -- --
CREATE
FUNCTION
-- -- Y Y -- -- -- -- -- --
CREATE
INDEX
Y Y Y -- Y -- Y#15 -- -- --
CREATE
PROCEDURE
-- -- Y Y -- -- -- -- -- --
CREATE SCHEMA -- -- Y -- -- -- -- -- -- --
CREATE SEQUENCE -- -- Y -- -- -- -- -- -- --
CREATE
TABLE
Y Y#2 Y Y#34 Y Y#9 -- Y#16 -- --
CREATE
TRIGGER
-- -- Y Y -- -- -- -- -- --
CREATE
TYPE
-- -- Y Y#24 -- -- -- -- -- --
CREATE
VIEW
Y -- Y -- -- -- -- -- -- --
DROP
CONNECTION
SECURITY
-- -- Y -- -- -- -- -- -- --
DROP
DATA TYPE
-- -- Y Y#24 -- -- -- -- -- --
DROP
FUNCTION
-- -- Y Y -- -- -- -- -- --
DROP
INDEX
Y Y Y -- Y -- Y#17 -- -- --
DROP
PROCEDURE
-- -- Y Y -- -- -- -- -- --
DROP
SCHEMA
Y#3 Y#3 Y Y#14 Y#38 Y#10 Y#18 Y#19 -- --
DROP SEQUENCE Y -- Y -- Y -- -- -- -- --
DROP
TABLE
Y Y#8 Y Y#34 Y#38 Y#9 Y#20 Y#21 -- --
DROP
TRIGGER
-- -- Y Y -- -- -- -- -- --
DROP
VIEW
Y -- Y -- -- -- -- -- -- --
ALLOCATE MEMORY TABLE -- -- Y -- -- -- -- -- -- --
DEALLOCATE MEMORY TABLE -- -- Y -- -- -- -- -- -- --
Definition SQL other than above Y#7 -- Y -- -- -- -- -- -- --
INSERT -- -- -- -- Y#13, #38, #39 Y#13 Y#22 Y#23 -- --
PURGE
TABLE
-- -- Y#35 -- Y#38 Y#9 Y#20 Y#21 -- --
UPDATE -- -- -- -- Y#13, #38, #39 Y#13 Y#22 Y#23 -- --
Other data manipulation SQL -- -- -- -- Y#13, #38 Y#13 Y#22 Y#23 -- --
Table definition or deletion via DBPARTNER Y Y#2, #8 Y -- Y Y#9 -- -- -- --
Table data extraction and updating via DBPARTNER -- -- -- -- Y#13, #38 Y#13 -- -- -- --
Database load utility -- -- Y#35 -- Y#39 Y#9 Y#20 Y#21 -- --
Database structure modif utility RDAREA addition Y -- Y Y#30 Y#5 -- Y#11 Y#11 -- --
RDAREA expansion Y -- Y Y#30 Y#5 Y#11 Y#11 Y#11 Y#25 Y#26
RDAREA deletion Y -- Y -- -- -- -- -- -- --
RDAREA re-initial Y Y#4 Y Y#30 Y#5 Y#11, #12 -- -- Y#25 Y#26
RDAREA attribute modification Y -- Y Y#40 Y#40 Y#40 Y#40 Y#40 Y#40 Y#40
Database reorg utility Reload -- -- Y#6, #35, #36 Y#6 Y#5, #36 Y#20 Y#21 Y#31 -- --
Reorg -- -- Y#6, #35, #36 Y#6 Y#5, #36 Y#20 Y#21 Y#31 -- --
Re-create an index -- -- -- -- Y#32 Y#33 Y#33 -- -- --
Index reorg -- -- -- -- Y -- -- -- -- --
Dict import/export utility Import table definition info Y Y Y Y#34 Y -- -- Y#9 -- --
Import of stored procedure -- -- Y Y -- -- -- -- -- --
Integrity check utility -- -- Y#35 -- Y#35 -- -- -- -- --
Optimizing information collection utility -- -- Y -- -- -- -- -- -- --
Registry facility initialization utility -- -- -- -- -- -- -- -- Y#25 Y#26
Rebalancing utility -- -- Y Y Y Y#9 Y#20 Y#21 -- --
Database definition utility Same as definition SQL
pddbchg command Y -- Y -- -- -- -- -- -- --
pdparaload command -- -- Y#35 -- Y#39 Y#9 Y#20 Y#21 -- --
pdplgrgst command -- -- Y Y -- -- -- -- -- --
pdorchg command Y -- Y -- Y Y#41 -- -- -- --
pdorend command Y -- Y -- Y Y#41 -- -- -- --
Deletion of plug-in Y Y Y Y Y Y#27 Y#28 Y#29 Y Y
HiRDB version upgrade Y Y Y Y Y Y Y Y Y Y

Y: RDAREAs to be backed up together (columns containing hyphens indicate that RDAREAs need not be backed up).

MST: Master directory RDAREA

DIR: Data directory RDAREA

DIC: Data dictionary RDAREA

DIC LOB: Data dictionary LOB RDAREA

USR: User RDAREA (excluding temporary table RDAREAs)

USR LOB: User LOB RDAREA

RG: Registry RDAREA

RG LOB: Registry LOB RDAREA

LOB indx: User LOB RDAREA (applicable if plug-in index is stored)

LOB data: User LOB RDAREA (applicable if abstract data type is stored)

Note
To back up a data dictionary LOB RDAREA for storing objects, either the -M option of the database copy utility must be omitted or x or r must be specified in the -M option.

#1: Required if a column comprising the index was deleted or a column with a low ID was deleted from the index columns. The column IDs can be obtained by searching the COLUMN_ID column of the SQL_COLUMNS dictionary table.

#2: Required if a row-partitioned table or cluster key was defined.

#3: Required if a table or index was defined for a schema that was deleted.

#4: Required if an index is stored in an RDAREA that was deleted.

#5: Required if a user RDAREA was processed.

#6: Required if a dictionary table was reorganized.

#7: Required if a view table was deleted because access privilege to the base table was lost by REVOKE access-privilege.

#8: Required in the following cases:

#9: Required if a LOB column is defined for a table that was processed.

#10: Required if a schema that was deleted contained a table for which a LOB column was defined.

#11: Required if a user LOB RDAREA was processed.

#12: Required if a user RDAREA that contained a table for which a LOB column was defined was initialized.

#13: If no LOB column is defined for the updated table, the user RDAREAs that contain this table must be backed up. If a LOB column is defined for the updated table, the RDAREAs listed in Table 6-4 RDAREAs to be backed up when a LOB column is defined for an updated table must be backed up.

#14: Required if a routine, a table for which a CASCADE referential constraint action was defined, or a trigger was defined in a schema that is subject to deletion.

#15: Required if a plug-in index was created.

#16: Required if an abstract data type was defined for a table has the LOB attribute.

#17: Required if a plug-in index was deleted.

#18: Required if a schema that was deleted contained a table for which a plug-in index was defined.

#19: Required if a schema that was deleted contained a table for which the LOB attribute was defined.

#20: Required if a plug-in index was defined for a table that was processed.

#21: Required if the LOB attribute was defined for a table that was processed.

#22: Required if an attribute for which a plug-in index was defined was updated.

#23: Required if the LOB attribute was updated.

#24: Required if there was a function definition specified with an SQL procedure.

#25: Required if a registry RDAREA was processed.

#26: Required if a registry LOB RDAREA was processed.

#27: Required if the LOB attribute was defined for a table for which an abstract data type provided by a plug-in was defined.

#28: Required if a plug-in index was defined.

#29: Required if the LOB attribute was defined for an abstract data type provided by a plug-in.

#30: Required if a data dictionary LOB RDAREA was processed.

#31: Required if a LOB column was defined for the target table. Also, in cases where only a LOB column structure base table is reconfigured (-j option is not specified), the LOB column must be acquired together with the user RDAREA.

#32: The table storage RDAREA and the index storage RDAREA must be acquired as a pair.

#33: Also in cases where plug-in indexes are subject to processing, the table storage RDAREAs (user RDAREAs) must be acquired in preparation for no-log hold.

#34: Required if a referential constraint's action is CASCADE.

#35: Required if a referencing table, a referenced table, or a table for which a check constraint was defined is the processing target.

#36: Required if the check pending status is changed.

#37: Required if the plug-in index is changed.

#38: If an index is defined in the table to be processed, both the RDAREA storing the table and the RDAREA storing the index must be backed up.

#39: If data is updated using a sequence generator, RDAREAs storing tables and indexes as well as the RDAREA storing the sequence generator must be backed up.

#40: Required if the configuration of the RDAREA is to be modified.

#41: Required if an updatable RDAREA targeted for online reorganization contains a user LOB RDAREA.

Table 6-4 RDAREAs to be backed up when a LOB column is defined for an updated table

Updating type and condition For user For user LOB
INSERT statement Data exists in a column other than LOB column. LOB column is null. Y --
LOB column contains data. Y Y
DELETE statement Data exists in a column other than LOB column. LOB column is null. Y --
LOB column contains data. Y Y
UPDATE statement Updating occurred in a column other than LOB column. LOB column was not updated. Y --
LOB column was updated. Y Y
No updating occurred in a column other than LOB column. LOB column was updated. Null value was updated to some data. Y Y
Data was updated to null. Y Y
Data A was updated to data B. -- Y

Y: Backup must be collected.

--: Backup need not be collected.