Informix - Problem description
Problem IC62190 | Status: Closed |
DBIMPORT FAILS WITH A -201 OR -620 ERROR WHEN USING DBEXPORT FILE FROM 11.50.XC4 OR 11.50.XC3W2 | |
product: | |
IBM IDS ENTRP E / 5724L2304 / B15 - IDS 11.50 | |
Problem description: | |
The problem can happen with either of the following scenarios: Dbimport fails with a -201 error when multiple collations are involved. Dbimport fails with a -620 error when external spaces or Virtual-Table Interface (VTI) or Virtual-Index Interface (VII) is involved. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users performing dbimport with the dbexport file from IDS * * 11.50.xC4/11.50.xC3W2 * **************************************************************** * PROBLEM DESCRIPTION: * * Dbexport in IDS 11.50xC3W2 or 11.50xC4 creates an incorrect * * DDL file (<dbname>.sql) in some instances. Using this * * incorrect DDL file in these releases or later releases for a * * dbimport causes dbimport to fail with -201 or -620 error. * **************************************************************** * RECOMMENDATION: * * Upgrade to IDS 11.50.xC5. After you upgrade you will need * * to re-run the dbexport to generate the correct DDL file. * **************************************************************** | |
Local Fix: | |
If you see -201 error running dbimport, then you should modify the dbexport-created DDL file. Place the "ALTER TABLE..." statement that failed after the create table statement it will alter. Re-run the dbimport command. If you see -620 error running dbimport, then you should modify the dbexport-created DDL file. Remove the "ALTER TABLE.... MODIFY EXTENT SIZE" statement that failed. Re-run the dbimport command again. | |
Solution | |
The problem has been fixed in IDS 11.50.xC5. When using Dbexport, the correct DDL file is created. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.07.2009 27.07.2009 27.07.2009 |
Problem solved at the following versions (IBM BugInfos) | |
11.50.xC5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
11.50.xC5 |