NetBase SQL Shadowing Handbook

NetBase SQL Troubleshooting
____________________________________________________________
ver A0195 QUEST Software, Inc. 4-5
Error Messages
The error messages are listed in alphabetical order. Some error messages require assistance
from Quest Technical Support if they are encountered. The following list contains error
messages whose solutions you may perform. If you encounter a message that is not listed below,
please contact Quest Technical Support. Make a note of the error message, any details included
in the error message, and the version of NetBase you are running.
Some of these error messages and their explanations were provided by Hewlett-Packard, and
are reprinted here with permission.
ERROR MESSAGE SUGGESTION
A BEGIN WORK WSL record
encountered out of sequence.
(DBERR 10048)
**Causes Abort**
Apply_Log encountered the BEGIN WORK WSL
record for a new transaction while a previous
Apply_Log transaction was still in progress. Probably,
a single Apply_Log process is applying transactions
received from multiple open scans (so the application
should be checked). Transmission errors can also
cause this problem. If the application is handling
transactions which span multiple log buffers correctly,
retry the transmission of the transactions being
applied.
A WSL record in the log buffer has
an invalid record length specified.
(DBERR 10047)
**Causes Abort**
The Apply_Log intrinsic attempts consistency
checking on the lengths (among other parameters) of
the 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. If the
BEGIN WORK op code of the next log record allows
its correct length to be predetermined, the specified
record length is checked against this value.
Active transactions found on
partition nnn
(DBERR 2821)
An attempt was made to hard resync a partition
(through Modify_SCR) that currently has transactions
active. This could also occur if the SCR array (for
update) or the partition array (for delete) contained
partition IDs that the user did not mean to hard
resync. Verify the SCR array (or partition array)
contains only partition IDs that are being hard
resync'ed. If so, verify the partitions being hard
resync'ed are inactive, and no transactions are active
(on those partitions) before calling Modify_SCR.
** Causes Abort ** indicates an error that aborts the apply. Other error messages (if a
post_user_exit_after is being used) are passed to the user exit, and the
apply continues.
ERROR MESSAGE SUGGESTION