Overview of timestamp mismatches

The DBRM timestamp is an encoded stored clock value, and the precise location of the corresponding timestamp in the load module varies, depending on the application language type. Mismatches of the load module’s timestamp and the DBRM that is bound to the Db2 subsystem can cause problems (such as -805 SQL errors) at execution time.

Before you promote an application into production, you must ensure that your DBRMs and load modules have been correctly promoted to your production libraries. You must also ensure that all your DBRMs or packages are bound to your plans in each subsystem.

The BMC AMI SQL Explorer for Db2 product provides the following functions to help you fulfill these requirements:

• The DBRM to Load Compare [DBRM library (DBRMLIB) and load library comparison] function ensures that the timestamps in your DBRMLIB and load libraries match, and alerts you to any promotion problems in your production libraries. When you use this feature, SQL Explorer produces a report that lists the timestamp matches between the specified DBRM libraries and corresponding load module libraries.
• The DBRMLIB to Db2 Catalog Compare (DBRMLIB and Db2 catalog comparison) function ensures that the timestamps in your DBRMLIB and Db2 catalog match, and alerts you when binds are missing. Binds are generated when the timestamp in the catalog is earlier than the timestamp in the DBRMLIB.