Using dump and load database When Shrinking Log Space

Shrinking log space requires careful planning.

The system administrator should keep the following in mind when performing dump and load database.
  • The database you are loading must have at least as much physical space as when it was dumped.

  • The physical space in the database you are loading is apportioned according to the physical fragments in the database that was dumped. This means a “hole”—an allocation unit for which there is no associated physical storage as a result of an earlier alter database log off command—in the database to be loaded does not necessarily remain a hole after the load.

  • Any leftover space in the database you are loading is apportioned in the same way as it is for dump and load database without holes.

  • You can determine the amount of physical space in the database that was dumped as well as whether it has holes, and information about the size and location of these holes, by running the load database with headeronly command.