Error: Extent number 61244 in tablespace 8 is orphaned

[c***@alfuttaim.ae]

Hi,
We are restoring a File system backup for our DB2 database,wile starting the DB it fails with some errors.When i executed db2dart it fails with the below error

Checking for orphaned extents:

Error: Extent number 52732 in tablespace 9 is orphaned

Tablespace-info inspection phase end.

Checking for orphaned extents:

Error: Extent number 61244 in tablespace 8 is orphaned

Tablespace-info inspection phase end.

How can i fix it?

Regards,
Sam

[Kelly Schlamb]

Hi Sam,

This would suggest to me that the backup of the file system took place while the database was active. Due to the way that DB2 caches work in the bufferpools when a database is active, the state of the data on disk is likely to be inconsistent from a data and an architectural point of view (and I would consider this orphaned extent issue of the architectural nature).

Because of this, restoring a DB2 database via file system backups is definitely not supported. The supported methods of backup/restore are using the BACKUP/RESTORE commands -- where backups can be done online (since we can use the logs to fix up the inconsistencies to the data that is being backed up). An alternate strategy, which is file system based is flash copy backup/restore (where other commands/utilities come into play to ensure that the database is made consistent upon restoring it).

If you have a DB2 backup then that is what you should be restoring (and rolling forward through logs, if the database enabled for log retain/archiving).

Regards,
Kelly

[b***@to.com]

Hi Kelly,

Post by Kelly Schlamb
An alternate strategy, which is file system based is
s flash copy backup/restore (where other
commands/utilities come into play to ensure that the
database is made consistent upon restoring it).

is a FS flash copy something like a FS snapshot? What other tools come into play, in order to make the DB consistent?

Thanks,
Bogdan

[Kelly Schlamb]

Yes, there are various terms that can be used to describe the technology, depending on the vendor and who you're talking to. :)

If the database is active when you wish to create the snapshot copy then you must use the SET WRITE SUSPEND command to suspend I/O against the disks (to avoid partial page writes in the copy). You use SET WRITE RESUME after the snapshot has been created.

At restore time you use the db2inidb tool to either perform restart recovery against the restored image, bringing it online, or putting it in a state where the database can be rolled forward.

Regards,
Kelly