HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
10031 MESSAGE Number of PARMS formats did not match the SQL
command. (DBERR 10031)
CAUSE The PARMS.PARMBUF_FMT is passed when not needed, or
is not passed when needed, or does not match the
number of input host variables.
ACTION Correct the PARMS.PARMBUF_FMT parameter.
----------------------------------------------------------------------------
10032 MESSAGE Number of DATABUF formats did not match the SQL
command. (DBERR 10032)
CAUSE The DATABUF.BUFFER_FMT is passed when not needed,
or is not passed when needed, or does not match the
number of input host variables.
ACTION Correct the DATABUF.BUFFER_FMT parameter.
----------------------------------------------------------------------------
10033 MESSAGE No input host variables specified for BULK
INSERT. (DBERR 10033)
CAUSE You have not specified input host variables for a
BULK INSERT statement.
ACTION Specify input host variables in the BULK INSERT
statement.
----------------------------------------------------------------------------
10034 MESSAGE No output host variables specified for FETCH or
SELECT. (DBERR 10034)
CAUSE You have not specified output host variables for
FETCH or SELECT statements.
ACTION Specify output host variables in the FETCH or
SELECT statements.
----------------------------------------------------------------------------
10035 MESSAGE The SQL statement is unknown. (DBERR 10035)
CAUSE The SQL statement you specified cannot be processed
by the SQLX interface.
ACTION Specify a valid SQL statement.
----------------------------------------------------------------------------
10036 MESSAGE The specified connection name is already in use.
(DBERR 10036)
CAUSE You have specified a connection name that is
already used by another CONNECT.
ACTION Specify a unique connection name.
----------------------------------------------------------------------------
10037 MESSAGE The specified connection name is not open.
(DBERR 10037)
CAUSE You specified a connection name that is not
associated with a CONNECT.
ACTION Specify a valid connection name.
----------------------------------------------------------------------------
10038 MESSAGE Invalid number of columns in
PARMCB.COLUMNS.NUM_COLUMNS. (DBERR 10038)
CAUSE The number of columns you specified in
PARMCB.COLUMNS.NUM_COLUMNS is less than 0 or
greater than 255.
ACTION Correct the value of PARMCB.COLUMNS.NUM_COLUMNS.
----------------------------------------------------------------------------
10039 MESSAGE Invalid number of formats specified. (DBERR
10039)
CAUSE The number of format elements you specified is
either less than or equal to 0, or greater than
1024.
ACTION Specify the correct number of format elements.
----------------------------------------------------------------------------
[REV BEG]
10040 MESSAGE No more WSL records to transmit. (DBERR 10040)
CAUSE A Transmit_Log reader has encountered the end of
log. No more log records can be transmitted beyond
this point until some more get written.
ACTION Wait for a certain period and then retry.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10041 MESSAGE Invalid MODE specified. (DBERR 10041)
CAUSE The mode specified is invalid. Each intrinsic has
a specified set of valid modes.
ACTION Check the specified mode.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10042 MESSAGE Invalid FLAG specified. (DBERR 10042)
CAUSE The flag specified in the arglist is invalid. Each
intrinsic has a specified set of valid flags.
ACTION Check the specified flag.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10043 MESSAGE Invalid log scan id passed. (DBERR 10043)
CAUSE This error can be seen by either Transmit_Log or
Close_Log_Scan when the scan_id specified in the
arglist does not match that of a valid log scan
currently open by this process.
ACTION Check the scan_id specified in the arglist against
the scan_ids previously returned by Open_Log_Scan.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10044 MESSAGE Invalid log buffer size. (DBERR 10044)
CAUSE The buffer_size specified in the arglist is not
large enough to contain even the smallest WSL
record. This error can be encountered by
Transmit_Log and Apply_Log.
ACTION Check the buffer_size field in the arglist to
determine if it has been properly initialized. If
it has been, then a larger buffer should be defined
since it is too small to receive any WSL records.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10045 MESSAGE Invalid value of used log buffer space. (DBERR
10045)
CAUSE Apply_Log has determined that the size_used
specified in the arglist is invalid. This
indicates that either the size_used is smaller than
the smallest WSL record possible, or that the
size_used is greater than the number of bytes
reserved in the log buffer (as indicated by the
buffer_size field in the arglist).
ACTION Check that the size_used is less than or equal to
the buffer_size field in the arglist. The
size_used being passed to Apply_Log should also be
checked against the value that was returned by
Transmit_Log.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10046 MESSAGE Invalid buffer offset passed. (DBERR 10046)
CAUSE Apply_Log has determined that the buffer_offset
field specified in the arglist does not point to a
valid position in the log buffer. This will occur
if the buffer_offset contains a negative value, or
a number greater than the size_used field specified
in the arglist.
ACTION Check the application.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10047 MESSAGE A WSL record in the log buffer has an invalid
record length specified. (DBERR 10047)
CAUSE The Apply_Log intrinsic attempts consistency
checking on the lengths of records encountered in
the log buffer. If the current position in the
buffer plus the length of the next log record takes
it beyond the end of the used buffer space,
Apply_Log will generate this error. On BEGIN WORK,
if the op code of the next log record allows
predetermining its correct length, the specified
record length is checked against this value.
ACTION Check the parameters set up by the application.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10048 MESSAGE A BEGIN WORK WSL record encountered out of
sequence. (DBERR 10048)
CAUSE This error is generated when Apply_Log encounters
the BEGIN WORK WSL record for a new transaction
while a previous Apply_Log transaction is still in
progress. A possible cause is if an application
started applying transaction T1 (which spanned
multiple log buffers) and tried to apply
transaction T2 before applying the COMMIT WORK WSL
record for T1. This error is most likely
encountered when a single Apply-Log server process
is applying transactions received from multiple
open scans. Another possible cause is if a
transmission error occurred and the end of the
transaction (containing the COMMIT WORK WSL record)
was lost.
ACTION Check the application. If the application is
handling transactions correctly (especially ones
that span multiple log buffers) then you may try
transmitting again the transactions being applied.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10049 MESSAGE No apply WSL records transaction currently
active. (DBERR 10049)
CAUSE Apply_Log encountered a WSL record that was not a
BEGIN WORK record, and the BEGIN WORK WSL record
has not been processed for the transaction. One
cause is if the Apply_Log transaction was aborted
and the user tries to continue applying log records
without starting at the beginning of the
transaction. Another cause is if a transmission
error has occurred and the beginning of the
transaction has been lost.
ACTION Check the application to determine if transactions
are correctly reapplied (especially transactions
which span multiple log buffers). Then try to
transmit the transactions and apply them again. If
the condition persists, try closing and reopening
the log scan.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10050 MESSAGE WSL records applied did not match transaction
length. (DBERR 10050)
CAUSE Apply_Log determined that applying the WSL record
will lead to a mismatch between the number of bytes
applied for the transaction and the length of the
transaction specified in the BEGIN WORK WSL record.
For all records, except a COMMIT WORK WSL record,
this indicates that the record length plus the
number of bytes previously applied would be greater
than the transaction length specified in the BEGIN
WORK record. For COMMIT WORK records, this error
indicates that the length of the COMMIT WORK record
plus the number of bytes previously applied does
not exactly equal the required transaction length.
This is encountered if part of the transaction has
been lost (due to transmission errors, buffering
schemes, etc.).
ACTION Check the application to make sure complete
transactions are being buffered and transmitted
correctly. Then try to transmit the transactions
and apply them again. If the condition persists,
try closing and reopening the log scan.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10051 MESSAGE Invalid number of partitions specified. (DBERR
10051)
CAUSE Get_Scr or Modify_Scr encountered an invalid
num_partitions in the arglist. The acceptable
values for this field are somewhat dependent on the
procedure being called in conjunction with the mode
specified.
ACTION Check the num_partitions specified in the arglist.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10052 MESSAGE Invalid partition id encountered. (DBERR 10052)
CAUSE Get_Scr or Modify_Scr encountered an invalid
partition id passed in from the user. For Get_Scr,
the partition id in error must be in the array
pointed to be the partition_array field in the
arglist. For Modify_Scr, the partition id must be
in the SCR array for mode 1 (UPDATE SCR), or the
partition array for mode 2 (DELETE SCR). All
partition ids are required to be positive, non-zero
numbers.
ACTION Check the partition ids specified by the
application.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10053 MESSAGE Invalid number of SCR slots specified. (DBERR
10053)
CAUSE An invalid num_SCR was specified in the arglist.
In most cases, a non-positive value was specified.
In the case of Get_Scr using mode 1 (SOFT RESYNC),
this error can also be encountered if the num_SCR
value is less than the value of num_partitions.
ACTION Check the parameters specified by the application.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10054 MESSAGE Invalid specification for number of SCR slots
used. (DBERR 10054)
CAUSE The num_SCR_used field specified in the arglist is
invalid so Open_Log_Scan or Modify_Scr generates
this error. For Open_Log_Scan and Modify_SCR (mode
1 only), num_SCR_used must be within the range from
1 to num_SCR.
ACTION Check the parameters specified by the application.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10055 MESSAGE Invalid specification for maximum number of log
files.(DBERR 10055)
CAUSE An invalid number of max_logfiles for the backward
scan during Open_Log_Scan was specified. This
parameter can be either -1 (the default) or a
non-positive number.
ACTION Check the parameters specified by the application.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10056 MESSAGE Could not allocate heap space needed for
procedure. (DBERR 10056)
CAUSE Open_Log_Scan gives this error while allocating
control blocks needed for opened scans. This error
states that the routine was unable to allocate the
necessary heap space to be able to open the log
scan. If multiple scans are opened on the same
DBEnvironment, each opened scan receives a new set
of control blocks (which are allocated in the
heap), and this problem could be due to having many
scans opened (instead of combining them into one
open scan).
ACTION Determine the amount of heap space used by the
application. If an excessive amount is used, the
application should be modified to use less. If the
heap allocation has previously worked on the
system, first check the number of users on the
system, then use SQLMON to see global swap space
utilization plus heap usage for individual user
processes. If numerous scans are open on the same
DBE, the problem could be alleviated if the open
scans are combined into one open scan (and thus
only one set of scan control blocks).
[REV END]
----------------------------------------------------------------------------
10057 MESSAGE Invalid exception number. (DBERR 10057)
CAUSE You specified an invalid exception number when
requesting diagnostic information.
ACTION Specify a valid exception number.
----------------------------------------------------------------------------
10058 MESSAGE Invalid DBEnvironment or connection name length.
(DBERR 10058)
CAUSE You specified a DBEnvironment or connection name
length which is less than or equal to 0, or greater
than 128.
ACTION Specify a valid DBEnvironment or connection name.
----------------------------------------------------------------------------