HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Warning Messages (Continued)
2045 MESSAGE DEFAULT 'literal' truncated, length ! exceeds
column length !. (DBWARN 2045)
CAUSE You specified a default constant length which is
longer than the column length defined when the
table was created.
ACTION Define a default value whose length will not exceed
the corresponding column length.
----------------------------------------------------------------------------
[REV BEG]
2046 MESSAGE String concatenation result is truncated.
(DBWARN 2046)
CAUSE Result length of string concatenation exceeds the
maximum.
ACTION No action needed.
[REV END]
----------------------------------------------------------------------------
2050 MESSAGE LONG column data exceeds defined length.
Truncated. (DBWARN 2050)
CAUSE The actual long column data is longer than the
defined length. The long column data was
truncated.
ACTION No action is necessary.
----------------------------------------------------------------------------
2051 MESSAGE LONG column data exceeds output file size.
Truncated. (DBWARN 2051)
CAUSE You tried to append to a file a long column whose
length plus the current file size exceeded the file
limit. The long column data was truncated.
ACTION No action necessary.
----------------------------------------------------------------------------
2052 MESSAGE Sort length of UNION may exceed maximum allowed !
bytes. (DBWARN 2052)
CAUSE The UNION command specifies 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.
----------------------------------------------------------------------------
2053 MESSAGE Sort length of ORDER BY/GROUP BY/DISTINCT/UNION
may exceed maximum allowed ! bytes. (DBWARN 2053)
CAUSE The ORDER BY, GROUP BY, DISTINCT, or UNION clause
of the SELECT statement specifies 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. You can calculate the maximum sort
tuple length from the formula given in Appendix A
of the ALLBASE/SQL Database Administration Guide.
----------------------------------------------------------------------------
2054 MESSAGE Sort length of sort merge join may exceed maximum
allowed ! bytes. (DBWARN 2054)
CAUSE The sort merge join query specifies 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 specified a redundant DISABLE AUDIT LOGGING
statement.
ACTION Check the sequence of operations.
----------------------------------------------------------------------------
2061 MESSAGE Audit logging already enabled. (DBWARN 2061)
CAUSE You specified 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 specified when
retrieving synchronization checkpoint data.
ACTION Check and correct the specified partition ids.
----------------------------------------------------------------------------
2063 MESSAGE Some partitions (but not all) failed on
Open_Log_Scan. (DBWARN 2063)
CAUSE Open_Log_Scan failed to open the scan for some of
the specified partitions.
ACTION Check the per partition return codes.
----------------------------------------------------------------------------
2065 MESSAGE DML ATOMICITY already set to ! level. (DBWARN
2065)
CAUSE The DML ATOMICITY is already set to row or
statement level.
ACTION Determine whether the SET DML ATOMICITY statement
is needed.
----------------------------------------------------------------------------
2066 MESSAGE ! constraints already set to !. (DBWARN 2066)
CAUSE Constraints specified were already set to deferred
or immediate.
ACTION Determine whether the SET CONSTRAINTS statement is
needed.
----------------------------------------------------------------------------
2067 MESSAGE User timeout exceeds maximum timeout; maximum
assumed (! seconds). (DBWARN 2067)
CAUSE The specified user timeout value is greater than
the maximum timeout value limit. When this error
occurs, the user timeout value is automatically set
to the maximum timeout limit.
ACTION Set the user timeout to a value less than or equal
to the maximum timeout limit
or
set the maximum timeout limit to a value greater
than or equal to the desired user timeout value.
----------------------------------------------------------------------------
2068 MESSAGE Length of substring requested ! starting at !
exceeds length of source string. (DBWARN 2068)
CAUSE In the SUBSTRING function, (Length - StartPosition
+ 1) is greater than the length of the SourceString
parameter.
ACTION No action is necessary. You should be aware that
the substring returned is shorter than expected.
----------------------------------------------------------------------------
2069 MESSAGE Length of substring requested ! exceeds maximum
length allowed !. (DBWARN 2069)
CAUSE The length of the substring requested by the
SUBSTRING function is longer than the maximum
length allowed.
ACTION No action is necessary. You should be aware that
the 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 you have validated the module
successfully in this manner, you will then be able
to use the VALIDATE statement on this module.
----------------------------------------------------------------------------
2076 MESSAGE Failed to validate module !.!. (DBWARN 2076)
CAUSE The module specified does not exist.
ACTION Check module name in the SYSTEM.SECTION view or
with the ISQL LIST INSTALL command.
----------------------------------------------------------------------------
2077 MESSAGE Failed to validate module !.!.(!). (DBWARN 2077)
CAUSE An error occurred during validation process.
ACTION Check the other error messages generated.
----------------------------------------------------------------------------
2078 MESSAGE No modules to be validated. (DBWARN 2078)
CAUSE There are no modules to be validated.
ACTION You specified the ALL option, but there are no
modules to be validated.
----------------------------------------------------------------------------
2079 MESSAGE Failed to validate procedure !.!. (DBWARN 2079)
CAUSE A procedure specified by name in the VALIDATE
statement does not exist.
ACTION Check your spelling, and verify the procedure owner
and name, then reissue the VALIDATE statement.
----------------------------------------------------------------------------
2080 MESSAGE No procedure(s) to be validated. (DBWARN 2080)
CAUSE You issued a VALIDATE ALL PROCEDURES statement, but
there are no procedures to be validated.
ACTION No action is required.
----------------------------------------------------------------------------
2081 MESSAGE Warning(s) occurred processing statement ! during
procedure creation/validation. (DBWARN 2081)
CAUSE An SQL statement in the procedure could not be
compiled at procedure creation or validation time.
The procedure was created or validated, but the
section corresponding to the statement was stored
as an invalid section.
ACTION Use the statement number in the message to
determine which procedure statement generated the
warning. Refer to the accompanying message or
messages for more information.
----------------------------------------------------------------------------