| Are you unable to restore your DB2 database from | | | | When you restore a DB2 database to another |
| one server to another? Does restore process fail with | | | | system, next database number for system is given to |
| SQL0298N “Bad container path” error while | | | | it. This number may not be equal to original system. |
| restoring database from one server to another? Well, | | | | Restore process attempts to recreate the table space |
| the problem may occur if either the DB2 database is | | | | through fully-qualified container path. Thus, restore |
| corrupted or the destination server does not have | | | | operation fails. |
| sufficient disk space. In case of DB2 database | | | | How to resolve this problem? |
| corruption, you must have an absolute backup of your | | | | You can sort out this behavior of DB2 database and |
| database to restore data from it. However, if the | | | | perform db2 recovery through the redirected restore. |
| backup is either invalid or not updated, DB2 database | | | | While using SET TABLESPACE CONTAINERS |
| recovery becomes need of hour. | | | | command for defining storage of affected table |
| What causes “Bad container path” error? | | | | spaces, don't fully-qualify the path in database |
| This DB2 database error may take place if table | | | | directory. After that, the table space is created under |
| space is declared with fully-qualified container path, | | | | appropriate directory of DB2 database. |
| which points to a database directory. For instance: | | | | If the DB2 database is corrupted and application can |
| “CREATE TABLESPACE tbsp MANAGED BY | | | | not read it, the problem can not be fixed using the |
| SYSTEM USING ('/home/db2inst1/db2inst1/NODE0000 | | | | above method. In such situations, you need to repair |
| SQL00003/tbsp')” | | | | and restore the database using third-party db2 |
| Although, it might be valid container path for particular | | | | database repair applications. |
| database, presence of “SQL00003/..” directory | | | | The applications recover DB2 database in all corruption |
| in path causes problems when you restore database | | | | scenarios. They use high-end scanning techniques to |
| from one system to another with varying set of | | | | methodically scan entire database and extract all |
| databases. | | | | inaccessible data from it. Such repair tools have |
| At this point, log of DB2 database may report the | | | | interactive and simple graphical user interface, and |
| following entries: | | | | offer easy recovery, without demanding sound |
| 2005-12-29-10.42.12.195000-300 I16206637H356 LEVEL: | | | | technical skills. |
| Error PID: 1688 TID: 3044 PROC: db2agent (SAMPLE) | | | | DB2 Recovery software repairs and restores |
| INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 | | | | corrupted DB2 database of all sizes. The software |
| UDB, buffer pool | | | | works well with DB2 (UDB) v8. It restores all DB2 |
| services,sqlbCheckContPathsForOtherDbDir, probe:10 | | | | database components, such as tables, views, |
| RETCODE : | | | | containers, table spaces, schemas, and buffer pools. |
| INER_PATH “Bad container path” | | | | |