ALLBASE/SQL Message Manual (36216-90213)

Chapter 2 39

ALLBASE/SQL Warning Messages

2054 MESSAGE Sort length of sort merge join may exceed

maximum

allowed ! bytes. (DBWARN 2054)

CAUSE The sort merge join query speciﬁes a number of columns

whose total sort tuple length exceeds the maximum

allowable and contains a VARCHAR column.

ACTION No action is necessary as long as the length of the

VARCHAR data does not cause the maximum sort tuple

length to be exceeded. The sort tuple length is determined

using the actual data length in the VARCHAR column. If

the maximum sort tuple length is exceeded, an error will

occur when the sorting is performed.

2056 MESSAGE A cursor opened using KEEP CURSOR WITH

NOLOCKS requires

sorting. You must ensure data integrity

yourself. (DBWARN 2056)

CAUSE You are using the KEEP CURSOR WITH NOLOCKS

option on a cursor requiring a sort operation such as the

ORDER BY clause or a join.

ACTION You need to verify that the data is correct if you want to do

an update where your cursor is located.

2059 MESSAGE There are deferred UNIQUE/PRIMARY KEY and/or

FOREIGN KEY

constraint violations that may not be

resolvable.

(DBWARN 2059)

CAUSE There are UNIQUE/PRIMARY KEY constraint or

FOREIGN KEY constraint violations pending at deferred

constraint checking mode.

ACTION Avoid truncating or dropping data when there are deferred

constraint violations.

2060 MESSAGE Audit logging already disabled. (DBWARN 2060)

CAUSE You speciﬁed a redundant DISABLE AUDIT LOGGING

statement.

ACTION Check the sequence of operations.

2061 MESSAGE Audit logging already enabled. (DBWARN 2061)

CAUSE You speciﬁed a redundant ENABLE AUDIT LOGGING

statement.

ACTION Check the sequence of operations.

2062 MESSAGE Partition not found. (DBWARN 2062)

CAUSE A non-existent partition id was speciﬁed when retrieving

synchronization checkpoint data.