Internal Mimer SQL Return Codes

Here the internal Mimer SQL return code values are listed together with the associated text message. See Run-time Errors for details on how to retrieve this information after an exception has been raised.

Data-dependent Errors

These errors arise when an SQL statement cannot be executed correctly because of the data content of variables, expressions, and so on in the statement. The appropriate corrective action is determined by the nature of the error and the specific context in the application program.

Number

Explanation

-10001

Transaction aborted due to conflict with other transaction

-10002

Transaction aborted due to conflict with in-doubt transaction Do not retry transaction until in-doubt state resolved

-10100

PRIMARY KEY constraint violation, attempt to insert NULL value

-10101

PRIMARY KEY constraint violation, attempt to insert duplicate value

-10102

Domain constraint violation <%>

-10103

Table constraint violation <%>

-10104

View constraint violation <%>

-10105

INSERT or UPDATE operation invalid because the referencing table <%> does not satisfy a referential constraint

-10106

UPDATE or DELETE operation invalid because the referenced table <%> does not satisfy a referential constraint

-10107

The result of a subquery is more than one value

-10108

Result of SELECT INTO or EXECUTE INTO statement is a table of more than one row

-10109

Type constraint violation

-10110

UNIQUE constraint violation

-10199

Host variable type packed decimal is not supported

-10200

Reserved numeric operand found during data type conversion

-10201

Length error or incorrect value found during data type conversion

-10202

Division by zero attempted

-10203

Negative overflow occurred during data type conversion

-10204

Positive overflow occurred during data type conversion

-10205

Loss of significance occurred during data type conversion

-10207

Undefined value found during data type conversion

-10208

Restricted data type attribute violation

-10210

Error in assignment

-10211

Undefined value found during data type conversion

-10212

Overflow occurred during data type conversion

-10221

The NULL value cannot be assigned to a host variable because no indicator variable is specified

-10222

NULL not allowed for item descriptor area

-10250

Data type not supported

-10301

Loss of significance occurred in arithmetic operation <%>

-10302

Positive overflow occurred in arithmetic operation <%>

-10303

Negative overflow occurred in arithmetic operation <%>

-10304

Division by zero attempted

-10305

Bad parameter encountered in arithmetic operation <%>

-10306

Invalid input for numeric function

-10307

The binary strings are of unequal length

-10310

Invalid character value for CAST

-10311

String data truncated

-10312

Numeric value out of range

-10313

Illegal (negative) substring length

-10314

Like pattern escape character not followed by underscore or percent character

-10315

Length of like pattern escape character is not equal to 1

-10316

Data truncated

-10317

Invalid hexadecimal string

-10321

Datetime loss of significance

-10322

Datetime positive overflow

-10323

Datetime negative overflow

-10325

Bad parameter encountered in datetime operation

-10326

Datetime illegal operand

-10327

Invalid datetime value

-10328

Datetime subtype mismatch

-10329

Invalid datetime format

-10331

Interval loss of significance

-10332

Interval positive overflow

-10333

Interval negative overflow

-10335

Bad parameter encountered in interval operation

-10336

Interval illegal operand

-10337

Invalid interval value

-10338

Interval subtype mismatch

-10339

Invalid interval format

-10340

Length error for large object

-10351

Character string contains non-ascii character

-10352

Character string literal contains illegal UNICODE character

-10354

Bad parameter encountered in UNICODE conversion routine

-10355

Bad length parameter encountered in UNICODE conversion routine

-10356

Character string not aligned on proper byte boundary

-10401

Illegal character found when converting from UNICODE to ASCII

-10402

Illegal character found when converting from ASCII to UNICODE

-10403

The argument to the UNICODE_CHAR function is an invalid UNICODE value

-10451

Character or binary string too long

-10601

Invalid value for field of item descriptor area

-10602

Invalid datetime or interval code

-10603

PRECISION field of SQL descriptor cannot be set on non-numeric data types

Limits Exceeded

These errors arise when internal limits in the Mimer SQL system are exceeded. Some of the limitations are determined by installation-specific parameters, while others are fixed by Mimer SQL. In general, errors of this nature require either re-installation of the system with extended limitations or modification of the application program to reduce the system demands.

Contact your Mimer representative if you have difficulty avoiding errors of this nature.

Number

Explanation

-11001

Dynamic storage area exhausted in host level interface (DYNDE3)

-11002

Internal DB dynamic storage area (SQLPOOL) exhausted

-11011

Internal storage (SQLPOOL) for like pattern exhausted

-11012

Transaction list exhausted

-11013

Too many databanks referenced in statement (max 30)

-11014

Too many databanks active in transaction

-11047

The maximum number of recursive invocations has been exceeded

-11100

Internal limit exceeded : query stack

-11101

Internal limit exceeded : scan stack

-11102

Internal limit exceeded : generation stack

-11103

Internal limit exceeded : table descriptor list

-11105

Internal limit exceeded : patch table

-11106

Internal limit exceeded : label table

-11107

Internal limit exceeded : traversal stack

-11108

Internal limit exceeded : sco list

-11109

Internal limit exceeded : boolean stack

-11111

Internal limit exceeded : semantic stack

-11113

Internal limit exceeded : statement too complex

-11114

Required temporary table row length is <%>, only <%> is possible

-11115

Internal limit exceeded : restriction group pool

-11118

Internal limit exceeded : scan queue

SQL Statement Errors

These errors arise from syntactic or semantic errors in SQL statements. In general, syntactic errors in ESQL programs are detected by the preprocessor, so errors cannot arise at run-time.

Dynamically submitted SQL statements are however parsed at run-time, and the syntax error codes are returned after attempting PREPARE for a syntactically incorrect source statement.

Semantic errors can arise at run-time from both dynamic and static SQL statements.

Name <%> in PRIMARY KEY specification not recognized as a column name of current table definition

-12537

<%> must be unqualified

-12538

Default value not compatible with domain definition

-12539

Host variable construction illegal in this context

-12540

<%> is not a column of the specified table(s)

-12542

Default value is outside the range specified by domain definition

-12544

Too many columns specified in <%> statement

-12545

Primary key column <%> may not be updated because the table is in a NULL databank

-12546

Column <%> is not type compatible with the corresponding column of the referenced table

-12547

Number of columns specified in the foreign key is not the same as the number of columns in the primary key of the referenced table

-12549

Databank option may not be changed to NULL since <%> contains tables with FOREIGN KEY, REFERENCE, UNIQUE or trigger specifications

-12550

Table <%> includes a FOREIGN KEY or UNIQUE constraint and may therefore not be created in a databank with NULL option

-12551

Table <%> is in a databank with NULL option and may therefore not be used as referential constraint

-12552

A UNIQUE index can not be created for table <%> as it is located in a databank with NULL option

-12553

Explicit grant membership on PUBLIC is not permitted

-12554

PUBLIC cannot be member of another group

-12556

<%> cannot be shadowed because it is a NULL databank

-12557

Shadow named <%> already exists

-12558

Ident named <%> already exists

-12559

Index named <%> already exists

-12560

Table, View or Synonym named <%> already exists

-12561

Domain <%> not found, domain does not exist or no usage privilege

-12563

Shadow <%> does not exist

-12564

Ident <%> does not exist

-12565

Maximum row length exceeded by index or key table

-12566

Maximum row length exceeded by base table

-12568

EXISTS construction illegal in this context

-12569

ALL or ANY construction illegal in this context

-12570

Set function construction illegal in this context

-12571

Subquery construction illegal in this context

-12572

Too many columns given in FOREIGN KEY clause

-12573

Name <%> in CHECK clause not recognized as a column name of current table definition

-12574

Name <%> in column constraint not recognized as current column name

-12577

Default value not compatible with column specification

-12579

No such unique constraint in referenced table

-12581

Too many columns given in UNIQUE constraint

-12582

UNIQUE constraint equivalent to PRIMARY KEY constraint

-12583

UNIQUE constraint equivalent to previously given UNIQUE constraint

-12585

Name <%> in FOREIGN KEY clause not recognized as a column name of current table definition

-12589

An ident or a schema owning any collation cannot be dropped. Drop collation first

-12590

Table contains too many columns

-12591

Cannot create unique index

-12592

Dependencies exist, RESTRICT specified

-12593

Column <%> does not exist

-12594

Column <%> cannot be dropped as it is the only column in table

-12595

Column <%> cannot be dropped, dependencies exist

-12596

Default value for column <%> does not exist

-12597

Change of data type is not allowed for a column included in a key or index

-12598

The datatype for a column can not be changed to/from a domain

-12599

The proposed data type change is not supported

-12600

Change of data type is not supported for a column used by a view, routine trigger or precompiled statement

-12601

Statement does not support backup of <%>

-12602

The same file name is given for backup and incremental backup

-12603

Database is already OFFLINE

-12604

Database is already ONLINE

-12605

Cannot RESET LOG, because database is ONLINE

-12606

Databank <%> is already OFFLINE

-12607

Databank <%> is already ONLINE

-12608

Cannot RESET LOG, because databank <%> is ONLINE

-12609

Shadow <%> is already OFFLINE

-12610

Shadow <%> is already ONLINE

-12611

Cannot RESET LOG, because shadow <%> is ONLINE

-12612

Shadow <%> is already specified

-12613

Cannot set more than one shadow OFFLINE for databank having shadow <%>

-12614

Statistics cannot be updated for <%> because it is a view

-12615

Filename already used by databank or shadow

-12616

Cannot SET DATABASE OFFLINE, because another user is connected

-12617

Cannot SET DATABANK <%> OFFLINE, because the databank is in use

-12618

INCREMENTAL backups can only be used in conjunction with EXCLUSIVE

-12620

A domain named <%> already exists

-12621

A schema named <%> already exists

-12622

The schema name for the index table must be the same as the schema name for the table

-12623

A PRIMARY KEY constraint for this table has already been defined

-12624

The UNIQUE constraint cannot be created because the columns contain duplicates

-12625

Referential constraint criteria not fulfilled

-12626

Check constraint criteria not fulfilled

-12627

One or more specified columns does not exist in table

-12628

Referenced table or column not found

-12629

FOREIGN KEY not referencing a compatible UNIQUE or PRIMARY KEY

-12630

Constraint <%> cannot be dropped, dependencies exist

-12631

PRIMARY KEY or UNIQUE column constraint not valid when records exist

-12632

Collation <%> does not exist

-12633

A collation named <%> already exists

-12634

Invalid collation definition string

-12635

Collation <%> cannot be dropped, used by domain or column

-12636

A collate clause can only be specified for character types

-12637

Expressions with different collating sequences can not be compared

-12638

Collation specified in ORDER BY must be the same as used in DISTINCT/UNION

-12639

Column of type LARGE OBJECT not allowed in PRIMARY KEY, UNIQUE, FOREIGN KEY or INDEX

-12640

Precompiled statement <%> does not exist (or no execute privilege)

-12641

A precompiled statement named <%> already exists

-12642

Invalid SQL construction used in CREATE STATEMENT

-12643

Column of datatype LARGE OBJECT not allowed in this context

-12644

SQL syntax error, only EXECUTE STATEMENT allowed

-12645

Column of datatype LARGE OBJECT not allowed in a databank having shadow

-12646

Precompiled statement is not scrollable

-12647

Precompiled statement is scroll only

-12648

Not allowed to change table as it is used by a precompiled statement

-12650

Only the creator of a precompiled statement may alter it

-12701

<%> is a reserved word, and cannot be used as the name for a symbol

-12702

<%> is a global variable, and cannot be used as the name for a variable or parameter

-12703

The class <%> is already present in the handler declaration

-12704

The SQLSTATE <%> is already present in the handler declaration

-12705

The condition identifier <%> is already present in the handler declaration

-12706

The condition identifier <%> is already used in another handler in this scope

-12707

A condition identifier for the SQLSTATE <%> has already been defined in this scope

-12708

<%> is not a valid SQLSTATE value

-12709

The SQLSTATE <%> associated with the condition identifier <%> is already present in the handler declaration

-12710

An exception handler for the state (<%>) associated with the condition identifier <%> has already been defined in this scope

-12711

An exception handler for the state <%> has already been defined in this scope

-12712

An exception handler for the class <%> has already been defined in this scope

-12713

The default literal is too large for this data type

-12714

The literal value is too large for this data type

-12715

The type of the default value is not compatible with the type of the variable

-12717

Invalid declaration. The maximum precision for this data type is <%>

-12718

The scale cannot exceed the precision

-12720

The number of correlation names for <%>, does not match number of result types

-12721

The parameter <%> for a result set procedure must be declared as IN

-12722

The parameter <%> is declared as IN, and cannot be assigned

-12723

The parameter <%> is declared as OUT, and cannot be used in expressions

-12724

<%> cannot be assigned a value directly

-12725

Result set procedures can only be used in cursor declarations

-12726

The formal argument of the routine is IN but the actual argument is OUT

-12727

The formal argument of the routine is OUT but the actual argument is IN

-12728

Literals or expressions cannot be used for OUT parameters

-12729

Return statements are only allowed in result set procedures or functions

-12730

Recursive call to <%>, not allowed

-12731

<%> statement not allowed in result procedure

-12732

The procedure <%> does not return a result set and cannot be used in a declare cursor for call

-12733

RESIGNAL statement only allowed in exception

-12734

Wrong number of items in result clause, <%> expected

-12735

Wrong number of parameters, <%> expected

-12736

Invalid type for argument, <%> expected

-12737

Too long name <%>

-12738

Duplicate declaration <%>

-12739

x.y.z names not allowed

-12740

Syntax error, <%> assumed to mean <%>

-12741

The label or routine <%> is not defined

-12742

The label <%> is not defined

-12743

The procedure <%> does not exist (or no execute privilege)

-12744

The variable <%> is not defined

-12745

The condition identifier <%> is not defined

-12746

The cursor <%> is not defined

-12747

Use of domains in PSM control statements not allowed

-12748

Operands are incompatible

-12749

The SQL module <%> already exists

-12750

The procedure <%> already exists

-12751

Duplicate parameter <%>

-12752

The procedure <%> is declared in an SQL module, and cannot be dropped directly

-12753

Failed to read data dictionary

-12754

The length of a host variable cannot exceed 32

-12755

Host variables cannot be used within a procedure

-12756

The data type for the parameter marker cannot be determined

-12757

The number of items in the into clause is less than the number of items in the select list

-12758

The number of items in the into clause is greater than the number of items in the select list

-12759

The number of items in the fetch into clause is less than the number of items in the cursor declaration

-12760

The number of items in the fetch into clause is greater than the number of items in the cursor declaration

-12761

A fetch direction other than next, can only be defined for a scrollable cursor

-12762

The value in a fetch absolute or relative must be an integer

-12763

The argument to fetch absolute must be larger than 0

-12764

A cursor for call is read only and cannot be used in a update or delete where current statement

-12765

The cursor is declared as read only and cannot be used in a update or delete where current statement

-12766

The table name in the <%> statement is not the same as the name used in the cursor declaration

-12767

The column <%> is not specified in the for update list of the cursor declaration

-12768

The size for a data type must be larger than zero

-12769

It is not allowed to declare exception handlers or condition identifiers for the SQLSTATE successful completion ('00000')

-12770

The formal argument of the procedure is declared as INOUT but the actual argument is <%>

-12771

A handler declaration cannot contain both an exception class and SQLSTATE values or condition identifiers

-12772

The procedure does not return a result set and therefore cannot be used with a scroll cursor

-12773

<%> is not a column and is not declared as a variable or parameter

-12774

The label <%> has already been declared

-12775

The statement requires <%> access

-12776

<%> statement is only allowed if the access indication is MODIFIES SQL DATA or READS SQL DATA

-12777

<%> statements are only allowed if the access indication is MODIFIES SQL DATA

-12778

The access indication for a result set procedure must be READS SQL DATA or CONTAINS SQL

-12779

An UNDO exception handler can only be specified in an atomic compound statement

-12781

Only assignment and comparison operations allowed

-12782

The column name <%> has already occurred in this row declaration

-12783

The field <%> is not defined in the row data type

-12784

The row data types do not have the same number of fields

-12785

A row data type variable may not be used as a parameter or result type nor in a DML statement

-12800

Functionality not supported: <%>

-12801

Referencing OLD TABLE is not allowed if trigger event is INSERT

-12802

Referencing NEW TABLE is not allowed if trigger event is DELETE

-12803

The compound statement in a triggered action must be atomic

-12804

Referencing OLD or NEW ROW may only be used if FOR EACH ROW is specified

-12805

A column list can only be specified if trigger event is UPDATE

-12806

Duplicate column name in OF list

-12807

It is not allowed to modify the <%> table

-12808

The trigger time for a view must be INSTEAD OF

-12809

The trigger time for a base table can not be INSTEAD OF

-12810

Only the creator of a table is allowed to create a trigger for the table

-12811

It is not allowed to create triggers for tables, located in databanks with NULL option

-12812

Referencing OLD or NEW table is not allowed in FOR EACH ROW triggers

-12813

A trigger with the name <%> already exists

-12830

A function with the name <%> already exists

-12831

The function <%> does not exist (or no execute privilege)

-12832

The result of the expression is not deterministic while the routine is declared as deterministic

-12833

All privileges used in a trigger must be held with grant option

-12834

The sequence <%> does not exist

-12835

A sequence with the name <%> already exists

-12836

The keyword NULL cannot be used <%>

-12837

The operands to a overlaps predicate must be of a row data type with two elements

-12838

The two elements in an operand to the overlaps predicate must either be of the same type or otherwise it shall be possible to add the second value to first value

-12839

<%> is not allowed in a before trigger

-12840

The simple value specification for a get diagnostics statement must be of integer type

-12841

<%> is not allowed in a trigger

-12842

The increment for a sequence must be non zero

-12843

Invalid values for sequence attributes

-12844

The schema <%> does not exist (or no privilege)

-12845

The schema name for routines in a module definition must be the same as the schema name for the module

-12846

The value for diagnostics size must be positive

-12847

The ident name in an authorization clause must be the same as the current user

-12848

Constraint name already exists

-12849

The function <%> MODIFIES SQL DATA and can thus not be used in a DML statement

-12850

A trigger must be located in the same schema as the table

-12851

A constraint must have the same schema name as the object to which it belongs

-12852

The schema name for a routine is not the same as the schema name for the module

-12853

Ident name not allowed as a schema with the same name exists

-12854

A non-deterministic expression is not allowed in a check clause

-12855

Default values with a reference to a sequence combined with a check clause is not allowed in an alter table statement

-12856

Triggers and large object columns not allowed on a table

-12857

The label <%> can not be used for an iterate statement

-12858

The record <%> is not compatible with the <%>

Program-dependent Errors

These errors arise as a result of incorrect program construction. In general, corrective action requires revision of the program source code.

Number

Explanation

-14001

Invalid sequence of SQL statements

-14002

SQL statement invalid because the user is not connected

-14003

CONNECT statement invalid because the user is already connected

-14004

System already closed down

-14005

Cannot perform DISCONNECT in a transaction

-14006

Login failure

-14011

Transaction already started

-14012

Transaction handling required

-14013

No transaction started

-14014

Cannot perform write operations as transaction status is read-only

-14015

Commit or rollback statements are not allowed in an atomic execution context

-14016

Select for update is not allowed for a read-only cursor

-14017

Mixing DDL and DML statements in a transaction is not allowed

-14018

Incremental backup not allowed in BACKUP transaction

-14019

Operation not allowed in BACKUP transaction

-14020

START BACKUP command required to perform an online backup

-14021

Cannot perform ENTER or LEAVE in a transaction

-14022

Cannot perform ENTER operation because program level is already active

-14023

No program level entered, cannot perform leave operation

-14024

Session statements are not allowed in a trigger

-14025

START LOAD command required to perform a load operation

-14026

The table name specified in the COMMIT/ROLLBACK LOAD statement does not match the table name (<%>) specified in the START LOAD statement

-14027

Invalid transaction state, held cursor requires same isolation level

-14031

DESCRIBE statement does not identify a prepared statement

-14032

EXECUTE statement does not identify a prepared statement

-14033

PREPARE statement identifies a SELECT statement of an opened cursor

-14034

The cursor is not in a prepared state

-14035

The cursor identified in a FETCH or CLOSE statement is not open

-14036

The cursor cannot be used because its statement name does not identify a prepared SELECT statement

-14037

The cursor identified in the UPDATE or DELETE statement is not open

-14038

UPDATE or DELETE CURRENT statement not allowed for a cursor of a prepared SELECT statement

-14039

Cursor is not scrollable

-14041

The cursor identified in the UPDATE statement is not positioned on a row

-14042

The cursor identified in the DELETE statement is not positioned on a row

-14043

Routine signaled SQLSTATE

-14044

Routine signaled a condition

-14045

Prepared statement not a cursor specification

-14046

The statement RESIGNAL was used outside a exception handler

-14047

Duplicate transaction identifier

-14048

Current user not owner of transaction

-14049

Already associated with transaction

-14050

The specified transaction identifier could not be found

-14051

Invalid distributed transaction state

-14052

It is not possible to mix local and distributed transactions

-14053

The transaction identifier is in use by other user

-14054

The requested operation cannot be performed in a distributed transaction

-14101

Invalid statement identifier

-14201

Compilation did not yield an executable program

-14202

The cursor identified in an OPEN statement is already open, but not declared as REOPENABLE

-14203

Statement position cannot be saved when temporary tables are used in the query

-14210

Cursor for result set procedure may not be reopenable

-14211

WITH HOLD option is only available for SELECT statements

-14301

SQLDA contains an invalid data address or indicator variable address

-14302

Invalid address of username or password

-14303

Invalid address

-14311

Illegal statement length given for SQL statement

-14312

Input character string too long

-14313

Like pattern string too long

-14314

Username or password too long

-14315

Illegal byte length of floating point number

-14316

Unterminated C string, null byte not found

-14321

Illegal host variable type

-14322

Illegal host variable type in like pattern string

-14323

Username and password must be fixed length character strings

-14324

Illegal indicator variable type

-14331

The number of provided host variables does not match the number of parameters

-14332

Using clause required for dynamic parameters

-14333

Using clause required for result fields

-14401

Column cannot be updated because it is not identified in the UPDATE clause of the SELECT statement of the cursor

-14402

The table identified in the UPDATE or DELETE statement is not the same as that designated by the cursor

-14403

Cannot describe statement without naming information

-14404

Cannot update table <%> because the declare statement is read-only

-14405

Cannot delete from table <%> because the declare statement is read-only

-14406

Unexpected statement type encountered in an UPDATE or DELETE statement

-14501

Database connection is not open

-14601

Invalid cursor state

-14611

Using clause does not match dynamic parameters

-14612

Using clause or Into clause does not match target specifications

-14621

Cursor not found

-14622

Ambiguous cursor name

-14623

Invalid cursor name

-14624

Cursor already allocated for statement

-14631

Invalid SQL statement name

-14641

Invalid SQL descriptor name

-14642

Invalid descriptor index

-14643

Invalid descriptor count

-14651

Invalid exception number

-14652

The xa_info string passed to xa_open or xa_close has an improper syntax

-14653

Invalid flags argument passed to XA routine

-14654

Asynchronous operations are not supported by XA routines

-14700

No return statement was encountered during the execution of a function

-14701

The statement is not allowed in an atomic execution context

-14702

The same column has been updated to different values when executing a trigger

-14703

An exception occurred during the execution of a trigger

-14720

The maximum_value for the sequence <%> has been reached

-14721

There is no current_value for the sequence <%> because the next_value function has not been invoked

-14722

Sequence <%> locked by another user

-14723

Update of attributes for the sequence <%> failed

-14724

Not possible to allocate multiple sequence values

-14725

WITH HOLD cursors can not be used with result procedures

Databank and Table Errors

These errors are associated with problems of physical access to databanks and tables. Locking errors should not result from transaction conflicts, but generally indicate either locking at the operating system level or malfunction of the internal Mimer SQL routines.

Many of the errors in this class are corrected by action taken at the operating system level. If errors persist in spite of corrective action, contact your Mimer representative.

Number

Explanation

-16001

Table locked by another user

-16002

Table locked by another cursor

-16003

Table in referential constraint definition locked by another user

-16004

Table in referential constraint definition locked by another cursor

-16005

Log locked by another user

-16006

Backup unit log file locked

-16101

No databank <%> found in dictionary

-16135

Record no longer exists

-16141

Syntax error in filename for databank <%>

-16142

Cannot open databank <%>, file <%> not found

-16143

File protection violation for databank <%>, file <%>

-16144

Cannot open databank <%>, file <%> locked by other user

-16145

Too many databanks open concurrently (direct access I/O limit)

-16146

File create error, disk full

-16147

File create error (quota exceeded) for databank <%>, file <%>

-16148

Device or network connection not ready, databank <%>, file <%>

-16149

Cannot open databank <%> in file <%>

-16150

Tried to access databank <%> on node which is inaccessible because TRANSDB is OFFLINE

-16151

Too many databanks open concurrently

-16152

Tried to open a non-MIMER databank

-16154

Table control area exhausted

-16155

Incompatible version of databank <%>

-16156

Databank <%> belongs to another system databank

-16157

Tried to open a read-only databank with write access

-16159

Old version of the databank <%> cannot be accessed without using the ALTER DATABANK .. RESTORE statement

-16160

Cannot set TRANSDB shadow OFFLINE on the same node as the master TRANSDB

-16161

Databank <%> disk space exhausted

-16162

Databank LOGDB disk space exhausted

-16163

Databank TRANSDB disk space exhausted

-16164

Databank SQLDB disk space exhausted

-16172

Databank <%> locked by another MIMER/DB user

-16182

Databank <%> corrupt

-16183

Bad parameter

-16184

I/O error

-16185

Internal databank identifier invalid

-16186

Internal table identifier invalid

-16187

Shadow <%> in file <%> has illegal sequence number

-16189

Corrupt bitmap page

-16190

Table root entry not found

-16191

Exclusive access to databank required for attempted operation

-16192

Load not allowed in databank with TRANS or LOG option

-16193

TRANSDB and/or LOGDB not open

-16194

Error occurred in transaction commit phase

-16195

Internal inconsistency detected

-16196

No end of table mark found for tableid

-16197

Shadow <%> is already OFFLINE

-16198

Shadow <%> is already ONLINE

-16199

Result of bitmap page I/O undefined

-16200

Result of index page I/O undefined

-16201

Result of root page I/O undefined

-16202

Result of data page I/O undefined

-16203

Corrupt index page

-16204

Corrupt root page

-16205

Corrupt data page

-16206

Write set corrupt

-16207

Table <%> has invalid record length

-16208

Unable to open databank <%>. SHADOW license required

-16209

Unable to open databank <%>. NETIO license required

-16210

Cleanup control area exhausted

-16211

Not properly closed, dbcheck initiated

-16212

TRANSDB restart directory corrupt

-16213

Error when closing databank file. Please consult multiuser log file

-16214

Blockdata DKBLK1 missing

-16215

Error accessing remote TRANSDB, node will not be accessed further

-16216

Blocksize not supported

-16217

Error when generating internal key

-16218

Operation not allowed. Licensed number of users exceeded

-16219

Too many multi systems started

-16220

Unable to retrieve limit on number of allowed users

-16221

Lost contact with peer

-16222

Record length from update before is invalid

-16224

Transaction state table entries exhausted

-16225

Transaction state identifier invalid

-16226

Invalid function code

-16227

Commit set corrupt

-16228

Restart set corrupt

-16229

Cancel requested

-16230

Transaction cache inconsistent

-16231

Shadow <%> is inaccessible due to incomplete CREATE SHADOW or SET ONLINE operation

-16232

Database upgrade required

-16233

Operation not allowed. Licensed number of users exceeded

-16234

Execution interrupted by scheduler

-16235

There are pending in-doubt transactions

-16401

Routine cannot be dropped because it is in use

-16402

Routine cannot be used because it is being dropped

Miscellaneous Errors

These errors arise from miscellaneous problems that do not fall into the other classes. If the corrective action is not indicated by the error description, contact your Mimer representative for help.

Number

Explanation

-18001

Blockdata BLKDS2 not included

-18002

Cannot log in, error in SYSDB initialization

-18003

No privilege to open log file

-18004

Databank LOGDB already opened by another MIMER/DB user. Could not be opened exclusively to drop log records

-18005

Unknown language

-18006

Language not properly installed

-18007

Unable to fetch message text

-18008

Restore in wrong sequence attempted

-18009

Mismatching version of Embedded SQL and MIMER/DB

-18010

Invalid log record found during restore operation

-18011

Mismatching version of MIMER/DB and utilities

-18012

The transformation of a TRANSDB shadow to master was interrupted before completion. Please login to BSQL to complete the transformation

-18013

MIMER/DB started from SYSDB shadow. Transform SYSDB shadow to master with BSQL, or restart system from master SYSDB

-18014

Alter shadow not allowed in SQL for system databanks. Use utility program instead.

-18015

Open with hold is not possible when temporary tables are used for evaluation of the query

-18016

Cursor could not be opened with hold as it is not prepared with hold

-18017

With hold functionality not supported

-18018

The network server version does not support scroll

-18019

Bad parameters passed to DBAPI4

-18020

Unknown information code = <%> used

-18021

Only SELECT, INSERT, UPDATE, and DELETE operations (excluding where current forms) may be compiled together in a single statement

-18022

Distributed transactions not supported by server

-18023

Requested DTC function not supported by server

-18024

Failed to enlist transaction in distributed transaction

-18025

Unable to retrieve transaction manager's whereabouts

-18026

Failed to import transaction identifier

-18027

Statement already active in other transaction

-18028

Cannot initiate a new PSM debugger session, because the number of request threads is insufficient

-18029

Execution interrupted by debugger

-18041

Update of primary key columns for a table located in a databank, with NULL option is not allowed

-18042

Primary key columns may not be updated by Level2 applications

-18043

The rowid column may not be updated

-18044

Inaccessible shadow found at LOAD operation

-18045

The table specified in the preceding START LOAD statement can only be referenced using single value inserts while the LOAD operation is active

Error codes used by the server when creating database dumps. These codes are never returned to application programs:

Number

Explanation

-21200

Error when creating dump file

-21201

Error when writing dump file

Error codes reflecting problems in the layer that creates and interprets network packets:

Number

Explanation

-21300

Too large network buffer requested on client side

Other file management error codes:

Number

Explanation

-21400

Illegal file name

-21401

File not found

-21402

File protection violation

-21403

File was locked

-21404

The file could not be opened since a system resource was exhausted

-21405

The disk space is exhausted

-21406

The file is not open

-21407

Read not allowed on file

-21408

Write not allowed on file

-21410

Illegal argument

-21411

Illegal character

-21412

Memory allocation error

-21499

Unspecified error

JDBC Errors

These errors arise when the Mimer JDBC Driver fails for some reason. The error codes are in the range -22000 to -22999. When using Java, the error message is always included in the exception that is thrown.

To get the complete and accurate list of error codes, execute the following command: