DB2 - Problembeschreibung
| Problem IC93161 | Status: Geschlossen |
BINDING DB2UCKTB.BND AGAINST LOWER RELEASE DB2 LUW DATABASE THROWS ERROR. | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problembeschreibung: | |
Binding db2ucktb.bnd from DB2 LUW 10.1 client to DB2 LUW 9.5 or
9.7 databases throws error as below. (Note that db2ucktb.bnd is
listed in db2ubind.lst file, therefore binding the db2ubind.lst
file will also hit the issue.)
db2 bind sqllib/bnd/db2ucktb.bnd BLOCKING ALL GRANT PUBLIC
LINE MESSAGES FOR db2ucktb.bnd
------
----------------------------------------------------------------
----
SQL0061W The binder is in progress.
666 SQL0104N An unexpected token "TEMPORAL" was found
following
"VALUES (CURRENT ". Expected tokens may
include: "CONCAT".
SQLSTATE=42601
SQL0082C An error has occurred which has terminated
processing.
SQL0092N No package was created because of previous
errors.
SQL0091N Binding was ended with "3" errors and "0"
warnings.
Explanation: The statement that causes the above error is valid
and needed for DB2 LUW 10.1 databases, and is not run against
DB2 LUW 9.5 or 9.7 databases, but it still causes the whole bind
operation to fail. Adding the SQLERROR CONTINUE bind option
will allow the bind operation to complete successfully, with the
statement giving a warning (no longer an error) that can be
safely ignored.
The fix for this APAR is to make the bind operation for
db2ucktb.bnd to use the SQLERROR CONTINUE option implicitly
(i.e. even when the option is not specified), thus the bind will
complete successfully.
Note: Similar issue may exist when binding db2ucktb.bnd against
DB2 non-LUW databases. The same fix applies (if the issue
exists). | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW Version 10.1 Fix Pack 3. * **************************************************************** | |
| Local-Fix: | |
Use SQLERROR CONTINUE option to bind db2ucktb.bnd against DB2 LUW 9.5 or 9.7 servers. | |
| verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Lösung | |
Problem was first fixed in DB2 LUW Version 10.1 Fix Pack 3. | |
| Workaround | |
Use SQLERROR CONTINUE option to bind db2ucktb.bnd against DB2 LUW 9.5 or 9.7 servers. | |
| Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC94025 Nachfolger : | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.06.2013 27.09.2013 27.09.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.1.0.3 |
|
| 10.1.0.3 |
|