Sql error code 901

Модераторы: kdv, dimitr

---

---

---

---

---

---

---

---

---

---

---

---

iBase.ru Forum

Форум по InterBase, Firebird и Yaffil

• Темы без ответов
• Активные темы
• Поиск
• Наша команда

Dynamic SQL Error code = -901

Модераторы: kdv, dimitr

Dynamic SQL Error code = -901

Сообщение hadz » 21 сен 2006, 21:54

Доброго времени суток.
Люди подскажите плиз что с этим можно сделать.
Подключаюсь из клиентского приложения к базе которая лежит
на другой машине, выдаёт ошибку.
Dynamic SQL Error code = -901
в логах оставляет приведённое ниже сообщение.

Сообщение hvlad » 21 сен 2006, 22:03

Сообщение Dimitry Sibiryakov » 22 сен 2006, 08:05

Сообщение hadz » 22 сен 2006, 10:25

Сообщение dimitr » 22 сен 2006, 11:35

Сообщение =_911_= » 09 окт 2006, 14:29

Тоже проблемка, выручайте плиз.
Сервер на ХП2 IB7.1. при попытке редактировать удаленные БД через IBConsole выдает

Dynamic SQL Error
SQL error code = -901
feature is not supported

Подскажите где я могу это пофиксить или хотябы в чем баг.
вообще потерялся.
очень спасибо!

Сообщение Dimitry Sibiryakov » 09 окт 2006, 14:33

Сообщение =_911_= » 10 окт 2006, 16:28

Сообщение kdv » 10 окт 2006, 16:59

Сообщение =_911_= » 10 окт 2006, 17:10

пасиб канеша. но у меня тут проблемка. на мене висит компьютерный класс, а я помощничег у преподавателя. так что поставил то что под руку попалось. и чего там такого — понять не могу. примитвно в настройках ничего не нашел. я б с удовольствие выкинул — но толку от этого не будет, у детишек Лабы не этом агрегате. и я тут ничего не поделю

есть еще идеи. помогите плиз. просто нету времени самому в этом разбираться.

Сообщение stix-s » 10 окт 2006, 18:14

Сообщение =_911_= » 16 окт 2006, 13:58

Источник

IBMDB2 simple query error 901 — system error

I’m working on a IBM iseries v6r1m0 system.

I’m trying to execute a very simple query :

The columns are:

If I change DES into REF (graphic(25)), it works.

I run some tests this afternoon, and it is very strange :

Just after the creation of the table/indexes, I have no errors.

• If I insert some datas : error
• If I clear the table : error
• If I remove an index (see below) : it works (with or without datas) !!

Here is the job log (sorry, it is in French. )

4 Answers 4

I finally contacted IBM.

It was an old bug from v5.

I have installed the latest PTF, and now, it works.

You need to use the GRAPHIC scalar function to convert your character literals on the LIKE predicate.

I know this guy got his problem fixed with an update. But here is something that worked for me that might work for the next guy here who has the problem.

My problem query had a lot of common table expressions. Most of them did not create tables with a whole lot of records. So if I figured that the maximum number of records a CTE would make was 1000, I added a «Fetch first 9999 rows only» to it. I knew that the CTE couldn’t possibly have more rows than that. I guess the query optimizer had less to think about with that added.

If you have that problem and you don’t have the option to upgrade or talk to IBM, I hope this help you.

For other people getting this errore, I encountered it on an IBM i Series v7r3, when tried an UPDATE , retrieving the value to be set on a field using a inner SELECT where multiple results where reduced to 1, using DISTINCT . I solved the problem removing DISTINCT and adding FETCH FIRST 1 ROW ONLY at the end of the inner SELECT.

E.g.: changed from

Hot Network Questions

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.1.14.43159

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

SQL0901. returned in SQL trace when accessing DB2/400

Troubleshooting

Problem

Encountering the following error when attempting to run anything other than a simple list report. [IBM Client Access][ODBC] SQL 0901 System error

Resolving The Problem

This is an ODBC errors that can be caused by a corrupt driver, an incorrectly installed driver, or a driver that needs to be updated.

Also check the following:

1. For some specific versions of this driver — Journalling needs to be turned on — Please contact the vendor for more detailed information.
2. Confirm the Library names in the ODBC driver are correct.
3. Confirm the AS/400 is not low on space.
4. Reinstall the driver.
5. Run an ODBC trace to trap any preceding errors and assist in identifying the call that is causing the error.
6. Perform a SQLTrace and look up the error code returned in the call to SQLErrorW in the trace. For example:

This error corresponds to:

Cause: An SQL system error has occurred. The current SQL statement cannot be completed successfully. The error will not prevent other SQL statements from being processed. Previous messages may indicate that there is a problem with the SQL statement and SQL did not correctly diagnose the error. If precompiling, processing will not continue beyond this statement.

Recovery: See the previous messages to determine if there is a problem with the SQL statement. To view the messages, use the DSPJOBLOG command if running interactively, or the WRKJOB command to view the output of a precompile. An application program receiving this return code may attempt further SQL statements. Correct any errors and try the request again. The SQLCODE is -901 and the associated message is SQL0901.

Источник

Sql 901 error code

Невозможно работать с удалённой базой. Препробовал множество вариантов gds32.dll IBExpert работает как часы,
почти со всеми вариантами клиентских библиотек Firebird.
А тут подключение происходит но невозможен даже простой select. Использую ibx, судя по тому что прочитал в интернете об этой проблеме, FIBPlus проблему не решает.
Удалённый сервер Firebird 1.5 LI-V6.3.2.4731

← →
maximsms ( 2006-03-05 17:40 ) [1]

Удалено модератором
Примечание: Создание пустых соощений

← →
Johnmen © ( 2006-03-05 18:50 ) [2]

← →
maximsms ( 2006-03-05 19:05 ) [3]

tibdatabase().connect
//SUCCEED
.
tibsql().sql.text:=»select id from table1″;
tibsql().execquery;
//CAUSES FAILURE WITH MESSAGE
//Dynamic SQL Error SQL error code = -901 feature is not supported

← →
Desdechado © ( 2006-03-05 20:49 ) [4]

что за странные скобочки?
может, лучше сначала создать экземпляр класса, потом его использовать, а то так ты просто теряешь указатели на свои объекты и их невозможно больше найти для использования.
ведь для выполнения SQL нужно указать, через какое соединение будешь это делать, а у тебя для него уже нет указателя.

> Desdechado © (05.03.06 20:49) [4]
> что за странные скобочки?

это я условно написал от фонаря что-то,
суть не в этом

← →
Desdechado © ( 2006-03-05 21:04 ) [6]

а в чем?
от фонаря и работать будет

← →
maximsms ( 2006-03-05 21:06 ) [7]

суть в том что любой select вызывает это сообщение.

с разными серверами на localhost, например:
Firebird 1.5 WI-V6.3.1
всё работает.
а с удалёнными успешно работает только IBExpert.

← →
Johnmen © ( 2006-03-06 10:11 ) [8]

Почему для селективного запроса используется .execquery?

← →
mbgmz © ( 2006-03-10 02:51 ) [9]

> Johnmen © (06.03.06 10:11) [8]
> Почему для селективного запроса используется .execquery?
>

потому что у TIBSQL нет другого походящего метода

вопрос снят, после того как я переставил Delphi и Firebird сервер,
каким-то чудом оно заработало. Но выявить причину почему оно не работало мне так и не удалось

← →
Johnmen © ( 2006-03-10 09:14 ) [11]

> mbgmz © (10.03.06 02:51) [9]
>
>
> > Johnmen © (06.03.06 10:11) [8]
> > Почему для селективного запроса используется .execquery?
>
> >
>
> потому что у TIBSQL нет другого походящего метода

Почему для селективного запроса используется TIBSQL?

← →
msguns © ( 2006-03-10 09:32 ) [12]

>mbgmz © (10.03.06 02:54) [10]
>вопрос снят, после того как я переставил Delphi и Firebird сервер,

Надо еще поменять комп, квартиру, жену и собаку.
Тогда точно заработает.

Справку по IBX не читаем по религиозным соображениям ?

← →
mbgmz © ( 2006-03-11 06:09 ) [13]

И что я найду в справке по IBX про ошибку N: -901 .
Лучше бы подсказали как выявить причину, вызывающую эту ошибку.

> [11]

это не имеет значения.
нравится мне tibsql и всё, точно также вели себя и tibquery.

← →
jack128 © ( 2006-03-11 15:44 ) [14]

Johnmen © (10.03.06 9:14) [11]
Почему для селективного запроса используется TIBSQL?
а почему бы и нет?? Я активно использую и проблем не имею

> это не имеет значения.
> нравится мне tibsql и всё, точно также вели себя и tibquery.
>

Ну если тебе побарабану, то чего спрашиваешь?

> jack128 © (11.03.06 15:44) [14]
> а почему бы и нет?? Я активно использую и проблем не имею

← →
jack128 © ( 2006-03-11 22:59 ) [16]

Johnmen © (11.03.06 20:47) [15]
Врешь ты всё. )

Не-а. Исходники не горят(с) 😛

← →
DrPass © ( 2006-03-12 12:38 ) [17]

> И что я найду в справке по IBX про ошибку N: -901 .
> Лучше бы подсказали как выявить причину, вызывающую эту
> ошибку

Насчет справки не знаю, а то, что IBX не поддерживает Firebird и не гарантирует совместимость с ней, разработчики IBX повторяли не раз.

Источник

Sql 901 error code

Frequently faced mainframes Errors / Abdends and Complete List follows

SQLCODE -102 String constant is too long

SQLCODE -117 The number of values you are trying to INSERT
does not match the number of columns

SQLCODE -180 SQLSTATE 22007
Bad data in Date/Time/Timestamp
String representation of DATE, TIME, TIMESTAMP is invalid

SQLCODE -181 SQLSTATE 22007
Bad data in Date/Time/Timestamp
Value for DATE, TIME, TIMESTAMP is invalid

SQLCODE -199 Illegal use of the specified keyword.

SQLCODE -204 Object not defined to DB2

SQLCODE -205 Column name not in specified table

SQLCODE -206 Column does not exist in any table in the SELECT

SQLCODE -216
You need to use the same number of expressions on both sides of the comparison.
when using multiple operands in a comparison,
Correct example:
WHERE (E.SALARY, E.COMM) IN
(SELECT S.PAY, S.COMMISSION
Incorrect example:
WHERE (E.SALARY, E.COMM, E.BONUS) IN
(SELECT S.PAY, S.COMMISSION

SQLCODE +222 Trying to fetch a row that fell through a DELETE hole

SQLCODE +223 Trying to fetch a row that fell through an UPDATE hole

SQLCODE -224 FETCH cannot make an INSENSITIVE cursor SENSITIVE

SQLCODE -229 The locale specified in a SET LOCALE statement was not found.

SQLCODE +231 FETCH
but you did a BEFORE or AFTER and you are not on a valid row

SQLCODE +304 Value cannot be assigned to this host variable because it is out of range

SQLCODE -305 Null indicator needed

SQLCODE -311 Varchar, insert or update.
You didn’t set the -LEN field with the right data length

SQLCODE -482 he procedure returned no locators

SQLCODE -501 Cursor not open on FETCH

SQLCODE -502 Opening cursor that is already open

SQLCODE -503 Updating column which needs to be specified in FOR UPDATE OF

SQLCODE -530 SQLSTATE 23503
Referential integrity prevents the INSERT/UPDATE

SQLCODE -532 SQLSTATE 23504
Referential integrity (DELETE RESTRICT rule) prevents the DELETE

SQLCODE -536 SQLSTATE 42914
Referential integrity (DELETE RESTRICT rule) prevents the DELETE

SQLCODE -545 SQLSTATE 23513
Check constraint prevents the INSERT/UPDATE

SQLCODE -747 The table specified is not available
because tables and/or indexes need to be created.

SQLCODE +802 The null indicator was set to -2
because an arithmetic statement didn’t work.

SQLCODE -803 SQLSTATE 23505
Duplicate key on insert or update

SQLCODE -805
DBRM or package not found in plan
Is plan name correct?

SQLCODE -811 More than one row retrieved in SELECT INTO

SQLCODE -818 Plan and program: timestamp mismatch

SQLCODE -904 SQLSTATE 57011
Unavailable resource. Someone is locking the data you need
you may choose to terminate the program

SQLCODE -911 SQLSTATE 40000
Deadlock or timeout. Rollback has been done.

SQLCODE -913 SQLSTATE 40502
Your program was the victim of a deadlock or timeout.
NO rollback has been done.
You should do a ROLLBACK.

SQLCODE -922 Authorization needed

SQLCODE -927 The language interface was called but no connection had been

SQLCODE reference: All the sqlcodes from -991 to +883 in DB2 Version 7.
Top of Page

SQLCODE -991, Error: CALL ATTACH WAS UNABLE TO ESTABLISH AN IMPLICIT CONNECT OR OPEN TO DB2.
RC1= RC2=

SQLCODE -981, Error: THE SQL STATEMENT FAILED BECAUSE THE RRSAF CONNECTION IS NOT IN
A STATE THAT ALLOWS SQL OPERATIONS, REASON

SQLCODE -950, Error: THE LOCATION NAME SPECIFIED IN THE CONNECT STATEMENT IS INVALID OR NOT
LISTED IN THE COMMUNICATIONS DATABASE

SQLCODE -948, Error: DISTRIBUTED OPERATION IS INVALID

SQLCODE -947, Error: THE SQL STATEMENT FAILED BECAUSE IT WILL CHANGE A TABLE DEFINED WITH DATA CAPTURE
CHANGES, BUT THE DATA CANNOT BE PROPAGATED

SQLCODE -939, Error: ROLLBACK REQUIRED DUE TO UNREQUESTED ROLLBACK OF A REMOTE SERVER

SQLCODE -929, Error: FAILURE IN A CHANGED DATA CAPTURE EXIT:

SQLCODE -927, Error: THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING ENVIRONMENT WAS NOT
ESTABLISHED. THE PROGRAM SHOULD BE INVOKED UNDER THE DSN COMMAND

SQLCODE -926, Error: ROLLBACK NOT VALID IN IMS OR CICS ENVIRONMENT

SQLCODE -925, Error: COMMIT NOT VALID IN IMS OR CICS ENVIRONMENT

SQLCODE -924, Error: DB2 CONNECTION INTERNAL ERROR, , ,

SQLCODE -923, Error: CONNECTION NOT ESTABLISHED: DB2 , REASON , TYPE , NAME

SQLCODE -922, Error: AUTHORIZATION FAILURE: ERROR. REASON

SQLCODE -919, Error: A ROLLBACK OPERATION IS REQUIRED

SQLCODE -918, Error: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE A CONNECTION HAS BEEN LOST

SQLCODE -917, Error: BIND PACKAGE FAILED

SQLCODE -913, Error: UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE ,
TYPE OF RESOURCE , AND RESOURCE NAME

SQLCODE -911, Error: THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT.
REASON ,TYPE OF RESOURCE , AND RESOURCE NAME

SQLCODE -910, Error: THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH A DROP OR ALTER IS PENDING

SQLCODE -909, Error: THE OBJECT HAS BEEN DELETED OR ALTERED

SQLCODE -908, Error: ERROR USING AUTHORITY. BIND, REBIND, OR AUTO-REBIND OPERATION IS NOT ALLOWED

SQLCODE -906, Error: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS FUNCTION IS
DISABLED DUE TO A PRIOR ERROR

SQLCODE -905, Error: UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED,
RESOURCE NAME = LIMIT = CPU SECONDS ( SERVICE UNITS) DERIVED FROM

SQLCODE -904, Error: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON ,
TYPE OF RESOURCE , AND RESOURCE NAME

SQLCODE -902, Error: POINTER TO ESSENTIAL CONTROL BLOCK(RDA/CT) HAS VALUE 0, REBIND REQUIRED

SQLCODE -901, Error: UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES NOT
PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS

SQLCODE -900, Error: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE APPLICATION
PROCESS IS NOT CONNECTED TO AN APPLICATION SERVER

SQLCODE -882, Error: SAVEPOINT DOES NOT EXIST

SQLCODE -881, Error: A SAVEPOINT WITH NAME ALREADY EXISTS, BUT THIS SAVEPOINT NAME CANNOT BE REUSED

SQLCODE -880, Error: SAVEPOINT DOES NOT EXIST OR IS INVALID IN THIS CONTEXT

SQLCODE -879, Error: CREATE OR ALTER STATEMENT FOR CANNOT DEFINE A COLUMN, DISTINCT TYPE, FUNCTION OR
STORED PROCEDURE PARAMETER AS MIXED OR GRAPHIC WITH ENCODING SCHEME

SQLCODE -878, Error: THE PLAN_TABLE USED FOR EXPLAIN CANNOT BE ASCII

SQLCODE -877, Error: CCSID ASCII IS NOT ALLOWED FOR THIS DATABASE OR TABLE SPACE

SQLCODE -876, Error: CANNOT BE CREATED, REASON

SQLCODE -875, Error: CANNOT BE USED WITH THE ASCII DATA REFERENCED

SQLCODE -874, Error: THE ENCODING SCHEME SPECIFIED FOR THE MUST BE THE SAME AS THE
CONTAINING TABLE SPACE OR OTHER PARAMETERS

SQLCODE -873, Error: DATA ENCODED WITH DIFFERENT CCSIDS CANNOT BE REFERENCED IN THE SAME SQL STATEMENT

SQLCODE -872, Error: A VALID CCSID HAS NOT YET BEEN SPECIFIED FOR THIS SUBSYSTEM

SQLCODE -867, Error: INVALID SPECIFICATION OF A ROWID COLUMN

SQLCODE -846, Error: INVALID SPECIFICATION OF AN IDENTITY COLUMN

SQLCODE -843, Error: THE SET CONNECTION OR RELEASE STATEMENT MUST SPECIFY AN EXISTING CONNECTION

SQLCODE -842, Error: A CONNECTION TO x ALREADY EXISTS

SQLCODE -840, Error: TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST

SQLCODE -822, Error: THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR INDICATOR VARIABLE ADDRESS

SQLCODE -820, Error: THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE CONTAINS A VALUE THAT
IS NOT VALID IN THIS RELEASE

SQLCODE -818, Error: THE PRECOMPILER-GENERATED TIMESTAMP IN THE LOAD MODULE IS DIFFERENT
FROM THE BIND TIMESTAMP BUILT FROM THE DBRM

SQLCODE -817, Error: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE STATEMENT WILL RESULT
IN A PROHIBITED UPDATE OPERATION

SQLCODE -815, Error: A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY SPECIFIED
IN A SUBSELECT OF A BASIC PREDICATE OR A SET CLAUSE OF AN UPDATE STATEMENT

SQLCODE -812, Error: THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE A BLANK COLLECTION-ID
WAS FOUND IN THE CURRENTPACKAGESET SPECIAL REGISTER WHILE TRYING TO FORM A QUALIFIED PACKAGE
NAME FOR PROGRAM USING PLAN

SQLCODE -811, Error: THE RESULT OF AN EMBEDDED SELECT STATEMENT OR A SUBSELECT IN THE SET
CLAUSE OF AN UPDATE STATEMENT IS A TABLE OF MORE THAN ONE ROW, OR THE RESULT OF
A SUBQUERY OF A BASIC PREDICATE IS MORE THAN VALUE

SQLCODE -808, Error: THE CONNECT STATEMENT IS NOT CONSISTENT WITH THE FIRST CONNECT STATEMENT

SQLCODE -807, Error: ACCESS DENIED: PACKAGE IS NOT ENABLED FOR ACCESS FROM

SQLCODE -805, Error: DBRM OR PACKAGE NAME NOT FOUND IN PLAN . REASON

SQLCODE -803, Error: AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE INDEX IN
INDEX SPACE CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE
VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X»

SQLCODE -802, Error: EXCEPTION ERROR HAS OCCURRED DURING OPERATION ON DATA, POSITION

SQLCODE -798, Error: YOU CANNOT INSERT A VALUE INTO A COLUMN THAT IS DEFINED WITH THE OPTION
GENERATED ALWAYS. COLUMN NAME

SQLCODE -797, Error: ATTEMPT TO CREATE TRIGGER WITH AN UNSUPPORTED TRIGGERED SQL STATEMENT

SQLCODE -771, Error: INVALID SPECIFICATION OF A ROWID COLUMN

SQLCODE -770, Error: TABLE CANNOT HAVE A LOB COLUMN UNLESS IT ALSO HAS A ROWID COLUMN

SQLCODE -768, Error: AN AUXILIARY TABLE ALREADY EXISTS FOR THE SPECIFIED COLUMN OR PARTITION

SQLCODE -767, Error: MISSING OR INVALID COLUMN SPECIFICATION FOR INDEX

SQLCODE -766, Error: THE OBJECT OF A STATEMENT IS AN AUXILIARY TABLE FOR WHICH THE REQUESTED
OPERATION IS NOT PERMITTED

SQLCODE -765, Error: TABLE IS NOT COMPATIBLE WITH DATABASE

SQLCODE -764, Error: A LOB TABLE SPACE AND ITS ASSOCIATED BASE TABLE SPACE MUST BE IN THE SAME DATABASE

SQLCODE -763, Error: INVALID TABLE SPACE NAME

SQLCODE -752, Error: THE CONNECT STATEMENT IS INVALID BECAUSE THE PROCESS IS NOT IN THE CONNECTABLE STATE

SQLCODE -751, Error: (SPECIFIC NAME ) ATTEMPTED TO EXECUTE AN SQL STATEMENT THAT IS NOT ALLOWED

SQLCODE -750, Error: THE SOURCE TABLE CANNOT BE RENAMED BECAUSE IT IS REFERENCED
IN EXISTING VIEW DEFINITIONS OR TRIGGER DEFINITIONS

SQLCODE -748, Error: AN INDEX ALREADY EXISTS ON AUXILIARY TABLE

SQLCODE -747, Error: TABLE IS NOT AVAILABLE UNTIL THE AUXILIARY TABLES AND INDEXES
FOR ITS EXTERNALLY STORED COLUMNS HAVE BEEN CREATED

SQLCODE -746, Error: THE SQL STATEMENT IN AN EXTERNAL FUNCTION, TRIGGER,
OR IN STORED PROCEDURE VIOLATES THE NESTING SQL RESTRICTION

SQLCODE -742, Error: DSNDB07 IS THE IMPLICIT WORK FILE DATABASE

SQLCODE -741, Error: A DATABASE IS ALREADY DEFINED FOR MEMBER

SQLCODE -740, Error: FUNCTION IS DEFINED WITH THE OPTION MODIFIES SQL DATA
WHICH IS NOT VALID IN THE CONTEXT IN WHICH IT WAS INVOKED

SQLCODE -739, Error: ALTER FUNCTION FAILED BECAUSE FUNCTIONS CANNOT MODIFY DATA WHEN THEY ARE
PROCESSED IN PARALLEL

SQLCODE -737, Error: IMPLICIT TABLE SPACE NOT ALLOWED

SQLCODE -736, Error: INVALID OBID SPECIFIED

SQLCODE -735, Error: DATABASE CANNOT BE ACCESSED BECAUSE IT IS NO LONGER A SHARED DATABASE

SQLCODE -734, Error: THE ROSHARE ATTRIBUTE OF A DATABASE CANNOT BE ALTERED FROM ROSHARE READ

SQLCODE -733, Error: THE DESCRIPTION OF A TABLE SPACE, INDEX SPACE, OR TABLE IN A ROSHARE READ DATABASE
MUST BE CONSISTENT WITH ITS DESCRIPTION IN THE OWNER SYSTEM

SQLCODE -732, Error: THE DATABASE IS DEFINED ON THIS SUBSYSTEM WITH THE ROSHARE READ ATTRIBUTE BUT THE
TABLE SPACE OR INDEX SPACE HAS NOT BEEN DEFINED ON THE OWNING SUBSYSTEM

SQLCODE -731, Error: USER-DEFINED DATASET MUST BE DEFINED WITH SHAREOPTIONS (1,3)

SQLCODE -728, Error: DATA TYPE IS NOT ALLOWED IN DB2 PRIVATE PROTOCOL PROCESSING

SQLCODE -726, Error: BIND ERROR ATTEMPTING TO REPLACE PACKAGE = . THERE ARE ENABLE OR DISABLE ENTRIES
CURRENTLY ASSOCIATED WITH THE PACKAGE

SQLCODE -725, Error: THE SPECIAL REGISTER AT LOCATION WAS SUPPLIED AN INVALID VALUE

SQLCODE -723, Error: AN ERROR OCCURRED IN A TRIGGERED SQL STATEMENT IN TRIGGER , SECTION NUMBER .
INFORMATION RETURNED: SQLCODE , SQLSTATE , AND MESSAGE TOKENS

SQLCODE -722, Error: ERROR USING AUTHORITY PACKAGE DOES NOT EXIST

SQLCODE -721, Error: BIND ERROR FOR PACKAGE = CONTOKEN = »X IS NOT UNIQUE SO IT CANNOT BE CREATED

SQLCODE -719, Error: BIND ADD ERROR USING AUTHORITY PACKAGE ALREADY EXISTS

SQLCODE -718, Error: REBIND OF PACKAGE FAILED BECAUSE IBMREQD OF IS INVALID

SQLCODE -717, Error: FOR WITH MARK FAILED BECAUSE DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH
FALLBACK HAS OCCURRED

SQLCODE -716, Error: PROGRAM PRECOMPILED WITH INCORRECT LEVEL FOR THIS RELEASE

SQLCODE -715, Error: PROGRAM WITH MARK FAILED BECAUSE IT DEPENDS ON FUNCTIONS OF THE RELEASE FROM
WHICH FALLBACK HAS OCCURRED

SQLCODE -713, Error: THE REPLACEMENT VALUE FOR IS INVALID

SQLCODE -697, Error: OLD OR NEW CORRELATION NAMES ARE NOT ALLOWED IN A TRIGGER DEFINED WITH THE FOR EACH
STATEMENT CLAUSE. OLD_TABLE OR NEW_TABLE NAMES ARE NOT ALLOWED IN A TRIGGER WITH THE BEFORE CLAUSE

SQLCODE -696, Error: THE DEFINITION OF TRIGGER INCLUDES AN INVALID USE OF CORRELATION
NAME OR TRANSITION TABLE NAME . REASON CODE=

SQLCODE -693, Error: THE COLUMN IN DDL REGISTRATION TABLE OR INDEX IS NOT DEFINED PROPERLY

SQLCODE -692, Error: THE REQUIRED UNIQUE INDEX FOR DDL REGISTRATION TABLE DOES NOT EXIST

SQLCODE -691, Error: THE REQUIRED REGISTRATION TABLE DOES NOT EXIST

SQLCODE -690, Error: THE STATEMENT IS REJECTED BY DATA DEFINITION CONTROL SUPPORT. REASON

SQLCODE -689, Error: TOO MANY COLUMNS DEFINED FOR A DEPENDENT TABLE

SQLCODE -688, Error: INCORRECT DATA RETURNED FROM FIELD PROCEDURE, ,

SQLCODE -687, Error: FIELD TYPES INCOMPARABLE

SQLCODE -686, Error: COLUMN DEFINED WITH A FIELD PROCEDURE CAN NOT COMPARE WITH ANOTHER COLUMN WITH
DIFFERENT FIELD PROCEDURE

SQLCODE -685, Error: INVALID FIELD TYPE,

SQLCODE -684, Error: THE LENGTH OF LITERAL LIST BEGINNING IS TOO LONG

SQLCODE -683, Error: THE SPECIFICATION FOR COLUMN, DISTINCT TYPE, FUNCTION, OR PROCEDURE CONTAINS
INCOMPATIBLE CLAUSES

SQLCODE -682, Error: FIELD PROCEDURE COULD NOT BE LOADED

SQLCODE -681, Error: COLUMN IN VIOLATION OF INSTALLATION DEFINED FIELD PROCEDURE RT: , RS: , MSG:

SQLCODE -680, Error: TOO MANY COLUMNS SPECIFIED FOR A TABLE, VIEW, OR TABLE FUNCTION

SQLCODE -679, Error: THE OBJECT CANNOT BE CREATED BECAUSE A DROP IS PENDING ON THE OBJECT

SQLCODE -678, Error: THE LITERAL SPECIFIED FOR THE INDEX LIMIT KEY MUST CONFORM
TO THE DATA TYPE OF THE CORRESPONDING COLUMN

SQLCODE -677, Error: INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION

SQLCODE -676, Error: ONLY A 4K PAGE BUFFERPOOL CAN BE USED FOR AN INDEX

SQLCODE -672, Error: OPERATION DROP NOT ALLOWED ON TABLE

SQLCODE -671, Error: THE BUFFERPOOL ATTRIBUTE OF THE TABLE SPACE CANNOT BE ALTERED AS SPECIFIED BECAUSE IT
WOULD CHANGE THE PAGE SIZE OF THE TABLE SPACE

SQLCODE -670, Error: THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT

SQLCODE -669, Error: A TABLE IN A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED

SQLCODE -668, Error: THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE HAS AN EDIT PROCEDURE

SQLCODE -667, Error: THE CLUSTERING INDEX FOR A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED

SQLCODE -666, Error: CANNOT BE EXECUTED BECAUSE IS IN PROGRESS

SQLCODE -665, Error: THE PART CLAUSE OF AN ALTER STATEMENT IS OMITTED OR INVALID

SQLCODE -663, Error: THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO, OR GREATER THAN
THE NUMBER OF COLUMNS IN THE KEY OF INDEX

SQLCODE -662, Error: A PARTITIONED INDEX CANNOT BE CREATED ON A NON-PARTITIONED TABLE SPACE

SQLCODE -661, Error: INDEX CANNOT BE CREATED ON PARTITIONED TABLE SPACE BECAUSE THE NUMBER OF PART
SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OF PARTITIONS OF THE TABLE SPACE

SQLCODE -658, Error: A CANNOT BE DROPPED USING THE STATEMENT

SQLCODE -655, Error: THE CREATE OR ALTER STOGROUP IS INVALID BECAUSE THE STORAGE GROUP WOULD HAVE BOTH
SPECIFIC AND NON-SPECIFIC VOLUME IDS

SQLCODE -653, Error: TABLE IN PARTITIONED TABLE SPACE IS NOT AVAILABLE BECAUSE
ITS PARTITIONED INDEX HAS NOT BEEN CREATED

SQLCODE -652, Error: VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION PROCEDURE

SQLCODE -651, Error: TABLE DESCRIPTION EXCEEDS MAXIMUM SIZE OF OBJECT DESCRIPTOR

SQLCODE -650, Error: THE ALTER INDEX CANNOT BE EXECUTED, REASON

SQLCODE -647, Error: BUFFERPOOL CANNOT BE SPECIFIED BECAUSE IT HAS NOT BEEN ACTIVATED

SQLCODE -646, Error: TABLE CANNOT BE CREATED IN SPECIFIED TABLE SPACE BECAUSE IT ALREADY CONTAINS A TABLE

SQLCODE -644, Error: INVALID VALUE SPECIFIED FOR KEYWORD IN STATEMENT

SQLCODE -643, Error: CHECK CONSTRAINT EXCEEDS MAXIMUM ALLOWABLE LENGTH

SQLCODE -642, Error: TOO MANY COLUMNS IN UNIQUE CONSTRAINTS

SQLCODE -640, Error: LOCKSIZE ROW CANNOT BE SPECIFIED BECAUSE TABLE IN THIS TABLESPACE HAS TYPE 1 INDEX

SQLCODE -639, Error: A NULLABLE COLUMN OF A FOREIGN KEY WITH A DELETE RULE OF SET NULL CANNOT BE A COLUMN
OF THE KEY OF A PARTITIONED INDEX

SQLCODE -638, Error: TABLE CANNOT BE CREATED BECAUSE COLUMN DEFINITION IS MISSING

SQLCODE -637, Error: DUPLICATE KEYWORD

SQLCODE -635, Error: THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET NULL

SQLCODE -634, Error: THE DELETE RULE MUST NOT BE CASCADE

SQLCODE -633, Error: THE DELETE RULE MUST BE

SQLCODE -632, Error: THE TABLE CANNOT BE DEFINED AS A DEPENDENT OF BECAUSE OF DELETE RULE RESTRICTIONS

SQLCODE -631, Error: FOREIGN KEY IS TOO LONG OR HAS TOO MANY COLUMNS

SQLCODE -630, Error: THE WHERE NOT NULL SPECIFICATION IS INVALID FOR TYPE 1 INDEXES

SQLCODE -629, Error: SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY CANNOT CONTAIN NULL VALUES

SQLCODE -628, Error: THE CLAUSES ARE MUTUALLY EXCLUSIVE

SQLCODE -627, Error: THE ALTER STATEMENT IS INVALID BECAUSE THE PAGESET HAS USER-MANAGED DATA SETS

SQLCODE -626, Error: THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGE SET IS NOT STOPPED

SQLCODE -625, Error: TABLE DOES NOT HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF THE PARENT KEY

SQLCODE -624, Error: TABLE ALREADY HAS A PRIMARY KEY

SQLCODE -623, Error: A CLUSTERING INDEX ALREADY EXISTS ON TABLE

SQLCODE -622, Error: FOR MIXED DATA IS INVALID BECAUSE THE MIXED DATA INSTALL OPTION IS NO

SQLCODE -621, Error: DUPLICATE DBID WAS DETECTED AND PREVIOUSLY ASSIGNED TO

SQLCODE -620, Error: KEYWORD IN STATEMENT IS NOT PERMITTED FOR A SPACE IN THE DATABASE

SQLCODE -619, Error: OPERATION DISALLOWED BECAUSE THE WORK FILE DATABASE IS NOT STOPPED

SQLCODE -618, Error: OPERATION IS NOT ALLOWED ON SYSTEM DATABASES

SQLCODE -617, Error: A TYPE 1 INDEX IS NOT VALID FOR TABLE

SQLCODE -616, Error: CANNOT BE DROPPED BECAUSE IT IS REFERENCED BY

SQLCODE -615, Error: IS NOT ALLOWED ON A PACKAGE IN USE

SQLCODE -614, Error: THE INDEX CANNOT BE CREATED OR THE LENGTH OF THE COLUMN CANNOT BE CHANGED BECAUSE THE
SUM OF THE INTERNAL LENGTHS OF THE IDENTIFIED COLUMNS IS GREATER THAN THE ALLOWABLE MAXIMUM

SQLCODE -613, Error: THE PRIMARY KEY OR A UNIQUE CONSTRAINT IS TOO LONG OR HAS TOO MANY COLUMNS

SQLCODE -612, Error: IS A DUPLICATE COLUMN NAME

SQLCODE -607, Error: OPERATION OR OPTION IS NOT DEFINED FOR THIS OBJECT

SQLCODE -604, Error: A DATA TYPE DEFINITION SPECIFIES AN INVALID LENGTH, PRECISION, OR SCALE ATTRIBUTE

SQLCODE -603, Error: A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE CONTAINS ROWS WHICH ARE DUPLICATES
WITH RESPECT TO THE VALUES OF THE IDENTIFIED COLUMNS

SQLCODE -602, Error: TOO MANY COLUMNS SPECIFIED IN A CREATE INDEX

SQLCODE -601, Error: THE NAME OF THE OBJECT TO BE CREATED OR THE TARGET OF A RENAME STATEMENT IS IDENTICAL
TO THE EXISTING NAME OF THE OBJECT TYPE

SQLCODE -594, Error: ATTEMPT TO CREATE A NULLABLE ROWID OR DISTINCT TYPE COLUMN

SQLCODE -593, Error: NOT NULL MUST BE SPECIFIED FOR ROWID OR DISTINCT TYPE COLUMN

SQLCODE -592, Error: NOT AUTHORIZED TO CREATE FUNCTIONS OR PROCEDURES IN WLM ENVIRONMENT

SQLCODE -590, Error: PARAMETER NAME IS NOT UNIQUE IN THE CREATE FOR ROUTINE

SQLCODE -586, Error: THE TOTAL LENGTH OF THE CURRENT PATH SPECIAL REGISTER CANNOT EXCEED 254 CHARACTERS

SQLCODE -585, Error: THE SCHEMA NAME CANNOT APPEAR MORE THAN ONCE IN THE CURRENT PATH

SQLCODE -582, Error: THE SEARCH-CONDITION IN A SEARCHED-WHEN-CLAUSE CANNOT BE A QUANTIFIED PREDICATE, IN
PREDICATE, OR AN EXISTS PREDICATE

SQLCODE -581, Error: THE DATA TYPES OF THE RESULT-EXPRESSIONS OF A CASE EXPRESSION ARE NOT COMPATIBLE

SQLCODE -580, Error: THE RESULT-EXPRESSIONS OF A CASE EXPRESSION CANNOT ALL BE NULL

SQLCODE -579, Error: ATTEMPTED TO READ DATA WHEN THE DEFINITION OF THE FUNCTION OR
PROCEDURE DID NOT SPECIFY THIS ACTION

SQLCODE -577, Error: ATTEMPTED TO MODIFY DATA WHEN THE DEFINITION OF THE FUNCTION OR
PROCEDURE DID NOT SPECIFY THIS ACTION

SQLCODE -574, Error: THE SPECIFIED DEFAULT VALUE OR IDENTITY ATTRIBUTE VALUE CONFLICTS WITH
THE DEFINITION OF COLUMN

SQLCODE -573, Error: TABLE DOES NOT HAVE A UNIQUE KEY WITH THE SPECIFIED COLUMN NAMES

SQLCODE -571, Error: THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE

SQLCODE -567, Error: AUTHORIZATION ERROR USING AUTHORITY PACKAGE = PRIVILEGE =

SQLCODE -559, Error: ALL AUTHORIZATION FUNCTIONS HAVE BEEN DISABLED

SQLCODE -558, Error: INVALID CLAUSE OR COMBINATION OF CLAUSES ON A GRANT OR REVOKE

SQLCODE -557, Error: INCONSISTENT GRANT/REVOKE KEYWORD . PERMITTED KEYWORDS ARE

SQLCODE -556, Error: CANNOT HAVE THE PRIVILEGE REVOKED BY BECAUSE THE REVOKEE DOES NOT POSSESS THE
PRIVILEGE OR THE REVOKER DID NOT MAKE THE GRANT

SQLCODE -555, Error: AN AUTHORIZATION ID CANNOT REVOKE A PRIVILEGE FROM ITSELF

SQLCODE -554, Error: AN AUTHORIZATION ID CANNOT GRANT A PRIVILEGE TO ITSELF

SQLCODE -553, Error: SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS

SQLCODE -552, Error: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION

SQLCODE -551, Error: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION ON OBJECT

SQLCODE -549, Error: THE STATEMENT IS NOT ALLOWED FOR BECAUSE THE BIND OPTION DYNAMICRULES(RUN)
IS NOT IN EFFECT FOR

SQLCODE -548, Error: A CHECK CONSTRAINT THAT IS DEFINED WITH IS INVALID

SQLCODE -546, Error: THE CHECK CONSTRAINT IS INVALID

SQLCODE -544, Error: THE CHECK CONSTRAINT SPECIFIED IN THE ALTER TABLE STATEMENT CANNOT BE ADDED BECAUSE AN
EXISTING ROW VIOLATES THE CHECK CONSTRAINT

SQLCODE -543, Error: A ROW IN A PARENT TABLE CANNOT BE DELETED BECAUSE THE CHECK CONSTRAINT
RESTRICTS THE DELETION

SQLCODE -539, Error: TABLE DOES NOT HAVE A PRIMARY KEY

SQLCODE -538, Error: FOREIGN KEY DOES NOT CONFORM TO THE DESCRIPTION OF A PARENT KEY OF TABLE

SQLCODE -537, Error: THE PRIMARY KEY CLAUSE, A FOREIGN KEY CLAUSE, OR A UNIQUE CLAUSE IDENTIFIES
COLUMN MORE THAN ONCE

SQLCODE -536, Error: THE DELETE STATEMENT IS INVALID BECAUSE TABLE CAN BE AFFECTED BY THE OPERATION

SQLCODE -534, Error: THE PRIMARY KEY CANNOT BE UPDATED BECAUSE OF MULTIPLE-ROW UPDATE

SQLCODE -533, Error: INVALID MULTIPLE-ROW INSERT

SQLCODE -532, Error: THE RELATIONSHIP RESTRICTS THE DELETION OF ROW WITH RID X»

SQLCODE -531, Error: PARENT KEY IN A PARENT ROW CANNOT BE UPDATED BECAUSE IT HAS ONE OR
MORE DEPENDENT ROWS IN RELATIONSHIP

SQLCODE -530, Error: THE INSERT OR UPDATE VALUE OF FOREIGN KEY IS INVALID

SQLCODE -526, Error: THE REQUESTED OPERATION OR USAGE DOES NOT APPLY TO TEMPORARY TABLE

SQLCODE -525, Error: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS IN ERROR AT
BIND TIME FOR SECTION = PACKAGE = CONSISTENCY TOKEN = X»

SQLCODE -519, Error: THE PREPARE STATEMENT IDENTIFIES THE SELECT STATEMENT OF THE OPENED CURSOR

SQLCODE -518, Error: THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT

SQLCODE -517, Error: CURSOR CANNOT BE USED BECAUSE ITS STATEMENT NAME DOES NOT IDENTIFY A
PREPARED SELECT STATEMENT

SQLCODE -516, Error: THE DESCRIBE FOR STATIC STATEMENT DOES NOT IDENTIFY A PREPARED STATEMENT

SQLCODE -514, Error: THE CURSOR IS NOT IN A PREPARED STATE

SQLCODE -513, Error: THE ALIAS MUST NOT BE DEFINED ON ANOTHER LOCAL OR REMOTE ALIAS

SQLCODE -512, Error: STATEMENT REFERENCE TO REMOTE OBJECT IS INVALID

SQLCODE -511, Error: THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE TABLE DESIGNATED
BY THE CURSOR CANNOT BE MODIFIED

SQLCODE -510, Error: THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR DELETE STATEMENT
CANNOT BE MODIFIED

SQLCODE -509, Error: THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT THE SAME TABLE
DESIGNATED BY THE CURSOR

SQLCODE -508, Error: THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT POSITIONED ON A ROW

SQLCODE -507, Error: THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT OPEN

SQLCODE -504, Error: THE CURSOR NAME IS NOT DEFINED

SQLCODE -503, Error: A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED IN THE UPDATE CLAUSE OF THE
SELECT STATEMENT OF THE CURSOR

SQLCODE -502, Error: THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY OPEN

SQLCODE -501, Error: THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS NOT OPEN

SQLCODE -500, Error: THE IDENTIFIED CURSOR WAS CLOSED WHEN THE CONNECTION WAS DESTROYED

SQLCODE -499, Error: CURSOR HAS ALREADY BEEN ASSIGNED TO THIS OR ANOTHER RESULT SET FROM PROCEDURE

SQLCODE -497, Error: THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN EXCEEDED FOR DATABASE

SQLCODE -496, Error: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT REFERENCES A RESULT SET THAT WAS NOT
CREATED BY THE CURRENT SERVER

SQLCODE -495, Error: ESTIMATED PROCESSOR COST OF PROCESSOR SECONDS ( SERVICE UNITS) IN COST CATEGORY
EXCEEDS A RESOURCE LIMIT ERROR THRESHOLD OF SERVICE UNITS

SQLCODE -492, Error: THE CREATE FUNCTION FOR HAS A PROBLEM WITH PARAMETER NUMBER . IT MAY INVOLVE A
MISMATCH WITH A SOURCE FUNCTION

SQLCODE -491, Error: CREATE STATEMENT FOR USER-DEFINED FUNCTION MUST HAVE A RETURNS CLAUSE, AND EITHER THE
EXTERNAL CLAUSE (WITH OTHER REQUIRED KEYWORDS) OR THE SOURCE CLAUSE

SQLCODE -490, Error: NUMBER DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OF ALLOWABLE
VALUES IN THIS CONTEXT (, )

SQLCODE -487, Error: ATTEMPTED TO EXECUTE AN SQL STATEMENT WHEN THE DEFINITION OF THE FUNCTION OR
PROCEDURE DID NOT SPECIFY THIS ACTION

SQLCODE -483, Error: IN CREATE FUNCTION FOR STATEMENT, THE NUMBER OF PARAMETERS DOES NOT MATCH THE NUMBER
OF PARAMETERS OF THE SOURCE FUNCTION

SQLCODE -482, Error: THE PROCEDURE RETURNED NO LOCATORS

SQLCODE -480, Error: THE PROCEDURE HAS NOT YET BEEN CALLED

SQLCODE -478, Error: DROP OR REVOKE ON OBJECT TYPE CANNOT BE PROCESSED BECAUSE OBJECT OF TYPE IS
DEPENDENT ON IT

SQLCODE -476, Error: REFERENCE TO FUNCTION WAS NAMED WITHOUT A SIGNATURE, BUT THE FUNCTION IS NOT UNIQUE
WITHIN ITS SCHEMA

SQLCODE -475, Error: THE RESULT TYPE OF THE SOURCE FUNCTION CANNOT BE CAST TO THE RETURNS TYPE OF THE
USER-DEFINED FUNCTION

SQLCODE -473, Error: A USER DEFINED DATA TYPE CANNOT BE CALLED THE SAME NAME AS A SYSTEM PREDEFINED TYPE
(BUILT-IN TYPE)

SQLCODE -472, Error: CURSOR WAS LEFT OPEN BY EXTERNAL FUNCTION (SPECIFIC NAME )

SQLCODE -471, Error: INVOCATION OF FUNCTION OR PROCEDURE FAILED DUE TO REASON

SQLCODE -470, Error: SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT PARAMETER , BUT THE STORED
PROCEDURE DOES NOT SUPPORT NULL VALUES

SQLCODE -469, Error: SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST VARIABLE FOR PARAMETER

SQLCODE -461, Error: A VALUE WITH DATA TYPE CANNOT BE CAST TO TYPE

SQLCODE -458, Error: IN A REFERENCE TO FUNCTION BY SIGNATURE, A MATCHING FUNCTION COULD NOT BE FOUND

SQLCODE -457, Error: A FUNCTION OR DISTINCT TYPE CANNOT BE CALLED SINCE IT IS RESERVED FOR SYSTEM USE

SQLCODE -456, Error: IN CREATE FUNCTION FOR , THE SPECIFIC NAME ALREADY EXISTS IN THE SCHEMA

SQLCODE -455, Error: IN CREATE FUNCTION FOR , THE SCHEMA NAME PROVIDED FOR THE SPECIFIC NAME DOES NOT
MATCH THE SCHEMA NAME OF THE FUNCTION

SQLCODE -454, Error: THE SIGNATURE PROVIDED IN THE CREATE FUNCTION STATEMENT FOR MATCHES THE SIGNATURE OF
SOME OTHER FUNCTION ALREADY EXISTING IN THE SCHEMA

SQLCODE -453, Error: THERE IS A PROBLEM WITH THE RETURNS CLAUSE IN THE CREATE FUNCTION STATEMENT FOR

SQLCODE -451, Error: THE DEFINITION, IN THE CREATE FUNCTION FOR CONTAINS DATA TYPE WHICH IS NOT
APPROPRIATE FOR AN EXTERNAL FUNCTION WRITTEN IN THE GIVEN LANGUAGE

SQLCODE -450, Error: USER-DEFINED FUNCTION OR STORED PROCEDURE , PARAMETER NUMBER , OVERLAYED STORAGE
BEYOND ITS DECLARED LENGTH

SQLCODE -449, Error: CREATE OR ALTER STATEMENT FOR FUNCTION OR PROCEDURE CONTAINS AN INVALID FORMAT OF THE
EXTERNAL NAME CLAUSE OR IS MISSING THE EXTERNAL NAME CLAUSE

SQLCODE -444, Error: USER PROGRAM COULD NOT BE FOUND

SQLCODE -441, Error: INVALID USE OF ‘DISTINCT’ OR ‘ALL’ WITH SCALAR FUNCTION

SQLCODE -440, Error: NO BY THE NAME HAVING COMPATIBLE ARGUMENTS WAS FOUND IN THE CURRENT PATH

SQLCODE -438, Error: APPLICATION RAISED ERROR WITH DIAGNOSTIC TEXT:

SQLCODE -435, Error: AN INVALID SQLSTATE IS SPECIFIED IN THE FUNCTION RAISE_ERROR OR IN A SIGNAL
SQLSTATE STATEMENT

SQLCODE -433, Error: VALUE IS TOO LONG

SQLCODE -430, ERROR: (SPECIFIC NAME ) HAS ABNORMALLY TERMINATED

SQLCODE -427, Error: DYNAMIC ROLLBACK NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED

SQLCODE -426, Error: DYNAMIC COMMIT NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED

SQLCODE -423, Error: INVALID VALUE FOR LOCATOR IN POSITION

SQLCODE -421, Error: THE OPERANDS OF A UNION OR UNION ALL DO NOT HAVE THE SAME NUMBER OF COLUMNS

SQLCODE -420, Error: THE VALUE OF A CHARACTER STRING ARGUMENT WAS NOT ACCEPTABLE TO THE FUNCTION

SQLCODE -419, Error: A DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE RESULT WOULD HAVE A NEGATIVE SCALE

SQLCODE -418, Error: A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE OF PARAMETER MARKERS

SQLCODE -417, Error: A STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER MARKERS AS THE OPERANDS
OF THE SAME OPERATOR

SQLCODE -416, Error: AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN

SQLCODE -415, Error: THE CORRESPONDING COLUMNS, , OF THE OPERANDS OF A UNION OR A UNION ALL DO NOT HAVE
COMPARABLE COLUMN DESCRIPTIONS

SQLCODE -414, Error: A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT A STRING

SQLCODE -413, Error: OVERFLOW OCCURRED DURING NUMERIC DATA TYPE CONVERSION

SQLCODE -412, Error: THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS

SQLCODE -411, Error: CURRENT SQLID CANNOT BE USED IN A STATEMENT THAT REFERENCES REMOTE OBJECTS

SQLCODE -410, Error: THE FLOATING POINT LITERAL CONTAINS MORE THAN 30 CHARACTERS

SQLCODE -409, Error: INVALID OPERAND OF A COUNT FUNCTION

SQLCODE -408, Error: THE VALUE IS NOT COMPATIBLE WITH THE DATA TYPE OF ITS TARGET

SQLCODE -406, Error: A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN THE RANGE OF ITS OBJECT COLUMN

SQLCODE -405, Error: THE NUMERIC LITERAL CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OF RANGE

SQLCODE -404, Error: THE SQL STATEMENT SPECIFIES A STRING THAT IS TOO LONG

SQLCODE -402, Error: AN ARITHMETIC FUNCTION OR OPERATOR IS APPLIED TO CHARACTER OR DATETIME DATA

SQLCODE -401, Error: THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT COMPARABLE

SQLCODE -400, Error: THE CATALOG HAS THE MAXIMUM NUMBER OF USER DEFINED INDEXES

SQLCODE -399, Error: ATTEMPTED TO INSERT AN INVALID VALUE INTO A ROWID COLUMN

SQLCODE -398, Error: A LOCATOR WAS REQUESTED FOR HOST VARIABLE NUMBER BUT THE VARIABLE IS NOT A LOB

SQLCODE -397, Error: THE OPTION GENERATED IS SPECIFIED WITH A COLUMN THAT IS NOT A ROW ID OR DISTINCT
TYPE BASED ON A ROW ID

SQLCODE -396, Error: ATTEMPTED TO EXECUTE AN SQL STATEMENT DURING FINAL CALL PROCESSING

SQLCODE -392, Error: SQLDA PROVIDED FOR CURSOR HAS BEEN CHANGED FROM THE PREVIOUS FETCH

SQLCODE -390, Error: THE FUNCTION NAME , SPECIFIC NAME , IS NOT VALID IN THE CONTEXT IN WHICH IT OCCURS

SQLCODE -373, Error: DEFAULT CANNOT BE SPECIFIED FOR IDENTITY COLUMN

SQLCODE -372, Error: ONLY ONE ROWID OR IDENTITY COLUMN IS ALLOWED IN A TABLE

SQLCODE -359, Error: THE RANGE OF VALUES FOR THE IDENTITY COLUMN IS EXHAUSTED

SQLCODE -355, Error: A LOB COLUMN IS TOO LARGE TO BE LOGGED

SQLCODE -352, Error: AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION OF THE INPUT-LIST

SQLCODE -351, Error: AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION OF THE SELECT-LIST

SQLCODE -350, Error: INVALID SPECIFICATION OF A LARGE OBJECT COLUMN

SQLCODE -339, Error: THE SQL STATEMENT CANNOT BE EXECUTED FROM AN ASCII BASED DRDA APPLICATION REQUESTOR TO
A V2R2 DB2 SUBSYSTEM

SQLCODE -338, Error: AN ON CLAUSE IS INVALID

SQLCODE -333, Error: THE SUBTYPE OF A STRING VARIABLE IS NOT THE SAME AS THE SUBTYPE KNOWN AT BIND TIME AND
THE DIFFERENCE CANNOT BE RESOLVED BY TRANSLATION

SQLCODE -332, Error: SYSSTRINGS DOES NOT DEFINE A TRANSLATION FROM CCSID TO

SQLCODE -331, Error: A STRING CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE IT CANNOT BE TRANSLATED.
REASON , CHARACTER , POSITION

SQLCODE -327, Error: THE ROW CANNOT BE INSERTED BECAUSE IT IS OUTSIDE THE BOUND OF THE PARTITION RANGE FOR
THE LAST PARTITION

SQLCODE -314, Error: THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE REFERENCE

SQLCODE -313, Error: THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETER MARKERS

SQLCODE -312, Error: IS AN UNDEFINED OR UNUSABLE HOST VARIABLE OR IS USED IN A DYNAMIC SQL STATEMENT OR A
TRIGGER DEFINITION

SQLCODE -311, Error: THE LENGTH OF INPUT HOST VARIABLE NUMBER IS NEGATIVE OR GREATER THAN THE MAXIMUM

SQLCODE -310, Error: DECIMAL HOST VARIABLE OR PARAMETER CONTAINS NON-DECIMAL DATA

SQLCODE -309, Error: A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL VALUE

SQLCODE -305, Error: THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER BECAUSE NO INDICATOR
VARIABLE IS SPECIFIED

SQLCODE -304, Error: A VALUE WITH DATA TYPE CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE VALUE IS NOT
WITHIN THE RANGE OF THE HOST VARIABLE IN POSITION WITH DATA TYPE

SQLCODE -303, Error: A VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER BECAUSE THE DATA TYPES ARE
NOT COMPARABLE

SQLCODE -302, Error: THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER IS INVALID OR TOO LARGE FOR THE
TARGET COLUMN OR THE TARGET VALUE

SQLCODE -301, Error: THE VALUE OF INPUT HOST VARIABLE OR PARAMETER NUMBER CANNOT BE USED AS SPECIFIED
BECAUSE OF ITS DATA TYPE

SQLCODE -300, Error: THE STRING CONTAINED IN HOST VARIABLE OR PARAMETER IS NOT NUL-TERMINATED

SQLCODE -251, Error: TOKEN IS NOT VALID

SQLCODE -250, Error: THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE-PART OBJECT NAME

SQLCODE -240, Error: THE PART CLAUSE OF A LOCK TABLE STATEMENT IS INVALID

SQLCODE -220, Error: THE COLUMN IN EXPLANATION TABLE IS NOT DEFINED PROPERLY

SQLCODE -219, Error: THE REQUIRED EXPLANATION TABLE DOES NOT EXIST

SQLCODE -214, Error: AN EXPRESSION STARTING WITH IN THE CLAUSE IS NOT VALID. REASON CODE =

SQLCODE -212, Error: IS SPECIFIED MORE THAN ONCE IN THE REFERENCING CLAUSE OF A TRIGGER DEFINITION

SQLCODE -208, Error: THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN IS NOT PART OF THE RESULT TABLE

SQLCODE -206, Error: IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A
FROM CLAUSE, OR IS NOT A COLUMN OF THE TRIGGERING TABLE OF A TRIGGER

SQLCODE -205, Error: IS NOT A COLUMN OF TABLE

SQLCODE -204, Error: IS AN UNDEFINED NAME

SQLCODE -203, Error: A REFERENCE TO COLUMN IS AMBIGUOUS

SQLCODE -199, Error: ILLEGAL USE OF KEYWORD , TOKEN WAS EXPECTED

SQLCODE -198, Error: THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANK OR EMPTY

SQLCODE -197, Error: QUALIFIED COLUMN NAMES IN ORDER BY CLAUSE NOT PERMITTED WHEN UNION OR UNION ALL
SPECIFIED

SQLCODE -191, Error: A STRING CANNOT BE USED BECAUSE IT IS INVALID MIXED DATA

SQLCODE -190, Error: ATTRIBUTES OF COLUMN IN TABLE ARE NOT COMPATIBLE WITH THE EXISTING COLUMN

SQLCODE -189, Error: CCSID IS UNKNOWN OR INVALID FOR THE DATA TYPE OR SUBTYPE

SQLCODE -188, Error: THE STRING REPRESENTATION OF A NAME IS INVALID

SQLCODE -187, Error: A REFERENCE TO A CURRENT DATE/TIME SPECIAL REGISTER IS INVALID BECAUSE THE MVS TOD
CLOCK IS BAD OR THE MVS PARMTZ IS OUT OF RANGE

SQLCODE -186, Error: THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN INCREASED AND EXECUTING PROGRAM
RELIES ON THE OLD LENGTH

SQLCODE -184, Error: AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER MARKER

SQLCODE -183, Error: AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A RESULT THAT IS NOT WITHIN THE
VALID RANGE OF DATES

SQLCODE -182, Error: AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IS INVALID

SQLCODE -181, Error: THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME VALUE

SQLCODE -180, Error: THE DATE, TIME, OR TIMESTAMP VALUE IS INVALID

SQLCODE -173, Error: UR IS SPECIFIED ON THE WITH CLAUSE BUT THE CURSOR IS NOT READ-ONLY

SQLCODE -171, Error: THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT OF IS INVALID

SQLCODE -170, Error: THE NUMBER OF ARGUMENTS SPECIFIED FOR IS INVALID

SQLCODE -164, Error: DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH QUALIFICATION

SQLCODE -160, Error: THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW

SQLCODE -159, Error: DROP OR COMMENT ON IDENTIFIES A(N) RATHER THAN A(N)

SQLCODE -156, Error: THE STATEMENT DOES NOT IDENTIFY A TABLE

SQLCODE -154, Error: THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION IS NOT VALID

SQLCODE -153, Error: THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION DOES NOT INCLUDE A
UNIQUE NAME FOR EACH COLUMN

SQLCODE -152, Error: THE DROP CLAUSE IN THE ALTER STATEMENT IS INVALID BECAUSE IS A

SQLCODE -151, Error: THE UPDATE STATEMENT IS INVALID BECAUSE THE CATALOG DESCRIPTION OF COLUMN INDICATES
THAT IT CANNOT BE UPDATED

SQLCODE -150, Error: THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW OR TRANSITION TABLE
FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED

SQLCODE -148, Error: THE SOURCE TABLE CANNOT BE RENAMED OR ALTERED

SQLCODE -147, Error: ALTER FUNCTION FAILED BECAUSE SOURCE FUNCTIONS CANNOT BE ALTERED

SQLCODE -144, Error: INVALID SECTION NUMBER

SQLCODE -142, Error: THE SQL STATEMENT IS NOT SUPPORTED

SQLCODE -138, Error: THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS OUT OF RANGE

SQLCODE -137, Error: THE LENGTH RESULTING FROM IS GREATER THAN

SQLCODE -136, Error: SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES

SQLCODE -133, Error: A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID BECAUSE ALL COLUMN
REFERENCES IN ITS ARGUMENT ARE NOT CORRELATED TO THE GROUP BY RESULT THAT THE HAVING CLAUSE IS APPLIED TO

SQLCODE -132, Error: AN OPERAND OF x IS NOT VALID

SQLCODE -131, Error: STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES

SQLCODE -130, Error: THE ESCAPE CLAUSE CONSISTS OF MORE THAN ONE CHARACTER, OR THE STRING PATTERN CONTAINS
AN INVALID OCCURRENCE OF THE ESCAPE CHARACTER

SQLCODE -129, Error: THE STATEMENT CONTAINS TOO MANY TABLE NAMES

SQLCODE -128, Error: INVALID USE OF NULL IN A PREDICATE

SQLCODE -127, Error: DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT

SQLCODE -126, Error: THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY CLAUSE

SQLCODE -125, Error: AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT

SQLCODE -123, Error: THE PARAMETER IN POSITION IN THE FUNCTION MUST BE A CONSTANT OR KEYWORD

SQLCODE -121, Error: THE COLUMN IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE OR SET TRANSITION
VARIABLE STATEMENT

SQLCODE -120, Error: A WHERE CLAUSE, SET CLAUSE, VALUES CLAUSE, OR A SET ASSIGNMENT STATEMENT INCLUDES A
COLUMN FUNCTION

SQLCODE -119, Error: A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED IN THE GROUP BY CLAUSE

SQLCODE -117, Error: THE NUMBER OF ASSIGNED VALUES IS NOT THE SAME AS THE NUMBER OF SPECIFIED OR IMPLIED
COLUMNS

SQLCODE -115, Error: A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR IS FOLLOWED BY A PARENTHESIZED
LIST OR BY ANY OR ALL WITHOUT A SUBQUERY

SQLCODE -114, Error: THE LOCATION NAME DOES NOT MATCH THE CURRENT SERVER

SQLCODE -113, Error: INVALID CHARACTER FOUND IN: . REASON CODE

SQLCODE -112, Error: THE OPERAND OF A COLUMN FUNCTION IS ANOTHER COLUMN FUNCTION

SQLCODE -111, Error: A COLUMN FUNCTION DOES NOT INCLUDE A COLUMN NAME

SQLCODE -110, Error: INVALID HEXADECIMAL LITERAL BEGINNING

SQLCODE -109, Error: CLAUSE IS NOT PERMITTED

SQLCODE -108, Error: THE NAME IS QUALIFIED INCORRECTLY

SQLCODE -107, Error: THE NAME IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS

SQLCODE -105, Error: INVALID STRING

SQLCODE -104, Error: ILLEGAL SYMBOL «». SOME SYMBOLS THAT MIGHT BE LEGAL ARE:

SQLCODE -103, Error: IS AN INVALID NUMERIC LITERAL

SQLCODE -102, Error: LITERAL STRING IS TOO LONG. STRING BEGINS

SQLCODE -101, Error: THE STATEMENT IS TOO LONG OR TOO COMPLEX

SQLCODE -097, Error: THE USE OF LONG VARCHAR OR LONG VARGRAPHIC IS NOT ALLOWED IN THIS CONTEXT

SQLCODE -084, Error: UNACCEPTABLE SQL STATEMENT

SQLCODE -079, Error: QUALIFIER FOR DECLARED GLOBAL TEMPORARY TABLE OR INDEX MUST BE SESSION, NOT

SQLCODE -060, Error: INVALID SPECIFICATION :

SQLCODE -029, Error: INTO CLAUSE REQUIRED

SQLCODE -010, Error: THE STRING CONSTANT BEGINNING IS NOT TERMINATED

SQLCODE -007, Error: STATEMENT CONTAINS THE ILLEGAL CHARACTER

SQLCODE 000,SUCCESSFUL EXECUTION

SQLCODE 012, Warning: THE UNQUALIFIED COLUMN NAME WAS INTERPRETED AS A CORRELATED REFERENCE

SQLCODE 098, Warning: A DYNAMIC SQL STATEMENT ENDS WITH A SEMICOLON

SQLCODE 110, Warning: SQL UPDATE TO A DATA CAPTURE TABLE NOT SIGNALED TO ORIGINATING SUBSYSTEM

SQLCODE 111, Warning: THE SUBPAGES OPTION IS NOT SUPPORTED FOR TYPE 2 INDEXES

SQLCODE 117, Warning: THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NUMBER OF OBJECT COLUMNS

SQLCODE 162, Warning: TABLE SPACE . HAS BEEN PLACED IN CHECK PENDING

SQLCODE 203, Warning: THE QUALIFIED COLUMN NAME WAS RESOLVED USING A NON-UNIQUE OR UNEXPOSED NAME

SQLCODE 204, Warning: IS AN UNDEFINED NAME

SQLCODE 218, Warning: THE SQL STATEMENT REFERENCING A REMOTE OBJECT CANNOT BE EXPLAINED

SQLCODE 219, Warning: THE REQUIRED EXPLANATION TABLE DOES NOT EXIST

SQLCODE 220, Warning: THE COLUMN IN EXPLANATION TABLE IS NOT DEFINED PROPERLY

SQLCODE 236, Warning: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED FOR COLUMNS

SQLCODE 237, Warning: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED BECAUSE AT LEAST ONE OF THE COLUMNS
BEING DESCRIBED IS A DISTINCT TYPE

SQLCODE 238, Warning: SQLDA INCLUDES SQLVAR ENTRIES, BUT SQLVAR ENTRIES ARE NEEDED FOR COLUMNS BECAUSE
AT LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A LOB

SQLCODE 239, Warning: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED FOR COLUMNS BECAUSE AT LEAST ONE
OF THE COLUMNS BEING DESCRIBED IS A DISTINCT TYPE

SQLCODE 304, Warning: A VALUE WITH DATA TYPE CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE VALUE IS
NOT WITHIN THE RANGE OF THE HOST VARIABLE IN POSITION WITH DATA TYPE

SQLCODE 331, Warning: THE NULL VALUE HAS BEEN ASSIGNED TO A HOST VARIABLE BECAUSE THE STRING CANNOT BE
TRANSLATED. REASON , CHARACTER , HOST VARIABLE

SQLCODE 339, Warning: THE SQL STATEMENT HAS BEEN SUCCESSFULLY EXECUTED BUT THERE MAY BE SOME CHARACTER
CONVERSION INCONSISTENCIES

SQLCODE 394, Warning: USER SPECIFIED OPTIMIZATION HINTS USED DURING ACCESS PATH SELECTION

SQLCODE 395, Warning: USER SPECIFIED OPTIMIZATION HINTS ARE INVALID (REASON CODE = »).
THE OPTIMIZATION HINTS ARE IGNORED

SQLCODE 402, Warning: LOCATION IS UNKNOWN

SQLCODE 403, Warning: THE LOCAL OBJECT REFERENCED BY THE CREATE ALIAS STATEMENT DOES NOT EXIST

SQLCODE 434, Warning: OPTION IS A DEPRECATED FEATURE

SQLCODE 445, Warning: VALUE HAS BEEN TRUNCATED

SQLCODE 462, Warning: EXTERNAL FUNCTION OR PROCEDURE (SPECIFIC NAME ) HAS RETURNED A WARNING SQLSTATE,
WITH DIAGNOSTIC TEXT

SQLCODE 464, Warning: PROCEDURE RETURNED QUERY RESULT SETS, WHICH EXCEEDS THE DEFINED LIMIT

SQLCODE 466, Warning: PROCEDURE RETURNED QUERY RESULT SETS

SQLCODE 494, Warning: NUMBER OF RESULT SETS IS GREATER THAN NUMBER OF LOCATORS

SQLCODE 495, Warning: ESTIMATED PROCESSOR COST OF PROCESSOR SECONDS ( SERVICE UNITS) IN COST CATEGORY
EXCEEDS A RESOURCE LIMIT WARNING THRESHOLD OF SERVICE UNITS

SQLCODE 535, Warning: THE RESULT OF THE POSITIONED UPDATE OR DELETE MAY DEPEND ON THE ORDER OF THE ROWS

SQLCODE 541, Warning: THE REFERENTIAL OR UNIQUE CONSTRAINT HAS BEEN IGNORED BECAUSE IT IS A DUPLICATE

SQLCODE 551, Warning: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION ON OBJECT

SQLCODE 552, Warning: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION

SQLCODE 558, Warning: THE WITH GRANT OPTION IS IGNORED

SQLCODE 561, Warning: THE ALTER, INDEX, REFERENCES, AND TRIGGER PRIVILEGES CANNOT BE GRANTED TO
PUBLIC AT ALL LOCATIONS

SQLCODE 562, Warning: A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY
HAS THE PRIVILEGE FROM THE GRANTOR

SQLCODE 585, Warning: THE SCHEMA NAME APPEARS MORE THAN ONCE IN THE CURRENT PATH

SQLCODE 610, Warning: A CREATE/ALTER ON OBJECT HAS PLACED OBJECT IN PENDING

SQLCODE 625, Warning: THE DEFINITION OF TABLE HAS BEEN CHANGED TO INCOMPLETE

SQLCODE 626, Warning: DROPPING THE INDEX TERMINATES ENFORCEMENT OF THE UNIQUENESS OF A KEY THAT WAS DEFINED
WHEN THE TABLE WAS CREATED

SQLCODE 645, Warning: WHERE NOT NULL IS IGNORED BECAUSE THE INDEX KEY CANNOT CONTAIN NULL VALUES

SQLCODE 650, Warning: THE TABLE BEING CREATED OR ALTERED CAN NOT BECOME A DEPENDENT TABLE

SQLCODE 653, Warning: TABLE IN PARTITIONED TABLE SPACE IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS
NOT BEEN CREATED

SQLCODE 655, Warning: STOGROUP HAS BOTH SPECIFIC AND NON-SPECIFIC VOLUME IDS. IT WILL NOT BE ALLOWED IN
FUTURE RELEASES.

SQLCODE 658, Warning: THE SUBPAGES VALUE IS IGNORED FOR THE CATALOG INDEX

SQLCODE 664, Warning: THE INTERNAL LENGTH OF THE LIMIT-KEY FIELDS FOR THE PARTITIONED INDEX EXCEEDS THE
LENGTH IMPOSED BY THE INDEX MANAGER

SQLCODE 738, Warning: DEFINITION CHANGE OF MAY REQUIRE SIMILAR CHANGE ON READ-ONLY SYSTEMS

SQLCODE 799, Warning: A SET STATEMENT REFERENCES A SPECIAL REGISTER THAT DOES NOT EXIST AT THE SERVER SITE

SQLCODE 802, Warning: EXCEPTION ERROR HAS OCCURRED DURING OPERATION ON DATA, POSITION

SQLCODE 807, Warning: THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE OVERFLOW

SQLCODE 863, Warning: THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE SUPPORTED

SQLCODE 883, Warning: ROLLBACK TO SAVEPOINT OCCURRED WHEN THERE WERE OPERATIONS THAT CANNOT BE UNDONE OR AN
OPERATION THAT CANNOT BE UNDONE OCCURRED WHEN THERE WAS A SAVEPOINT OUTSTANDING

Источник

← →
maximsms
 
(2006-03-05 14:20)
[0]

Невозможно работать с удалённой базой. Препробовал множество вариантов gds32.dll IBExpert работает как часы,
почти со всеми вариантами клиентских библиотек Firebird.
А тут подключение происходит но невозможен даже простой select. Использую ibx,  судя по тому что прочитал в интернете об этой проблеме, FIBPlus проблему не решает.
Удалённый сервер Firebird 1.5 LI-V6.3.2.4731

---

← →
maximsms
 
(2006-03-05 17:40)
[1]

Удалено модератором
Примечание: Создание пустых соощений

---

← →
Johnmen ©
 
(2006-03-05 18:50)
[2]

Код в студию!

---

← →
maximsms
 
(2006-03-05 19:05)
[3]

tibdatabase().connect
//SUCCEED
……
tibsql().sql.text:=»select id from table1″;
tibsql().execquery;
//CAUSES FAILURE WITH MESSAGE
//Dynamic SQL Error SQL error code = -901 feature is not supported

---

← →
Desdechado ©
 
(2006-03-05 20:49)
[4]

что за странные скобочки?
может, лучше сначала создать экземпляр класса, потом его использовать, а то так ты просто теряешь указатели на свои объекты и их невозможно больше найти для использования.
ведь для выполнения SQL нужно указать, через какое соединение будешь это делать, а у тебя для него уже нет указателя…

---

← →
maximsms
 
(2006-03-05 21:00)
[5]

---

← →
Desdechado ©
 
(2006-03-05 21:04)
[6]

а в чем?
от фонаря и работать будет

---

← →
maximsms
 
(2006-03-05 21:06)
[7]

---

← →
Johnmen ©
 
(2006-03-06 10:11)
[8]

Почему для селективного запроса используется .execquery?

---

← →
mbgmz ©
 
(2006-03-10 02:51)
[9]

> Johnmen ©   (06.03.06 10:11) [8]
> Почему для селективного запроса используется .execquery?
>

потому что у TIBSQL нет другого походящего метода

---

← →
mbgmz ©
 
(2006-03-10 02:54)
[10]

вопрос снят, после того как я переставил Delphi и Firebird сервер,
каким-то чудом оно заработало. Но выявить причину почему оно не работало мне так и не удалось

---

← →
Johnmen ©
 
(2006-03-10 09:14)
[11]

---

← →
msguns ©
 
(2006-03-10 09:32)
[12]

---

← →
mbgmz ©
 
(2006-03-11 06:09)
[13]

---

← →
jack128 ©
 
(2006-03-11 15:44)
[14]

Johnmen ©   (10.03.06 9:14) [11]
Почему для селективного запроса используется TIBSQL?
а почему бы и нет?? Я активно использую и проблем не имею

---

← →
Johnmen ©
 
(2006-03-11 20:47)
[15]

---

← →
jack128 ©
 
(2006-03-11 22:59)
[16]

---

← →
DrPass ©
 
(2006-03-12 12:38)
[17]

> И что я найду в справке по IBX про ошибку N: -901 ???
> Лучше бы подсказали как выявить причину, вызывающую эту
> ошибку

Насчет справки не знаю, а то, что IBX не поддерживает Firebird и не гарантирует совместимость с ней, разработчики IBX повторяли не раз…

---