| Are you encountering an error message during DB2 | | | | the database. |
| database startup? Or during the execution of Alter | | | | The container is improperly tagged to a different table |
| Tablespace SQL command? If 'yes', then the three | | | | space. |
| possible reasons for the error message are, container | | | | Resolution: |
| could not be found, container is not tagged, or | | | | To resolve the database startup error message and |
| container is corrupt. In most of these situations, the | | | | to access database records, you need to follow the |
| database becomes unmountable, rendering to | | | | steps mentioned underneath: |
| inaccessibility of stored records. To get past the | | | | Verify that the container (raw device, directory, or file) |
| above error message and to access DB2 database | | | | exists at its specified location. |
| records, the user needs to restore the tablespace or | | | | Restore the database from an updated backup. |
| database from an updated backup. However, if the | | | | In case of unavailable backup or backup falling short of |
| backup is not available or corrupted, then you need to | | | | restoring the database, the database needs to be |
| repair corrupted DB2 database using an effective DB2 | | | | repaired using a commercial DB2 Recovery software. |
| Recovery application. | | | | A DB2 Repair utility uses effective repair techniques to |
| To illustrate the above case, consider a practical | | | | repair corrupted DB2 databases, and restore them at |
| scenario wherein you encounter the below error | | | | required location. The non destructive utility maintains |
| message while trying to start your DB2 database: | | | | complete security of the original database. The repair |
| "SQL0293N Error accessing a table space container." | | | | application is built with user-friendly interface that |
| After the above error message pops up, data saved | | | | makes the software self-explanatory. |
| in the database becomes inaccessible. In addition, no | | | | DB2 Recovery Software is used by most of the |
| operations can be performed on the database after | | | | database administrators to repair their logically |
| the error message flashes on the screen. | | | | corrupted databases. DB2 Recovery tool supports |
| Cause: | | | | repair of IBM DB2 (UDB) v8 databases. Designed for |
| The above error message appears when the | | | | Windows 2003, XP, and 2000, it recovers almost all |
| container becomes unreadable due to any of the | | | | DB2 database components, including, tables, views, |
| underneath reasons: | | | | schemas, triggers, buffer pools etc. The recovery utility |
| The container tag is corrupt. | | | | recovers primary foreign keys associated with tables. |
| The container was not found at the time of mounting | | | | |