ALLBASE/SQL Message Manual (36216-90213)

Chapter 8 245
ALLBASE/SQL Error Messages: 8221-10999
size_used is smaller than the smallest WSL record
possible, or that the size_used is greater than the number
of bytes reserved in the log buffer (as indicated by the
buffer_size field in the arglist).
ACTION Check that the size_used is less than or equal to the
buffer_size field in the arglist. The size_used being passed
to Apply_Log should also be checked against the value
that was returned by Transmit_Log.
10046 MESSAGE Invalid buffer offset passed. (DBERR 10046)
CAUSE Apply_Log has determined that the buffer_offset field
specified in the arglist does not point to a valid position in
the log buffer. This will occur if the buffer_offset contains a
negative value, or a number greater than the size_used
field specified in the arglist.
ACTION Check the application.
10047 MESSAGE A WSL record in the log buffer has an invalid
record length specified. (DBERR 10047)
CAUSE The Apply_Log intrinsic attempts consistency checking on
the lengths of records encountered in the log buffer. If the
current position in the buffer plus the length of the next
log record takes it beyond the end of the used buffer space,
Apply_Log will generate this error. On BEGIN WORK, if
the op code of the next log record allows predetermining
its correct length, the specified record length is checked
against this value.
ACTION Check the parameters set up by the application.
10048 MESSAGE A BEGIN WORK WSL record encountered out of
sequence. (DBERR 10048)
CAUSE This error is generated when Apply_Log encounters the
BEGIN WORK WSL record for a new transaction while a
previous Apply_Log transaction is still in progress. A
possible cause is if an application started applying
transaction T1 (which spanned multiple log buffers) and
tried to apply transaction T2 before applying the COMMIT
WORK WSL record for T1. This error is most likely
encountered when a single Apply-Log server process is
applying transactions received from multiple open scans.
Another possible cause is if a transmission error occurred
and the end of the transaction (containing the COMMIT
WORK WSL record) was lost.
ACTION Check the application. If the application is handling
transactions correctly (especially ones that span multiple
log buffers) then you may try transmitting again the
transactions being applied.