ALLBASE/SQL Error Messages (Continued) [ ALLBASE/SQL Message Manual ] MPE/iX 5.5 Documentation
ALLBASE/SQL Message Manual
ALLBASE/SQL Error Messages (Continued)
4009 MESSAGE ALLBASE/SQL shared memory allocation failed in
DBCore. (DBERR 4009)
CAUSE ALLBASE/SQL ran out of run-time control block
space. Your transaction was rolled back.
ACTION In multi-user mode, try your query again later
or
issue the ALTDBE command in SQLUtil to increase the
number of control block pages
or
use LOCK TABLE so that individual pages are not
locked
or
you may be able to use BEGIN WORK CS or BEGIN WORK
RU to prevent this error.
----------------------------------------------------------------------------
4010 MESSAGE ALLBASE/SQL lock limit for session exceeded.
(DBERR 4010)
CAUSE The total number of locks currently in place for
your user session is at the limit specified in the
HPSQLDEBUG JCW.
ACTION Either delete the JCW or else set it to a higher
value.
----------------------------------------------------------------------------
4012 MESSAGE ALLBASE/SQL pseudocode error. (DBERR 4012)
CAUSE Internal error. ALLBASE/SQL opcode is invalid.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
4013 MESSAGE ALLBASE/SQL tmp buffer overflow at !. Query
aborted. (DBERR 4013)
CAUSE A temporary, internal SQL buffer overflowed.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
4050 MESSAGE ALLBASE/SQL internal error at !(!) (Node ! out of
context). (DBERR 4050)
CAUSE Internal error. The node in question is not a
valid one in current context.
ACTION If you have performed a backward migration, the
view or stored section that you are accessing needs
to be dropped and recreated under the current
release. If you continue to see this message,
record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
4051 MESSAGE ALLBASE/SQL internal error at ! (! ). (DBERR
4051)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
4053 MESSAGE ALLBASE/SQL internal error (! !). (DBERR 4053)
CAUSE Internal error, possibly caused by the incorrect
handling of installed sections after database
migration.
ACTION Re-preprocess the application and install the new
module into the migrated database.
----------------------------------------------------------------------------
4054 MESSAGE ALLBASE/SQL internal error (! !). (DBERR 4054)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
4059 MESSAGE ALLBASE/SQL internal error (!,!,!,!,!). (DBERR
4059)
CAUSE Internal error.
ACTION Record the file system error code returned and as
much information as possible. Contact your HP
Service Representative or Response Center.
----------------------------------------------------------------------------
4111 MESSAGE Cannot get ALLBASE/SQL system pointer. (DBERR
4111)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
4112 MESSAGE Cannot set ALLBASE/SQL system pointer. (DBERR
4112)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
4116 MESSAGE ALLBASE/SQL internal error in Multiple Connect
processing. (DBERR 4116)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP service representative or Response Center.
----------------------------------------------------------------------------
4117 MESSAGE Number of multiple CONNECTs exceeds the maximum
limit, 32. (DBERR 4117)
CAUSE You have attempted to issue a CONNECT statement
when you already have 32 connections.
ACTION DISCONNECT at least one of your existing
connections and reissue the CONNECT statement.
----------------------------------------------------------------------------
4118 MESSAGE Invalid JRB version is found. (DBERR 4118)
CAUSE The application being run is linked to a newer
version of ALLBASE than what is currently installed
on your system.
ACTION The application needs to be relinked with the
current version which is currently installed on
your system, or a version of ALLBASE consistent
with the application needs to be installed on your
system. Contact your system administrator.
----------------------------------------------------------------------------
4150 MESSAGE ALLBASE/SQL already started. (! !) (DBERR 4150)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
4200 MESSAGE ALLBASE/SQL alignment error on column ! in buffer
!. (DBERR 4200)
CAUSE The formatting information on host variables was
generated incorrectly.
ACTION Check the format node information in your
application program. If the problem was not caused
by a programming error, record as much information
as possible and contact your HP Service
Representative or Response Center.
----------------------------------------------------------------------------
[REV BEG]
4201 MESSAGE Too many temporary files open. Use CREATE
TEMPSPACE for larger files. (DBERR 4201)
CAUSE You have exceeded the allowance for temporary
files.
ACTION Use CREATE TEMPSPACE to accommodate larger files.
[REV END]
----------------------------------------------------------------------------
4250 MESSAGE Failed to start monitor process. (DBERR 4250)
CAUSE DBCore MONITOR did not start in multi-user
environment.
ACTION Check that you have DBMON.PUB.SYS. If not, contact
your HP service representative or Response Center.
If it does exist, try again.
----------------------------------------------------------------------------
8101 MESSAGE Unrecognized command. (DBERR 8101)
CAUSE The command name you entered does not exist or was
entered incorrectly.
ACTION Use the SQLUtil HELP command or refer to the
ALLBASE/SQL Database Administration Guide to obtain
a list and description of valid SQLUtil commands.
----------------------------------------------------------------------------
8102 MESSAGE Command not yet implemented. (DBERR 8102)
CAUSE The command name you entered does not exist or was
entered incorrectly.
ACTION Use the SQLUtil HELP command or refer to the
ALLBASE/SQL Database Administration Guide to obtain
a list and description of valid SQLUtil commands.
----------------------------------------------------------------------------
8103 MESSAGE File '!' not found. (DBERR 8103)
CAUSE The file name specified in the MOVEFILE or
PURGEFILE command was entered incorrectly or does
not exist.
ACTION Check your spelling. Use the MPE/iX LISTF command
to verify the existence of the specified file.
----------------------------------------------------------------------------
8111 MESSAGE Re-typed maintenance word doesn't match.
Maintenance word not changed. (DBERR 8111)
CAUSE The maintenance word was not changed because
SQLUtil was unsure what the new maintenance word
should be.
ACTION Issue the SETDBEMAINT command.
----------------------------------------------------------------------------
8115 MESSAGE Value must be in the range !..!. (DBERR 8115)
CAUSE The value specified for one or more parameters of
the ALTDBE is invalid.
ACTION Issue the ALTDBE command again, specifying valid
numbers for following parameters: Number of
Runtime Control Block Pages should be 17 to 128
pages; Number of Data Buffer Pages should be a
minimum of 15; Number of Log Buffer Pages should be
24 to 120 pages; and Max. Transactions should be 2
to 240 transactions.
----------------------------------------------------------------------------
8116 MESSAGE Bad numeric input. (DBERR 8116)
CAUSE You entered non-numeric input where numeric input
was expected.
ACTION Issue the ALTDBE command again, specifying valid
numbers.
----------------------------------------------------------------------------
8118 MESSAGE Cannot open file. (! !). (DBERR 8118)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
8131 MESSAGE File '!' is not a DBEFile. (DBERR 8131)
CAUSE The specified file is not a DBEFile.
ACTION Issue the command again, specifying a valid
DBEFile.
----------------------------------------------------------------------------
8132 MESSAGE File '!' not accessible. (! !). (DBERR 8132)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
8133 MESSAGE Internal error occurred. (! !). (DBERR 8133)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
8160 MESSAGE Failed to purge the ATCINFO file. (DBERR 8160)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
8201 MESSAGE Open failed on DBECon file. (! !). (DBERR 8201)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
8202 MESSAGE Close failed on DBECon file. (! !). (DBERR
8202)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
8203 MESSAGE Read failed on DBECon file. (! !). (DBERR 8203)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
8204 MESSAGE Write failed on DBECon file. (! !). (DBERR
8204)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
8205 MESSAGE STORE failed. (! !). (DBERR 8205)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
8206 MESSAGE RESTORE failed. (! !). (DBERR 8206)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
MPE/iX 5.5 Documentation