HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Warning Messages(Cont.)
1804 MESSAGE Use of multiple DISTINCTs within a query or
subquery is a non-standard extension. (DBWARN 1804)
CAUSE Allowing multiple distincts in a query or subquery
is an ALLBASE/SQL extension to the ANSI SQL/89
standard.
ACTION Do not use this statement if portability is a
concern.
----------------------------------------------------------------------------
1805 MESSAGE DDL statement outside a CREATE SCHEMA statement
is a non-standard extension. (DBWARN 1805)
CAUSE ANSI SQL/89 requires DDL commands to be within a
CREATE SCHEMA AUTHORIZATION statement.
ACTION Place all DDL commands within the CREATE SCHEMA
statement if portability is a concern.
----------------------------------------------------------------------------
1806 MESSAGE Use of keyword as an identifier is a non-standard
extension. (DBWARN 1806)
CAUSE Use of keywords as identifiers is an ALLBASE/SQL
extension to the ANSI SQL/89 standard.
ACTION Do not use keywords as identifiers if portability
is a concern.
----------------------------------------------------------------------------
1807 MESSAGE Access to SYSTEM/CATALOG tables/views is a
non-standard extension. (DBWARN 1807)
CAUSE ALLBASE/SQL system/catalog views and tables are
non-standard objects.
ACTION Do not access these objects if portability is a
concern.
----------------------------------------------------------------------------
1808 MESSAGE An object with owner (!) not equal to schema name
(!) is a non-standard extension. (DBWARN 1808)
CAUSE This is an ALLBASE/SQL extension to the ANSI SQL/89
standard.
ACTION Modify the syntax if portability is a concern.
----------------------------------------------------------------------------
2005 MESSAGE The index dropped is a clustering index. (DBWARN
2005)
CAUSE The index you just dropped with the DROP INDEX
statement was created with the CLUSTERED attribute.
ACTION No action is necessary.
----------------------------------------------------------------------------
2006 MESSAGE User ! already has ! authorization. (DBWARN
2006)
CAUSE You tried to grant an authorization to a user that
already has that authorization.
ACTION No action is necessary.
----------------------------------------------------------------------------
2007 MESSAGE User ! already has ! authorization on !.!.
(DBWARN 2007)
CAUSE You tried to grant authority on a table or a module
to a user that had already been granted authority
on the specified table or module. Either you
granted the table authority before, or you are the
OWNER of the table or a DBA (and so you will be
able to revoke it even if you are not the grantor
of it).
ACTION No action is necessary.
----------------------------------------------------------------------------
2008 MESSAGE User ! already has ! authorization on !.!.!.
(DBWARN 2008)
CAUSE You tried to grant authority on a specific column
to a user that had already been granted authority
on the specified column. Either you granted the
column authority before, or you are the OWNER of
the table or a DBA (and so you will be able to
revoke it even if you are not the grantor of it).
ACTION No action is necessary.
----------------------------------------------------------------------------
2010 MESSAGE A transaction in progress was aborted. (DBWARN
2010)
CAUSE You issued a RELEASE or STOP DBE statement without
issuing a COMMIT WORK or ROLLBACK WORK statement
first.
ACTION No action is necessary.
----------------------------------------------------------------------------
2011 MESSAGE Use SQLUtil to purge physical file !. (DBWARN
2011)
CAUSE When you issue a DROP DBEFILE statement, the actual
physical file is not deleted; it is only deleted
from the system catalog.
ACTION Use the SQLUtil PURGEFILE command to purge the
physical file.
----------------------------------------------------------------------------
2012 MESSAGE DBEFile already of specified DBEFile type.
(DBWARN 2012)
CAUSE The DBEFile you attempted to ALTER was already of
the specified type.
ACTION No action is necessary.
----------------------------------------------------------------------------
2014 MESSAGE Module !.! not found. (DBWARN 2014)
CAUSE The module specified 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 satisfies the cursor definition. 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 defined on the table
exceeds the maximum key length and the key contains
a VARCHAR column.
ACTION No action is necessary as long as the actual 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 hash
structure is accessed.
----------------------------------------------------------------------------
2019 MESSAGE ASCII definition of view !.! not available for
storage. (DBWARN 2019)
CAUSE The stored module being executed contains a CREATE
VIEW that was prepared or preprocessed before the
existence of the SYSTEM.VIEWDEF table. Therefore,
it is not possible to store the select string that
defines the view.
ACTION If it is important that the ASCII view definition
be stored, use the PREPARE statement through ISQL
to create a new version of the module containing
the CREATE VIEW statement or preprocess the program
again. Refer to the ALLBASE/SQL Reference Manual
for information on the PREPARE statement.
----------------------------------------------------------------------------
2020 MESSAGE DBEnvironment corruption suspected - Rollforward
recovery required. (DBWARN 2020)
CAUSE An error may have caused the DBEnvironment to be
corrupted. An additional message will be returned.
ACTION Refer to the cause and action of the additional
message. Do not perform additional transactions at
this time. Contact your database administrator for
rollforward recovery on the DBEnvironment.
----------------------------------------------------------------------------
2022 MESSAGE Device does not exist on replicated system.
(DBWARN 2022)
CAUSE The CREATE DBEFile command contained a device
specification. The MPE/iX system where the
replicated database resides does not have a device
with this name. Therefore, the DBEFile will be
created on whatever device the system chooses.
ACTION Ignore the warning, or move the DBEFile to a device
using SQLUtil.
----------------------------------------------------------------------------
[REV BEG]
2023 MESSAGE Please close all open scans before proceeding
with RESUME. (DBWARN 2023)
CAUSE CREATE DBEFile command contained a DEVICE
specification. The MPE/iX system where the
replicated database resides does not have a volume
with this name. DBEFile is create on whatever
volume the system chooses.
ACTION Ignore the warning, or MOVE the DBEFile to a
desired device using SQLUtil.
[REV END]
----------------------------------------------------------------------------
2025 MESSAGE User ! has no grantable authority on !.!.
(DBWARN 2025)
CAUSE You issued a GRANT ALL statement but have no Owner
or DBA authority and have no grantable privileges
on the table. Nothing was granted.
ACTION No action required.
----------------------------------------------------------------------------
2026 MESSAGE REVOKE CASCADE has dropped a view or foreign key.
(DBWARN 2026)
CAUSE A view or foreign key depended on the SELECT or
REFERENCES privilege being revoked, so REVOKE
CASCADE dropped the dependent item.
ACTION Rollback will recover the item if it needs
recovery; otherwise, no action is necessary.
----------------------------------------------------------------------------
2027 MESSAGE Column ! not found in table/view !.!. (DBWARN
2027)
CAUSE A column included in a column-level GRANT was not
found in the table or view specified.
ACTION If the column was mis-spelled, revoke that column
authority and grant on the correct column.
----------------------------------------------------------------------------
2028 MESSAGE User ! already has ! authorization on columns of
!.! from a different grantor. (DBWARN 2028)
CAUSE Your GRANT of a table level authority has
overridden one performed by another grantor. The
column authorities given by that grantor are
removed, and replaced with your table level
authorities (with you as the grantor).
ACTION None necessary. The other grantor will not be able
to revoke this table level authority.
----------------------------------------------------------------------------
2029 MESSAGE User ! does not have any explicit authority on
!.!. (DBWARN 2029)
CAUSE REVOKE ALL failed to find any applicable
authorities for the given user.
ACTION None necessary. REVOKE ALL will only include those
authorities which the revoker is authorized to
revoke, so the user may still have authorities from
other grantors. Owner and DBA are authorized to
revoke all authorities.
----------------------------------------------------------------------------
2040 MESSAGE Character string truncation during storage in
host variable. (DBWARN 2040)
CAUSE A host variable character string was shorter than a
character column in the select list.
ACTION Check the string returned to see if it needs to be
longer in order to capture all necessary
information from the column. If so, modify the
declaration of the datatype.
----------------------------------------------------------------------------
2041 MESSAGE NULL values eliminated from the argument of an
aggregate function. (DBWARN 2041)
CAUSE A NULL value occurred in a column where an
aggregate (SUM, AVG, MAX, MIN, COUNT) was
evaluated, but was dropped from the computation.
ACTION Determine whether the information was needed for
correct computation. If it was, set the NULL
column to the needed value. To prevent future
lapses, change the column to be NOT NULL if
possible.
----------------------------------------------------------------------------
2042 MESSAGE ADD_MONTHS result adjusted to last day of month.
(DBWARN 2042)
CAUSE Result of ADD_MONTHS function was an invalid date,
which resulted in the day being adjusted to the
last day of the month.
ACTION No action required.
----------------------------------------------------------------------------
2043 MESSAGE Binary literal truncation during insert on column
!. (DBWARN 2043)
CAUSE The binary input is longer than the column
definition.
ACTION No action is necessary; however, the extra data is
lost.
----------------------------------------------------------------------------
2044 MESSAGE DEFAULT USER is specified, corresponding column
length should be at least 20 characters long.
(DBWARN 2044)
CAUSE You entered a column length less than 20 bytes.
ACTION No action necessary.
----------------------------------------------------------------------------