HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
2449 MESSAGE TRANSFER OWNERSHIP OF MODULE is not supported.
(DBERR 2449)
CAUSE You specified the MODULE option of the TRANSFER
OWNERSHIP statement. However, the ownership of
modules cannot be transferred.
ACTION DROP the existing modules and preprocess the
program with the -o option.
----------------------------------------------------------------------------
2450 MESSAGE BEGIN WORK MULTI is not supported. (DBERR 2450)
CAUSE You attempted to use the MULTI option for the BEGIN
WORK statement.
ACTION You can have only one active transaction at a time.
Issue a COMMIT WORK or ROLLBACK WORK statement
before beginning the second transaction.
----------------------------------------------------------------------------
2452 MESSAGE Clustering index not allowed on table on which
hash structure has already been defined. (DBERR
2452)
CAUSE You tried to create a clustering B-tree index on a
table on which a hash structure already existed.
ACTION Issue the CREATE INDEX statement again, omitting
the CLUSTERING option
or
UNLOAD the data from the table. DROP the table.
ReCREATE the table, omitting the HASH option.
Issue the CREATE INDEX statement again to create a
clustering B-tree index. LOAD the data.
----------------------------------------------------------------------------
2453 MESSAGE Non-unique hash is not supported. (DBERR 2453)
CAUSE You tried to create a table with a non-unique hash
structure.
ACTION Issue the CREATE TABLE statement again, including
the UNIQUE keyword with the HASH option.
----------------------------------------------------------------------------
2454 MESSAGE Operation not allowed on non-SQL table. (DBERR
2454)
CAUSE You attempted an operation on a TurboIMAGE table.
ACTION TurboIMAGE tables are read-only through
ALLBASE/SQL.
----------------------------------------------------------------------------
2500 MESSAGE Cannot drop a non-empty DBEFileSet. (DBERR 2500)
CAUSE You attempted to DROP a DBEFileSet which has
DBEFiles associated with it.
ACTION Before dropping the DBEFileSet, drop the DBEFiles
then remove them. Remember that the DBEFiles must
be empty before they can be dropped.
----------------------------------------------------------------------------
2501 MESSAGE DBEFileSet has no DBEFiles. (DBERR 2501)
CAUSE You created a table in an empty DBEFileSet and then
tried to INSERT into that table.
ACTION ADD a DBEFile to the DBEFileSet before attempting
an INSERT statement.
----------------------------------------------------------------------------
2502 MESSAGE ! space exhausted in DBEFileSet !. (DBERR 2502)
CAUSE This message can have several meanings as follows:
1. All the space is exhausted in a DBEFileset
if no expandable DBEFiles are available.
2. All fixed-length DBEFiles in the DBEFileSet
have run out of space, and all expandable
DBEFiles have been fully expanded.
The first parameter is the setting for the
DBEFile's TYPE attribute. Valid settings are
INDEX, TABLE, and MIXED.
ACTION Add new DBEFiles of the appropriate type to the
DBEFileSet. If space has been exhausted in the
System.DBEFileSet during a query, try adding more
tempspace and more contiguous physical disk space.
----------------------------------------------------------------------------
2503 MESSAGE DBEFile not empty. (DBERR 2503)
CAUSE You attempted to REMOVE a non-empty DBEFile from
its DBEFileSet.
ACTION The DBEFile must be empty before it can be removed
from the DBEFileSet.
----------------------------------------------------------------------------
2505 MESSAGE DBEFile size must be between ! and ! pages.
(DBERR 2505)
CAUSE The file size you specified in the CREATE DBEFILE
statement was not within the valid range.
ACTION Issue the CREATE DBEFILE statement again,
specifying a valid file size.
----------------------------------------------------------------------------
2506 MESSAGE TempSpace file size limit must be between ! and !
pages. (DBERR 2506)
CAUSE The file size you specified in the CREATE TEMPSPACE
statement was not within the valid range.
ACTION Issue the CREATE TEMPSPACE statement again,
specifying a valid file size.
----------------------------------------------------------------------------
2507 MESSAGE DBEFile must be empty or new type must be mixed.
(DBERR 2507)
CAUSE You attempted to ALTER a non-empty DBEFile to a
type other than mixed.
ACTION The type of a non-empty DBEFile can be changed from
TABLE or INDEX to MIXED. No other changes are
allowed.
----------------------------------------------------------------------------
2508 MESSAGE DBEFileSet has no DBEFile of required DBEFile
type. (DBERR 2508)
CAUSE You tried to insert rows into a table whose
DBEFileSet has only INDEX DBEFiles
or
you tried to create an index on a non-empty table
whose DBEFileSet contains only DATA DBEFiles.
ACTION Ask your database administrator to CREATE and ADD
the appropriate DBEFiles.
----------------------------------------------------------------------------
2509 MESSAGE Index uniqueness or UNIQUE/PRIMARY KEY constraint
violated. (DBERR 2509)
CAUSE You tried to insert a duplicate key value into a
column used in a unique index or a unique
constraint.
ACTION Issue the INSERT or UPDATE statement again without
the duplicate row.
----------------------------------------------------------------------------
2510 MESSAGE Table is read only. (DBERR 2510)
CAUSE You tried a LOCK or WRITE operation (DROP, DELETE,
INSERT, LOCK TABLE, UPDATE, UPDATE STATISTICS) on a
read only table.
ACTION No action is necessary. These operations cannot be
performed on SYSTEM.CALL, SYSTEM.ACCOUNT,
SYSTEM.USER, SYSTEM.COUNTER, or SYSTEM.TRANSACTION.
----------------------------------------------------------------------------
2511 MESSAGE User ! does not exist. (DBERR 2511)
CAUSE The DBEUserId you specified in the TERMINATE USER
or RESET SYSTEM.ACCOUNT command is not currently
connected to the DBEnvironment.
ACTION Issue the command again, specifying a valid userid.
----------------------------------------------------------------------------
2512 MESSAGE Session ID ! does not exist. (DBERR 2512)
CAUSE You attempted to terminate a session ID that does
not exist, or you do not have the authority to
terminate it.
ACTION Check that a valid session ID was used. If the
session ID is valid, have your DBA issue the
statement.
----------------------------------------------------------------------------
2513 MESSAGE Number of primary pages must be between ! and !.
(DBERR 2513)
CAUSE You specified a number of primary pages for the
hash in the CREATE TABLE statement which was not
within the valid range.
ACTION Issue the CREATE TABLE statement again, specifying
a valid number of primary pages.
----------------------------------------------------------------------------
2514 MESSAGE Hash key uniqueness or UNIQUE/PRIMARY KEY
constraint violated. (DBERR 2514)
CAUSE You tried to insert a duplicate key value into a
column used in a unique hash structure, which might
be supporting a unique constraint.
ACTION Issue the INSERT statement again without the
duplicate row.
----------------------------------------------------------------------------
2515 MESSAGE DBEFile is currently associated with a
DBEFileSet. (DBERR 2515)
CAUSE You tried to DROP a DBEFile which was associated
with a DBEFileSet
or
you tried to ADD a DBEFile to a DBEFileSet which
already is associated with another DBEFileSet.
ACTION You must REMOVE the DBEFile from the DBEFileSet
before it can be dropped
or
you must REMOVE the DBEFile from the DBEFileSet
with which it is currently associated before you
can ADD it to a different DBEFileSet.
----------------------------------------------------------------------------
2516 MESSAGE This table already has a clustering index.
(DBERR 2516)
CAUSE When you use the CREATE INDEX statement, no more
than one index per table can have the clustering
attribute.
ACTION Drop the existing clustering index or create the
new index without the clustering attribute.
----------------------------------------------------------------------------
2518 MESSAGE DBEFile in use for hash. (DBERR 2518)
CAUSE You tried to DROP or ALTER a DBEFile that is
allocated for hash table data.
ACTION First DROP the hash table. Then, the DBEFile may
be DROPped or ALTERed.
----------------------------------------------------------------------------
2519 MESSAGE Exceeded maximum number of DBEFiles for hash
space (!). (DBERR 2519)
CAUSE The DBEFileSet specified for the hash table does
not contain DBEFiles large enough that the primary
pages for the hash table can be allocated using 16
or fewer DBEFiles.
ACTION Create additional DBEFiles large enough that the
primary pages for the hash table can be allocated
using 16 or fewer DBEFiles.
----------------------------------------------------------------------------
2520 MESSAGE Not enough space in DBEFileset for hash primary
pages. (DBERR 2520)
CAUSE There is not enough space in the empty table or
mixed DBEFiles in the DBEFileSet specified for the
number of primary pages specified.
ACTION Create additional DBEFile(s) with enough space for
the primary pages, and add them to the specified
DBEFileSet. If you create the files in the same
transaction as you create the table with the hash
structure, you can ensure that no other transaction
will be able to use the files.
----------------------------------------------------------------------------
2521 MESSAGE Maximum size for DBEFile expansion exceeds !
pages. (DBERR 2521)
CAUSE The maximum size that a DBEFile can be expanded, as
specified in the MAXPAGES clause, exceeds the
DBEFile maximum limit. The maximum size may not be
exactly the same size specified with MAXPAGES,
because it could be a rounded number.
ACTION Make sure the maximum DBEFile size specified is
within the system limit.
----------------------------------------------------------------------------
2522 MESSAGE DBEFile INCREMENT size must be between ! and !
pages. (DBERR 2522)
CAUSE The size you specified in the INCREMENT clause for
DBEFile expansion is not within the range.
ACTION Specify a valid INCREMENT size for the
corresponding DBEFile.
----------------------------------------------------------------------------
2523 MESSAGE Maximum size ! pages for DBEFile expansion is
less than the initial size ! pages. (DBERR 2523)
CAUSE The maximum size that a DBEFile can be expanded, as
specified in the MAXPAGES clause, is less than the
initial DBEFile size specified in the WITH PAGES
clause. The maximum size may not be exactly the
same size specified with MAXPAGES, because it could
be a rounded number.
ACTION Make sure the maximum DBEFile size specified is at
least equal to the initial DBEFile size, and that
it is a multiple of the INCREMENT size. If dynamic
DBEFile expansion is required, the maximum size
must be greater than the initial size.
----------------------------------------------------------------------------
[REV BEG]
2524 MESSAGE Connection ID ! does not exist. (DBERR 2524)
CAUSE The Connection ID specified does not exist.
ACTION Use a valid Connection ID.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2525 MESSAGE Transaction ID ! does not exist. (DBERR 2525)
CAUSE The Transaction ID specified does not exist.
ACTION Use a valid Transaction ID.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2526 MESSAGE Attempting to terminate current query. (DBERR
2526)
CAUSE The current query is being terminated.
ACTION Take appropriate action for this query.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2527 MESSAGE There is no transaction for Connection ID !.
(DBERR 2527)
CAUSE There was an attempt to terminate a transaction for
the specified Connection ID, but no transaction was
in progress.
ACTION No action is required.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2528 MESSAGE Attempting to terminate persistent transaction.
(DBERR 2528)
CAUSE There is an attempt to terminate a persistent
transaction.
ACTION The SQLUtil command cannot be used to terminate a
persistent transaction.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2529 MESSAGE The user termination level does not allow this
type of termination. (DBERR 2529)
CAUSE The user attempted to perform an unauthorized
termination.
ACTION A user can terminate a transaction or query if the
user is the owner or the user has DBA authority.
No action required.
[REV END]
----------------------------------------------------------------------------