HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
3075 MESSAGE DBECon Error - File already being accessed
exclusively. (DBERR 3075)
CAUSE The file specified is being accessed exclusively by
another user.
ACTION Wait until the file is no longer being accessed
exclusively and issue your command again.
----------------------------------------------------------------------------
[REV BEG]
3076 MESSAGE DBECon Error - Security Violation. (DBERR 3076)
CAUSE The file mode of the DBECon file is incorrect.
ACTION Refer to the ALLBASE/SQL Database Administration
Guide for additional information.
[REV END]
----------------------------------------------------------------------------
3077 MESSAGE DBECon Error - File already exists. (DBERR 3077)
CAUSE The file name you specified already exists.
ACTION Issue the command again, specifying a unique file
name.
----------------------------------------------------------------------------
3078 MESSAGE DBECon Error - (! !). (DBERR 3078)
CAUSE An MPE/iX file system error occurred on the DBECon
file.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
3079 MESSAGE DBECon error - Permission denied. (DBERR 3079)
CAUSE The DBECon file is inaccessible because the
security access of the DBECon file has been
changed.
ACTION Correct the security access of the DBECon file.
----------------------------------------------------------------------------
3080 MESSAGE DBECon error - Attempted a MULTI user session on
a SINGLE user DBEnvironment. (DBERR 3080)
CAUSE You tried to initiate a multi-user session on a
single user DBEnvironment
or
your database administrator has started the
DBEnvironment in single-user mode in order to make
changes through SQLUtil.
ACTION Ask your database administrator to change the
DBECon file user mode to MULTI
or
ask your database administrator to notify you when
the DBEnvironment is again accessible in multi-user
mode.
----------------------------------------------------------------------------
3088 ME[REVEBEG]MOVEFILE cannot be used to move DBECon.
(DBERR 3088)
CAUSE You tried to move the DBECon file using the
MOVEFILE statement.
ACTION The DBECon file stores the start up parameters for
the DBEnvironment defined by the START DBE NEW
statement and must remain in the same location as
the DBEnvironment.
[REV END]
----------------------------------------------------------------------------
3100 MESSAGE COMMIT ARCHIVE attempt was not preceded by a
successful BEGIN ARCHIVE. (DBERR 3100)
CAUSE Some user has already got a BEGIN ARCHIVE in
progress, and some other user attempts to COMMIT
ARCHIVE. This is illegal.
ACTION Refrain from performing a COMMIT ARCHIVE if you
were not the one to have a BEGIN ARCHIVE in the
first place.
----------------------------------------------------------------------------
3101 MESSAGE START DBE NEWLOG disallowed. Need rollforward
recovery. (DBERR 3101)
CAUSE You are most probably trying a START DBE NEWLOG on
a DBEnvironment that has incomplete transactions in
its log. The only operations permitted are START
DBE or CONNECT (if AutoStart is enabled); either of
these will roll back incomplete transactions and
force completed transactions to disk.
ACTION First, issue a START DBE statement or a CONNECT (if
AutoStart is enabled). Next, stop the
DBEnvironment. Finally, attempt the START DBE
NEWLOG again.
----------------------------------------------------------------------------
3102 MESSAGE START DBE disallowed. Need rollforward recovery.
(DBERR 3102)
CAUSE The DBEnvironment is still in a fuzzy state.
Either you are attempting a START DBE or START DBE
NEWLOG on a restored version of an online backup of
the DBEnvironment, OR you have performed some but
not all the necessary rollforward recovery on this
DBEnvironment.
ACTION Check the previous rollforward steps if any.
Perform as many RECOVERLOG steps with as many logs
as necessary to reach the matching COMMIT ARCHIVE
point in the log file.
----------------------------------------------------------------------------
3103 MESSAGE There are no more logs to switch to. (DBERR 3103)
CAUSE This is different from a log full condition.
Essentially, if the user attempts to overwrite an
archive checkpoint, DBCore will first try to switch
to the next log. If this operation fails, the
above error is generated.
ACTION Check to see if indeed an attempt was made to
overwrite an existing archive checkpoint. If the
need is genuine, use the ADDLOG command in SQLUtil
to add one or more new logs.
----------------------------------------------------------------------------
3104 MESSAGE Attempt to create a file in an account other than
the DBCon's. (DBERR 3104)
CAUSE You issued a START DBE NEW or START DBE NEWLOG
statement with a DBEfile or log file in an account
other than the DBECon file's account.
ACTION Check that all files specified in the statement are
in the same account as the DBECon file and reissue
the statement.
----------------------------------------------------------------------------
3105 MESSAGE Syntax error in file name. (DBERR 3105)
CAUSE You issued a START DBE or START DBE NEWLOG
statement containing an invalid file name.
ACTION Reissue the statement, specifying a valid file
name.
----------------------------------------------------------------------------
3106 MESSAGE START DBE disallowed: DBEnvironment points to a
wrong log file. (DBERR 3106)
CAUSE You did not follow your static restore of a
DBEnvironment with the NEWLOG command.
ACTION Restore DBEnvironment again and perform a NEWLOG
command.
----------------------------------------------------------------------------
3200 MESSAGE Invalid LONG column I/O syntax. (DBERR 3200)
CAUSE You specified a long column input or output target
which is not correct.
ACTION Check the > or < I/O redirection syntax.
----------------------------------------------------------------------------
3201 MESSAGE Invalid LONG column file name. (DBERR 3201)
CAUSE The file name is incorrect.
ACTION Refer to the MPE/iX General User's Reference Manual
for information on file naming conventions.
----------------------------------------------------------------------------
3202 MESSAGE Invalid LONG column heap space. (DBERR 3202)
CAUSE The heap space address is not correctly specified.
ACTION Check that the heap space address is the same as
returned in the program to obtain it.
----------------------------------------------------------------------------
3203 MESSAGE Missing LONG column heap space length. (DBERR
3203)
CAUSE The length for heap address is not specified.
ACTION Specify the length of the heap address.
The syntax for the heap address is
>%HeapAdressValue:LengthOfHeap.
----------------------------------------------------------------------------
3205 MESSAGE LONG column file access error in module !(!),
status code !. (DBERR 3205)
CAUSE There is a problem with the file used as the input
or output device in a LONG column operation.
Either the file does not exist, cannot be read, or
cannot be written to.
ACTION Ensure that the file exists and has the appropriate
security access.
----------------------------------------------------------------------------
3206 MESSAGE LONG column file already exists. (DBERR 3206)
CAUSE The output file exists but the OVERWRITE option was
not specified.
ACTION Remove the file or add the OVERWRITE option.
----------------------------------------------------------------------------
3208 MESSAGE LONG columns exceed maximum 40 columns. (DBERR
3208)
CAUSE You entered more than 40 LONG columns.
ACTION Reduce the number of LONG columns.
----------------------------------------------------------------------------
3209 MESSAGE LONG column heap attachment failed. (DBERR 3209)
CAUSE The heap space address cannot be attached. The
heap space address may be missing or is incorrect.
ACTION Verify that you are using the correct heap space
address.
----------------------------------------------------------------------------
3210 MESSAGE Negative length value not allowed for LONG column
INSERT. (DBERR 3210)
CAUSE You specified a negative value for the length of
the long value to be read from the heap.
ACTION Remove the unary minus sign from the length
specification and reissue the statement.
----------------------------------------------------------------------------
3211 MESSAGE Length specified is greater than allowed. (DBERR
3211)
CAUSE The length of the long value to be read from the
heap is too large.
ACTION Specify a shorter length for the heap and reissue
the statement.
----------------------------------------------------------------------------
3220 MESSAGE LONG column disallowed from remote access.
(DBERR 3220)
CAUSE You tried to access a long column on another
machine.
ACTION This feature is not supported yet.
----------------------------------------------------------------------------
3221 MESSAGE LONG column disallowed on ORDER
BY/DISTINCT/UNION. (DBERR 3221)
CAUSE You tried to use an ORDER BY, DISTINCT or UNION on
a column defined as a long data type.
ACTION Remove the long column from ORDER BY, DISTINCT or
UNION clause.
----------------------------------------------------------------------------
3222 MESSAGE LONG column disallowed on GROUP BY. (DBERR 3222)
CAUSE You tried to use the GROUP BY clause with a column
defined as a long data type.
ACTION Remove the long column from the GROUP BY clause.
----------------------------------------------------------------------------
3223 MESSAGE LONG column disallowed on Expression. (DBERR
3223)
CAUSE You tried to use an expression with a column that
has been defined as a long data type.
ACTION Remove the long column from the expression.
----------------------------------------------------------------------------
3224 MESSAGE LONG column disallowed on INDEX. (DBERR 3224)
CAUSE You tried to create an index on a column defined as
a long data type.
ACTION Remove the long column from the column list in the
CREATE INDEX statement.
----------------------------------------------------------------------------
3225 MESSAGE LONG column disallowed on HASH. (DBERR 3225)
CAUSE You tried to specify a hash structure on a column
that has been defined as a long data type.
ACTION Remove the UNIQUE HASH clause from the CREATE TABLE
syntax, or the long column from the UNIQUE HASH
clause.
----------------------------------------------------------------------------
3226 MESSAGE LONG column disallowed on INSERT from SELECT.
(DBERR 3226)
CAUSE You tried to insert a column defined as a long data
type in a type II INSERT statement.
ACTION Remove the long column from the SELECT clause in
the INSERT statement.
----------------------------------------------------------------------------
3227 MESSAGE Long fields cannot be replicated. (DBERR 3227)
[REV BEG]
CAUSE You attempted to replicate a long data type field.
ACTION Remove the long column from the replicate
statement.
[REV END]
----------------------------------------------------------------------------