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
To illustrate the above problem, consider a scenario wherein you create a tablespace with three containers, out of which, one is taken from a previous database. The tablespace works fine until you received below mentioned error message:
“SQL0294N The container is already in use.”
The error message flashes at the time of mounting of the database and makes the records saved in the database inaccessible.
The above error message appears when you use a DB2untag command on a container, while it is being used by the DB2 database. In such cases, both the databases (that you are currently using and the one from which the container was taken) get corrupted.
To get past the above error message and to access the records, you need to:
Use a copy of a database backup to perform restoration.
In case of deficient or corrupted database backup, use a third-party DB2 Repair
Such DB2 Database Recoverytools use powerful, yet safe repair methods to repair the database after all cases of logical corruption. The original database remains untouched and unmodified during repair. Such software are easily understandable as they come with highly interactive and user-friendly interface.