| In the DB2 databases, there is the concept of | | | | already in use by AUTOMATIC STORAGE. This |
| 'automatic storage' database using which the | | | | condition can be checked by listing the container paths |
| database automatically grows whenever the need | | | | for the tablespaces, and by checking if the automatic |
| arises to do so. This feature can save you the hassles | | | | storage is in use. You can verify this by using the |
| of managing the storage containers thereby improving | | | | following command: |
| the flexibility and performance of the database. | | | | |
| However, you should define the automatic storage | | | | "db2pd -db <DBNAME> -tablespaces" |
| settings while creating the database. Having said that, | | | | |
| at times you do face problems while creating a | | | | Resolution: |
| tablespace in the database container because of this | | | | To overcome this problem, you should use a different |
| feature. Also, database corruption can be a potential | | | | folder to use this command to create a new |
| cause behind this purpose. You should try to find out | | | | tablespace. This can be done by using either of the |
| the cause behind this and try to recover DB2 | | | | following methods: |
| database. If it is database corruption, then you should | | | | - You should create a sub-folder using the same path |
| use a third-party DB2 database recovery software to | | | | for which you tried creating the tablespace earlier. |
| recover DB2 database. | | | | - You should create a new folder at a new location. |
| | | | | |
| Let us think of a situation in which you are working on | | | | If the problem is still not solved and you are unable to |
| IBM DB2 (UDB) v8 database. In this database, you are | | | | create a tablespace, then there is quite a possibility |
| adding a tablespace, which you are unable to perform. | | | | that the database is corrupt. For this, you should use a |
| An error message is displayed in this case, which is: | | | | third-party DB2 repair software to repair DB2 |
| | | | | database. With the help of these read-only DB2 |
| "db2 "create tablespace one managed by database | | | | recovery tools, you can make sure that the recovery |
| using (file '/home/v95inst1/SAMPLE/v95inst1' 1000)" | | | | is safe and secure. |
| DB221034E The command was processed as an | | | | |
| SQL statement because it was not a valid Command | | | | The most trusted name in the field of DB2 database |
| Line Processor command. During SQL processing it | | | | recovery is Stellar Phoenix DB2 Recovery Software, |
| returned: SQL0298N Bad container path. | | | | which recovers DB2 database from IBM DB2 (UDB) |
| SQLSTATE=428B2" | | | | v8 databases. Compatible with Windows Server 2003, |
| | | | | XP, and 2000, this DB2 recovery utility recovers DB2 |
| Cause: | | | | database by recovering various database |
| The most possible cause of this error is that the path | | | | components including tables, schemas, views, |
| that you have provided for creating the tablespace is | | | | containers, triggers, buffer pools, etc. |