Return Codes

Mimer SQL returns two kinds of return codes to an application, SQLSTATE and a native error code (aka. SQLCODE). The SQLSTATE variable returns a standardized, general error code, which gives a rough description of the status for the most recently executed SQL statement.

GET DIAGNOSTICS can be called to access the exception information stored in the diagnostics area that applies to the most recently executed SQL statement, see Run-time Errors.

The symbol <%> in the text of error messages listed in this chapter indicates the location of an identifier inserted at run-time

SQLSTATE Return Codes

SQLSTATE contains a 5-character long return code string that indicates the status of an SQL statement. These return codes are standardized following the established standards. Observe that not all standardized SQLSTATE return codes are used by Mimer SQL.

SQLSTATE values consists of two fields. The class field, which is the first two characters of the string, and the subclass field, which is the terminating three characters of the string.

List of SQLSTATE Values

Class

Subclass

Meaning

00

000

Successful completion

01

000

Warning

01

002

- disconnect error

01

003

- null value eliminated in set function

01

004

- string data, right truncation

01

005

- insufficient item descriptor areas

01

006

- privilege not revoked

01

007

- privilege not granted

01

008

- implicit zero-bit padding

01

997

- some statement(s) not altered**

01

998

- row has been updated**

01

999

- row has been deleted**

01

S01

- error in row

01

S02

- option value changed

01

S05

- cancel treated as close

01

S06

- attempt to fetch before the result set returned the first rowset

01

S07

- fractional truncation

02

000

No data

07

000

Dynamic SQL error

07

001

- using clause does not match dynamic parameter specifications

07

002

- using clause does not match target specifications

07

003

- cursor specification cannot be executed

07

004

- using clause required for dynamic parameters

07

005

- prepared statement is not a cursor specification

07

006

- restricted data type attribute violation

07

007

- using clause required for result fields

07

008

- invalid descriptor count

07

009

- invalid descriptor index

07

00F

- invalid DATETIME_INTERVAL_CODE

08

000

Connection exception

08

001

- client unable to establish connection

08

002

- connection name in use

08

003

- connection does not exist

08

004

- server rejected the connection

08

006

- connection failure

08

S01

- communication link failure

09

000

Triggered action exception

0A

000

Feature not supported

0B

000

Invalid transaction initiation

0K

000

Resignal when handler not active

0W

000

Prohibited statement encountered during trigger execution

21

000

Cardinality violation

21

S01

- insert value list does not match column list

21

S02

- degree of derived table does not match column list

22

000

Data exception

22

001

- string data, right truncation

22

002

- null value, no indicator parameter

22

003

- numeric value out of range

22

005

- error in assignment

22

006

- invalid interval format

22

007

- invalid datetime format

22

008

- datetime field overflow

22

011

- substring error

22

012

- division by zero

22

015

- interval field overflow

22

018

- invalid character value for cast

22

019

- invalid escape character

22

023

- invalid parameter value

22

024

- unterminated C string

22

025

- invalid escape sequence

22

026

- string data, length mismatch

22

027

- trim error

22

029

- noncharacter in UCS string

23

000

Integrity constraint violation

24

000

Invalid cursor state

25

000

Invalid transaction state

25

S03

- transaction is rolled back

26

000

Invalid SQL statement name

27

000

Triggered data change violation

28

000

Invalid authorization specification

2E

000

Invalid connection name

2F

000

SQL routine exception

2F

003

- prohibited SQL-statement attempted

2F

005

- function executed no return statement

33

000

Invalid SQL descriptor name

34

000

Invalid cursor name

35

000

Invalid condition number

37

000

Syntax error or access violation
in PREPARE or EXECUTE IMMEDIATE *

3C

000

Ambiguous cursor name

40

000

- transaction rollback

40

001

- serialization failure

42

000

Syntax error or access rule violation

42

S01

- base table or view already exists

42

S02

- base table or view not found

42

S11

- index already exists

42

S21

- column already exists

42

S22

- column not found

44

000

WITH CHECK OPTION violation

45

000

Unhandled user-defined exception

HY

000

General error   

HY

001

- memory allocation error

HY

003

- invalid application buffer type

HY

004

- invalid SQL data type

HY

007

- associated statement is not prepared

HY

008

- operation canceled

HY

009

- invalid use of null pointer

HY

010

- function sequence error

HY

011

- attribute cannot be set now

HY

012

- invalid transaction operation code

HY

013

- memory management error

HY

014

- limit on the number of handles exceeded

HY

015

- no cursor name available

HY

016

- cannot modify an implementation row descriptor

HY

017

- invalid use of an automatically allocated descriptor handle

HY

018

- server declined cancel request   SQLCancel

HY

019

- non-character and non-binary data sent in pieces

HY

020

- attempt to concatenate a null value

HY

021

- inconsistent descriptor information

HY

024

- invalid attribute value

HY

090

- invalid string or buffer length

HY

091

- invalid descriptor field identifier

HY

092

- invalid attribute/option identifier

HY

093

- invalid parameter number

HY

095

- function type out of range

HY

096

- invalid information type

HY

097

- column type out of range

HY

098

- scope type out of range

HY

099

- nullable type out of range

HY

100

- uniqueness option type out of range

HY

101

- accuracy option type out of range

HY

102

- table type out of range

HY

103

- invalid retrieval code

HY

104

- invalid precision or scale value

HY

105

- invalid parameter type

HY

106

- fetch type out of range

HY

107

- row value out of range

HY

108

- concurrency option out of range

HY

109

- invalid cursor position

HY

110

- invalid driver completion

HY

111

- invalid bookmark value

HY

C00

- optional feature not implemented

HY

T00

- timeout expired

HY

T01

- connection timeout expired

IM

000

ODBC specific return codes

IM

001

- driver does not support this function

IM

008

- dialog failed

S0

000

ODBC 2.0 codes *

S0

001

- base table or view already exists *

S0

002

- base table not found *

S0

011

- index already exists *

S0

012

- index not found *

S0

021

- column already exists *

S0

022

- column not found *

S1

000

General error

S1

001

- memory allocation failure

S1

002

- invalid column number

S1

003

- program type out of range

S1

004

- SQL data type out of range

S1

008

- operation canceled

S1

009

- invalid argument value

S1

010

- function sequence error

S1

012

- invalid transaction operation code specified

S1

090

- invalid string or buffer length

S1

091

- descriptor type out of range

S1

092

- option type out of range

S1

093

- invalid parameter number

S1

095

- function type out of range

S1

096

- information type out of range

S1

097

- column type out of range

S1

098

- scope type out of range

S1

099

- nullable type out of range

S1

100

- uniqueness option out of range

S1

101

- accuracy option type out of range

S1

102

- table type out of range

S1

105

- direction option out of range

S1

106

- fetch type out of range

S1

107

- row value out of range

S1

108

- concurrency option out of range

S1

109

- invalid cursor position

S1

C00

- driver not capable

S1

T00

- timeout expired

* Return code will only be returned to ODBC applications executing in ODBC 2.0 mode.

‘** Mimer SQL specific SQLSTATE code.

Native Mimer SQL Return Codes

Here the native Mimer SQL return codes 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.

Sometimes the deprecated term SQLCODE is used when referring to the native return code.

The codes are grouped according to function as follows:

Code numbers

Functional group

> 0

Warnings and Messages

= 0

Success

100

No data

-100 to -999

ODBC Errors and Warnings

-10000 to -10999

Data-dependent Errors

-11000 to -11999

Limits Exceeded

-12000 to -12999

SQL Statement Errors

-14000 to -14999

Program-dependent Errors

-16000 to -16999

Databank and Table Errors

-18000 to -18999

Miscellaneous Errors

-19000 to -19999

Internal Errors

-21000 to -21999

Communication Errors

-22000 to -22999

JDBC Errors

-23000 to -23999

Mimload Errors

-24000 to -24999

Mimer SQL C API Return Codes

Corrective action is given in general terms for each group of codes. When reporting errors to Mimer support, make sure you include the native Mimer SQL return code.

Warnings and Messages

No corrective action is normally required for internal Mimer SQL return code values greater than zero.

Number

Explanation

53

Null values eliminated in set function

54

Character string was truncated

55

Insufficient item descriptor areas

56

Privilege not revoked

57

Privilege not granted

58

Zero bits were added to the binary string

90

Login failure

91

Soft enter performed

92

No cursor state was saved on stack

94

Message text not found

100

Row not found for FETCH, UPDATE or DELETE, or the result of a query is an empty table

100

No data - Item number is greater than the value of count

997

It was not possible to alter all executable statements

998

The row has been updated by an update where current statement for this cursor

999

The row has been deleted by a delete where current statement for this cursor

ODBC Errors and Warnings

These errors occur when ODBC calls to Mimer SQL fail for some reason.

Number

Explanation

-100

Illegal sequence

-101

Out of memory

-102

Option out of range

-103

Function not supported

-104

Connection not open

-105

Connection in use

-106

Invalid argument value

-107

Invalid transaction operation code

-108

Internal network buffer overflow

-109

Invalid C data type

-110

Invalid SQL data type

-111

Bad address

-112

Function already active

-113

Operation canceled

-114

Wrong number of parameters

-115

Use ODBC function SQLEndTran (or SQLTransact for ODBC 2 applications) to commit or rollback transaction

-116

Statement is not in a prepared state

-117

Invalid transaction state

-118

Unknown statement type

-119

Server data type not supported by client

-120

Unknown data type

-121

Invalid buffer length

-122

String data truncated

-123

Numeric data truncated

-124

Numeric value out of range

-125

Invalid numeric value

-126

Bad parameter passed to numeric package

-127

Invalid column number

-128

Database name mandatory

-129

Connect dialog failed

-130

Data truncated

-131

Invalid connection string attribute

-132

Invalid cursor state

-133

Invalid parameter number

-134

Descriptor type out of range

-135

Invalid type passed to DICOA3

-136

Function type out of range

-137

Invalid cursor name

-138

Duplicate cursor name

-139

Cursor hash table corrupt

-140

ODBC database control block chain corrupt

-141

Option type out of range

-142

Option value not supported

-143

Option not supported

-144

Invalid row or keyset size

-145

Invalid concurrency option

-146

Invalid fetch type

-147

Not a scrollable cursor

-148

Row position out of range

-149

Only one SQLPutData for fixed length parameter

-150

SQLPutData does not support block cursors

-151

Driver not capable

-152

Table type out of range

-153

Invalid string length

-154

Data type out of range

-155

Syntax error found in escape clause

-156

DDO buffer overflow

-157

Uniqueness option type out of range

-158

Accuracy option type out of range

-159

Column type out of range

-160

Scope type out of range

-161

Nullable type out of range

-162

Internal type mismatch

-163

Conversion between data types not supported

-164

Invalid date, time, or timestamp

-165

Restricted data type attribute violation

-166

Date, time, or timestamp data truncated

-167

Database has not been configured. Run Configure Mimer 7.1

-168

Translated native SQL string was truncated

-169

ODBC extension DATE, TIME or TIMESTAMP is not supported

-170

ODBC extension OUTER JOIN is not supported

-171

ODBC extension for procedure invocation is not supported

-172

Unrecognized first word in escape clause, expected 'CALL','FN','OJ','D','T' or 'TS'

-173

This server version does not support the used scalar function

-174

Unrecognized scalar function found in escape clause

-175

Argument missing in scalar function

-176

Too many arguments in scalar function

-177

Syntax error, incomplete escape clause

-178

Syntax error, unmatched apostrophe in string literal

-179

Syntax error, unmatched quote in delimited identifier

-180

Invalid data type specified in scalar function CONVERT

-181

Information type out of range

-182

Parameter type may only be used with procedures

-183

Parameter type out of range

-184

Update and delete where current fully supported (not simulated)

-185

Option value changed

-186

Static scrollable cursor used instead of keyset or dynamic cursor

-187

Error in row, please check next error code

-188

Cancel treated as FreeStatement/CLOSE

-189

Attempt to fetch before the result set returned the first rowset

-190

Invalid cursor position

-191

Unknown first parameter in scalar function TIMESTAMPADD

-192

Unknown first parameter in scalar function TIMESTAMPDIFF

-193

Bad parameter passed to datetime package

-194

Out of critical section objects

-196

Invalid attribute option identifier

-197

Attribute cannot be set now

-198

General error

-199

Invalid use of an automatically allocated descriptor

-200

Invalid descriptor field identifier

-201

Invalid descriptor index

-202

Associated statement not prepared

-203

Interval second fraction truncated

-204

Interval truncation error

-205

Interval convert error

-206

Year to month interval cannot be converted to a numeric value because it is not a single field

-207

Interval cannot be converted to a numeric value because it is not a single field

-208

Invalid interval literal

-209

Interval leading field truncation error

-210

Interval trailing field truncated

-211

Binary data truncated

-212

Binary truncation error

-213

Binary length invalid

-214

Binary data invalid

-215

Binary not supported

-216

Inconsistent descriptor information

-217

Cannot modify IRD

-218

Invalid use of null pointer

-219

Character data not hexadecimal

-220

Internal error

-221

Significant parts of datetime/interval string truncated

-222

Interval field truncation

-223

String data truncated

-224

Binary data truncated

-225

String data truncated

-226

Binary data truncated

-227

Internal error - Must put blob separately

-228

Unicode string data conversion error

-229

LOB data larger than specified in SQL_LEN_DATA_AT_EXEC(x)

-230

Distributed transaction mode is active, but no transaction enlist has been performed. May be due to early transaction abort or illegal sequence of calls in application.

-232

Wide character data types not supported by server

-233

SQL_LEN_DATA_AT_EXEC(n) only allowed for long data types

-235

Maximum escape clause nesting depth reached

-236

The character string '%' could not be casted to an %

-237

An SQL % interval cannot be casted to a %

-238

A non-fractional part of a TIME or a TIMESTAMP was truncated

-239

The % character string '%' could not be casted to an %

-300

Failed to read dictionary

-801

Error loading library XOLEHLP.DLL or locating entry point to DtcGetTransactionManager in XOLEHLP

-801

Pending transaction, commit or rollback before exit

-802

Unable to retrieve MSDTC transaction object (IID_IDtcToXaHelperSinglePipe)

-802

Invalid transaction number, must be between 1 and <%>

-803

Unable to retrieve MSDTC resource manager cookie

-803

Server version and BSQL version must be the same when using READLOG

-804

Unable to translate MSDTC transaction id to an XA transaction id (XID)

-805

Unable to perform distributed transaction enlist

-806

Invalid sequence of calls within ODBC to MSDTC interface routines

-807

Error initiating transaction object

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.

-10003

Transaction aborted due to a preceding problem with databanks or resources

-10004

Current transaction has been invalidated by a conflicting system administration statement

-10100

PRIMARY KEY constraint violated, attempt to insert null value in table <%>, column <%>

-10101

PRIMARY KEY constraint violated, attempt to insert duplicate key in table <%>

-10102

Domain constraint <%> violated for table <%>, column <%>

-10103

Table constraint <%> violated for table <%>

-10104

View constraint violation

-10105

Referential constraint <%> violated INSERT/UPDATE operation not valid for table <%>

-10106

INSERT/UPDATE operation not valid for table <%> UPDATE/DELETE operation not valid for table <%>

-10107

The result of a subquery or select into is more than one row

-10108

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

-10109

Data type constraint violation (numeric value out of range)

-10110

UNIQUE constraint <%> violated for table <%>

-10111

Domain constraint <%> violated for CAST

-10112

Deferred referential constraint <%> violated, INSERT/UPDATE operation not valid for table <%>

-10113

Deferred referential constraint <%> violated, UPDATE/DELETE operation not valid for table <%>

-10114

The referential action for the constraint <%> would cause multiple updates on the table <%>

-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

A corrupt numeric value was encountered

-10308

Binary data truncated

-10309

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

-10318

Invalid regular expression <%>

-10319

The search string used in a BEGINS_WORD or MATCH_WORD invocation contains invalid characters. Only characters that can be used in an identifier are allowed. More information can be found in the section on identifiers in the Mimer SQL Reference Manual.

-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

-10341

Cannot set attribute value for UDT instance as it is null

-10351

Character string contains non-ascii character

-10352

Character string 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

-10361

The used collation cannot be loaded

-10371

Coordinate value out of range

-10372

Latitude value out of range

-10373

Longitude value out of range

-10380

Invalid value in fetch first clause, must be larger than zero

-10381

Invalid value in fetch offset clause, must be positive

-10390

The builtin.uuid character representation is invalid. The expected value is a string in the format HHHHHHHH-HHHH-HHHH-HHHH-HHHHHHHHHHHH, where each H is a hexadecimal value specified by using the symbols 0-9 and A-F.

-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

-10701

Invalid LEVEL value in item descriptor area

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

-11015

The allocated number of realtime tasks in the server has been exhausted

-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

-11112

Internal limit exceeded: working storage

-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.

Number

Explanation

-12001

Too many errors, error collection terminated

-12101

Syntax error, <%> assumed missing

-12102

Syntax error, <%> ignored

-12103

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

-12104

Invalid construction

-12106

Internal parser error, analysis aborted

-12107

Syntax analysis resumed here

-12108

Multiple statements not allowed

-12109

Character string literal contains non-ascii character, use nchar literal instead (i.e. N'text')

-12110

Delimited identifier contains non-ascii character

-12111

Delimited identifier contains invalid character

-12112

Delimited identifier contains illegal Unicode character

-12116

The table <%> does not have a generated primary key

-12117

The internal column MIMER_ROWID cannot be altered

-12119

Password string contains non-ascii character

-12120

Table name too long

-12121

String literal too long

-12122

Numeric literal too long

-12123

Invalid password string

-12124

<%> is an invalid hexadecimal literal

-12125

Reserved word may not be used as an identifier

-12126

Invalid name

-12127

Character string literal contains illegal Unicode character

-12128

Result of concatenation too long

-12129

Table definition does not include any column specification

-12131

Table definition includes more than one PRIMARY KEY specification

-12132

Only one column allowed in column list

-12152

<%> not allowed in EXECUTE mode

-12154

User name too long

-12156

Column name too long

-12157

Synonym name too long

-12158

Correlation name too long

-12159

Cursor name too long

-12160

Databank name too long

-12161

Shadow name too long

-12162

Host variable name too long

-12163

File name too long

-12164

Label name too long

-12165

Index name too long

-12166

Object name too long

-12167

View name too long

-12168

Domain name too long

-12169

Too many identifier names given

-12174

Syntax error in escape clause, expecting comma before PRODUCT or CONFORMANCE specification

-12175

Syntax error in escape clause, invalid CONFORMANCE specification

-12176

Syntax error in escape clause, invalid YEAR specification

-12177

Syntax error in escape clause, invalid PRODUCT specification

-12178

Syntax error in escape clause, invalid VENDOR specification

-12179

Syntax error in escape clause, expecting VENDOR or YEAR after '--(*'

-12180

Syntax error, unexpected token '*)--'

-12181

Syntax error in escape clause, terminating '*)--' missing

-12182

Syntax error in escape clause

-12200

Table <%> not found, table does not exist or no access privilege

-12201

Table reference <%> is ambiguous

-12202

<%> is not a column of an inserted table, updated table or any table identified in a FROM clause

-12203

<%> is neither an object table of an INSERT, UPDATE or DELETE statement, nor specified in a FROM clause

-12204

Column reference <%> ambiguous

-12205

Column <%> not referenced in GROUP BY clause

-12207

DISTINCT specified more than once in a subselect

-12208

SELECT clause of a subquery specifies more than one column

-12209

Column <%> identified in HAVING clause but not included in GROUP BY clause

-12210

Operand of set function includes a set function

-12211

NEXT VALUE of sequence not allowed in ORDER BY clause

-12212

Operand of set function includes a correlated reference specified in an expression

-12213

Set function not specified in a SELECT clause or HAVING clause

-12214

Invalid data type used, expected type is <%>

-12215

Operand not of <%> type

-12216

Operands are not comparable

-12217

Set function containing DISTINCT may not be specified within an expression

-12218

Constant expression not allowed in ORDER BY clause

-12219

The length of the trim character expression is not one

-12220

Expression must be a column

-12221

SELECT clause contains both column expressions and set function expressions

-12222

ORDER BY expression contains no valid column reference

-12223

ORDER BY clause invalid because it includes a column name that is not part of the result table

-12224

ORDER BY clause invalid because it includes an integer which does not identify a column of the result table

-12225

The ORDER BY clause is invalid because it includes duplicate column references

-12226

Set function argument not bound in HAVING context

-12227

Duplicate column reference in FOR UPDATE OF clause

-12228

ORDER BY clause must contain only SELECT list items when DISTINCT, GROUP BY or UNION is specified

-12229

Set function not allowed in ORDER BY clause

-12230

Invalid numeric literal

-12231

Update or insert value is null, but the object column <%> cannot contain NULL values

-12232

Insert value must be a constant expression or NULL

-12233

The number of insert values is not the same as the number of object columns

-12234

Insert value not compatible with the column <%>'s <%> data type

-12235

Subquery not allowed in ORDER BY clause

-12236

Column name <%> does not identify a unique column of the result table

-12237

User-defined type <%> not found, does not exist or no usage privilege

-12238

Column <%> cannot be updated because it is derived from a set function or expression

-12239

The use of NULL in a SELECT clause is only allowed in a UNION

-12240

Statement contains too many table references

-12241

Domains not allowed in parameter list

-12242

The corresponding columns of the operands of a UNION do not have compatible column descriptions

-12243

Result table contains a column for which the type cannot be determined

-12244

Operands of a <%> do not have the same number of columns

-12245

FOR UPDATE clause may not be specified because the result table cannot be modified

-12246

Column <%> in the FOR UPDATE clause is not part of the identified table or view

-12250

A host variable or parameter marker is not allowed in a view definition

-12251

CREATE VIEW statement must include a column list because the SELECT clause contains an expression

-12252

CREATE VIEW statement must include a column list because the SELECT clause contains duplicated column name <%>

-12253

The number of columns specified for the view is not the same as specified by the SELECT clause

-12254

WITH CHECK OPTION cannot be used for the specified view because it cannot be modified

-12258

<%> operation not permitted because the view cannot be modified

-12259

<%> operation not permitted because the joined table cannot be modified

-12260

LOAD operation not permitted, as there is a trigger for insert defined on the table

-12261

INSERT statement not permitted because the object column <%> is derived from an expression

-12262

The type of the parameter marker cannot be determined

-12263

Parameter markers and host variables not allowed in EXECUTE IMMEDIATE environment

-12264

Parameter markers may not be specified in SELECT clause

-12265

Literal or computed value overflow

-12266

Decimal divide operation invalid because the result would have a negative scale

-12267

Duplicate column reference in INSERT column list

-12268

Duplicate column reference in UPDATE set clauses

-12269

Duplicate column name specified in column list

-12270

<%> does not have <%> privilege on object <%>

-12271

Duplicate column reference in GROUP BY clause

-12273

The types of the results of a CASE expression are not type compatible

-12274

The type of the CASE expression result cannot be determined

-12275

At least one result in a CASE expression must be non-null

-12277

Invalid CAST data type specification

-12278

Cannot extract <%> field from data type <%>

-12280

<%> is an invalid datetime literal

-12281

<%> is an invalid interval literal

-12282

Invalid interval qualifier

-12283

Invalid use of interval qualifier

-12284

The recursive WITH-clause <%> may only contain a single UNION-clause

-12285

There can only be a single reference to recursive table <%>

-12286

Incorrectly placed reference to recursive table <%>, it may not occur in right side of outer join, in a subquery etc.

-12287

The number of with-clause columns does not match the underlying query select list

-12288

Cycle detected in recursive WITH clause data

-12289

Search and/or cycle-clause may only be used in recursive with-clause

-12290

Locator types may not be passed to client

-12300

Syntax error in escape clause

-12301

Translated native SQL string was truncated

-12302

The function <%> is not supported

-12303

Unrecognized first word, <%> in escape clause expected 'CALL', 'FN','OJ', 'D', 'T' or 'TS'

-12304

Unrecognized scalar function <%>

-12305

Invalid data type <%> in function CONVERT

-12306

Syntax error, incomplete escape clause

-12307

Syntax error, unmatched apostrophe in string literal

-12308

Syntax error, unmatched quote in delimited identifier

-12309

Unknown first parameter <%> in scalar function <%>

-12310

Argument missing in scalar function <%>

-12311

Too many arguments in scalar function <%>

-12330

Statement was not a query

-12331

Statement was not an UPDATE, DELETE or INSERT

-12500

A databank named <%> already exists (or filename already used)

-12501

Table <%> does not exist

-12502

<%> does not have <%> privilege

-12503

<%> does not have <%> privilege on object <%>

-12504

Statement not allowed within transaction

-12505

<%> is not a USER or PROGRAM ident

-12506

No privilege

-12507

<%> does not have any databank available (see CREATE DATABANK)

-12509

An ident cannot REVOKE a privilege from itself

-12510

An ident cannot GRANT a privilege to itself

-12511

Duplicate column specification

-12512

Invalid type description

-12513

The cascade option would cause a drop of the last column <%> for table <%> in schema <%>

-12514

The value for <%> must be less than <%>

-12515

The value of <%> must be <%> than or equal to the value of <%>

-12516

Qualified column name required

-12517

Object <%> does not exist

-12518

Circular grant of membership between groups not permitted

-12519

Invalid type description, <%> length must be between <%> and <%>

-12520

An ident cannot GRANT a privilege to itself

-12521

Create <%> option <%> specified more than once

-12522

Alter <%> option <%> specified more than once

-12523

Databank <%> does not exist

-12524

READ ONLY option only available for ALTER DATABANK

-12525

Alter table option <%> specified more than once

-12526

Default value for NOT NULL column <%> missing

-12527

Constraints and unique indexes must be specified WITHOUT CHECK when the database is set to AUTOUPGRADE

-12528

It is not allowed to create a shadow when the database is set to AUTOUPGRADE

-12529

The database cannot be set to AUTOUPGRADE when there are shadows defined

-12530

Operand not of type <%>

-12531

Operands not comparable

-12532

Invalid option, should be ON or OFF

-12533

Literal or computed value overflow

-12534

Invalid numeric literal

-12535

Invalid identifier, keyword VALUE expected

-12536

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)

-12541

Data pagesize too small for table record length

-12542

Default value is outside the range specified by domain definition

-12543

Index pagesize too small for table key length

-12544

Too many columns specified in <%> statement

-12545

Primary key column <%> may not be updated because the table is in a WORK 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

-12548

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

-12549

Databank option may not be changed to WORK since <%> either contains tables with FOREIGN KEY or UNIQUE constraints or sequences

-12550

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

-12551

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

-12552

A UNIQUE index or a UNIQUE or FOREIGN KEY constraint cannot be created for table <%> as it is located in a databank with WORK option

-12553

Explicit grant membership on PUBLIC is not permitted

-12554

PUBLIC cannot be member of another group

-12555

The option cannot be changed to READ ONLY since <%> contains a table using a current collation

-12556

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

-12557

Shadow named <%> already exists

-12558

Ident named <%> already exists

-12559

There is no index <%> defined for <%>

-12560

Table, view, synonym, index or constraint named <%> already exists

-12561

User-defined type or domain <%> not found, does not exist or no usage privilege

-12562

Only foreign key constraints can be deferrable

-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

-12575

Constraints for generated keys cannot be dropped explicitly

-12577

Default value not compatible with column specification

-12579

No such unique constraint in referenced table

-12580

It is not possible to add new columns to the table since the <%> has an implicit reference to all columns in <%> statement. There may be further dependencies.

-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

-12584

The added constraint is equivalent to a previously defined PRIMARY KEY or UNIQUE constraint

-12585

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

-12586

Data pagesize not supported

-12587

Index pagesize not supported

-12588

Compression <%> not supported

-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 data type for a column cannot be changed to a domain if that domain has any check constraints

-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 or trigger

-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

-12619

The column <%> is not of structured type

-12620

A domain or user-defined type 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 added PRIMARY KEY or UNIQUE constraint cannot be created as there are duplicates

-12625

The added referential constraint is not fulfilled by existing records

-12626

The added check constraint criteria is not fulfilled by existing records

-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 cannot be compared or concatenated

-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 data type large object not allowed in this context

-12644

SQL syntax error, only EXECUTE STATEMENT allowed

-12645

Column of data type 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

-12649

Statement <%> was compiled with an earlier version

-12650

Only the creator of a precompiled statement may alter it

-12651

Invalid syntax in statement invocation

-12562

The constructor function <%> can only be used in a NEW invocation

-12653

A foreign key constraint between <%> and <%> using the same columns and referencing the same key already exists

-12654

It is not possible to create a special index on a table that has fixed format

-12655

It is not possible to alter table to fixed format since there is a special index defined on the table

-12660

No column result set

-12661

The data type list does not match any routine

-12662

There is no matching <%> with the specified number of parameters

-12663

Invalid type description, <%> precision must be between <%> and <%>

-12664

Invalid type description, <%> fraction must be between <%> and <%>

-12665

It is not possible to cast data with type <%> to <%>

-12666

It is not possible to assign data with type <%> to <%>

-12667

It is not possible to assign data with types <%> and <%>

-12668

It is not possible to concatenate <%> data and <%> data

-12669

It is not possible to use arithmetic operations on data with types <%> and <%>

-12670

Support for structured user-defined types is not included in this version

-12671

Support for read only databanks is not included in this version

-12672

Support for this diagnostic item is not included in this version

-12673

CURRENT_COLLATION not allowed for column in unique constraint

-12674

CURRENT_COLLATION not allowed for column in primary key

-12675

CURRENT_COLLATION not allowed for column in unique index

-12676

Collation <%> may not be used as base since it is binary

-12678

INSERT columns must be specified when CREATE STATEMENT, i.e. INSERT INTO table (column-list) ...

-12679

SELECT * not allowed when CREATE STATEMENT, specify selected columns (at top level)

-12680

An ident may not drop himself

-12681

CASE expression's return values have different collating sequences

-12682

Columns defined as structured user-defined types cannot be used in constraints or indexes

-12683

Invalid combination of sequence attributes

-12684

The column <%> has invalid type for a PINYIN index, must be NCHAR or NCHAR VARYING

-12685

Invalid <%> value specified for column <%>

-12686

Unable to determine result type for expression, use syntax: (datetime1 - datetime2)interval qualifier, for example: (date '2018-03-04' - date'1634-01-06')year(3) to month

-12687

Invalid <%> value specified

-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

-12716

A locator can only be declared for a lob type

-12717

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

-12718

The scale cannot exceed the precision

-12719

A lob type can only be used in PSM if it is declared as a locator

-12720

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

-12721

The parameter <%> must be declared as IN as it is defined in a function, method or result set procedure

-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 set 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

Incorrect number of items in return statement, <%> expected

-12735

Incorrect number of parameters, <%> expected when invoking routine <%>

-12736

Invalid type for argument, <%> expected

-12737

Too long name <%>

-12738

Duplicate declaration <%>

-12739

x.y.z names not allowed

-12740

There is no matching start label for the ending label <%>

-12741

The label or routine <%> is not defined

-12742

The label <%> is not defined

-12743

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

The use of a domain (<%>) is invalid in this context

-12748

Operands are incompatible

-12749

The SQL module <%> already exists

-12750

There already exists a procedure named <%> having the same parameters

-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

The cursor <%> is declared as not scrollable, only next is allowed as fetch direction

-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 an update or delete where current statement

-12765

The cursor is declared as read only and cannot be used in an 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

-12780

<%> is an invalid argument for the signal statement, only integer values allowed

-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 for the variable <%>

-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

-12786

A parameter specified as RESULT is not allowed in <%>

-12787

If a RESULT parameter is specified the return data type for the SQL invoked function must be a structured user-defined type and the same as the data type for the parameter

-12788

There can only be one RESULT parameter for an SQL invoked function

-12789

The data type for a parameter defined as RESULT must be a structured user-defined type and it must be the same as the data type returned by the SQL invoked function

-12790

The function <%> can not be altered since it is used as an ordering function for the structured user-defined type <%>. The function must be deterministic and the return data type must be a predefined data type excluding large objects.

-12791

The function <%> can not be altered since it is used as an ordering function for the structured user-defined type <%>. The function must be deterministic and the return data type must be an integer.

-12792

The collating sequence for the parameter <%> is different from the collating sequence used in the method specification

-12793

The collating sequence for the return data type is different from the collating sequence used in the method specification

-12794

The schema names for the dropped method and the user-defined type are not equal

-12795

Specifying a value by using the keyword DEFAULT is only allowed in INSERT and UPDATE statements

-12796

Specifying a value by using the keyword NULL is only allowed in INSERT and UPDATE statements or in a cast expression

-12797

It is not allowed to use the builtin.serialize function on a record that is part of another record

-12798

The result of the builtin.deserialize function cannot be assigned to a record that is part of another record

-12800

Functionality not supported: <%>

-12801

Referencing OLD <%> is not allowed if trigger event is INSERT

-12802

Referencing NEW <%> 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 cannot be INSTEAD OF

-12810

Only the creator of a table can create a trigger for the table

-12811

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

-12812

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

-12813

A trigger named <%> already exists

-12814

Sequences cannot be created in a databank with WORK option

-12815

The OS_USER name already exists for this ident

-12816

The OS_USER does not exists for this ident

-12817

Add or drop OS_USER is only allowed for idents defined as USER

-12818

Drop password is only allowed for idents defined as USER

-12819

The view cannot be used in an Experience server since it uses functionality that is specific to an Engine server

-12820

The statement <%> is invalid because it could not be upgraded from an earlier version of Mimer SQL

-12821

It is not possible to change the name of a parameter when altering a routine

-12822

The alter routine statement would cause the loss of grant option for execute on the routine. This is due to the presence of statements that uses a privilege which is held without grant option. The first reference of this type is <%> privilege on <%> <%>.

-12823

The data type for a parameter declared as RESULT must be the same as the data type in the returns clause

-12824

It is not possible to alter the returns data type to an incompatible data type or to change the number of result items since there are objects using this routine. The first such object is the <%> <%>.

-12825

The return data type for the function <%> can not be changed since there is a relative ordering for the user-defined type <%> using this function. The return type must be an integer type.

-12826

The alter routine is not allowed. If a return statement is present in the routine body a returns clause must also be given.

-12827

The alter operation is invalid since the routine is declared as deterministic but it contains expressions that are not deterministic

-12828

A null call clause can not be specified for a procedure

-12829

Routine attributes or specific name for a method can only be changed by altering the method specification. A method specification is altered by using the ALTER TYPE statement.

-12830

There already exists a function named <%> having the same parameters

-12831

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. This is violated as <%> privilege on the <%> <%> is not held with grant option.

-12834

Sequence <%> does not exist, or no privilege

-12835

A sequence named <%> already exists

-12836

The keyword NULL cannot be used <%>

-12837

The operands to an 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

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

A constraint named <%> 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

References to LOB columns in the NEW table in an instead of trigger is not allowed

-12857

The label <%> cannot be used for an iterate statement

-12858

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

-12859

Creation of recursive statements is not supported

-12860

No user-defined type or domain named <%> is defined

-12861

The attribute name <%> is already specified in this user-defined type or in a supertype

-12862

INSTANTIABLE or NOT INSTANTIABLE cannot be specified for a distinct type

-12863

FINAL or NOT FINAL cannot be specified for a distinct type

-12864

A type cannot be FINAL and NOT INSTANTIABLE

-12865

The default value for the attribute is invalid

-12866

There already exists a routine with specific name <%>

-12867

Parameters for functions and methods may not be specified as IN explicitly

-12868

A parameter name for the routine is missing

-12869

The type attribute <%> specified multiple times

-12870

No specification for the method <%> was found

-12871

The parameter type does not match method specification for <%>

-12872

The parameter name <%> does not match the name used in method specification

-12873

A type name must be specified

-12874

A method must be created in the same schema as the type

-12875

A type binding can only be specified for methods

-12876

A structured type must be declared as FINAL or NOT FINAL

-12877

When creating a user-defined type it is not possible to use that type as the data type for an attribute or as a supertype in an under clause

-12878

No <%> method specification exists

-12879

The method does not have the same return data type as the method specification

-12880

SELF is not allowed as parameter or variable name in an instance method

-12881

A method named <%> is already defined for this user-defined type

-12882

A method specification named <%> with equal parameters is already defined for this user-defined type or for a subtype or supertype

-12883

The type for the parameter <%> does not match the method specification

-12884

Type user-defined <%> does not exist or no usage privilege

-12885

As the type <%> is declared as NOT INSTANTIABLE it cannot be used when defining columns or variables

-12886

The method specification <%> does not have a returns clause

-12887

The schema name for the type <%> and the method specification are not the same

-12888

<%> is a static method and must be invoked with the syntax typename::method

-12889

<%> is an instance method and must be invoked with the syntax object.method

-12890

There is no method <%> defined for the type, or no execute privilege

-12891

The attribute <%> does not exist in the type <%>

-12892

The subject routine for <%> cannot be determined, there exists multiple routines with the same name. Provide more specific data types

-12893

The method specification for <%> cannot be determined, there exists multiple method specifications with the same number of parameters but none matching the data types for this method definition

-12894

The distinct type cannot be created since there exists a function with the name <%> and one parameter having the same type

-12895

The object <%> has been created implicitly and cannot be altered or dropped

-12896

A constructor method can only be defined for a structured user-defined type

-12897

A constructor method must have the same name as the user-defined type

-12898

A constructor method must have the same return type as the user-defined type, <%> does not fulfill this requirement

-12899

<%> is a constructor method and must be invoked using the new operator

-12900

The attribute name is the same as an existing routine

-12901

Source as distinct is only valid for distinct types

-12902

Multiple source as distinct or distinct as source clauses not allowed

-12904

Order full not allowed for state orderings

-12905

There is no EQUALS ordering defined for the type <%>, comparison not allowed

-12906

Not allowed to create or drop ordering for distinct type

-12907

The user-defined type does not have any ordering

-12908

There is already an ordering defined for this type

-12909

<%> orderings are not supported

-12910

A function named EQUALS with the same parameter types already exists

-12911

There is no FULL ordering defined for the type <%>, comparison not allowed

-12912

Distinct as source is only valid for distinct types

-12913

Only method specifications can be dropped with the alter type statement

-12914

CASCADE not allowed for alter type or alter routine

-12915

Cast to and from structured types not allowed

-12916

Not possible to add or drop attributes for a distinct type

-12917

Only the creator of a user-defined type may alter it

-12918

Not allowed to add or drop attribute to this type as it is used as the data type for a column

-12919

The addition of the attribute would cause a circular dependency

-12920

<%> is the last attribute for the type and cannot be dropped

-12921

The cursor <%> is declared in a for statement and cannot be used explicitly

-12922

All items in the select list in a for statement must be named

-12923

Duplicate name <%> in select list in for statement

-12924

All result items for a result set procedure must have a name when used in a for statement

-12925

Duplicate result item name <%> for result set procedure which is not allowed when used in a for statement

-12926

Locators can only be compared with = or <>

-12927

Locators cannot be used in expressions

-12928

The information item <%> has already been specified

-12929

<%> is not a constructor function, and cannot be invoked using the new operator

-12930

The constructor function for the user-defined type <%> cannot be created since there already exists a function with the same name and parameters

-12931

The default value for <%> is not within the range of the data type

-12932

The literal value <%> is outside the valid range for the data type of the variable <%>

-12933

The schema for the user-defined type does not match the schema for the method

-12934

As the type <%> is distinct, a new specification is not allowed

-12935

There is no method specification for the type <%>, with the number of parameters used in the create method statement

-12936

Invalid type for argument number <%>, expected <%> when invoking routine <%>

-12937

Invalid type for argument number <%>, expected <%> in operation <%>

-12938

<%> has already been specified

-12939

Ident <%> is not authorized to create external routines

-12940

The host variable <%> is used in multiple contexts where the data types are incompatible

-12941

The host variable <%> will be assigned multiple times

-12942

The host variable <%> has inconsistent use of indicator variables

-12943

The special column MIMER_ROWID cannot be accessed in a before row trigger

-12944

<%> cannot be modified as it is defined as a large object

-12945

The definition for the index <%> contains multiple type clauses which is not allowed

-12946

The column <%> has an invalid data type. If the index type is <%> only <%> is allowed

-12947

The index <%> is defined as unique, which is not allowed for index type <%>

-12948

The data type of <%> is not compatible with the data type of <%>

-12949

<%> is a field in the old row variable in a trigger and cannot be assigned

-12950

It is not allowed to specify size for a locator

-12951

The type <%> is not instantiable

-12952

No UNDER privilege on type <%>

-12953

The type <%> is final and cannot be inherited from

-12954

A distinct type cannot have an under clause

-12955

The type <%> is distinct and cannot be inherited from

-12956

A state or relative ordering cannot be defined for an inherited type

-12957

The routine <%> cannot be used as an ordering function. A map ordering function should have one parameter with the same type as the user-defined type for which the ordering is defined and the return type must be a predefined data type. The function must also be deterministic and cannot modify SQL data.

-12958

The routine <%> cannot be used as an ordering function. A relative ordering function should have two parameters with the same type as the user-defined type for which the ordering is defined and the return type must be integer. The function must also be deterministic and cannot modify SQL data.

-12960

The type <%> must be a subtype of <%> (the type of the left operand) when used in a type predicate or treat expression

-12961

The overriding attribute cannot be specified for a method specification defined as static or constructor, it is only allowed for instance method specifications

-12962

There is no matching original method specification for <%> in any supertype of <%>

-12963

The method <%> is an observer or mutator method in a supertype of <%> and cannot be overridden

-12964

The attribute <%> is inherited and cannot be dropped

-12965

A realtime aggregation for this statement already exists

-12966

The statement <%> can not be used for realtime aggregation since it is not of type select;

-12967

The interval value <%> does not match the data type <%>, expected format is <%> with each field in the valid range

-12968

You are not authorized to create an external library

-12969

There already exists a library with the name <%>

-12970

There already exists a library with the name <%> already used by another library

-12971

The interval value <%> is invalid. The maximum value for the <%> field in an <%> is <%>.

-12972

The interval value <%> is too large with regard to the given precision

-12973

The library <%> does not exist or you are not authorized to use it

-12974

The value <%> does not match the data type <%>, expected format is <%> with each field in the valid range

-12975

Invalid access mode NO SQL specified for the routine <%>. NO SQL is only allowed for external routines.

-12976

The file <%> is not defined for the databank <%>

-12977

<%> is the last remaining file for the databank <%> and cannot be dropped

-12978

There already exists a file named <%> for the databank <%>

-12979

It is not allowed to add files for the SYSDB databank

-12980

At most 15 files can be specified for a databank

-12981

As the databank <%> has multiple files it is not possible to change a file specific option without specifying a file name. Use the ALTER DATABANK ... ALTER FILE ... statement instead.

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

-14007

The option for the databank cannot be changed since a backup of the databank is active

-14008

The option for the databank cannot be changed since there are shadows defined on the databank

-14009

Operation is not allowed when a transaction is active

-14010

Operation is not allowed in an atomic execution context

-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

-14028

The routine <%> tries to modify SQL data which is not allowed with the current access mode

-14029

The routine <%> tries to read SQL data which is not allowed with the current access mode

-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

-14061

Cursor has been invalidated by a conflicting system administration statement

-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

-14212

The external routine <%> was not found

-14213

Error when executing external routine <%>
Error code from routine: <%>

-14214

The number of parameters does not match the external routine

-14215

The data types of the parameters do not match the definition of the external routine

-14216

Invalid databank option, valid options are READ ONLY, WORK, TRANSACTION or LOG

-14217

The global variable <%> has not been assigned

-14218

The global variable <%> which is declared as <%> cannot implicitly be converted to <%>

-14219

Cannot open external library <%> in file <%>, <%>

-14220

The external routine <%> was not found, <%>

-14221

Error when executing external routine <%>, <%>

-14222

The version number of external library <%> is not compatible with the database server. Please recompile the library.

-14223

Illegal format character for a parameter in external routine <%>

-14224

The initiation routine in external library <%> did not call init()

-14225

The format character for a parameter does not support the specified database type

-14226

Memory allocation for stream failed

-14227

It is not possible to add more data to this stream since it has been assigned to a routine parameter

-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

Server name, username, password or connection name too long

-14315

Illegal byte length of floating point number

-14316

Unterminated C string, null byte not found

-14318

Username or password too long

-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 use update where current for table <%> since the cursor is read-only

-14405

Cannot use delete where current for table <%> since the cursor is read-only

-14406

Unexpected statement type encountered in an UPDATE or DELETE statement

-14410

Update or delete where current is not allowed for tables located in a databank with WORK option

-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 when executing a function or method

-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 the trigger <%>

-14720

All possible values for the sequence <%> has been used, no more values can be generated.

-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 cannot be used with result set procedures

-14726

A realtime control structure (RTCS) could not be found

-14727

The databank containing the sequence is set to WORK mode, new values cannot be generated.

-14728

The operation is not allowed as the databank is temporarily set to WORK option

-14729

Table % has a UNIQUE constraint and cannot be updated while the databank option is set to WORK

-14730

Table % is involved in a FOREIGN KEY constraint and cannot be updated while the databank option is set to WORK

-14731

The primary key columns of table % cannot be updated while the databank option is set to WORK

-14732

Bind is attempted within an active transaction

-14733

The parameter value for the function builtin.uuid_from_text is invalid. The expected value is a string in the format HHHHHHHH-HHHH-HHHH-HHHH-HHHHHHHHHHHH, where each H is a hexadecimal value specified by using the symbols 0-9 and A-F.

-14734

The target area for the result of the method as_text for the distinct type builtin.uuid is too short, minimum length is 36.

-14735

When converting to coordinate, location etc. the binary length must match the underlying type

-14801

The type for an instance in a treat expression is not among the subtypes of <%>

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

-16007

Databank <%> is read only, data modifications are not allowed

-16008

Sequence <%> is located in a read only databank, new values cannot be generated

-16009

Sequence <%> is located in a databank which is offline, new values cannot be generated

-16010

The table <%> cannot be recreated since no dictionary information has been saved

-16011

The requested operation cannot be executed until previous change operation for <%> has completed

-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 SQL databank

-16153

Data no longer available, storage device has been removed

-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 SQL 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 Mimer 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. Configured number of users exceeded.

-16219

Too many Mimer databases 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

-16237

Unable to load collation information for tableid = <%>

-16239

Databank <%> maximum size reached, unable to insert more data

-16240

The option for databank <%> is not supported

-16241

The allocated real-time control structures have been exhausted.

-16242

An attempt was made to bind a pointer to a compressed table

-16243

Disk full will be reached for databank <%>, unable to insert more data

-16244

The page on which the real-time data value resides is currently updated elsewhere

-16245

The page checksum is invalid when reading page

-16248

Databank <%> not available, probably removed storage device

-16249

Databank LOGDB maximum size reached, unable to handle more data

-16250

Databank TRANSDB maximum size reached, unable to handle more data

-16251

Databank SQLDB maximum size reached, unable to handle more data

-16252

Invalid database pointer type

-16253

Invalid database pointer policy

-16254

Incompatible database pointer type

-16255

The result set partially overlaps a previously bound multirow database pointer

-16256

The column set does not match a previously bound multirow database pointer

-16257

Incompatible database pointer policy

-16258

Cannot lock realtime pages in memory, bufferpool region exhausted

-16259

An attempt to delete a non-existing database pointer

-16262

An attempt was made to bind a pointer to a variable format table

-16263

Bufferpool memory exhausted for blocksize <%>

-16264

One of the files for databank <%> does not match the other files in databank file set

-16265

Not all files in multi-file databank <%> are open yet

-16266

The file number for the multi-file databank <%> is incorrect

-16267

The attempted operation for the databank <%> is not supported as the databank consists of several files

-16268

Missing a file for databank <%>, please add it with ALTER DATABANK ADD FILENAME

-16269

Too many files for databank <%>, please drop extra file with ALTER DATABANK DROP FILENAME

-16401

Routine cannot be dropped because it is in use

-16402

Routine cannot be used because it is being altered or 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 SQL 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 SQL

-18010

Invalid log record found during restore operation

-18011

Mismatching version of Mimer SQL 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 SQL 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

-18031

A more recent version of BSQL is required to redefine system databanks

-18032

An older matching version of BSQL is required by the server to redefine system databanks

-18041

Update of primary key columns for a table located in a databank, with WORK 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

-18046

WITH HOLD cursors cannot be used in XA transactions

-18047

Update or delete where current cannot modify a row that was fetched outside the current transaction

-18048

Cannot set databank option because a WITH HOLD cursor is open

-18049

Cannot set databank option because XA transaction are used

-18050

Cannot set databank option while LOAD operation is active

-18051

Cannot START LOAD because databank has temporary WORK option

-18052

Cannot use XA transactions when temporary WORK option is used

-18053

Connection rejected by server. The server security level requires the client version to be 11.0 or later.

-18054

Cannot get exclusive access to external library <%>.

-18055

Cannot open external library <%>, because it is locked

-18057

Could not set up access to external library <%>. Failed to call the initialization routine xlib_init in file <%>.

-18058

Symbol <%> not found in external library <%>, <%>

-18101

Operation not allowed. SHADOW license required

-18102

Operation not allowed. Mimer SQL license required

-18103

Operation not allowed. Mimer SQL Level2 license required

-18107

Operation not allowed. Beta test version of Mimer requires BETA license.

-18108

Cannot find a valid Mimer SQL license key

-18109

Operation not allowed. XA, distributed transaction license required

-18110

Operation not allowed, 64 bit license required

-18111

Operation not allowed, immediate restart license required

-18112

Operation not allowed, in-memory server license required.

-18121

Operation not allowed. VAR specific Mimer license required

-18122

Authorization failure. Invalid attempt to connect

-18201

SYSDB cannot be backed up using CREATE BACKUP without an ONLINE shadow

-18231

<%> records dropped from LOGDB

-18232

Shadow <%> is OFFLINE

-18233

Unable to access databank <%>, because it is OFFLINE

-18234

Error <%> occurred when trying to access shadow <%>

-18235

Error <%> occurred when trying to access databank <%>

-18236

Statistics updated for <%> tables

-18237

Databank <%> does not have LOG option

-18238

<%> records copied to incremental backup

-18239

Unable to CONNECT, because database is OFFLINE

-18240

Unable to CONNECT, because database is OFFLINE and one connection already exists

-18241

Unable to CONNECT, because SYSDB is OFFLINE

-18242

Unable to CONNECT, because SYSDB is OFFLINE and one connection already exists

-18243

Unable to access databank <%>, because database is OFFLINE

-18244

Could not get exclusive access to the database because one or more connections already exists

-18245

Could not connect to database <%>, a system administrator is executing a statement that requires exclusive access to the database

-18246

The bind-query contains multiple statements

-18247

The bind-query points to several columns

-18248

The bind-query points to several rows

-18250

The bind-query contains input parameters

-18251

The bind-query includes a scroll cursor

-18252

The bind-query is not a SELECT statement

.18253

Table Information Package mismatch

-18254

An attempt was made to bind a pointer to a primary key

-18255

An attempt was made to bind a pointer to an indexed data element

-18257

The bind-query contains a join or subselect

-18258

An update elsewhere is not yet written to stable storage

-18259

The user does not have enough privilege to perform flush

-18260

Timeout when setting CURRENT COLLATION

-18261

No critical section objects available

-18500

Database <%> not found in SQLHOSTS file

-18501

Database <%> unknown on remote node <%>

-18502

Handshake message invalid, incompatible protocol <%>

-18503

Only remote databases are allowed, specify database which is not local

-18504

The network server version of database <%> is not compatible

-18505

Local memory pool in network server exhausted (SQLPOOL)

-18506

In the current version only one local (and several remote) databases can be connected at a time

-18507

Unknown connection name <%> specified

-18508

Already connected to database <%>

-18509

Database name <%> invalid, too long or contains invalid characters

-18510

Connection name invalid, too long or contains invalid characters

-18512

Illegal reentrant call

-18513

Use another TCP/IP port number

-18514

Too deep address indirection

-18515

Cannot get value of thread-local variable

-18516

The network server version does not support Level2

-18517

MIMER_DATABASE cannot be read

-18518

Catalog version from beta test. See Release Notes, how to upgrade.

-18519

Erroneous contents in SQLHOSTS

-18521

Error opening SQLHOSTS, filename syntax error

-18522

Error opening SQLHOSTS, file not found

-18523

Error opening SQLHOSTS, file protection violation

-18524

Error opening SQLHOSTS, file locked

-18525

Error opening SQLHOSTS, too many opened files

-18526

Error opening SQLHOSTS, file create error, disk space exhausted

-18527

Error opening SQLHOSTS, other error (-7)

-18528

Error opening SQLHOSTS, other error (-8)

-18529

Error opening SQLHOSTS, other error (-9)

-18530

Error opening SQLHOSTS, illegal access options

-18531

Client/server communication must be encrypted, but client does not support this

-18550

Invalid network package format

-18551

Unknown request code in network package (<%>)

-18552

Network package longer than expected

-18553

Internal data structures corrupt (DSNEE4)

-18554

The UTILITY program does not have client/server support

-18555

Client is using a deprecated function in the server (<%>)

-18594

Query timeout period expired

-18595

Network partner disconnected

-18601

Could not connect to database <%>, unknown node '<%>'

-18602

Could not connect to database <%>, unknown protocol '<%>'

-18603

Could not connect to database <%>, unknown interface '<%>'

-18604

Could not connect to database <%>, unknown service '<%>'

-18605

Could not connect to database <%>, chosen protocol not supported on ALPHA/VMS '<%>'

-18606

Could not connect to database <%>, network type not supported '<%>'

-18607

Could not connect to database <%>, remote node is unreachable '<%>'

-18608

Bad parameter NETID=<%> passed to network package

-18609

Invalid parameter RECLEN=<%> passed to network package

-18610

Invalid parameter BUFFER=<%> passed to network package

-18611

Too many concurrent network connections

-18612

Connection refused '<%>'

-18613

Unexpected network event '<%>'

-18614

The underlying network protocol does not have enough capabilities '<%>'

-18615

Network service busy '<%>'

-18616

Local or remote system resources are insufficient '<%>'

-18617

Connection timed out '<%>'

-18618

Insufficient privileges for attempted network operation '<%>'

-18619

Unexpected network error '<%>'

-18620

Network operation would block (asynch mode)

-18621

Could not load network library

-18622

Required routines missing from network library

-18901

Database <%> not available on node <%>

-18902

Mimer logins are currently disabled, try again later

-18903

Access denied to Mimer multi-user system

-18904

Unable to attach to multi-user system, no response

-18905

Operation not allowed. Licensed number of users exceeded

-18906

Invalid database path

-18920

Machine dependent error-18920

-18921

Machine dependent error-18921

-18922

Machine dependent error-18922

-18923

Machine dependent error-18923

-18924

Machine dependent error-18924

-18925

Machine dependent error-18925

-18926

Machine dependent error-18926

-18927

Machine dependent error-18927

-18928

Machine dependent error-18928

-18929

Machine dependent error-18929

Internal Errors

These errors arise from malfunction in internal Mimer SQL routines. Contact your Mimer representative for help.

Number

Explanation

-19001

Program level list corrupt

-19002

No program level found

-19003

Statement list corrupt

-19004

Output parameter list corrupt

-19005

Table list corrupt

-19006

Unable to find log file, LOGDB corrupt

-19007

Inconsistency detected when trying to update dictionary

-19008

Unable to open SYSTEM base tables

-19009

Dictionary table SYSTEM.USERS corrupt

-19010

Unable to extract correct information from SYSTEM.DATABANKS

-19011

Unable to extract correct information from SYSTEM.TABLE_CONSTRAINTS

-19012

Dictionary mismatch found for table with TABLE_SYSID = <%>

-19015

Sysid record in SYSTEM.OBJECTS not found

-19016

Function not supported <%>

-19017

Invalid MAE program

-19018

Invalid operation code PC=<%>

-19019

Pattern not compiled due to invalid MAE instruction sequence

-19020

Invalid function code passed to instruction <%>

-19021

No databank control block found for <%>

-19022

Bad function code passed to DSCDB3

-19023

Invalid pointer to naming structure

-19024

Severity message program corrupt

-19025

Invalid table descriptor

-19026

Invalid table descriptor, log status invalid

-19027

Base table must be opened before index tables

-19028

Table root entry not found

-19029

Unable to change position on write set because no mark is set

-19030

Invalid length for allocation of program space

-19031

Invalid table type

-19032

No table control block found

-19033

Cannot delete databank file outside transaction

-19034

Bad function code passed to DSCRD2

-19035

Invalid index descriptor

-19036

Error detected when closing table, hash chain corrupt

-19037

Invalid internal table type encountered

-19038

Write set inconsistency encountered

-19039

Invalid internal statement identifier

-19040

Invalid internal system identifier

-19041

Invalid internal user identifier

-19042

The static statement cannot be compiled because it is already identified with some other statement

-19043

The statement cannot be prepared because it is already identified with a static statement

-19044

Transaction control block chain corrupt

-19045

Shadow <%> cannot be transformed because it is OFFLINE

-19046

Databank <%> is referenced but not opened

-19047

Table has not been opened with sufficient access to allow current operation

-19048

Databank <%>, no shadow is found in dictionary with sequence number = <%>

-19049

The internal update operation has not been prepared with the old record

-19050

Catalog version not compatible with server

-19051

Compiled LIKE pattern corrupt

-19052

Could not store lookup path, inconsistency detected

-19053

Output descriptor overflow

-19054

Unable to initialize database system

-19055

Unable to generate an internal key

-19056

Inconsistent user identifier (not logged in)

-19057

Scroll program corrupt

-19058

Extended name not supported in static SQL

-19059

Invalid error message descriptor

-19061

Loss of significance for VARCHAR length

-19062

Positive overflow for VARCHAR length

-19063

Negative overflow for VARCHAR length

-19065

Bad parameter for VARCHAR length

-19066

Illegal operand for VARCHAR length

-19067

Bad record number

-19068

No matching record

-19069

Corrupt cancel state

-19071

Unrecognized data types for conversion

-19072

Invalid read set record

-19073

Insufficient internal descriptor area

-19074

Internal inconsistency encountered in TCACHE

-19075

Invalid internal DDU identifier

-19076

Internal inconsistency encountered in table list

-19077

Internal inconsistency encountered in DU1

-19078

Invalid parameter encountered in MOS

-19079

Internal inconsistency encountered in DSETH3

-19080

Thread initialization failure

-19081

Hash table missing in system control block

-19082

Internal inconsistency encountered in DSGSH2

-19083

Internal inconsistency encountered in MCOMEM

-19084

Runtime assertion failed

-19085

Invalid descriptor encountered on server

-19086

Invalid statement status encountered on server

-19087

PSM debugger resources already allocated

-19088

PSM debugger resources already deallocated

-19089

Invalid parameter encountered in DDU

-19091

Invalid function code passed to routine

-19092

Invalid function code 2 passed to routine

-19093

Invalid function code 3 passed to routine

-19094

Failed to create login response message or validation

-19101

Not valid conversion of data types

-19102

Not supported data type conversion

-19103

Initialization failure for data type conversion

-19111

STMs for called statements remaining after disconnect

-19112

Release of statements terminated due to error <%>

-19113

Nonexistent parameter specified

-19114

Specified collation not found

-19115

LOB identification not found in directory table

-19116

No LOB column in parameter list

-19117

LOB start position out of bounds

-19118

Client and server disagreed on LOB length

-19119

Internal truncation error encountered in Mimer client driver

-19122

Failed to load name information package for system id=<%>

-19123

Failed to load table information package for table id=<%>

-19124

Failed to load domain information package for domain id=<%>

-19125

Cannot commit transaction for WITH HOLD

-19126

WITH HOLD resource mismatch

-19127

Not allowed to use CURRENT_COLLATION

-19128

Large objects not supported by current server type

-19129

Internal inconsistency detected by SQL optimizer in <%>

-19130

Could not insert LOB value due to a LOB identification failure

-19131

Internal LOB length inconsistency

-19132

Invalid sequence of internal LOB operations

-19201

System error: <%>- Area outside MAE data storage

-19202

System error: <%>- Attempt to qqwsal() in closed area

-19203

System error: <%>- Cost value out of range

-19204

System error: <%>- Error converting into Mimer format

-19205

System error: <%>- Error from MDRCCI call

-19206

System error: <%>- Error when reading databank option

-19207

System error: <%>- Expression switch case not recognized

-19208

System error: <%>- Factor was left unused

-19209

System error: <%>- Failed to get a slave RST

-19210

System error: <%>- Generation stack underflow

-19211

System error: <%>- Group is not allocated

-19212

System error: <%>- Host variable not defined

-19213

System error: <%>- Host variable number mismatch

-19214

System error: <%>- Illegal Set Func. mode switch case

-19215

System error: <%>- Illegal Status switch case <%>

-19216

System error: <%>- Index table not found

-19217

System error: <%>- Invalid base pointer

-19218

System error: <%>- Invalid object type

-19219

System error: <%>- Invalid pointer

-19220

System error: <%>- Main switch case not recognized

-19221

System error: <%>- Multiple offset assignment

-19222

System error: <%>- Multiple restriction groups

-19223

System error: <%>- No area opened

-19224

System error: <%>- Nonexistent member

-19225

System error: <%>- No Tbl_desc for SCO

-19226

System error: <%>- NOT stack overflow

-19227

System error: <%>- NOT stack underflow

-19228

System error: <%>- Offset outside MAE data storage

-19229

System error: <%>- qqcbix() with illegal operator

-19230

System error: <%>- qqcunx() with illegal operator

-19231

System error: <%>- Error from MDRCFC call

-19232

System error: <%>- qqrlst() with NULL list

-19233

System error: <%>- qqwlst() with NULL list

-19234

System error: <%>- Query result stack underflow

-19235

System error: <%>- Query stack underflow

-19236

System error: <%>- Rule matrix index out of range

-19237

System error: <%>- Scan kind not implemented

-19238

System error: <%>- Scan stack underflow

-19239

System error: <%>- Selectivity factor value out of range

-19240

System error: <%>- Semantic stack underflow

-19241

System error: <%>- Set range violation

-19242

System error: <%>- Set size incompatibility

-19243

System error: <%>- Stack underflow

-19244

System error: <%>- Statement switch case not recognized

-19245

System error: <%>- Switch case not recognized

-19246

System error: <%>- Too complicated UNION query

-19247

System error: <%>- Too many nested subqueries

-19248

System error: <%>- Traversal stack underflow

-19249

System error: <%>- Unexpected EXPRESSION in HOST variables

-19250

System error: <%>- Unexpected expression operand

-19251

System error: <%>- Unexpected expression subtype

-19252

System error: <%>- Unexpected node class

-19253

System error: <%>- Unexpected SELECT ITEM

-19254

System error: <%>- Unexpected statement subclass

-19255

System error: <%>- Unexpected DD return code <%>

-19256

System error: <%>- Unknown Host Variable type

-19257

System error: <%>- Unknown statement type

-19258

System error: <%>- WS stack overflow

-19259

System error: <%>- X stack overflow

-19260

System error: <%>- X stack underflow

-19261

System error: <%>- Error logging is not enabled

-19262

System error: <%>- Source position line or column is negative

-19263

System error: <%>- Message insert string too long

-19264

System error: <%>- Error logging is already enabled

-19265

System error: <%>- MAE constant storage overflow

-19266

System error: <%>- Selectivity rule number out of range

-19267

System error: <%>- No entry for index id

-19268

System error: <%>- qqcfnx() with illegal operator

-19269

Unexpected duplicate row found in temporary table

-19270

System error: <%>- Scan queue underflow

-19271

System error: CPL - PSM depth overflow

-19280

System error: <%>- Error from MDRTDC call

-19290

Out of memory

-19291

Invalid attribute type

-19292

Error when trying to store procedure in dictionary

-19293

Error when trying to share program

-19300

<%> unhandled production

-19301

Internal inconsistency detected in PSM

-19302

The syntax in the view definition is not allowed when with check option is used

-19303

Recursive or cycle temporary table operation failed unexpectedly

-19310

Internal error: Invalid stream type

-19311

Internal error: Invalid stream handle

-19312

Internal error: Stream handle is in use and cannot be dropped

-19901

Function not yet implemented

Communication Errors

When an application has received a communication error, the connection will become unusable. The only valid operation on that connection will be DISCONNECT.

Error codes from the communication kernel layer (network routines):

Number

Explanation

-21001

Already listening on service <%>

-21002

Error trying to ASSIGN channel for TCP/IP communication

-21003

Error when creating socket

-21004

Error when binding socket address for service <%>

-21005

Error when connecting to database <%>, could not get port number for service <%>

-21006

Error when connecting to database <%>, unknown protocol <%>

-21007

Error when connecting to database <%>, unknown node <%>

-21008

Error when connecting to database <%> on <%> using <%> to service <%>

-21009

Illegal channel id specified

-21010

Error when reading data from network channel

-21011

Error when writing data to network channel

-21012

Channel is not open

-21013

Channel is not accessible from this process

-21014

Error when creating mailbox

-21015

Error when declaring network object for service <%>

-21016

Unimplemented feature

-21017

Error when accepting new channel

-21018

Error when doing local listen for database <%> on path <%>

-21019

Too many channels used

-21020

Multiple read requests on channel

-21021

Multiple write requests on channel

-21022

Local write when not owning buffer

-21023

Cancel request illegal on channel

-21024

No available channel id number

-21025

Tried to open too many local servers

-21026

Database server for database <%> not running

-21027

Incompatible buffer versions

-21028

Failed to do a LOCAL connection to the server for database <%>

-21029

Illegal reentrant request on channel

-21030

Network request would block caller

-21031

Too large network I/O requested

-21032

Could not find DSINI4 in single-user library

-21033

Could not find DSHND4 in single-user library

-21034

Could not find DSGMD4 in single-user library

-21035

Could not find DSUMP4 in single-user library

-21036

The channel is closed

-21037

The specified network interface is not supported

-21038

Could not lock communication buffers in memory

-21039

Error trying to ASSIGN channel for DECNET communication

-21040

Could not map library for single-user mode

-21041

Could not initialize CK package

-21042

Error when performing initial communication with database server

-21043

Server rejected connection to database <%> on <%> using <%> to service <%>

-21044

Server rejected named pipe connection to database <%>

-21045

The address family for network protocol was unknown

-21046

Error when creating named pipe server objects

-21047

Error when setting up TCP server objects

-21048

Unexpected communication error

-21049

Error when reading/writing data to/from network channel

-21050

Error when closing communication with database server

-21051

All local communication slots are in use

-21052

Database server request failed

-21053

Database or network service not started Error when connecting to database <%> on <%> using <%> to service <%>

-21054

Database server for database <%> not started

-21055

The Mimer network service on <%> for <%> does not currently accept new connections. Try again later.

-21056

Local communication has been disabled for database server <%>

-21057

Named pipe communication has not been enabled for database server <%>

-21058

TCP/IP communication has not been enabled for database server <%>

-21059

Library for single-user mode not self-contained

-21061

The data source name specified in connection string was not found in system information

-21062

Invalid parameters found in connection string, DSN cannot be combined with PROTOCOL, NODE, SERVICE, INTERFACE, or DIRECTORY

-21063

PROTOCOL is mandatory when any of NODE, SERVICE, INTERFACE, or DIRECTORY is specified in connection string

-21064

When PROTOCOL is specified in connection string also a DATABASE specification is required

-21065

DIRECTORY specification is required in connection string for specified PROTOCOL: <%>

-21066

NODE (host name) specification in connection string is required for specified PROTOCOL: <%>

-21067

When DRIVER is specified in connection string also a DATABASE specification is required

-21071

Remote real time connections not supported

-21072

The started server does not have real time support

-21073

Bad parameter for real time request

-21074

Error when allocating resources for real-time tasks

-21075

Internal error during flush

-21076

Cryptographic protocol failure, session is not safe and is terminated

-21077

Failed to allocate memory for cryptographic operation

-21078

Cryptographic key is exhausted, the session is terminated

-21079

Cryptographic engine is currently unavailable

-21080

A malformed network message was received

-21100

Command timed out

-21101

Error mapping MCS (Mimer Control Storage)

-21102

Error when doing system communication through the MCS

-21103

MCS communication area is busy. Try again later

-21104

Server for database <%> is already started

-21105

Illegal directory specified for the SYSDB file

-21106

Error in parameter file

-21107

Error when starting database server process

-21108

Error when looking up database name

-21109

Error when creating memory pool in database server

-21110

Could not allocate space from SQLPool

-21111

Error when initiating the ENQ/DEQ package

-21112

Error when attaching a thread to the ENQDEQ area

-21113

Error when initiating server I/O package

-21114

Error when setting default directory for database server I/O package

-21115

Could not start database server thread

-21116

Protocol error- received new request before completion of last request

-21117

Could not create proper execution environment

-21118

Database server not operational

-21119

Notification thread failed. Server can no longer respond to mimcontrol.

-21120

Illegal directory path

-21121

Could not create new directory

-21122

Channel closed by administrator

-21123

Invalid channel number specified

-21124

Error when initiating request (rq) queue

-21125

Could not lock the bufferpool in memory

-21126

Database server halted. Failed to generate automatic database dumps.

-21127

Database server halted. Dump files from the failed database are placed under <%>.

-21128

Error when stopping database server process

-21129

Error when deleting memory pool in database server

-21130

Error getting database server parameters

-21131

Must be superuser to perform this function

-21132

The environment variable MIMER_HOME must point to the Mimer distribution

-21133

An illegal combination of command switches was specified

-21134

The database parameter must be specified

-21135

Permission denied

-21136

Bad network packet length. Channel was dropped.

-21137

Failed to load mimschema_database dynamic library

-21138

Cannot locate the SYSDB databank file

-21180

Error opening SQLHOSTS file

-21181

Error opening SQLHOSTS file - file name syntax error

-21182

Error opening SQLHOSTS file - file not found

-21183

Error opening SQLHOSTS file - file protection violation

-21184

Error opening SQLHOSTS file - file is locked

-21185

Error opening SQLHOSTS file - too many files are opened

-21186

Error opening SQLHOSTS file - file creation error (diskspace exhausted)

-21187

Error opening SQLHOSTS file - machine dependent code -7

-21188

Error opening SQLHOSTS file - machine dependent code -8

-21189

Error opening SQLHOSTS file - other error

-21190

Error opening SQLHOSTS file - illegal access option

-21191

Could not find a local definition for the specified database name

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:

$ java com.mimer.jdbc.Driver -errors

Mimload Errors

The following error codes are used by the Mimload application.

Number

Explanation

-23001

Unexpected DB error

-23003

Load/Unload is not allowed within transaction

-23004

Syntax error

-23005

Out of memory

-23006

Schema not found

-23007

Databank not found

-23008

Table not found

-23009

No results were created for statement

-23010

Statement has no parameters

-23011

Output parameters are not allowed

-23012

Could not open file

-23013

Could not read from file

-23014

Could not write to file

-23015

Could not close file

-23016

Syntax error in data descriptor

-23017

Could not open log file

-23018

Could not write to log file

-23019

Could not close log file

-23020

Too long field encountered

-23021

Statement failed, see next error

-23022

Length indicator for BLOB/CLOB data invalid

-23023

Invalid escape sequence encountered

Mimer SQL C API Return Codes

The ‘Definition name’ in the below tables are C defines from the provided mimerrors.h header file.

Status Codes

Number

Definition name

Explanation

0

MIMER_SUCCESS

Success.

100

MIMER_NO_DATA

No data.

Error Codes

The Mimer API returns error codes in the range -24000 to -24999.

Number

Definition name

Explanation

-24001

MIMER_OUTOFMEMORY

An attempt to allocate heap memory failed

-24002

MIMER_SQL_NULL_VALUE

A data retrieval function returned the SQL NULL value

-24003

MIMER_TRUNCATION_ERROR

Characters were truncated when setting string or binary data

-24004

MIMER_ILLEGAL_CHARACTER

An input string contained illegal characters

-24005

MIMER_STATEMENT_CANNOT_BE_PREPARED

A statement that cannot be prepared

-24006

MIMER_UNDEFINED_COMMUNICATION

Communication feature was not defined with a call to MimerSetComRoutines

-24007

MIMER_COULD_NOT_RELEASE

Mimer API was unable to release a resource

-24010

MIMER_POSITIVE_OVERFLOW

Value was too large to fit in destination

-24011

MIMER_NEGATIVE_OVERFLOW

Value was too small to fit in destination

-24012

MIMER_UNDEFINED_FLOAT_VALUE

Floating point value was either Not-A-Number or Infinity

-24101

MIMER_SEQUENCE_ERROR

An illegal sequence of API calls was detected

-24102

MIMER_NONEXISTENT_COLUMN_PARAMETER

An API call was made referring to a column or parameter that does not exist

-24103

MIMER_UNSET_PARAMETER

Incomplete set of input parameters when executing a statement or opening a cursor

-24104

MIMER_CAST_VIOLATION

An attempt was made to obtain column or parameter data of the wrong type

-24105

MIMER_PARAMETER_NOT_OUTPUT

An attempt was made to get the value of an input parameter

-24106

MIMER_PARAMETER_NOT_INPUT

An attempt was made to set the value of an output parameter

-24107

MIMER_PARAMETER_INVALID

A parameter to an API call was invalid

-24108

MIMER_HANDLE_INVALID

An attempt was made to call an API routine with an invalid handle

-24109

MIMER_TIMESTAMP_FORMAT_ERROR

A conversion of a TIMESTAMP from a character string failed

-24110

MIMER_ALLOCATION_FAILURE_THREAD

An attempt was made to allocate more threads than allowed

-24111

MIMER_WRONG_SERVER_TYPE

An attempt was made to establish a realtime connection to a non-realtime server

-24112

MIMER_NONEXISTENT_RECORD

The bind query does not point to a data element

-24113

MIMER_INCOMPATIBLE_POINTER_
ATTRIBUTES

The pointer type and policy are incompatible

-24114

MIMER_INVALID_POINTER_TYPE

The operation does not match the database pointer type

-24115

MIMER_UNSUPPORTED_AUTHENTICATION_
METHOD

Unsupported authentication method error

-24116

MIMER_NULL_VIOLATION

Cannot assign the null value to a non-nullable parameter

-24117

MIMER_UUID_FORMAT_ERROR

A conversion of an UUID from a character string failed

-24414

MIMER_MEMORY_MAP_ERROR

Cannot map a shared memory

-24415

MIMER_TLS_ERROR

Error using Thread Local Storage

-24416

MIMER_INVALID_CONTROL_BLOCK

Invalid parameter

-24417

MIMER_INTERNAL_CLIENT_ERROR

An internal error in the client has occurred

Programming Dependent Errors

Number

Definition name

Explanation

-14726

MIMER_RTCS_NOT_FOUND

A realtime control structure (RTCS) could not be found.

-14732

MIMER_INVALID_TRANSACTION_STATE

Bind is attempted within an active transaction.

Databank And Table Errors

Number

Definition name

Explanation

-11015

MIMER_TASKS_EXHAUSTED

The allocated real-time tasks in the server have been exhausted.

-16241

MIMER_RTCS_EXHAUSTED

The allocated real-time control structures have been exhausted.

-16242

MIMER_TABLE_COMPRESSED

An attempt to bind a pointer to a compressed table was made. Use "ALTER TABLE nn SET COMPRESS OFF;" to resolve this.

-16244

MIMER_PAGE_UPDATED

The page on which the real-time data value resides is currently updated elsewhere.

-16252

MIMER_INVALID_RTTYPE

Invalid database pointer type.

-16253

MIMER_INVALID_RTPOLICY

Invalid database pointer policy.

-16254

MIMER_TYPE_MISMATCH

The type (single/multicol/multirow) of the database pointer is not compatible with a previously created database pointer.

-16255

MIMER_RESULT_SET_MISMATCH

The result set (data records) partially overlaps a previously bound multirow database pointer.

-16256

MIMER_COLUMN_SET_MISMATCH

The column set does not match a previously bound multirow database pointer.

-16258

MIMER_COULD_NOT_LOCK_PAGE

Could not lock real-time pages in memory. The number of bufferpool pages in the region need to be increased.

-16259

MIMER_RTCS_INVALID

An attempt was made to delete a non-existing database pointer.

-16242

MIMER_TABLE_VARFORMAT

An attempt to bind a pointer to a variable format table was made.

Miscellaneous Errors

Number

Definition name

Explanation

-18246

MIMER_NOT_SINGLE_STATEMENT

The bind query contains multiple statements.

-18247

MIMER_NOT_SINGLE_COLUMN

The bind query points to several columns.

-18248

MIMER_NOT_SINGLE_ROW

The bind query points to several rows.

-18250

MIMER_INPUT_PARAMETER_FOUND

The bind query contains input parameters.

-18251

MIMER_SCROLL_USED

The bind query includes a scroll cursor.

-18252

MIMER_NOT_SELECT

The bind query is not a select statement.

-18253

MIMER_TIP_MISMATCH

Table Information Package mismatch.

-18254

MIMER_COLUMN_IS_PART_OF_KEY

An attempt to bind a pointer to a primary key was made.

-18255

MIMER_COLUMN_IS_PART_OF_INDEX

An attempt to bind a pointer to an indexed data element was made.

-18257

MIMER_NOT_SINGLE_TDA

The bind query contains a join or subselect.

-18258

MIMER_VOLATILE_DATA

An update elsewhere is not yet written to stable storage.

-18259

MIMER_NO_FLUSH_PRIVILEGE

The user does not have enough privilege to perform flush.

-18261

MIMER_NO_CRITICAL_SECTION_OBJECTS

The are no critical section objects available.

Internal Errors

 

Number

Definition name

Explanation

-19086

MIMER_INVALID_STATEMENT_STATUS

A statement is performed in a wrong order, or using a handle from a different thread or process.

-21074

MIMER_ERROR_ALLOCATING_TASK

Error when allocating resources for real-time tasks.

-21075

MIMER_INTERNAL_FLUSH_ERROR

Internal error during flush.

MimerPy Errors

The following error codes are used by the Mimer Python interface.

Number

Explanation

-25000

Unsupported method

-25001

TPC is unsupported

-25010

Connection not open

-25011

Invalid number of parameters

-25012

Invalid number of parameters, key: <%> does not exist in dictionary

-25013

Invalid parameter format

-25014

Previous execute did not produce a result set

-25015

Cursor not open

-25016

Illegal scroll mode

-25020

Data conversion error

-25030

Out of memory

-25031

Login failure

-25101

The operation requires Mimer API version 11.0.5A or newer. You have <%>.

-25102

The operation requires Mimer API version 11.0.5B or newer. You have <%>.