Using DB2 Universal Database on 64-bit Platforms

Chapter 7. Messages

A new sqlcode error message (SQL1434N) is returned when incompatible client/server attachment or connection attempts are made.

A new sqlcode error message (SQL4020N) is returned by sqlaprep when the precompiler encounters a host variable of long type.

A new warning (SQL5066W) is returned if sqlfxdb is called with the old DBHEAP token (SQLF_DBTN_DBHEAP) instead of the new one (SQLF_DBTN_DB_HEAP), and the value of the DBHEAP database configuration parameter is larger than that which the old type can handle.

SQL0450NRoutine "<routine-name>" (specific name "<specific-name>") has generated a result value, SQLSTATE value, message text, or scratchpad which is too long.

Explanation: Upon return from routine "<routine-name>" (specific name "<specific-name>"), DB2 has detected that more bytes were returned than were allocated for one of the following:

This is not permitted.

This error will also be returned if the length field of the scratchpad is altered by the routine.

User Response: See your Database Administrator, or the author of the routine.

sqlcode: -450

sqlstate: 39501

SQL1434NA CONNECT or ATTACH statement failed because of a client/server incompatibility between 32-bit and 64-bit platforms.

Explanation: This release does not support client/server connections between 32-bit and 64-bit platforms.

User Response: You can issue a CONNECT or ATTACH statement in the following scenarios:

sqlcode: -1434

sqlstate: 08004

SQL1706WAt least one non local database was detected in the node directory for this instance during word size instance migration.

Explanation: While performing word size instance migration, at least one database not created under this instance was encountered. Such databases must have the same word size as this instance for migration to complete successfully.

User Response: Ensure that all databases cataloged at the instance have the same word size.

SQL1707NUnable to migrate the instance word size.

Explanation: There was an error while attempting to migrate the word size of the instance. Please contact your IBM service representative.

User Response: Contact your IBM service representative.

SQL4020NThe 'long' host variable "<token 1>" is not valid. Use 'sqlint32' instead.

Explanation: If the LONGERROR YES precompile option is in effect or the precompile option LONGERROR has not been specified and the platform has 8-byte 'long's, then the INTEGER host variable must be declared with the data type 'sqlint32', not 'long'.

On 64-bit platforms with 8-byte 'long' types the precompile option LONGERROR NO can be used to specify that 'long' host variables are to be used for BIGINT data types. For maximum portability the use of 'sqlint32' and 'sqlint64' are recommended for INTEGER and BIGINT data types respectively.

User Response: Replace the current data type of the host variable with the data type specified in the message.

SQL5066WThe database configuration parameter value for token "<token-name>" has been truncated.

Explanation: The database configuration parameter value is larger than the specified token can contain.

A new token now represents this database configuration parameter value and should be used if the value is larger than can be contained by the old token.

User Response: Use the new token for this database configuration parameter.


[ Top of Page | Previous Page | Next Page ]