Stores the current database root Unique Identifier value into the
current storage area file or storage area snapshot file header
for the storage area with the specified name or number when the
user executes the next COMMIT command.
Any changes to the area header Unique Identifier values will
only be written to the actual area files when the next "COMMIT"
command is executed at the "RdbALTER>" prompt. Any changes to the
area file headers since the last "COMMIT" command was issued can
be undone by executing the "ROLLBACK" command at the "RdbALTER>"
prompt. "COMMIT" and "ROLLBACK" are existing RMU/ALTER commands
and affect any current uncommitted changes made in RMU/ALTER, not
just changes to the storage area header Unique Identifier values.
To execute the DEPOSIT AREA_HEADER command, the user must be
attached to the database which the root and areas belong to,
either by specifying the database name when issuing the RMU/ALTER
command or by executing the "ATTACH" command from the "RdbALTER>"
prompt.
1 – Format
(B)0[mqwqqqqqq>qqqqqwq> [4mAREA_HEADER[m qwq> area-id qqqwqwqqqqqqq>qqqqqwqqqk
mq> [4mDEPOSIT[m qj mq> area-name qj mq> [4mSNAPSHOT[m qj x
lqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqq> [4mUNIQUE_IDENTIFIER[m
2 – Arguments
2.1 – name_or_id
Specifies the name or number of the .rda or .snp file where you
are storing the current database root Unique Identifier value.
2.2 – SNAPSHOT
Specifies that the file whose .rdb file fields you are changing
is an .snp file.
2.3 – Unique Identifier
Specifies that you are storing the Unique Identifier in the
storage area or the storage area snapshot header.
3 – Examples
Example 1
The following example shows that for Oracle Rdb single file
databases, the Unique Identifier value can only be set for the
storage area snapshot file since the storage area is part of the
root file. Therefore, the DEPOSIT AREA_HEADER command can only
specify the "SNAPSHOT" file or an error will be returned.
$ RMU/ALTER PERSONNEL
%RMU-I-ATTACH, now altering database
"DEVICE:[DIRECTORY]PERSONNEL.RDB;1"
DEPOSIT AREA_HEADER RDB$SYSTEM UNIQUE_IDENTIFIER
%RMU-F-NOTSFDB, This command is not allowed for a single file
database
DEPOSIT AREA_HEADER RDB$SYSTEM SNAPSHOT UNIQUE_IDENTIFIER
Area RDB$SYSTEM:
(marked) Root file unique identifier is: "22-OCT-2010 13:49:29.32"
(00AA557869612643)
COMMIT
EXIT
Example 2
Since the DEPOSIT ROOT UNIQUE_IDENTIFIER command always stores
the Unique Identifier value in ALL storage area file headers when
the user executes the RMU/ALTER "COMMIT" command, it would be
redundant to execute the DEPOSIT AREA_HEADER UNIQUE_IDENTIFIER
command if a DEPOSIT ROOT UNIQUE_IDENTIFIER command is already
pending for the current RMU/ALTER session. Therefore, as the
following example shows, in this case a DEPOSIT AREA_HEADER
UNIQUE_IDENTIFIER command cannot be executed until the user ends
the current session with a COMMIT or ROLLBACK command.
$ RMU/ALTER MF_PERSONNEL
%RMU-I-ATTACH, now altering database
"DEVICE:[DIRECTORY]MF_PERSONNEL.RDB;1"
DEPOSIT ROOT UNIQUE_IDENTIFIER = NEW
(marked) Root file unique identifier is: "22-OCT-2010 13:49:31.72"
(00AA55786ACFB115)
DEPOSIT AREA_HEADER SALARY_HISTORY UNIQUE_IDENTIFIER
%RMU-F-COMROOTCOM, COMMIT or ROLLBACK DEPOSIT ROOT
UNIQUE_IDENTIFIER command to use this command
commit
DEPOSIT AREA_HEADER SALARY_HISTORY UNIQUE_IDENTIFIER
Area SALARY_HISTORY:
(marked) Root file unique identifier is: "22-OCT-2010 13:49:31.72"
(00AA55786ACFB115)
COMMIT
EXIT
Example 3
The following example shows that RMU/ALTER is invoked specifying
the database MF_PERSONNEL.RDB. The user then displays the current
Unique Identifier value in the root file. He then executes the
"deposit" commands to designate that the Unique Identifer value
in the root file is to be moved to the DEPARTMENTS area storage
and the DEPARTMENTS area snapshot files, displays the Unique
Identifier value that is to be moved to the DEPARTMENTS area
storage and the DEPARTMENTS area snapshot files, and finally
specifies "commit" to actually write the root unique identifier
value to the DEPARTMENTS area storage and the DEPARTMENTS area
snapshot files. The display messages designate the pending
Unique Identifier value as "(marked)" until the user either
executes "commit" to write out the Unique Identifier value or
"rollback" to restore the original Unique Identifier value. The
user then verifies the database changes. The example shows that
the user can use either the storage area name or the storage area
identifier number in the root to designate the target storage
area.
$ RMU/ALTER MF_PESONNEL
%RMU-I-ATTACH, now altering database "DEVICE:[DIRECTORY]MF_PERSONNEL.RDB;1"
DISPLAY ROOT UNIQUE_IDENTIFIER
Root file unique identifier is: "22-OCT-2010 13:49:28.34"
(00AA557868CC9F7A)
DEPOSIT AREA_HEADER DEPARTMENTS UNIQUE_IDENTIFIER
Area DEPARTMENTS:
(marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
(00AA557868CC9F7A)
DEPOSIT AREA_HEADER 2 SNAPSHOT UNIQUE_IDENTIFIER
Area DEPARTMENTS:
(marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
(00AA557868CC9F7A)
DISPLAY AREA_HEADER DEPARTMENTS UNIQUE_IDENTIFIER
Area DEPARTMENTS:
(marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
(00AA557868CC9F7A)
DISPLAY AREA_HEADER 2 SNAPSHOT UNIQUE_IDENTIFIER
Area DEPARTMENTS:
(marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
(00AA557868CC9F7A)
COMMIT
EXIT
$ RMU/VERIFY/ALL/NOLOG MF_PERSONNEL