If corrupted database container is present in tablespace, the container has to be untagged. But untagging while the database is using it can be problematic and mostly results into unmounting of the database. Every attempt to access the database fails and its data remains inaccessible. This is usually accompanied by error message-“SQL0294N the container is already in use” while mounting database.

The problem takes place due to use of DB2untag command on container, when it is being processed DB2 database. This damages both the database one which is in use and from which container was taken off.

In such situation database backup will help restore data if not you need to use db2 repair tool. It efficiently takes up the problem by firstly scanning the database and retrieving data from it. It is no way modify records of the database only it retrieves data in accessible form and store it into a new one. DB2 database repair software has a user friendly interface and is easy to use with few simple steps.

In order to resolve the issue first try to restore the DB2 database and after several hours start both the servers up and run again in the peer mode and see if the problem gets resolved. If not then you must repair your DB2 database using any third party software. DB2 Repair software is simply perfect for it as it performs the extensive scans to find the source of the problem using its sophisticated algorithm and resolves the issue in seconds.