Creating additional allocations

Your output from sysusages may have more allocations on the master device if:

You must restore these allocations up to the last row for the master database, dbid 1. Here is an example of sysusages showing additional allocations on the master device, in vstart order:

Figure 28-4: Sample sysusages output with additional allocations

This copy of sysusages shows the following allocations on the master device (excluding the three created by dataserver):

The final allocations in this output are not on the master device.

Figure 28-5 shows the allocations on the master device.

Figure 28-5: Complex allocations on a master device

You need to issue a set of alter database and create database commands to re-create all the allocations with the correct sizes and vstart values. If sysusages lists additional allocations on the master device after the last allocation for master, you do not have to re-create them.

To determine the size for the create database and alter database commands, divide the value shown in the size column of the sysusages output by 512.

To reconstruct the allocation, issue these commands, in this order:

You need to restore only the allocations up to and including the last line for the master database. When you load the backup of master, this table is completely restored from the dump.

At this point, carefully check the current sysusages values with the values in your hard copy: