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 IC96397 Status: Closed

SQL0440N ON SYSIBM BUILT IN FUNCTIONS AFTER RESTORE REPLACE EXISTING OF A
DATABASE ONTO A PREVIOUS RELEASE FIX PACK

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
After restoring a backup made on a higher fix pack level onto a 
lower level fix pack, SQL0440N will be raised on calling a 
sysibm qualified routine such as sysibm.rtrim() : 
 
1. create sample database on v97fp8 
2. backup database 
3. restore database on v97fp6 
4. connect to db 
5. db2 "values(sysibm.rtrim('hello'))" ---> fails with SQL0440N 
 
This error will persist throughout first activation of the 
database. Once the database is deactivated and reactivated, the 
error will no longer be raised.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to version 10.1 Fix Pack 3                           * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
first fixed in version 10.1 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
01.10.2013
01.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList