DB2 Version 9.7 for Linux, UNIX, and Windows

Maximum limit of log sequence numbers has increased

Individual log records within a database are identified by their log sequence number (LSN). In this release, the upper limit for LSNs has increased. The size of the LSN has been changed from six bytes to eight bytes.

Details

A new API data type, db2LSN, has been defined in db2ApiDf.h in support of the new LSN size.

For information about what happens between new and old client and server combinations, see "Log sequence number changes affecting API and application behavior".

User response

There is no down level API support for the log read APIs affected by this change. You need to update existing applications using log read APIs (db2ReadLog and db2ReadLogNoConn APIs) to use the new release libraries after upgrading the database server. Clients must also be upgraded to the new release to use the new libraries.

You must also change applications to use the new LSN data structure differences present in the log flow that is returned in the log buffer during a log read API operation.

The error message, SQL2032N, is returned to indicate an unsupported down level API call.