This section identifies incompatibilities introduced by 64-bit engine support in DB2 Universal Database (UDB) Version 7.1.
| UNIX |
|
32-bit object code will not link against 64-bit libraries.
Application fails to link. When you attempt to link 32-bit objects against the 64-bit DB2 application library, an operating system linker error message is returned.
Note that operating systems may behave differently. For example, AIX will ignore 32-bit archive libraries, and the symptom for mismatched 32-bit and 64-bit objects could be unresolved symbols.
The application must be recompiled as a 64-bit executable, and relinked against the new 64-bit DB2 libraries.
WIN | UNIX | OS/2 |
No 32-bit clients can connect to databases on 64-bit servers.
If a 32-bit client tries to connect or attach to a 64-bit server, or a 64-bit client tries to connect or attach to a 32-bit server, when both the server and the client are running DB2 UDB Version 7, then error message SQL1434N is returned. All other connection or attachment attempts fail with SQLCODE -30081.
Use 64-bit clients.
32-bit client connections or attachments to a 64-bit server, and 64-bit client connections or attachments to a 32-bit server will be supported in a future release.
WIN | UNIX | OS/2 |
A UDF that changes the length field of the scratchpad passed to it triggers SQLCODE -450.
Any UDF that changes the length field of the scratchpad fails. The invoking statement receives error message SQL0450N, including the schema and specific name of the function.
Rewrite the UDF body to not change the length field of the scratchpad.
This restriction was previously documented, but is only now being enforced.