DB2 - Problembeschreibung
| Problem IT10097 | Status: Geschlossen |
PREPARE FOR 32BIT ON 64BIT MACHINE MAY RECEIVE SQL20537W | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problembeschreibung: | |
PREPARE for 32bit on 64bit machine under
DB2_COMPATIBILITY_VECTOR=ORA may receive SQL20537W unexpectedly
even if no array is used in source code.
An example scenario.
------
export LANG=C
db2stop
db2set DB2_COMPATIBILITY_VECTOR=ORA
db2start
db2 drop db TESTDB
db2 create db TESTDB using codeset UTF-8 territory US
db2 connect to TESTDB
db2 -tvf objects.txt
# create bufferpool, tablespaces, tables
db2 terminate
db2 connect to TESTDB
db2 prep test.sqc COMPATIBILITY_MODE ORA LONGERROR NO
------
* test.sqc : C program source code with no array
Here is the message by prep:
LINE MESSAGES FOR test.sqc
------
----------------------------------------------------------------
----
SQL0060W The "C" precompiler is in progress.
1234 SQL20537W The precompiler detected a combination of
arrays
with different cardinalities in the same SQL
statement.
The application was compiled to populate all
arrays in the
applicable statement with the minimum
cardinality: "0"
SQL0091W Precompilation or binding was ended with "0"
errors and "1" warnings. | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 10.5 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.5 FixPack 7. * **************************************************************** | |
| Local-Fix: | |
| Lösung | |
Problem was first fixed in DB2 UDB Version 10.5 FixPack 7. | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 15.07.2015 21.01.2016 21.01.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.5.0.7 |
|