home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC68306 Status: Closed

DBI1225W WAS ENCOUNTERED EVEN IF THE AUTHENTICATION TYPE HAS NOT BEEN
CHANGED.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
User issued db2imigr command and may encounter the "DBI1225W 
The authentication type of a cataloged local database has been 
changed" message, even though there was no change to the 
authentication settings. The message is being returned whenever 
db2ckmig returns a warning, which doesn't necessarily mean 
migration cannot continue. 
 
The two cases that cause DBI1225W are as follows: 
 
Case 1) If the downlevel database has unfenced routine or 
wrapper. 
 
Case 2) If the downlevel database has user views defined on V8 
catalog view(s). 
 
In both cases, the actual warning message(s) return by db2ckmig 
will be written to the migration.log, but the DBI1225W message 
will be outputted to the console, which may mislead the user 
thinking it's some authentication problem.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* User issued db2imigr command and may encounter the "DBI1225W * 
*                                                              * 
* The authentication type of a cataloged local database has    * 
* been                                                         * 
* changed" message, even though there was no change to the     * 
*                                                              * 
* authentication settings. The message is being returned       * 
* whenever                                                     * 
* db2ckmig returns a warning, which doesn't necessarily mean   * 
*                                                              * 
* migration cannot continue.                                   * 
*                                                              * 
*                                                              * 
*                                                              * 
* The two cases that cause DBI1225W are as follows:            * 
*                                                              * 
*                                                              * 
*                                                              * 
* Case 1) If the downlevel database has unfenced routine or    * 
*                                                              * 
* wrapper.                                                     * 
*                                                              * 
*                                                              * 
*                                                              * 
* Case 2) If the downlevel database has user views defined on  * 
* V8                                                           * 
* catalog view(s).                                             * 
*                                                              * 
*                                                              * 
*                                                              * 
* In both cases, the actual warning message(s) return by       * 
* db2ckmig                                                     * 
* will be written to the migration.log, but the DBI1225W       * 
* message                                                      * 
* will be outputted to the console, which may mislead the user * 
*                                                              * 
* thinking it's some authentication problem.                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 Fix Pack 3                    * 
****************************************************************
Local Fix:
User may ignore the DBI1225W message and find the detailed 
reason causing the warning(s) from migration.log.
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
Problem was first fixed in Version 9.7 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.05.2010
20.09.2010
20.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList