Restrictions for database rebuild

You can use the REBUILD option to complete a set of restore commands, but it has restrictions that you need to be aware of.

The following list is a summary of database rebuild restrictions:

If you are rebuilding the catalog partition, you must include SYSCATSPACE among the tablespaces that you restore.
You must either issue commands using the command line processor (CLP) or use the corresponding application programming interfaces (APIs) to perform a REBUILD operation.
You cannot specify the TRANSPORT option during a REBUILD operation.
You can perform a REBUILD operation using a backup image from a downlevel database if the backup was taken offline and the backup image is a full database level backup.
You can perform a REBUILD operation using an offline backup image taken on a different platform if the backup image is a full database level backup.
You can perform a REBUILD operation using an online backup image taken on a different platform if the backup image is a full database level backup and the source database where the backup was taken is at the same Db2 version as the system you are restoring to.
The REBUILD operation can include only the tablespaces that are in the specified backup image. Any tablespaces that are not restored in the original REBUILD operation will have to be dropped.

Note: When a REBUILD is performed and the target image is an offline database level backup, then the REBUILD will behave like a traditional RESTORE. In this case, the same rules for downlevel and cross-platform restore will apply. Please see Backup and restore operations between different operating systems and hardware platforms for details on downlevel and cross-platform restore.