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