A DB2 database user can create a tablespace. A tablespace map is created automatically, and all the containers also get systematically lined up. The user can also add new containers or extend a pre-existing container using ALTER TABLESPACE command. However, if a tablespace contains container of a corrupted database (that no longer exists), then the user needs to untag that container. But, main problem occurs, when database user untags the container when it is in use. In such situations, the DB2 database gets corrupted and becomes unmountable. Furthermore, a user encounters an error message each time s/he tries to mount the database, which makes the records saved in the database inaccessible. To access the database in such situations, in case of no backup availability, a database user needs to opt for DB2 Recovery application...

DB2 database, although considered a reliable database, can get corrupted due to various reasons, such as, improper server shutdown, virus attack, and creating administrating objects without using characters listed in 7-bit ASCII range. The database records become inaccessible once it gets corrupted due to any of the above reasons. In such cases, an adequate backup acts as a boon and allows the user to access the database records. While in most cases, the user creates a backup of his DB2 database, there might situations, wherein, the user forgets to do so. In these situations, the user can repair his corrupted database using a commercial DB2 Repair software.

To explain the above case, consider a real-time scenario where your client for Windows with Big5 code page = 950 is created on TCH_Windows and DB2 Content Manager Server with code page 1252 is created on German_Windows. Now, if you create a database object on the client machine using Big5 characters, the creation will be successful, but when you try to access that object, it will appear to be blank. Furthermore, all the other objects in the database can not be accessed or deleted after you perform the above operation...