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. Table 6-3 lists the RDAREAs that should 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
Processing executed since previous backup		MST	DIR	DIC	DIC LOB	USR	USR LOB	REG	REG LOB	LOB indx	LOB data
ALTER PROCEDURE				Y	Y
ALTER ROUTINE				Y	Y
ALTER TABLE		Y¹	Y¹	Y		Y
ALTER TRIGGER				Y	Y
CREATE FUNCTION				Y	Y
CREATE INDEX		Y	Y	Y		Y				Y¹⁵
CREATE PROCEDURE				Y	Y
CREATE SCHEMA, CREATE CONNECTION SECURITY				Y
CREATE TABLE		Y	Y²	Y	Y³⁴	Y	Y⁹				Y¹⁶
CREATE TRIGGER				Y	Y
CREATE TYPE				Y	Y²⁴
CREATE VIEW		Y		Y
DROP CONNECTION SECURITY				Y
DROP DATA TYPE				Y	Y²⁴
DROP FUNCTION				Y	Y
DROP INDEX		Y	Y	Y		Y				Y¹⁷
DROP PROCEDURE				Y	Y
DROP SCHEMA		Y³	Y³	Y	Y¹⁴	Y	Y¹⁰			Y¹⁸	Y¹⁹
DROP TABLE		Y	Y⁸	Y	Y³⁴	Y	Y⁹			Y²⁰	Y²¹
DROP TRIGGER				Y	Y
DROP VIEW		Y		Y
Definition SQL other than above		Y⁷		Y
PURGE TABLE				Y³⁵		Y	Y⁹			Y²⁰	Y²¹
Other data manipulation SQL						Y¹³	Y¹³			Y²²	Y²³
Database load utility				Y³⁵		Y	Y⁹			Y²⁰	Y²¹
Database structure modif utility	RDAREA addition	Y		Y	Y³⁰	Y⁵				Y¹¹	Y¹¹
	RDAREA expansion	Y		Y	Y³⁰	Y⁵	Y¹¹	Y²⁵	Y²⁶	Y¹¹	Y¹¹
	RDAREA deletion	Y		Y
	RDAREA re-initial	Y	Y⁴	Y	Y³⁰	Y⁵	Y^{11, 12}	Y²⁵	Y²⁶
Database reorg utility	Reload			Y^{6, 35}	Y⁶	Y	Y³¹			Y²⁰	Y²¹
	Reorg			Y³⁶		Y³⁶
	Re-create an index					Y³²				Y³³	Y³³
	Index reorg					Y
Dict import/export utility	Import table definition info	Y	Y	Y	Y³⁴	Y	Y⁹
Dict import/export utility	Import of stored procedure			Y	Y
Integrity check utility				Y³⁵		Y³⁵
Optimizing information collection utility				Y
Registry facility initialization utility								Y²⁵	Y²⁶
Rebalancing utility				Y	Y	Y	Y⁹			Y²⁰	Y²¹
Database definition utility		Same as definition SQL
pdplgrgst command				Y	Y
pdorend command				Y³⁶		Y³⁶
Deletion of plug-in		Y	Y	Y	Y	Y	Y²⁷	Y	Y	Y²⁸	Y²⁹

modif: modification

re-initial: re-initialization

reorg: reorganization

Re-create: Re-creating

Dict: Dictionary

info: information

Y: RDAREAs to be backed up together

MST: Master directory RDAREA

DIR: Data directory RDAREA

DIC: Data dictionary RDAREA

DIC LOB: Data dictionary LOB RDAREA

USR: User RDAREA

USR LOB: User LOB RDAREA

REG: Registry RDAREA

REG 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.

¹ 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.

² Required if a row-partitioned table or cluster key was defined.

³ Required if a table or index was defined for a schema that was deleted.

⁴ Required if an index is stored in an RDAREA that was deleted.

⁵ Required if a user RDAREA was processed.

⁶ Required if a dictionary table was reorganized.

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

⁸ Required in the following cases:

A row-partitioned table was deleted
An index was defined for a table that was deleted
A cluster key was defined for a table that was deleted

⁹ Required if a LOB column is defined for a table that was processed.

¹⁰ Required if a schema that was deleted contained a table for which a LOB column was defined.

¹¹ Required if a user LOB RDAREA was processed.

¹² Required if a user RDAREA that contained a table for which a LOB column was defined was initialized.

¹³ 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 must be backed up.

¹⁴ 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.

¹⁵ Required if a plug-in index was created.

¹⁶ Required if an abstract data type was defined for a table has the LOB attribute.

¹⁷ Required if a plug-in index was deleted.

¹⁸ Required if a schema that was deleted contained a table for which a plug-in index was defined.

¹⁹ Required if a schema that was deleted contained a table for which the LOB attribute was defined.

²⁰ Required if a plug-in index was defined for a table that was processed.

²¹ Required if the LOB attribute was defined for a table that was processed.

²² Required if an attribute for which a plug-in index was defined was updated.

²³ Required if the LOB attribute was updated.

²⁴ Required if there was a function definition specified with an SQL procedure.

²⁵ Required if a registry RDAREA was processed.

²⁶ Required if a registry LOB RDAREA was processed.

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

²⁸ Required if a plug-in index was defined.

²⁹ Required if the LOB attribute was defined for an abstract data type provided by a plug-in.

³⁰ Required if a data dictionary LOB RDAREA was processed.

³¹ 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.

³² The table storage RDAREA and the index storage RDAREA must be acquired as a pair.

³³ 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.

³⁴ Required if a referential constraint's action is CASCADE.

³⁵ Required if a referencing table, a referenced table, or a table for which a check constraint was defined is the processing target.

³⁶ Required if the check pending status is changed.

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
INSERT statement	Data exists in a column other than LOB column.	LOB column contains data.		Y	Y
DELETE statement	Data exists in a column other than LOB column.	LOB column is null.		Y
DELETE statement	Data exists in a column other than LOB column.	LOB column contains data.		Y	Y
UPDATE statement	Updating occurred in a column other than LOB column.	LOB column was not updated.		Y
	Updating occurred in a column other than LOB column.	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.

[Figure] : Backup need not be collected.

6.3 RDAREAs to be backed up together