Sql error code 607

Sql error code 607 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 […]

Sql error code 607

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

Источник

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
/******************************************************************************/
/***         Generated by IBExpert 2017.10.11.1 22.10.2017 4:19:34          ***/
/******************************************************************************/
 
SET SQL DIALECT 3;
 
SET NAMES WIN1251;
 
SET CLIENTLIB 'C:Program FilesFirebirdFirebird_2_5WOW64fbclient.dll';
 
CREATE DATABASE 'C:UsersannasDesktopВузБакалавриат ЗДисциплиныУправление даннымиЛабараторныеЛабараторная 4П4.FDB'
USER 'SYSDBA' PASSWORD 'masterkey'
PAGE_SIZE 16384
DEFAULT CHARACTER SET WIN1251 COLLATION WIN1251;
 
 
 
/******************************************************************************/
/***                                Domains                                 ***/
/******************************************************************************/
 
CREATE DOMAIN B AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN ESKIZ AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN GPT AS
SMALLINT
NOT NULL;
 
CREATE DOMAIN HEL AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN HOP AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN HRABOCHAYA AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN HZAPAS AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN K AS
SMALLINT
NOT NULL;
 
CREATE DOMAIN K1 AS
SMALLINT
NOT NULL;
 
CREATE DOMAIN KO AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN L AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN M1 AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN M2 AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN MARKA AS
VARCHAR(30)
NOT NULL;
 
CREATE DOMAIN MARKA1 AS
VARCHAR(30)
NOT NULL;
 
CREATE DOMAIN MM AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN MPR AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN MSTR AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN N1 AS
SMALLINT
NOT NULL;
 
CREATE DOMAIN N2 AS
SMALLINT
NOT NULL;
 
CREATE DOMAIN NE AS
SMALLINT
NOT NULL;
 
CREATE DOMAIN OM AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN PM AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN PPZ AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN PSM AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN PTM AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN SOE AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN SS AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN T AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN UPZ AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN USM AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN UTM AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN VMONT AS
NUMERIC(10,10)
NOT NULL;
 
CREATE DOMAIN VR AS
SMALLINT
NOT NULL;
 
CREATE DOMAIN VS AS
SMALLINT
NOT NULL;
 
CREATE DOMAIN VU AS
SMALLINT
NOT NULL;
 
 
 
/******************************************************************************/
/***                                 Tables                                 ***/
/******************************************************************************/
 
 
 
CREATE TABLE SKHEMAOPIRANIYAISTROPOVKIKONSTR (
    NOMER                     N1,
    NAIMENOVANIEELEMENTOV     MARKA,
    SKHEMYOPIRANIYAELEMENTOV  SOE,
    SKHEMYSTROPOVKI           SS
);
 
 
CREATE TABLE SPECIPIKACIYAMONTAGNIHELEMENTOV (
    NOMER                  NE,
    NAIMENIVANIE           MARKA,
    MASSA                  M1,
    KOLICHESTVO            K,
    OBSHAYMASSA            OM,
    DLINA                  L,
    SHIRINA                B,
    TOLSHINA               T,
    KOEFFITSIENTOTTYAZHKI  KO,
    VREMYASTROPOVKI        VS,
    VREMYAUSTANOVKI        VU,
    VREMYARASCTROPOVKI     VR
);
 
 
CREATE TABLE TEPVARIANTA (
    PRODOLGINELNOSTMONTAGA       PM,
    POLNAYATRUDOEMKOSTMONTAGA    PTM,
    POLNAYASEBESTOIMOSTMONTAGA   PSM,
    POLNIEPIVEDENNIEZATRATI      PPZ,
    MASSAVSEHELEMENTOV           MM,
    UDELNAYATRUDOEMKOSTMONTAGA   UTM,
    UDELNAYASEBESTOIMOSTMONTAGA  USM,
    UDELNIEPIVEDENNIEZATRATI     UPZ
);
 
 
CREATE TABLE VEDOMOSTGRUZOZAKHVATNYKHUSTR (
    NOMER                      N2,
    NAIMENOVANIEELEMENTOV      MARKA1,
    ESKIZOSNASTKI              ESKIZ,
    GRUZOPODEMNOST             GPT,
    VYSOTAVRABOCHEMPOLOZHENII  HRABOCHAYA,
    MASSA                      M2,
    KOLICHESTVO                K1
);
 
 
CREATE TABLE VEDOMOSTMONTAGNIHHARAKTERISTIK (
    MASSAODNOGOELEMENTA       M1,
    MASSASTROPOV              MSTR,
    MASSAMONTAZHNYKHPRIBOROV  MPR,
    VYSOTAOPORY               HOP,
    ZAPASPOVYSOTE             HZAPAS,
    VYSOTAELEMENTA            HEL,
    VYSOTASTROPOVKI           VS,
    MONTAZHNAYAVYSOTA         VMONT
);
 
 
 
 
/******************************************************************************/
/***                                Indices                                 ***/
/******************************************************************************/
 
CREATE INDEX IDNAIMENOVANIEELEMENTOVW ON SKHEMAOPIRANIYAISTROPOVKIKONSTR (NAIMENOVANIEELEMENTOV);
CREATE INDEX IDSKHEMYOPIRANIYAELEMENTOVW ON SKHEMAOPIRANIYAISTROPOVKIKONSTR (SKHEMYOPIRANIYAELEMENTOV);
CREATE INDEX IDSKHEMYSTROPOVKIW ON SKHEMAOPIRANIYAISTROPOVKIKONSTR (SKHEMYSTROPOVKI);
CREATE INDEX IDDLINAW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (DLINA);
CREATE INDEX IDKOEFFITSIENTOTTYAZHKIW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (KOEFFITSIENTOTTYAZHKI);
CREATE INDEX IDKOLICHESTVOW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (KOLICHESTVO);
CREATE INDEX IDMASSAW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (MASSA);
CREATE INDEX IDNAIMENIVANIEW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (NAIMENIVANIE);
CREATE INDEX IDNOMERW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (NOMER);
CREATE INDEX IDOBSHAYMASSAW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (OBSHAYMASSA);
CREATE INDEX IDSHIRINAW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (SHIRINA);
CREATE INDEX IDTOLSHINAW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (TOLSHINA);
CREATE INDEX IDVREMYARASCTROPOVKIW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (VREMYARASCTROPOVKI);
CREATE INDEX IDVREMYASTROPOVKIW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (VREMYASTROPOVKI);
CREATE INDEX IDVREMYAUSTANOVKIW ON SPECIPIKACIYAMONTAGNIHELEMENTOV (VREMYAUSTANOVKI);
CREATE INDEX IDMASSAVSEHELEMENTOVW ON TEPVARIANTA (MASSAVSEHELEMENTOV);
CREATE INDEX IDPOLNAYASEBESTOIMOSTMONTAGAW ON TEPVARIANTA (POLNAYASEBESTOIMOSTMONTAGA);
CREATE INDEX IDPOLNAYATRUDOEMKOSTMONTAGAW ON TEPVARIANTA (POLNAYATRUDOEMKOSTMONTAGA);
CREATE INDEX IDPOLNIEPIVEDENNIEZATRATIW ON TEPVARIANTA (POLNIEPIVEDENNIEZATRATI);
CREATE INDEX IDPRODOLGINELNOSTMONTAGAW ON TEPVARIANTA (PRODOLGINELNOSTMONTAGA);
CREATE INDEX IDUDELNAYASEBESTOIMOSTMONTAGAW ON TEPVARIANTA (UDELNAYASEBESTOIMOSTMONTAGA);
CREATE INDEX IDUDELNAYATRUDOEMKOSTMONTAGAW ON TEPVARIANTA (UDELNAYATRUDOEMKOSTMONTAGA);
CREATE INDEX IDUDELNIEPIVEDENNIEZATRATIW ON TEPVARIANTA (UDELNIEPIVEDENNIEZATRATI);
CREATE INDEX IDESKIZOSNASTKIW ON VEDOMOSTGRUZOZAKHVATNYKHUSTR (ESKIZOSNASTKI);
CREATE INDEX IDGRUZOPODEMNOSTW ON VEDOMOSTGRUZOZAKHVATNYKHUSTR (GRUZOPODEMNOST);
CREATE INDEX IDKOLICHESTVO ON VEDOMOSTGRUZOZAKHVATNYKHUSTR (KOLICHESTVO);
CREATE INDEX IDVYSOTAVRABOCHEMPOLOZHENIIW ON VEDOMOSTGRUZOZAKHVATNYKHUSTR (VYSOTAVRABOCHEMPOLOZHENII);
CREATE INDEX IDMASSAMONTAZHNYKHPRIBOROVW ON VEDOMOSTMONTAGNIHHARAKTERISTIK (MASSAMONTAZHNYKHPRIBOROV);
CREATE INDEX IDMASSAODNOGOELEMENTAW ON VEDOMOSTMONTAGNIHHARAKTERISTIK (MASSAODNOGOELEMENTA);
CREATE INDEX IDMASSASTROPOVW ON VEDOMOSTMONTAGNIHHARAKTERISTIK (MASSASTROPOV);
CREATE INDEX IDMONTAZHNAYAVYSOTAW ON VEDOMOSTMONTAGNIHHARAKTERISTIK (MONTAZHNAYAVYSOTA);
CREATE INDEX IDVYSOTAELEMENTAW ON VEDOMOSTMONTAGNIHHARAKTERISTIK (VYSOTAELEMENTA);
CREATE INDEX IDVYSOTAOPORYW ON VEDOMOSTMONTAGNIHHARAKTERISTIK (VYSOTAOPORY);
CREATE INDEX IDVYSOTASTROPOVKIW ON VEDOMOSTMONTAGNIHHARAKTERISTIK (VYSOTASTROPOVKI);
CREATE INDEX IDZAPASPOVYSOTEW ON VEDOMOSTMONTAGNIHHARAKTERISTIK (ZAPASPOVYSOTE);


Description


Richard Demattio



2020-09-26 10:18:46 UTC

Description:
I tried to change a previously defined boolean type column to varchar(30) and got the error "SQL_BOOLEAN does not exist".


Steps to Reproduce:
1.I tried to change the field type of a table column from BOOLEAN to VARCHAR(30)
2.I was asked to confirm, that the column will be deleted and readded as new type
3.I confirmed and got an error message: - see below

Actual Results:
Errormessage:
firebird_sdbc error:
*unsuccessful metadata update
*ALTER TABLE tlg_Nutzbarkeit failed
*SQL error code = -607
*Invalid command
*Specified domain or source column SQL_BOOLEAN does not exist
caused by
'ALTER TABLE "tlg_Nutzbarkeit" ADD "frei" SQL_BOOLEAN'
 /home/buildslave/source/libo-core/connectivity/source/drivers/firebird/Util.cxx:68

Expected Results:
it should work.



Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
It is possible to select that "Yes/no[boolean]" type in the "table design view".
(I did it this way earlier.)

Similar behaviour, when I tried to change a column type from other type to varchar.

Changing via "SQL ALTER TABLE ..." works


Comment 1


Richard Demattio



2020-10-17 20:48:04 UTC

I testesd this time with LO 7.1.1.0,
Build 
https://gerrit.libreoffice.org/gitweb?p=core.git;a=log;h=17cbc559be6936777904e5cf8a517cac89045264

I could not reproduce the message "SQL_BOOLEAN does not exist" with the daily build, but I could reproduce a crash this time, when I tried to change the type..

TESTCASE: based on a table with two fields I did the following in design view:

1.) Add new field "test1" VARCHAR
2.) add new field "Test2" INTEGER
3.) change Type of "test1" to BOOLEAN
    Error code: 1
    firebird_sdbc error:
    *unsuccessful metadata update
    *ALTER TABLE tla_Kontaktarten failed
    *action cancelled by trigger (1) to preserve data integrity
    *Cannot update index segment used by an Integrity Constraint
    caused by
    'ALTER TABLE "tla_Kontaktarten" ALTER COLUMN "Typ" TYPE BOOLEAN'
     /tinderbox/buildslave/source/libo-master/connectivity/source/drivers/firebird/Util.cxx:68

4.) I confirmed (nevertheless)
    The change happened, although the errormessage said, it failed

5.) I again changed "test1" back to VARCHAR

 ... CRASH (two times ... reproducable)


Comment 2


Richard Demattio



2020-10-17 20:51:35 UTC

I sent two crash reports, but I myself could not see the Report number
sorry


Comment 3


Robert Großkopf



2020-10-18 16:38:35 UTC

First this error appears when changing Boolean field to Varchar:
Conversion from base type BOOLEAN to VARCHAR is not supported.

When I confirm to delete the old Boolean field and add a new Varchar field it will work here. So I could not confirm the buggy behavior.

Tested with LO 7.0.2.2 on OpenSUSE 15.1 64bit rpm Linux


Comment 4


Richard Demattio



2020-10-18 17:00:50 UTC

(In reply to Robert Großkopf from comment #3)
> First this error appears when changing Boolean field to Varchar:
> Conversion from base type BOOLEAN to VARCHAR is not supported.
> 
> When I confirm to delete the old Boolean field and add a new Varchar field
> it will work here. So I could not confirm the buggy behavior.
> 
> Tested with LO 7.0.2.2 on OpenSUSE 15.1 64bit rpm Linux

I agree - it is stupid, changing VARCHAR to BOOLEAN and the other way round.
Your way makes more sense.

But what I did must not lead to a crash, but should be prohibited by logic.
In general: rejecting forbidden conversions by logic will increase stability.

Such kind of inputs can happen accidentally.


Comment 5


Richard Demattio



2020-10-19 08:19:03 UTC

(In reply to Richard Demattio from comment #4)
> (In reply to Robert Großkopf from comment #3)
> > First this error appears when changing Boolean field to Varchar:
> > Conversion from base type BOOLEAN to VARCHAR is not supported.
> > 
> > When I confirm to delete the old Boolean field and add a new Varchar field
> > it will work here. So I could not confirm the buggy behavior.
> > 
> > Tested with LO 7.0.2.2 on OpenSUSE 15.1 64bit rpm Linux

The crash happens, when you continue 
and try to change the now boolean field back to VARCHAR.

(My last answer was based on a misunderstanding of what you said)


Comment 6


Robert Großkopf



2020-10-19 09:27:26 UTC

(In reply to Richard Demattio from comment #5)
> 
> The crash happens, when you continue 
> and try to change the now boolean field back to VARCHAR.

And exactly this I couldn't confirm. The only thing I noticed: The changing of the field type will switch back in the GUI table editor. So I have to change the type again.


Comment 7


Julien Nabet



2020-11-01 09:22:27 UTC

On pc Debian x86-64 with master sources updated today, here what I got with an embedded Firebird:
- I create a table with "id"/INTEGER as primary key + "f1" as BOOLEAN field
- save + quit editing
=> OK
- reopen to edit the table and change BOOLEAN to VARCHAR + click save (arrow icon at the left)
=> message: "the column "f1" could not be changed. Should the column instead be deleted and the new format appended?
Console logs show:
warn:connectivity.firebird:15955:15955:connectivity/source/drivers/firebird/Statement.cxx:114: isc_dsql_execute failed
warn:connectivity.firebird:15955:15955:connectivity/source/drivers/firebird/Util.cxx:57: firebird_sdbc error:
*unsuccessful metadata update
*ALTER TABLE Table3 failed
*Cannot change datatype for f1.  Conversion from base type BOOLEAN to VARCHAR is not supported.
caused by
'ALTER TABLE "Table3" ALTER COLUMN "f1" TYPE VARCHAR(100)'

- click Yes
=> UI shows back BOOLEAN instead of VARCHAR
- click Save icon + quit editing
- editing again, the field shows now VARCHAR (!!)

So for me no crash but a pb of UI refresh, it shouldn't display "BOOLEAN" just before final editing quit.


Comment 8


Richard Demattio



2020-11-01 10:33:52 UTC

(In reply to Julien Nabet from comment #7)
> .....
> 
> So for me no crash but a pb of UI refresh, it shouldn't display "BOOLEAN"
> just before final editing quit.

I can no longer reproduce the crash too - not even, when doing really crazy things.

Meanwhile I changed a lot in the database, where it happened first.
Maybe I forgot to document the one little, but significant step leading to reproducable crash. - sorry


Comment 9


Julien Nabet



2020-11-01 11:11:27 UTC

Let's put this one to WFM then.

Richard: if you can find the way to reproduce the crash or -607 error, don't hesitate to reopen this tracker.


Comment 11


Julien Nabet



2020-11-02 19:54:31 UTC

The request to create the first table worked but not the second request.

Would it be possible you attach the odb file?


Comment 12


Richard Demattio



2020-11-02 20:23:16 UTC

Created attachment 166953 [details]
here you are - the requested Database;

The database is at the status before that step below

"    - now I entered design mode again by "<right klick> / Edit"
      - and set "Entry required" to "YES"
      - and klicked the save icon for the table"

~~~~~~~~~~~+
I tested the SQLs and it worked.

Maybe you tried to execute all the SQL statements  in one step.
This does not work!

You have to execute every instruction ending by a semicolon separately.


Comment 13


Julien Nabet



2020-11-03 12:35:22 UTC

(In reply to Richard Demattio from comment #12)
> ...
> Maybe you tried to execute all the SQL statements  in one step.
> This does not work!
> ...
Thank you for your feedback but I did try one by one and it failed for me.

Anyway, I gave a try with your DB and tested from
"
    - now I entered design mode again by "<right klick> / Edit"
      - and set "Entry required" to "YES"
      - and klicked the save icon for the table
~~~~~~~~~~~~~~~~~~~~~~~      
I got the Warning: "The column "Unit" could not be changed. 
                    Should the column be deleted and the new format appended?"
and on "More" I got the additional information:
Error code: 1

firebird_sdbc error:
*UPDATE operation is not allowed for system table RDB$RELATION_FIELDS
caused by
'UPDATE RDB$RELATION_FIELDS SET RDB$NULL_FLAG = 1 WHERE RDB$FIELD_NAME = 'Unit' AND RDB$RELATION_NAME = 'BUG137042''
 /tinderbox/buildslave/source/libo-70/connectivity/source/drivers/firebird/Util.cxx:68
=> OK, I got the same

then:
I said "yes" to the warning message
but got:
*Cannot make field Unit of table BUG137042 NOT NULL because there are NULLs present
caused by
'ALTER TABLE "BUG137042" ADD "Unit" VARCHAR(5) NOT NULL'

I think the change of message is due to some recent commits on I did master sources.
About this new problem, it seems LO is stucked because it removed a column where there was a value but when trying to add the column, it has no value whereas it's required.
I don't know how and even if it can be fixed.


Comment 14


Julien Nabet



2020-11-03 12:37:53 UTC

BTW, with LO Debian package 7.0.2.2, I reproduce your pb with exactly the same message.=>NEW
So I confirm the recent commits made the message change.


Comment 15


QA Administrators



2022-12-07 03:22:26 UTC


Comment hidden (obsolete)

Dear Richard Demattio,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug


Comment 16


Richard Demattio



2022-12-09 17:56:22 UTC

I testesd this time with LO 7.4.2.3.
In table design view 
I changed some field types in the test table and it works as it should:
-> the fields are deleted and appended at the end with the new type.

I also tried to change the type of the field, which is part of an index.
-> this change was rejected without a crash. --> also OK

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Version: 7.4.2.3 / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: de-AT (en_US.UTF-8); UI: en-US
Calc: threaded

Go Up to InterBase Quick Start: Part II — Data Definition

You should now understand how to create tables. You create the rest of the tables using an SQL script.
If you wish to examine the syntax regarding tables further, take a look at the TABLES.SQL script. For example, the definition of the Employee table contains a complex CHECK constraint for the salary column:

CHECK ( salary >=
(
       SELECT min_salary
       FROM   job
       WHERE  job.job_code = employee.job_code
       AND    job.job_grade = employee.job_grade
       AND    job.job_country = employee.job_country)
AND
salary <=
(
       SELECT max_salary
       FROM   job
       WHERE  job.job_code = employee.job_code
       AND    job.job_grade = employee.job_grade
       AND    job.job_country = employee.job_country))

This constraint ensures that the salary of an employee is greater than the minimum salary for the job of that employee (specified by job_code, job_grade, and job_country) and lesser than a corresponding maximum salary.

Contents

  • 1 Run the TABLES.SQL Script
    • 1.1 Time to Back up
    • 1.2 Troubleshooting
  • 2 Altering Tables
    • 2.1 Altering the Department Table
  • 3 More Troubleshooting
  • 4 Advance To:

Image 025.jpgRun the TABLES.SQL Script

  1. Load the TABLES.SQL script.
  2. Execute the query.

    Note:
    If you see any errors, refer to the Troubleshooting section for help.

  3. To confirm that the tables now exist, click on Tables item in the left pane of IBConsole. You should see the following tables:
TutorialTables3.png

Time to Back up

If you have successfully executed the TABLES.SQL script, it is a good time to back up your database.

Troubleshooting

If you make a mistake when entering domain definitions, you get an error message when you run the TABLES.SQL script or when you define the tables manually.

To identify an error:

  • When you run a script: Take a look at the log file. You can find the log file in the same directory as your script file.
  • When you execute a query: The SQL output area displays any errors that occur.

In any case, if there is a problem with a particular table, an error message like this appears:

Statement failed, SQLCODE = -607 
Dynamic SQL Error
-SQL error code = -607
-Invalid command
-Specified domain or source column does not exist

Follow these steps to resolve the problem:

  1. Read the error text. In this case it says that the specified domain does not exist. That means you probably made an error when typing the domain name.
  2. Select Domains in the left pane of IBConsole.
  3. You should see four domains that you manually defined: FIRSTNAME, LASTNAME, EMPNO, and DEPTNO. Confirm that the names of the domains are correct. It is likely that you misspelled a name.
  4. Drop the incorrect domain by entering and executing the following command:
    DROP DOMAIN domain_name
  5. Recreate the domain using the appropriate CREATE DOMAIN statement.
  6. Run the TABLES.SQL script again.

If you still see an error:

  1. Identify the table related to the error.
  2. Make sure that any domains that the definition for this table contains, exist in your database. If they do, the problem may be in the definition of a domain. To examine the definition of a specific domain, do the following:
    1. Select Domains in the left pane of IBConsole.
    2. Right-click on a domain name in the right pane and select Properties.
    3. Switch to the Metadata tab.
    4. Confirm that the domain definition is correct. Do this for any domains or tables that the error refers to.

As an example, this is the Metadata tab for the COUNTRYNAME domain:

TutorialDomainMetadata.png

Altering Tables

Take a look at the definition of the Department table.

  1. Select Tables in the left pane of IBConsole.
  2. Right-click on the Department table in the right pane and select Properties.
  3. Switch to the Metadata tab. The image below shows what you should see:
    TutorialTableMetadata.png

You can change the structure of existing tables with the ALTER TABLE statement. A simplified syntax for altering a table is:

ALTER TABLE table_name 
  <operation1> [, 
  <operation2>, ]
operation = ADD column 
| ADD table_constraint 
| ALTER [column] col_name <alt_col_clause>
| DROP column
| DROP CONSTRAINT constraint_name

Notice how you can only drop a constraint if you assign it a name upon creation. For more detailed definition of the ALTER TABLE statement, see ALTER TABLE.

Image 025.jpgAltering the Department Table

This section guides you to add five new columns and two foreign key constraints to the Department table.

  1. Open the Interactive SQL window and enter the following statement:
    ALTER TABLE Department
      ADD head_dept DEPTNO,
      ADD mngr_no EMPNO,
      ADD budget BUDGET,
      ADD location VARCHAR(15),
      ADD phone_no PHONENUMBER DEFAULT '555-1234',
      ADD FOREIGN KEY (mngr_no) REFERENCES employee (emp_no) ON DELETE CASCADE ON
      UPDATE CASCADE,
      ADD CONSTRAINT fkdept FOREIGN KEY (head_dept) REFERENCES department (dept_no)
      ON DELETE CASCADE ON UPDATE CASCADE
    
  2. Open the Metadata for the Department table again (see steps in Altering Tables section) and see the differences in the definition:
    TutorialTableMetadata2.png

More Troubleshooting

If you receive error messages when you are alter tables or insert data, use the Metadata tab to investigate.

  • Examine the definition of each table that you enter by hand and compare it to the code snippets that this tutorial provides.
  • When you find a problem you can either drop the table and recreate it or use the ALTER TABLE statement to drop a column (ALTER TABLE table_name DROP column_name) and then add the column again using the correct definition (ALTER TABLE table_name ADD column_name column_def). If you misspell the name of the table itself, you must drop the table(DROP TABLE table_name) and recreate it.

Advance To:

  • Creating Tablespaces

Понравилась статья? Поделить с друзьями:
  • Spring response entity error
  • Sql error code 3621
  • Sql error 26 visual studio
  • Sql error 1064 sqlstate 42000
  • Spring param error