ALLBASE/SQL Message Manual (36216-90213)

34 Chapter2

ALLBASE/SQL Warning Messages

2014 MESSAGE Module !.! not found. (DBWARN 2014)

CAUSE The module speciﬁed in the EXECUTE or DROP

MODULE statement does not exist.

ACTION Check your spelling. Ask your database administrator to

check the SYSTEM.SECTION view to make sure that the

module exists in the DBEnvironment to which the

application is connected.

2015 MESSAGE Row size of table !.! exceeds ! bytes.

(DBWARN 2015)

CAUSE The row size of the table you created exceeds the

maximum number of bytes.

ACTION No action necessary. An error will occur only if you

attempt an operation that causes the row length of the

table to exceed the maximum number of bytes.

2016 MESSAGE Length of index ! on table !.! exceeds !

bytes. (DBWARN

2016 )

CAUSE The index that you created exceeds the maximum key

length and contains a VARCHAR column.

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

VARCHAR data does not cause the maximum key length

to be exceeded. The key length is determined using the

actual data length in the VARCHAR column. If the

maximum key length is exceeded, an error will occur when

the index is accessed.

2017 MESSAGE The data updated/deleted is in the RC/RU

transaction. (DBWARN 2017)

CAUSE You updated or deleted data in the transaction which is

started in RC or RU mode.

ACTION If you are using a non-cursor UPDATE or DELETE

statement, you may ignore this message.

If you are using the UPDATE/DELETE WHERE

CURRENT statement, ALLBASE/SQL only guarantees

that the data still satisﬁes the cursor deﬁnition. To

guarantee integrity, you might wish to use the REFETCH

statement to validate the data before you actually

update/delete the data.

2018 MESSAGE Length of hash key on table !.! exceeds !

bytes. (DBWARN 2018)

CAUSE The key length of the hash deﬁned on the table exceeds

the maximum key length and the key contains a

VARCHAR column.