Are you encountering an error message during DB2 database startup? Or during the execution of Alter Tablespace SQL command? If 'yes', then the three possible reasons for the error message are, container could not be found, container is not tagged, or container is corrupt. In most of these situations, the database becomes unmountable, rendering to inaccessibility of stored records. To get past the above error message and to access DB2 database records, the user needs to restore the tablespace or database from an updated backup. However, if the backup is not available or corrupted, then you need to repair corrupted DB2 database using an effective DB2 Recovery application.

To illustrate the above case, consider a practical scenario wherein you encounter the below error message while trying to start your DB2 database:

“SQL0293N Error accessing a table space container.”...