Restoring the database

If a program aborts processing with “ABNORMAL END” during the renaming process, you must perform one of the following actions depending on the severity of the error and where it occurred in the renaming cycle:

• re-execute the terminated program, or

• fall back on the backup created and repeat the renaming process

When it is necessary to fall back on a backup of the database and to repeat the renaming process and when it is sufficient to repeat the aborted program is explained in the descriptions of the various programs.

The table below shows which programs modify files or realms of the database in the course of renaming:

	D B D I R	D B C O M	D B C O M . O	C O S S D	C O S S D . O	User realms which have to be accessed
BRENAME	RW	RW	W	R	W	-
DDL compiler	RW	RW	-	W	-	-
SSL compiler	RW	RW	-	W	-	-
BGSIA	RW	RW	-	-	-	-
BALTER (renaming phase)	RW	R	R	-	-	RW
DDL compiler (subschemas)	RW	RW	-	W	R	-
BGSSIA	RW	R	-	-	-	-

Table 47: Access to files and realms of the database during renaming

R W -

read access write access no access

The following options are available for restoring the database:

• You can convert the shadow database to an original database by renaming it with the die MODIFY-FILE-ATTRIBUTES command.

• You can read in the ARCHIVE backup and then change the database name, if desired, with the MODIFY-FILE-ATTRIBUTES command. If the ARCHIVE backup was created on-line, you may have to mend it with the BMEND utility routine (see "BMEND" in the “Recovery, Information and Reorganization" manual).

For further information on restoring a database, refer to the section "Saving and recovering a database in the event of errors" in the "Database Operation" manual.