HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
3040 MESSAGE Command rejected - DBCore was terminated. (DBERR
3040)
CAUSE Your database administrator issued a STOP DBE
statement causing your transaction to be
terminated.
ACTION Contact your database administrator to find out
when the DBEnvironment will be available.
----------------------------------------------------------------------------
3041 MESSAGE Command rejected - DBCore is terminating now.
(DBERR 3041)
CAUSE Your database administrator issued a STOP DBE
statement causing the DBEnvironment to shut down.
ACTION Contact your database administrator to find out
when the DBEnvironment will be available.
----------------------------------------------------------------------------
3042 MESSAGE Command rejected - User session was terminated.
(DBERR 3042)
CAUSE Your database administrator or another user
connected to the DBEnvironment using your login
name issued a TERMINATE USER statement for your
login name. Any active transactions for your login
name were terminated.
ACTION Contact the person who issued the TERMINATE USER
statement and reconnect to the DBEnvironment.
----------------------------------------------------------------------------
3043 MESSAGE Command rejected - User session is terminating
now. (DBERR 3043)
CAUSE Your database administrator or another user
connected to the DBEnvironment issued a TERMINATE
USER statement for your login name. Any active
transactions for your login name were terminated.
ACTION Contact the person who issued the TERMINATE USER
statement and reconnect to the DBEnvironment.
----------------------------------------------------------------------------
3047 MESSAGE Number of query sections exceeds system limit !.
(DBERR 3047)
CAUSE The number of PREPARE commands exceeded system
limit per session.
ACTION Keep the number of PREPARE commands within the
limit.
----------------------------------------------------------------------------
3050 MESSAGE File System Error - Privileged file violation.
(DBERR 3050)
[REV BEG]
CAUSE The same name for the DBEnvironmentName and the
SystemFileName was used.
ACTION Use different names for the DBEnvironmentName and
the SystemFileName.
[REV END]
----------------------------------------------------------------------------
3051 MESSAGE File System Error - Not enough space in device.
(DBERR 3051)
CAUSE There is not enough space in the device to support
your operation.
ACTION Use a different device or contact your database
administrator to add more space to the current
device.
----------------------------------------------------------------------------
3052 MESSAGE File System Error - Nonexistent account name.
(DBERR 3052)
CAUSE The account name you specified in the START DBE or
CONNECT statement does not exist or was entered
incorrectly.
ACTION Check your spelling. If you still receive this
error, contact your system administrator to make
sure that the account really exists.
----------------------------------------------------------------------------
3053 MESSAGE File System Error - Nonexistent group name.
(DBERR 3053)
CAUSE You specified a nonexistent group name in the START
DBE or CONNECT statement.
ACTION Check your spelling. If you still receive this
error, use the MPE/iX REPORT command to make sure
that the group exists in the specified account.
----------------------------------------------------------------------------
3054 MESSAGE File System Error - Nonexistent DBEFile or log
file. (DBERR 3054)
CAUSE You attempted to access a DBEFile or log file which
is missing.
ACTION Use the SQLUtil SHOWDBE command and/or SELECT
information from SYSTEM.DBEFILE to find out the
names of DBEFile0, DBELog and other DBEFiles. Make
sure they co-exist with your DBECon file.
----------------------------------------------------------------------------
3055 MESSAGE File System Error - Invalid file reference.
(DBERR 3055)
CAUSE The file name specified is not valid.
ACTION Check your spelling. Refer to the MPE/iX General
User's Reference Manual for information on file
naming conventions.
----------------------------------------------------------------------------
3056 MESSAGE File System Error - Insufficient virtual memory.
(DBERR 3056)
CAUSE System out of virtual memory.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
3057 MESSAGE File System Error - Exclusive access not
possible. (DBERR 3057)
CAUSE You attempted to access a file exclusively while
other users were accessing the specified file.
ACTION Wait until there are no other users accessing the
file.
----------------------------------------------------------------------------
3058 MESSAGE File System Error - File already being accessed
exclusively. (DBERR 3058)
CAUSE The file specified is being accessed exclusively by
another user.
ACTION Wait until the file is no longer being exclusively
accessed.
----------------------------------------------------------------------------
3059 MESSAGE File System Error - Security Violation. (DBERR
3059)
CAUSE The file mode of the DBEFile or executable program
files is incorrect.
ACTION Refer to the ALLBASE/SQL Database Administration
Guide for additional information.
----------------------------------------------------------------------------
3060 ME[REVEBEG]File System Error - File already exists.
(DBERR 3060)
CAUSE The file name specified in the CREATE DBEFILE
statement already exists.
ACTION Issue the command again, specifying a unique file
name.
[REV END]
----------------------------------------------------------------------------
3061 MESSAGE File System Error - (! !). (DBERR 3061)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume I
for an error description.
----------------------------------------------------------------------------
3062 MESSAGE Location already used for another Tempspace.
(DBERR 3062)
CAUSE The physical location you specified by the CREATE
TEMPSPACE statement is already being used for
another tempspace.
ACTION Issue the CREATE TEMPSPACE statement again with a
different physical location. Or, execute the DROP
TEMPSPACE statement to remove the original
tempspace from the physical location, and issue the
CREATE TEMPSPACE statement again.
----------------------------------------------------------------------------
3063 MESSAGE DBECon Error - Cannot use CONNECT command with
autostart off. (DBERR 3063)
CAUSE You tried to initiate a single-user session with
the CONNECT statement and the autostart flag is
OFF.
ACTION Either use the START DBE statement to initiate the
session or ask your database administrator to
change the autostart flag to ON.
----------------------------------------------------------------------------
3064 MESSAGE DBECon Error - This DBEnvironment does not have
!. (DBERR 3064)
CAUSE You tried to CONNECT to a DBEnvironment which is
not an ALLBASE/SQL DBEnvironment.
ACTION No action is necessary. You can only CONNECT to an
ALLBASE/SQL DBEnvironment.
----------------------------------------------------------------------------
3065 MESSAGE DBECon Error - User attempted NEWLOG and is not
creator of DBECon file. (DBERR 3065)
CAUSE You attempted to execute the START DBE NEWLOG
statement and you are not the creator of the
specified DBEnvironment.
ACTION Contact your database administrator to find out who
the DBECreator is and have the DBECreator issue the
appropriate command.
----------------------------------------------------------------------------
3066 MESSAGE DBECon Error - File is invalid. (DBERR 3066)
CAUSE The file specified is not a DBECon file.
ACTION Check your spelling. Issue the command again,
specifying a valid DBECon file.
----------------------------------------------------------------------------
3067 MESSAGE DBECon Error - Privileged file violation. (DBERR
3067)
CAUSE The operation attempted requires privileged
capabilities
or
the DBEnvironment name specified in the START DBE
or CONNECT statement is not a DBECon file.
ACTION Contact your database administrator to get the
required capability or log on as a user who does
have the required capability.
----------------------------------------------------------------------------
3068 MESSAGE DBECon Error - Not enough space in device.
(DBERR 3068)
CAUSE There is not enough space in the device to support
your operation.
ACTION Use a different device or contact your database
administrator to add more space to the current
device.
----------------------------------------------------------------------------
3069 MESSAGE DBECon Error - Nonexistent account name. (DBERR
3069)
CAUSE You specified a nonexistent account name in the
CONNECT statement.
ACTION Check your spelling. If you still receive this
error, contact your database administrator to make
sure that the account really exists.
----------------------------------------------------------------------------
3070 MESSAGE DBECon Error - Nonexistent group name. (DBERR
3070)
CAUSE You specified a nonexistent group name in the
CONNECT statement.
ACTION Check your spelling. If you still receive this
error, use the MPE/iX REPORT command to make sure
that the group exists in the specified account.
----------------------------------------------------------------------------
3071 MESSAGE DBEcon Error - Nonexistent file name. (DBERR
3071)
CAUSE This message may be the first of two messages
received. HP ALLBASE/SQL attempted a remote
connection but was unsuccessful. If the remote
DBEnvironment does not exist, this error is
returned by itself.
ACTION If your START DBE or CONNECT statement is for a
DBEnvironment on the local node, check your
spelling. If you still receive this error, use the
MPE/iX LISTF command to make sure that the file
really exists in your group and account. If your
CONNECT statement is for a remote DBEnvironment,
read about the action to be taken in the second
message.
----------------------------------------------------------------------------
3072 MESSAGE DBECon Error - Invalid file reference. (DBERR
3072)
CAUSE The file name specified is not valid.
ACTION Check your spelling. Refer to the MPE/iX General
User's Reference Manual for information on file
naming conventions.
----------------------------------------------------------------------------
3073 MESSAGE DBECon Error - Insufficient virtual memory.
(DBERR 3073)
CAUSE System out of virtual memory.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
3074 MESSAGE DBECon Error - Exclusive access not possible.
(DBERR 3074)
CAUSE You attempted to access a file exclusively while
other users were accessing the specified file.
ACTION Wait until there are no other users accessing the
file and issue the command again.
----------------------------------------------------------------------------