ALLBASE/SQL Error Messages (Cont.) [ ALLBASE/SQL Message Manual ] MPE/iX 5.5 Documentation
ALLBASE/SQL Message Manual
ALLBASE/SQL Error Messages (Cont.)
2805 MESSAGE NLINFO error !. Language ID = !. (DBERR 2805)
CAUSE An error was returned from the NLS library routine
NLINFO, with the specified language.
ACTION Check the validity of your NLS data and reissue the
statement.
----------------------------------------------------------------------------
2806 MESSAGE Comment text cannot be NULL for LOG COMMENT.
(DBERR 2806)
CAUSE The value passed to a LOG COMMENT was NULL.
ACTION Check the value and reissue the statement with a
non-null value.
----------------------------------------------------------------------------
2807 MESSAGE Cannot drop a non-empty partition. (DBERR 2807)
CAUSE You issued a DROP PARTITION on a partition that
currently contains tables.
ACTION Remove the tables from the partition with the ALTER
TABLE SET PARTITION statement and reissue the
statement.
----------------------------------------------------------------------------
2808 MESSAGE Partition ! already exists. (DBERR 2808)
CAUSE A CREATE PARTITION attempted to create a partition
with a name of a partition that is already defined.
ACTION Reissue the CREATE PARTITION statement with another
partition name or issue a DROP PARTITION to remove
the existing partition and then reissue the CREATE
PARTITION statement.
----------------------------------------------------------------------------
2809 MESSAGE Partition ! not found. (DBERR 2809)
CAUSE The partition name you specified by a DROP
PARTITION, ALTER TABLE SET PARTITION, or CREATE
TABLE statement does not exist.
ACTION Check the partition name against the system catalog
table SYSTEM.PARTITION and reissue the CREATE TABLE
or ALTER TABLE SET PARTITION statement with the
name of an existing partition.
----------------------------------------------------------------------------
2810 MESSAGE Audit logging not set for DBE. (DBERR 2810)
CAUSE You issued an ENABLE AUDIT LOGGING statement for
the session, but audit logging is turned off for
the DBEnvironment.
ACTION Check the correctness of operations. Either audit
logging for the DBEnvironment should be turned on
(this may be done through the START DBE NEWLOG
statement) or the ENABLE AUDIT LOGGING statement is
not valid.
----------------------------------------------------------------------------
2811 MESSAGE Insufficient size specified for the new SCR.
(DBERR 2811)
CAUSE Note that it is possible to change the
MAXPARTITIONS parameter through the START DBE
NEWLOG statement. In so doing, the product
restores the current SCR slots into this new log
file (the current SCR value has an image stored in
the DBECon file). If the new MAXPARTITIONS
specified is not large enough to contain all the
occupied slots from the old SCR, this error is
generated.
ACTION Reissue the START DBE NEWLOG statement with the
appropriate MAXPARTITIONS.
----------------------------------------------------------------------------
2812 MESSAGE There are still some active transactions in the
old SCR. (DBERR 2812)
CAUSE You attempted a START DBE NEWLOG, and the old SCR
(out of the DBECon file) still contains some active
transactions. This can only happen if the database
was not shut down in a manner such that all
operations could be properly terminated.
ACTION Connect to the database and release it. This
allows ALLBASE/SQL to terminate any uncommitted
transactions. Then you can reissue the START DBE
NEWLOG statement.
----------------------------------------------------------------------------
2813 MESSAGE More than one slot found for the same partition.
(DBERR 2813)
CAUSE The partition was specified twice when opening a
log scan.
ACTION Eliminate the duplication.
----------------------------------------------------------------------------
2814 MESSAGE Open_Log_Scan failed on ALL specified partitions.
(DBERR 2814)
CAUSE Check the per partition return codes.
ACTION Use the per partition return code information to
determine your action.
----------------------------------------------------------------------------
2815 MESSAGE Hard resync record encountered in partition !.
Scan aborted. (DBERR 2815)
CAUSE The master and slave databases are inconsistent.
ACTION Resync the indicated partition.
----------------------------------------------------------------------------
2816 MESSAGE Open_Log_Scan could not reserve log for
partitions found. (DBERR 2816)
CAUSE The specified starting point for opening a log scan
has been overwritten.
ACTION Use a Wrapper DBE to recover the needed log records
or hard resync the partition.
----------------------------------------------------------------------------
2817 MESSAGE Invalid audit log record found. (DBERR 2817)
CAUSE The log record being applied in an Apply_Log was
not a valid audit log record.
ACTION The log records being applied in an Apply_Log
command must have come from an Transmit_Log from a
master instance. Check your application to make
sure that the log records from the Transmit_Log are
being passed appropriately to the Apply_Log
according to the External Specifications.
----------------------------------------------------------------------------
2818 MESSAGE Apply_Log cannot find the tuple to be
modified/deleted. (DBERR 2818)
CAUSE The master and slave databases are not
synchronized.
ACTION Perform a hard resync.
----------------------------------------------------------------------------
2819 MESSAGE Attempting to apply a log record while audit is
not enabled. (DBERR 2819)
CAUSE The architecture of Apply_Log requires audit to be
turned on at the slave (target).
ACTION Use SQLUTIL (SHOWDBE) to check the startup
parameters, and turn audit on (through a START DBE
NEWLOG) if necessary.
----------------------------------------------------------------------------
2820 MESSAGE Audit parameters not set. (DBERR 2820)
CAUSE You tried to use audit logging without setting all
of the required parameters.
ACTION Check that the AUDIT NAME, DEFAULT PARTITION, and
MAXPARTITIONS are all set in the DBEnvironment, or
set them (through a START DBE NEWLOG) if necessary.
----------------------------------------------------------------------------
2821 MESSAGE Active transactions found on partition !. (DBERR
2821)
CAUSE An attempt is being made to hard resync an active
partition.
ACTION Terminate access to the partition and redo the hard
resync.
----------------------------------------------------------------------------
2822 MESSAGE Duplicate partition instance found in SCR array.
(DBERR 2822)
CAUSE The duplicate partition instance (PID/DBID) was
found in the SCR array passed to modify SCR.
ACTION Eliminate the duplicates and try again.
----------------------------------------------------------------------------
2823 MESSAGE Open log scan failed due to missing log file
(sequence #!). (DBERR 2823)
CAUSE A log needed for the log scan being opened has been
purged.
ACTION For a resync application, perform a hard resync.
Auditing cannot be done.
----------------------------------------------------------------------------
2824 MESSAGE More than one tuple qualified for key column
search. (DBERR 2824)
CAUSE Multiple tuples found during Apply_Log with key
column search enabled.
ACTION Try the Apply_Log with key column search disabled.
----------------------------------------------------------------------------
2825 MESSAGE Timeout expired (! seconds). (DBERR 2825)
CAUSE A request for a database resource, such as a lock,
could not be granted before the user timeout was
exceeded. The current transaction was rolled back.
ACTION Retry the transaction when the requested resource
becomes available, or increase the user timeout
value.
----------------------------------------------------------------------------
2826 MESSAGE Insufficient number of transactions. (! is
required) (DBERR 2826)
CAUSE An attempt to start the DBE with the maximum
allowable transactions less than or equal to the
number of persistent transactions currently present
in the DBE.
ACTION Specify a larger number of transactions to start
the DBE.
----------------------------------------------------------------------------
2827 MESSAGE The function was invoked in an improper context.
(DBERR 2827)
CAUSE An XA function has been invoked in an invalid
context.
ACTION Correct the context and try again.
----------------------------------------------------------------------------
2828 MESSAGE Comment is disallowed. (DBERR 2828)
CAUSE An attempt was made to log a comment for a
transaction that is already persistent.
ACTION Retry the function without a comment.
----------------------------------------------------------------------------
2829 MESSAGE Blocking condition exists. (DBERR 2829)
CAUSE A transaction join was attempted with the nowait
option specified. The function would have had to
wait.
ACTION Try again later or remove the nowait option.
----------------------------------------------------------------------------
2830 MESSAGE Duplicate global transaction identifier. (DBERR
2830)
CAUSE Attempted to start a transaction with a global
identifier that already exists.
ACTION Try again with a unique GTRID.
----------------------------------------------------------------------------
2831 MESSAGE The global transaction identifier is unknown.
(DBERR 2831)
CAUSE The specified global transaction identified does
not exist in the DBE.
ACTION Check the validity of the GTRID.
----------------------------------------------------------------------------
2832 MESSAGE A transaction scan is already opened. (DBERR
2832)
CAUSE An attempt was made to open a recovery scan when
was already open. A session can have only one open
recovery scan.
ACTION Close the open scan before opening another.
----------------------------------------------------------------------------
2833 MESSAGE A transaction scan is not opened. (DBERR 2833)
CAUSE A recovery scan is required for the requested
function, but one is not open.
ACTION Open a recovery scan and try again.
----------------------------------------------------------------------------
2834 MESSAGE The transaction has already been heuristically
committed. (DBERR 2834)
CAUSE A request was made to commit or abort a transaction
that has already been heuristically committed.
ACTION None.
----------------------------------------------------------------------------
2836 MESSAGE Timeout. (DBERR 2836)
CAUSE The requested function has timed out waiting for
access to a transaction.
ACTION Try again when the transaction is available.
----------------------------------------------------------------------------
2837 MESSAGE The global transaction identifier is invalid.
(DBERR 2837)
CAUSE The specified global transaction id has an invalid
format.
ACTION Check the GTRID.
----------------------------------------------------------------------------
3228 MESSAGE Log lock point specified is invalid. (DBERR
3228)
CAUSE The log location specified for a log lock is
invalid.
ACTION Check the location.
----------------------------------------------------------------------------
MPE/iX 5.5 Documentation