Syslog message BXB during table logging

[] [] [] [] [] [] [] [] []

Symptom

In the system log (syslog), the following error messages are displayed with the syslog ID BXB: “Data records of table

already contained in the log table DBTABLOG”.
In addition, the dev_w* work process trace files frequently display entries such as the following:
M Wed Mar 11 20:50:11 2009
M *** WARNING => big time diff 4262270423 [4032523715 3999826842]for
stamp STAT_READSEQ, correct ???
M *** WARNING => big time diff 4271402346 [4032538710 4008973760]for
stamp STAT_READSEQ, correct ???
M *** WARNING => big time diff 4285835994 [4008974183 3999842881]for
stamp STAT_READSEQ, correct ???

Other terms

Table log, DBTABLOG, BXB, dbprt.c

Reason and Prerequisites

Log records that are written during table logging to the log table DBTABLOG are identified by a time stamp (among other things) that is precise to the micro second. You can obtain this time stamp via a relevant operating system routine. If the operating system routine does not work correctly (if the sequence of time stamps provided is not in ascending order), the system may generate a key of a record that already exists when it writes the new log record. In this situation, the new log record cannot be written to log table DBTABLOG and the syslog entry described above is generated.

Solution

The operating system routine for determining the time stamp must function correctly. These problems are known to occur on Microsoft Windows platforms in particular. Read Note 1036194 and implement the solution it describes.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment