|
Problem IC70517
|
Status: Closed |
SQL1323N IS RETURNED FROM THE DB2IUPGRADE/DB2IMIGR COMMAND WHEN MIGRATING A V9.1/9.5 DB2 INSTANCE TO V9.7. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When the db2iupgrade.exe (or db2imigr.exe) command is executed
in a batch file or some script to migrate DB2 instance from a
V9.1/V9.5 DB2 copy to V9.7, although the DB2 instance is
upgraded to V9.7 successfully, the return code from
db2iupgrade.exe is -1323, which provides false information.
If the same db2iupgrade command line is executed in a db2
command window, you will see a message that tells the instance
was upgraded successfully, even its return code (which is not
displayed) is also -1323. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* WINDOWS *
****************************************************************
* PROBLEM DESCRIPTION: *
* When the db2iupgrade.exe (or db2imigr.exe) command is *
* executed *
* in a batch file or some script to migrate DB2 instance from *
* a *
* V9.1/V9.5 DB2 copy to V9.7, although the DB2 instance is *
* *
* upgraded to V9.7 successfully, the return code from *
* *
* db2iupgrade.exe is -1323, which provides false information. *
* *
* *
* *
* If the same db2iupgrade command line is executed in a db2 *
* *
* command window, you will see a message that tells the *
* instance *
* was upgraded successfully, even its return code (which is *
* not *
* displayed) is also -1323. *
****************************************************************
* RECOMMENDATION: *
* Since the DB2 instance actually was upgraded from v91/v95 to *
* v97 correctly, this error return code can be ignored. *
* *
* Since this problem has been fixed in v97fp3, you can *
* consider to upgrade to DB2 Version 9.7 Fix Pack 3 *
**************************************************************** |
| Local Fix: |
Since the DB2 instance actually was upgraded from v91/v95 to v97
correctly, you can ignore this error code.
The other option to double check whether the DB2 instance was
migrated to V9.7 correctly is to execute the following DB2
commands:
1). db2ilist : -- whether the DB2 instance is listed in
the V9.7 DB2 copy it should be upgraded to
2). set DB2INSTANCE=[instanceName]
db2start: -- whether the upgraded DB2 instance can
be started successfully in the V9.7 copy |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7 Fix Pack 3. |
| Workaround |
N/A |
| Comment |
N/A |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.08.2010
28.09.2010
28.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1./V95,
9.7.,
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
