HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
1684 MESSAGE Cannot close message catalog (!). (DBERR 1684)
CAUSE An unexpected error was encountered when trying to
close the ALLBASE/SQL message catalog.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
1685 MESSAGE Failed loading keyword (!). (DBERR 1685)
CAUSE An unexpected error occurred while trying to obtain
information from the ALLBASE/SQL message catalog.
The version of the message catalog is probably
incompatible with the version of the program.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
1686 MESSAGE Failed to determine minimum uniqueness of
keywords (!). (DBERR 1686)
CAUSE An unexpected error occurred while trying to obtain
information from the ALLBASE/SQL message catalog.
The version of the message catalog is probably
incompatible with the version of the program.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
1687 MESSAGE Failed to obtain string constant (set !, msg !,
!). (DBERR 1687)
CAUSE An unexpected error occurred while trying to obtain
information from the ALLBASE/SQL message catalog.
The version of the message catalog is probably
incompatible with the version of the program.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
1688 MESSAGE Cannot open $STDINX. (! !) (DBERR 1688)
CAUSE An MPE/iX file system error was encountered.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
1689 MESSAGE Cannot close $STDINX. (! !) (DBERR 1689)
CAUSE An MPE/iX file system error was encountered.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
1690 MESSAGE Cannot read from $STDINX. (! !) (DBERR 1690)
CAUSE An MPE/iX file system error was encountered.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
1813 MESSAGE The statement is not valid in SETOPT. (DBERR
1813)
CAUSE The statement is not supported with SETOPT.
ACTION Do not use the statement in SETOPT.
----------------------------------------------------------------------------
1814 MESSAGE Conflict ! statements or conflict conditions on !
statement occur in SETOPT statement. (DBERR 1814)
CAUSE ! statements or conditions on ! statement in
SETOPT are conflicting.
ACTION Remove incorrect ! statement or incorrect
conditions from ACCESS statement and reexecute
SETOPT and the query.
----------------------------------------------------------------------------
1815 MESSAGE WITH clause of GENPLAN is not allowed in the
GENPLAN on a section. (DBERR 1815)
CAUSE You tried to specify a GENPLAN on a section with a
WITH clause.
ACTION Remove WITH clause from GENPLAN statement.
----------------------------------------------------------------------------
[REV BEG]
2032 MESSAGE Cannot use WITH AUTOCOMMIT if rule enabled.
(DBERR 2032)
CAUSE WITH AUTOCOMMIT was used incorrectly.
ACTION See the DELETE or VALIDATE statement in the "SQL
Statements" chapter of the ALLBASE/SQL Reference
Manual.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2033 MESSAGE Cannot use WITH AUTOCOMMIT inside atomic
block.(DBERR 2033)
CAUSE WITH AUTOCOMMIT was used incorrectly.
ACTION See the DELETE or VALIDATE statement in the "SQL
Statements" chapter of the ALLBASE/SQL Reference
Manual.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2034 MESSAGE Cannot use WITH AUTOCOMMIT inside global
transaction. (DBERR 2034)
CAUSE WITH AUTOCOMMIT was used incorrectly.
ACTION See the DELETE or VALIDATE statement in the "SQL
Statements" chapter of the ALLBASE/SQL Reference
Manual.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2035 MESSAGE Cannot use WITH AUTOCOMMIT if constraints are
deferred. (DBERR 2035)
CAUSE WITH AUTOCOMMIT was used incorrectly.
ACTION See the DELETE or VALIDATE statement in the "SQL
Statements" chapter of the ALLBASE/SQL Reference
Manual.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2036 MESSAGE Cannot use WITH AUTOCOMMIT on a TurboIMAGE table.
(DBERR 2036)
CAUSE WITH AUTOCOMMIT was used incorrectly.
ACTION See the DELETE or VALIDATE statement in the "SQL
Statements" chapter of the ALLBASE/SQL Reference
Manual.
[REV END]
----------------------------------------------------------------------------
2100 MESSAGE ALLBASE/SQL not running. (DBERR 2100)
CAUSE An SQL statement was issued before a DBE session
was started.
ACTION Start a DBE session with the CONNECT or START DBE
statement, then issue the SQL statement again.
----------------------------------------------------------------------------
2101 MESSAGE ALLBASE/SQL already started. (DBERR 2101)
CAUSE A START DBE or CONNECT statement was entered after
a DBE session was already started.
ACTION No action is necessary.
----------------------------------------------------------------------------
2102 MESSAGE Command requires a transaction to be in progress.
(DBERR 2102)
CAUSE A COMMIT WORK or ROLLBACK WORK statement was issued
before a transaction was started.
ACTION No action is necessary. To begin a transaction,
issue a BEGIN WORK statement.
----------------------------------------------------------------------------
2103 MESSAGE Transaction already started. (DBERR 2103)
CAUSE You attempted to start a second transaction before
the current transaction was committed.
ACTION Issue a COMMIT WORK or ROLLBACK WORK statement to
terminate the previous transaction, then issue a
BEGIN WORK statement to start the next transaction.
----------------------------------------------------------------------------
2105 MESSAGE Specified DBEnvironment already exists. (DBERR
2105)
CAUSE You tried to create a DBEnvironment that already
exists.
ACTION Issue the START DBE NEW statement again, specifying
a unique name.
----------------------------------------------------------------------------
2106 MESSAGE Backward migration is needed - use SQLMigrate.
(DBERR 2106)
CAUSE The release of the ALLBASE/SQL software does not
match the version of the DBEnvironment.
ACTION Use the migration tool, SQLMigrate, to migrate the
DBEnvironment backward to the proper version or use
a newer release of the ALLBASE/SQL software.
----------------------------------------------------------------------------
2107 MESSAGE Forward migration is needed - use SQLMigrate.
(DBERR 2107)
CAUSE The release of the ALLBASE/SQL software does not
match the version of the DBEnvironment.
ACTION Use the migration tool, SQLMigrate, to migrate the
DBEnvironment forward to the proper version or use
an older release of the ALLBASE/SQL software.
----------------------------------------------------------------------------
2108 MESSAGE DBEnvironment corrupted during previous
migration. (DBERR 2108)
CAUSE At some prior time, a migration attempt failed
which corrupted the DBEnvironment in the process.
ACTION Restore the DBEnvironment from the backup.
----------------------------------------------------------------------------
2109 MESSAGE DBEnvironment must be recreated to use this
release of ALLBASE/SQL. (DBERR 2109)
CAUSE The release under which the DBE was created is not
supported in the current release of ALLBASE/SQL.
ACTION Recreate the DBE using the current release of
ALLBASE/SQL.
----------------------------------------------------------------------------
2200 MESSAGE DBEFileSet ! not found. (DBERR 2200)
CAUSE You tried to access a DBEFileSet that does not
exist.
ACTION Check your spelling. If you still receive this
error ask your Database Administrator to check the
SYSTEM.DBEFILESET system catalog to make sure that
the DBEFileSet exists.
----------------------------------------------------------------------------
2201 MESSAGE DBEFileSet ! already exists. (DBERR 2201)
CAUSE You tried to CREATE a DBEFileSet that already
exists.
ACTION Issue the CREATE DBEFILESET statement again,
specifying a unique name.
----------------------------------------------------------------------------
2202 MESSAGE DBEFile ! not found. (DBERR 2202)
CAUSE You tried to access a DBEFile that does not exist
in this DBEnvironment by using the ADD DBEFILE,
DROP DBEFILE, or REMOVE DBEFILE statement.
ACTION Check your spelling. Check the SYSTEM.DBEFILE view
to make sure that the specified DBEFile does exist.
----------------------------------------------------------------------------
2203 MESSAGE DBEFile ! already exists. (DBERR 2203)
CAUSE You tried to create a DBEFile that was already
created in this DBEnvironment.
ACTION Issue the command again, specifying a unique name.
----------------------------------------------------------------------------
2204 MESSAGE DBEFile ! not associated with DBEFileSet !.
(DBERR 2204)
CAUSE The DBEFile named in the command is not associated
with the DBEFileSet named in the same command.
ACTION Ask your database administrator to check the
SYSTEM.DBEFILE view to verify which DBEFileSet the
DBEFile is associated with.
----------------------------------------------------------------------------
2205 MESSAGE DBEFile ! already associated with DBEFileSet !.
(DBERR 2205)
CAUSE The ADD DBEFILE statement contained a DBEFile that
is already a member of the DBEFileSet specified.
ACTION No action is necessary.
----------------------------------------------------------------------------
2206 MESSAGE Table/View !.! not found. (DBERR 2206)
CAUSE The table or view specified in the query or command
does not exist in the DBEnvironment.
ACTION Check your spelling, owner name, and system
catalog. If you still receive this error ask your
database administrator to check the SYSTEM.TABLE or
SYSTEM.VIEW view to make sure that the specified
table does exist.
----------------------------------------------------------------------------
2207 MESSAGE Table/View !.! already exists. (DBERR 2207)
CAUSE The table or view you specified in the CREATE TABLE
or CREATE VIEW statement already exists in the
DBEnvironment.
ACTION Create the table or view with a different name
(same owner) or different owner name (same table or
view name).
----------------------------------------------------------------------------
2208 MESSAGE Column ! not found in table/view !.!. (DBERR
2208)
CAUSE The column name you specified was not found in the
specified table or view.
ACTION Check your spelling. If you still receive this
error, use the ISQL INFO command or ask your
database administrator to check SYSTEM.COLUMN to
make sure that the specified column does exist in
the table.
----------------------------------------------------------------------------
2209 MESSAGE Duplicate column !. (DBERR 2209)
CAUSE You specified a column name twice in the CREATE
TABLE or CREATE INDEX statement or you specified a
column already existing in the table in the ALTER
TABLE statement.
ACTION Issue the command again, specifying unique column
names.
----------------------------------------------------------------------------
2210 MESSAGE Ambiguous column !. (DBERR 2210)
CAUSE The column you specified in the query exists in
more than one table specified in the query.
ACTION Execute your query again, specifying the table name
as well as the column name.
----------------------------------------------------------------------------