ALLBASE/SQL Message Manual (36216-90213)

Chapter 2 41
ALLBASE/SQL Warning Messages
substring returned is shorter than expected and that
truncation may occur.
2070 MESSAGE The transaction was committed, since it is
read only.
(DBWARN 2070)
CAUSE The transaction that was being prepared for COMMIT was
found to have no associated updates. The transaction was
therefore committed.
ACTION No action needed.
2071 MESSAGE The transaction was aborted due to deadlock.
(DBWARN
2071)
CAUSE A deadlock situation caused the transaction to abort.
ACTION Refer to the ALLBASE/SQL Advanced Application
Programming Guide to determine ways to avoid deadlock
situations.
2072 MESSAGE The transaction was aborted due to integrity
violation.
(DBWARN 2072)
CAUSE An unresolved integrity violation caused the transaction
to abort.
ACTION Check the application logic to ensure that all uniqueness
and referential constraint violations are resolved before
attempting to commit the transaction.
2073 MESSAGE The transaction was aborted due to timeout.
(DBWARN
2073)
CAUSE A timeout occurred while the application was waiting for a
resource.
ACTION Check the application for possible cross-database
deadlocks.
2074 MESSAGE The transaction was aborted. (DBWARN 2074)
CAUSE A database internal problem caused the transaction to
abort.
ACTION Retry the transaction.
2075 MESSAGE Cannot revalidate Section !.!(!).
(DBWARN 2075)
CAUSE Either you have recently performed a migration or you
have installed a module that was created on an earlier
release of ALLBASE/SQL.
ACTION Preprocess or run the application to validate module. After