Your Prompted Query is too complex for the database.
An internal QMF query needed to build or run the Prompted Query failed. This situation can occur if:
Your query cannot be completed or run using Prompted Query.
Shorten your query or rewrite it as more than one query.
SQLCODE: -00101 Database: SQL/DS QMF Function: PQ
Data is too long. Check your quotes.
A character constant must be enclosed in quotes. If you omit a closing quote, your data could exceed the maximum length: 254 characters normally, or 127 graphic characters if you are using the Double Byte Character Set under SQL/DS.
Change your data and run the query again.
SQLCODE: -00102 Database: SQL/DS QMF Function: PQ
&V1 starts with a digit, but is not a valid number.
&V1 starts with a digit, but is not a valid integer, decimal, or floating-point number. If it is meant to be a:
Change &V1 and run the query again.
SQLCODE: -00103 Database: SQL/DS QMF Function: PQ
Either &V1 or something near it is invalid.
Some of the possible causes are:
Examine your query, make the necessary changes, and run it again.
SQLCODE: -00104 Database: SQL/DS QMF Function: PQ
Incorrect usage of &V1 or &V2..
Some possibilities are:
Make the correction and continue.
SQLCODE: -00105 Database: SQL/DS QMF Function: PQ
An unmatched single quote appears in your expression.
You have inserted a single quote in an expression and do not have a matching single quote to end the quoted data.
Insert the matching quote in the correct place.
SQLCODE: -00106 Database: SQL/DS QMF Function: PQ
The name &V1 is to long. The maximum allowable length is &V2.
The query contains a name whose length exceeds the maximum length. When determining the length of this name, an EBCDIC character counts as one byte and a DBCS character counts as two bytes. A qualifier for a table or view name cannot be more than eight bytes long. This can also be caused by an unmatched double quote in your expression.
Use a shorter name, or add the missing quote.
SQLCODE: -00107 Database: SQL/DS QMF Function: PQ
The name &V1 is to long. The maximum allowable length is &V2.
The query contains a name whose length exceeds the maximum length. When determining the length of this name, an EBCDIC character counts as one byte and a DBCS character counts as two bytes. A qualifier for a table or view name cannot be more than eight bytes long. This can also be caused by an unmatched double quote in your expression.
Use a shorter name, or add the missing quote.
SQLCODE: -00108 Database: SQL/DS QMF Function: PQ
&V1 is not a function name.
Some of the functions are AVG, MAX, MIN, SUM, COUNT, DATE, TIME, TIMESTAMP, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, MICROSECOND, CHAR, and DAYS. If &V1 is a valid function, be sure that the punctuation used with it is correct. For example:
MIN(PRICE), MAX(PRICE) is correct
DATE('1996-10-01') -10102433. is correctCheck the QMF Reference manual to be sure you are using a valid function correctly.
SQLCODE: -00110 Database: SQL/DS QMF Function: PQ
A summary function must specify a column name.
You specified a summary function that contains an expression without a column name. A summary function must refer to a column name. Examples:
AVG(COMM + SALARY) is correct. AVG(1200 + 3498) is not correct.
Correct the expression of the summary function.
SQLCODE: -00111 Database: SQL/DS QMF Function: PQ
A summary function contains an invalid expression.
The summary functions are AVG, COUNT, MAX, MIN, and SUM. Any expressions used in a summary function cannot contain summary functions.
Correct: AVG(UNITS * PRICE) Incorrect: AVG(UNITS * MAX(PRICE))
Change your query so that the summary function has the correct expression.
SQLCODE: -00112 Database: SQL/DS QMF Function: PQ
&V1 is used incorrectly.
A simple comparison like '>' or '=' must not be followed by a list of items. ANY and ALL comparisons must be followed by a subselect, rather than an expression or a list of items. For Example:
Correct: WHERE SALARY > ALL (SELECT COMM FROM Q.STAFF) Incorrect: WHERE SALARY > ALL (10000)
Change the usage of &V1 and run your query again.
SQLCODE: -00115 Database: SQL/DS QMF Function: PQ
The database label is too long.
The length of the label for a column or table exceeds the maximum of 30 bytes. An EBCDIC character counts as one byte and a DBCS character counts as two bytes.
Shorten the label and run the query again.
SQLCODE: -00116 Database: SQL/DS QMF Function: PQ
The number of values does not match the number of columns.
In a statement like INSERT INTO Q.STAFF, you must provide a value for every column that was defined as NOT NULL.
If you do not give a list of columns after the table name, then give a value for every column in the table, after VALUES.
If you do give a list of columns after the table name, then give a value for every column in that list, after VALUES.
Example:
INSERT INTO Q.STAFF (ID, NAME, DEPT)
VALUES (400, 'HARRISON', 20)Provide a value for each column you want to INSERT INTO and run the query again.
SQLCODE: -00117 Database: SQL/DS QMF Function: PQ
You cannot modify a table used in a subquery.
"Modify" includes INSERT, UPDATE, and DELETE.
Incorrect: INSERT INTO Q.STAFF SELECT * FROM Q.STAFF WHERE YEARS > 7
The example tries to modify the table from which it is receiving data.
Change your query so that the same table used in the subquery is not modified or write a separate query to modify the table.
SQLCODE: -00118 Database: SQL/DS QMF Function: PQ
The grouping is inconsistent.
One of the following has occurred:
Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Correct: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)(If you use * after SELECT, list all column names after GROUP BY.
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6)Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Change the SQL statement and run your query again.
SQLCODE: -00119 Database: SQL/DS QMF Function: PQ
A built-in function or grouped column is used incorrectly.
You cannot use a built-in function (AVG, COUNT, MAX, MIN or SUM) after WHERE or SET except as part of a subquery.
Correct:
WHERE YEARS > (SELECT AVG(YEARS)
FROM Q.STAFF)
Incorrect:
WHERE YEARS > AVG(YEARS)If your query refers to a view, a column named after GROUP BY in the view definition cannot be used in a condition in your query. For example, if DEPT is used after GROUP BY in defining VIEW, then the following is
Incorrect: SELECT DEPT, SUMSALARY FROM VIEW WHERE DEPT = 20
Change your query and run it again. If your query uses a view, write a query to select from the table the view is based on.
SQLCODE: -00120 Database: SQL/DS QMF Function: PQ
You cannot modify a column twice in the same query.
"Modify" includes INSERT and UPDATE. For example, in the following invalid statement, the column 'YEARS' cannot be modified more than once.
Incorrect:
INSERT INTO Q.STAFF (ID, YEARS, JOB,
YEARS)
VALUES (400, 7, 'clerk', 8)Change the SQL statement so that there is only one modification and run it again.
SQLCODE: -00121 Database: SQL/DS QMF Function: PQ
No more than 16 columns allowed after ORDER BY.
Your ORDER BY list contains more than 16 columns referred to by name or integer. The maximum allowed is 16.
Reduce the number of columns referred to in the ORDER BY clause to 16 or less and run the query again.
SQLCODE: -00124 Database: SQL/DS QMF Function: PQ
You cannot ORDER BY column &V1..
There is no column &V1 in the list after SELECT. (The column number refers to the place of a column in the list after SELECT. You cannot use column 8, for example, if fewer than eight columns are listed.)
Correct the query and run it again.
SQLCODE: -00125 Database: SQL/DS QMF Function: PQ
DISTINCT cannot be used more than once in a query.
DISTINCT was used more than once in your query. DISTINCT is implied if you chose to keep a single copy of selected rows. You may have done that and also used DISTINCT in a summary function.
Use DISTINCT no more than once in your query.
SQLCODE: -00127 Database: SQL/DS QMF Function: PQ
Use NULL with IS or IS NOT.
NULL cannot be used as an item in a list following IN in a WHERE clause. For example
WHERE AMT IN (20,50,NULL) is wrong, but WHERE AMT IN (20,50) OR AMT IS NULL is OK.
Change the phrase with NULL and run your query again.
SQLCODE: -00128 Database: SQL/DS QMF Function: PQ
You used too many tables or columns in your query.
In your query, one of the following items exceeds the limits listed:
Table Names 15
Selected columns 255Correct your query to conform to the limits, then rerun it.
SQLCODE: -00129 Database: SQL/DS QMF Function: PQ
You use SELECT twice; parentheses needed.
Your query refers to a value or set of values computed by another query, called a subquery. The subquery portion of the complete query must be enclosed in parentheses.
Place parentheses around the subquery (SELECT..........) and run the query again.
SQLCODE: -00130 Database: SQL/DS QMF Function: PQ
LIKE is used incorrectly.
A condition written with LIKE is invalid. Follow LIKE by a character constant; you may use the symbols '%' and '_'.
Write NAME LIKE 'JO%' , where NAME is
a column name.Change the condition using LIKE and run your query again.
SQLCODE: -00132 Database: SQL/DS QMF Function: PQ
An expression is improperly used after a HAVING or WHERE clause.
You must use a column name, rather than an expression, as the argument of a built-in function, when that column is a correlated reference column in a WHERE or HAVING clause. For example:
SELECT DEPT,SUM(YEARS) FROM Q.STAFF VARX GROUP BY DEPT HAVING SUM(YEARS) > ANY (SELECT AVG(YEARS) FROM Q.STAFF GROUP BY DEPT HAVING MAX(YEARS) > MIN(1*VARX.YEARS))
is incorrect -- (1*VARX.YEARS) cannot be the argument of a built-in function MIN because it is an expression containing the correlated reference variable VARX.YEARS.
Correct your query and rerun it.
SQLCODE: -00133 Database: SQL/DS QMF Function: PQ
A LONG VARCHAR column is used incorrectly.
Several restrictions exist when using a column with data type LONG VARCHAR or LONG VARGRAPHIC. It cannot be selected in the Columns section of the query when the Duplicate Rows indicates to keep a single copy of each row. Some releases of the Relational Database manager do not allow it to be used in a Row Condition with an operator of Starting With, Ending With, or Containing.
Change your use of the column with data type LONG VARCHAR or LONG VARGRAPHIC, or remove the Keep Single Copy line from the query.
SQLCODE: -00134 Database: SQL/DS QMF Function: PQ
A LONG VARCHAR column is used incorrectly.
The following limitations apply to using a column of data type LONG VARCHAR or LONG VARGRAPHIC:
Either comply with the previously listed conditions for columns of data type LONG VARCHAR or LONG VARGRAPHIC, or remove the column, and rerun the query.
SQLCODE: -00135 Database: SQL/DS QMF Function: PQ
The length of the result from &V1 is greater than &V2..
The result of the &V1 operation is too long. It cannot be greater than &V2..
Change your query to create a shorter result, and run the query again.
SQLCODE: -00137 Database: SQL/DS QMF Function: PQ
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00150 Database: SQL/DS QMF Function: PQ
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00151 Database: SQL/DS QMF Function: PQ
Condition uses a column defined by a built-in function.
One of the tables used in your query is a view. After WHERE, a condition uses a column from that view that is defined in terms of one of the built-in functions (AVG, COUNT, MAX, MIN, SUM). Columns defined in that way cannot be used in conditions.
Check the definition of the view to see what columns you cannot use after WHERE. Correct your query and run it again.
SQLCODE: -00152 Database: SQL/DS QMF Function: PQ
View columns defined by expressions or functions need names.
Your CREATE VIEW statement includes a column defined from an expression, such as UNITS * PRICE; a built-in function, such as AVG(YEARS); or a constant, such as 'JUNE 1'. You must supply names for those columns, and so you must have a name list with a name for each column.
Provide new names for all columns defined from functions or expressions in your CREATE VIEW query.
SQLCODE: -00153 Database: SQL/DS QMF Function: PQ
Invalid definition or use of view.
The operation violates one of these rules:
Make your command valid according to the rules on views and give it again.
SQLCODE: -00154 Database: SQL/DS QMF Function: PQ
A view defined by GROUP BY or HAVING is named after FROM.
One of the tables named after FROM in your query is a view defined by a query that uses a GROUP BY or HAVING clause. That view cannot be named after FROM along with any other table.
Rewrite your query so as not to name the view along with another table, after FROM. Run the query again.
SQLCODE: -00155 Database: SQL/DS QMF Function: PQ
Invalid definition or use of view.
This view was created using DISTINCT or GROUP-BY. You must conform to the following rules in order to use the view.
For example, if the view definition is as follows:
CREATE VIEW V1 (COLA,COLB) AS SELECT DISTINCT (COL1,COL2) FROM TABLEA
You must select both COLA and COLB from V1. You cannot use AVG(COLA) or other column functions.
Change the query and run it again.
SQLCODE: -00156 Database: SQL/DS QMF Function: PQ
The CREATE VIEW and SELECT lists need the same number of columns.
There must be a column name in your SELECT list for every column name in the CREATE VIEW list. If you replace the list of names in the SELECT list with an asterisk (*), the view will contain the same column names as the original table.
Change the SELECT list column names to conform to the CREATE VIEW list and run the query again.
SQLCODE: -00158 Database: SQL/DS QMF Function: PQ
Invalid use of colon (:).
Your query uses a name preceded by a colon, as in "WHERE NAME = :NAME (That usage has a meaning in a query submitted to the preprocessor program, but not in a query in QMF.)
Correct your query. Use names of tables, columns, or views, or else character constants enclosed in single quotes.
SQLCODE: -00163 Database: SQL/DS QMF Function: PQ
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00164 Database: SQL/DS QMF Function: PQ
Data within double quotes cannot begin with a blank.
In your expression you have a double quote followed by data that begins with a blank. This is not allowed. No valid name that must be placed within double quotes can begin with a blank.
Change the expression so that the name within double quotes is correct.
SQLCODE: -00165 Database: SQL/DS QMF Function: PQ
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00166 Database: SQL/DS QMF Function: PQ
Invalid hexadecimal literal.
Your query included a "hexadecimal literal", a constant that begins with X'.
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a hexadecimal literal, use a valid hexadecimal code expressed with an even number of characters.
Correct your query and run it again.
SQLCODE: -00167 Database: SQL/DS QMF Function: PQ
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X'.
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00169 Database: SQL/DS QMF Function: PQ
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X'.
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00170 Database: SQL/DS QMF Function: PQ
Argument '&V1' of scalar function '&V2' is invalid.
The data type, length, or value specified for scalar function '&V2' is incorrect. Refer to SQL query publications for more information.
Change the data type, length, or value of '&V2' function and run the query again.
SQLCODE: -00171 Database: SQL/DS QMF Function: PQ
The number of arguments specified for scalar function '&V1' is invalid.
The SQL statement has specified the scalar function &V1 with either too many or too few arguments. The supported functions are:
DATE, TIME, TIMESTAMP, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, MICROSECOND, CHAR, DAYS, AVG, MAX, MIN, COUNT.
Examine the use of the scalar function &V1. Change the scalar function and run the query again.
SQLCODE: -00172 Database: SQL/DS QMF Function: PQ
The datetime value has invalid syntax.
The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
Correct the syntax for the datetime value and run the query again.
SQLCODE: -00180 Database: SQL/DS QMF Function: PQ
The datetime value is not a valid value.
The string representation of a datetime value contains a value which is out of range. The proper ranges for datetime values are as follows:
Years - 1 to 9999 Months - 1 to 12 Days - 1 to 31 Hours - 0 to 24 Minutes - 0 to 59 Seconds - 0 to 59
Correct the datetime value and run the query again.
SQLCODE: -00181 Database: SQL/DS QMF Function: PQ
An arithmetic expression with a datetime value is invalid.
The specified arithmetic expression contains an improperly used datetime value or simple duration. Some correct examples are:
SELECT STARTD + 10102433. FROM Q.PROJECT SELECT STARTD + 1 YEAR FROM Q.PROJECT
Correct the expression and run the query again.
SQLCODE: -00182 Database: SQL/DS QMF Function: PQ
An arithmetic operation on a date or timestamp has a result that is invalid.
The result of an arithmetic operation is a date or timestamp that is not within the valid range. Valid dates are between 0001-01-01 and 9999-12-31.
Correct the datetime value and run the query again.
SQLCODE: -00183 Database: SQL/DS QMF Function: PQ
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00184 Database: SQL/DS QMF Function: PQ
The date or time value cannot be formatted.
One of the following has occurred:
Either change your string representation of the date or time value to be one of the recognized formats, or contact your QMF administrator for assistance in making the local date or time routine available to the database.
SQLCODE: -00185 Database: SQL/DS QMF Function: PQ
A simple duration is not in a date/time arithmetic expression.
Simple durations such as 1 MONTH must be used in a correct date/time arithmetic context. For example, a WHERE clause for the statement:
SELECT PROJNO FROM Q.PROJECT could be:
WHERE STARTD - 1 MONTH > '1987-05-05'
WHERE STARTD > DATE('1987-05-05') +
1 MONTHDO NOT use them alone in an expression such as:
WHERE STARTD > 1 MONTH.
Or in an expression that is not identified as a date:
SELECT PROJNO FROM Q.PROJECT could be:
WHERE STARTD - 1 MONTH > '1987-05-05'
WHERE STARTD > DATE('1987-05-05') +
1 MONTHPut the simple duration in a correct date/time arithmetic expression and run the query again.
SQLCODE: -00187 Database: SQL/DS QMF Function: PQ
The mixed data consists of improper DBCS data value.
The mixed data may have a missing X'OE' (shift-out) or X'OF' (shift-in) or half of a DBCS character.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of this error with reason code &V1..
Verify that the referenced data values are correct. If not, make the necessary change and rerun the query.
SQLCODE: -00191 Database: SQL/DS QMF Function: PQ
The first argument of the &V1 scalar function cannot be of MIXED subtype.
You cannot use an expression of MIXED subtype as the first argument of the &V1 scalar function.
Correct your SQL statement and try again.
SQLCODE: -00192 Database: SQL/DS QMF Function: PQ
&V1 is not a valid table name in this query.
A table name identifier, &V1, is used incorrectly in this expression. Table names in an expression may only be used to qualify a column name. For example,
Q.STAFF.SALARY
Correct the expression so that the table name is used correctly or remove the table name from the expression.
SQLCODE: -00201 Database: SQL/DS QMF Function: PQ
Column &V1 is not in any table named in the query.
&V1 is not a column in any table or view named in the query. If it is intended to be a character constant, enclose it in single quotes.
Change the column name or add the table containing column &V1 to the query, and run the query again.
SQLCODE: -00202 Database: SQL/DS QMF Function: PQ
Column &V1 is in more than one table.
An unqualified column name is ambiguous if more than one table or view in the FROM clause has a column with that name, or if more than one column of a nested table expression has that name. A qualified column name is ambiguous only if the correlation name for the column name and for a nested table expression is not unique.
If the problem is caused by a non-unique column name in a nested table expression, change the nested table expression so that the column is unique. If the problem is caused by the use of an unqualified name, qualify it with a table, view or correlation name.
SQLCODE: -00203 Database: SQL/DS QMF Function: PQ
&V1..&V2 not in system catalog.
The object named in your statement cannot be found in the system catalog. The name may be misspelled or you may have the wrong qualifier (&V1).
Correct the name and run your query again.
SQLCODE: -00204 Database: SQL/DS QMF Function: PQ
&V1 is not a column defined in a selected table.
&V1 has been specified as a column, and it could not be found in any of the tables you selected. You may have misspelled the name. If &V1 is intended to be a character constant, enclose it in single quotes.
You can use the command DISPLAY Q.COLUMN_LIST to display a table of information about all the columns in tables you are authorized to use. Verify the spelling of the column name, and then correct the column name or add the table containing column &V1 to the query.
SQLCODE: -00205 Database: SQL/DS QMF Function: PQ
Use column numbers with ORDER BY, not column names.
When using ORDER BY with UNION, do not use a column name after ORDER BY. Instead, use a number that tells the position of the column in the list after SELECT.
Example: SELECT NAME, ID FROM Q.STAFF UNION SELECT NAME, TEMPID FROM Q.APPLICANT ORDER BY 1
Change the column names to column numbers and run the query again.
SQLCODE: -00207 Database: SQL/DS QMF Function: PQ
&V1 must be in the SELECT list.
&V1 follows ORDER BY. Either &V1 was not included in the SELECT list or it is misspelled after ORDER BY.
Add &V1 to the SELECT list; be sure it agrees with the column name after ORDER BY.
SQLCODE: -00208 Database: SQL/DS QMF Function: PQ
Column &V1 appears after ORDER BY and twice after SELECT.
Your SELECT list contains the column name &V1 from more than one table. Which of the columns of the same name do you wish to ORDER BY?
After ORDER BY, refer to the proper column by a number. Or add a qualifier to the column name.
SQLCODE: -00209 Database: SQL/DS QMF Function: PQ
Table name &V1 is ambiguous.
The table name &V1 occurs two or more times in the query. Since the table name is not unique, the alternate identifier must be used. For example:
A.SALARY
Use the alternate identifier to qualify the column name in your expression.
SQLCODE: -00211 Database: SQL/DS QMF Function: PQ
Invalid use of colon (:).
Your query uses a name preceded by a colon, as in "WHERE NAME = :NAME (That usage has a meaning in a query submitted to the preprocessor program, but not in a query in QMF.)
Correct your query. Use names of tables, columns, or views, or else character constants enclosed in single quotes.
SQLCODE: -00312 Database: SQL/DS QMF Function: PQ
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00313 Database: SQL/DS QMF Function: PQ
One or more characters could not be converted into a usable code for the current server.
Your SQL statement referenced a character string, which must be converted to a code suitable for the application server. However, due to a mismatch in data representation, this was not possible. The character string is incompatible with the corresponding column data type. Consequently, you cannot use the character string as specified.
Verify that the character columns and values you referenced are correct. If not, make the necessary change and try the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00330 Database: SQL/DS QMF Function: PQ
A character string could not be converted due to incompatible CCSIDs.
Your SQL statement referenced a character string that has a coded character set ID(CCSID) &V1 in a coded character set that differs from the current one. To use this character string at the current server, it must be converted from the source CCSID &V1 to the target CCSID &V2. However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of this error with reason code &V3. Possible causes for this conversion error are:
Verify that the referenced character columns and values that you referenced are correct. If not, make the necessary change and rerun the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: SQL/DS QMF Function: PQ
Invalid data type in position &V1..
Some SQL data types are not supported by the application requester. &V1 is the position of the first element with an invalid data type in the SQLDA. A common cause for this error is that the application requester has attempted to describe large object data residing at the application server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB, and DBLOB.
Remove the invalid data types and run the query again.
SQLCODE: -00351 Database: SQL/DS QMF Function: PQ
Data of different types cannot be mixed or compared.
Either an expression mixes numeric with non-numeric data, an attempt is made to compare numeric and non-numeric data, or an attempt is made to compare character and graphic data.
Assuming SALARY is a numeric column and NAME is non-numeric, the following examples are invalid:
SALARY - NAME - is an invalid
expression
NAME/2 - is an invalid
expression
If NAME Is Equal
To SALARY - is an invalid
conditionChange your expression so that it does not mix data of different types.
SQLCODE: -00401 Database: SQL/DS QMF Function: PQ
Numeric data is required.
You used non-numeric data with a numeric operator or function. Two examples are:
NAME AVG(NAME)
where NAME is column name not defined as numeric.
Change your query to use only numeric data with the arithmetic expression or function.
SQLCODE: -00402 Database: SQL/DS QMF Function: PQ
Some character value is too long for the corresponding column.
One of the values you are trying to insert is longer than the width of the column you want to insert it into.
Change the value to fit the column and run the query again.
SQLCODE: -00404 Database: SQL/DS QMF Function: PQ
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of
the column. For example,
if the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun your query.
SQLCODE: -00405 Database: SQL/DS QMF Function: PQ
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of
the column. For example,
if the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun your query.
SQLCODE: -00406 Database: SQL/DS QMF Function: PQ
You cannot update a NOT NULL column with a null value.
Some column you are updating does not allow NULL, and you want to update it with a null value. The null value could be from a subquery.
Remove the invalid NULL from your query and run it again.
SQLCODE: -00407 Database: SQL/DS QMF Function: PQ
A subquery returned an incompatible data type.
A value from a subquery used to update or insert was incompatible with the corresponding column. The subquery value and the corresponding column must have the same data type. For example, to update a numeric column, you must select only a numeric value in the subquery.
Change the subquery and run the query again.
SQLCODE: -00408 Database: SQL/DS QMF Function: PQ
DISTINCT must be used in the expression of a COUNT summary function.
In prompted query, the function COUNT can be used only with DISTINCT and a column name. Example of usage:
COUNT(DISTINCT column name)
gives the number of different values in the column.
Change your use of COUNT.
SQLCODE: -00409 Database: SQL/DS QMF Function: PQ
&V1 is not a valid numeric value.
Your query tried to assign &V1 to a numeric field. What it tried to assign is either a floating point constant of 31 characters or more, or a value containing non-numeric characters.
Change &V1 and run your query again.
SQLCODE: -00410 Database: SQL/DS QMF Function: PQ
Use of USER, CURRENT DATE/TIME, or CURRENT SQLID is invalid.
USER is not valid in Prompted Query. The CURRENT DATE/TIME or CURRENT SQLID is used in a way that is invalid for its data type:
Change your query to conform to the above rules.
SQLCODE: -00411 Database: SQL/DS QMF Function: PQ
Use only one column after SELECT in the subquery.
When SELECT is used in a subquery, (except after INSERT), it can select only one column name.
Incorrect: (SELECT PARTNO, PRICE.......)
Change the SELECT list in your subquery and run the query again.
SQLCODE: -00412 Database: SQL/DS QMF Function: PQ
Arithmetic overflow during change of data type.
The result of an arithmetic or insert operation is not valid because arithmetic overflow occurred. For example, you may have tried to INSERT values with a data type of INTEGER into a column with data type of SMALLINT. Conversion is possible so long as the INTEGER values are small enough. But a value larger than 32767 will cause arithmetic overflow.
Change your operation and run the query again.
SQLCODE: -00413 Database: SQL/DS QMF Function: PQ
LIKE requires character or graphic data, the column has numeric or datetime data.
You wrote something like this: LIKE '1%' or LIKE '%12.40.25', where LIKE compares a partial value to the values in some column. The column has a numeric or datetime data type and LIKE requires character or graphic data.
Correct your query and run it again. With numeric data, use a numeric comparison, like "n >= 1000 and n < 2000".
SQLCODE: -00414 Database: SQL/DS QMF Function: PQ
Column attributes in your SELECT lists do not agree.
You connected two or more queries by UNION or UNION ALL. The SELECT lists in each query must have the same number of columns. Corresponding columns in each SELECT list must have comparable data definitions for the SELECT to succeed. If corresponding columns have field procedures, the columns must have the same field procedure and column CCSID value.
Rewrite your query with the SELECT lists of comparable columns, and rerun your query.
SQLCODE: -00415 Database: SQL/DS QMF Function: PQ
Wide character columns cannot be used with UNION.
A column with data type LONG VARCHAR, or with a width greater than 254, cannot be listed after SELECT in a query that uses UNION. Columns with these data types can be used: INTEGER, SMALLINT, DECIMAL, FLOAT, CHAR. A VARCHAR column can be used if its width is less than 255.
Remove any column wider than 254 characters from the SELECT list of any query used with UNION.
SQLCODE: -00416 Database: SQL/DS QMF Function: PQ
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00417 Database: SQL/DS QMF Function: PQ
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00418 Database: SQL/DS QMF Function: PQ
Decimal division is not possible with the values used.
Either the precision of the numerator or the scale of the denominator is too large for decimal division.
Change the precision or scale of your decimal division values and run the query again. Note that an integer or small integer value may have been converted to decimal for this calculation.
SQLCODE: -00419 Database: SQL/DS QMF Function: PQ
Even number of hexadecimal characters needed.
Your query included a "hexadecimal literal", a constant that begins with X'. The constant is associated with a column that has a GRAPHIC data type, and so must represent an even number of hexadecimal characters. Check that the length of the constant (between the single quotes) is divisible by four.
Correct your query and run it again.
SQLCODE: -00421 Database: SQL/DS QMF Function: PQ
SELECT lists do not have the same number of columns.
You connected two or more queries by UNION. The SELECT lists in each query must have the same number of columns.
Correct the query and run it again.
SQLCODE: -00422 Database: SQL/DS QMF Function: PQ
Invalid hexadecimal literal after IN.
Your query included a "hexadecimal literal", a constant that begins with X'. If there is a hexadecimal literal before IN, the first item in the list after IN may NOT be a hexadecimal literal.
Incorrect: X'C9C4' IN (X'F1F0', X'F2F0') Correct: X'C9C4' IN (10, X'F2F0')
Correct your query and run it again.
SQLCODE: -00423 Database: SQL/DS QMF Function: PQ
A subquery using a GROUP BY or HAVING clause needs ALL, ANY, EXISTS, or IN.
A subquery that uses a GROUP BY or HAVING clause can be expected to produce more than one value. It should be preceded by one of the keywords ALL, ANY, EXISTS, or IN.
Change the query and run the query again.
SQLCODE: -00516 Database: SQL/DS QMF Function: PQ
You cannot create &V1 for the owner "SYSTEM".
For example, you cannot run a query that contains a statement like this:
CREATE TABLE SYSTEM.&V1 .....
Do not attempt this operation.
SQLCODE: -00550 Database: SQL/DS QMF Function: PQ
The specified object does not exist, or you lack needed authority.
The specified object does not exist, or it is a read-only view, or you lack some needed authority:
If you misnamed an existing object, use the correct name. If you lack needed authority, contact your QMF administrator.
SQLCODE: -00551 Database: SQL/DS QMF Function: PQ
The specified object does not exist, or you lack needed authority.
The specified object does not exist, or it's a read-only view, or you lack some needed authority, as follows:
If you misnamed an existing object, use the correct name. If you lack needed authority, contact your QMF administrator.
SQLCODE: -00552 Database: SQL/DS QMF Function: PQ
You cannot grant a privilege to yourself.
The database manager does not allow you to grant your own privileges or set your password even though you have been granted CONNECT authority implicitly through the command "GRANT CONNECT TO ALL USERS". You can only change your password after the DBA has granted CONNECT authority to you explicitly and set you initial password.
Correct the statement and run it again.
SQLCODE: -00554 Database: SQL/DS QMF Function: PQ
You cannot revoke a privilege from yourself.
Privileges can only be revoked by one user with the proper authority from another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you want any database privileges reduced.
SQLCODE: -00555 Database: SQL/DS QMF Function: PQ
You cannot revoke this privilege from &V1..
Either &V1 does not have the privilege you are trying to revoke, or it was granted by a user with a different authorization identifier from yours. You can revoke only privileges granted under your authorization identifier.
Proceed to another operation.
SQLCODE: -00556 Database: SQL/DS QMF Function: PQ
You cannot grant or revoke this combination of privileges.
One privilege you want to grant or revoke conflicts with the granting or revoking of another privilege in the same statement.
Break up your GRANT or REVOKE statement into separate statements and run the query again.
SQLCODE: -00557 Database: SQL/DS QMF Function: PQ
You cannot revoke a "special" privilege from a DBA.
Users cannot revoke "special" privileges , such as RESOURCE, from those with DBA authority.
Don't attempt this operation.
SQLCODE: -00558 Database: SQL/DS QMF Function: PQ
You cannot use the database without CONNECT authority.
In order to use the database, you need CONNECT authority. If you have already used the database during this session, another user may have revoked your CONNECT authority while you were running.
Report your problem to your QMF administrator.
SQLCODE: -00561 Database: SQL/DS QMF Function: PQ
Statement references an invalid userid.
A SQL userid must begin with an alphabetic character and contain eight or fewer alphabetic or numeric characters. It must contain no embedded blanks or special characters.
The userids PUBLIC and SYSTEM can be used only in certain restricted contexts.
In particular, the special privileges (CONNECT, DBA, and RESOURCE) cannot be GRANTed to or REVOKEd from PUBLIC or SYSTEM.
Do not attempt this operation unless you can change the userid it names.
SQLCODE: -00564 Database: SQL/DS QMF Function: PQ
The name of the object you are creating already exists.
The object you are creating or acquiring has a name that already exists.
Change the name to one that doesn't exist in the data base and run your query again.
SQLCODE: -00601 Database: SQL/DS QMF Function: PQ
Your table or view contains too many columns.
Your query would create a table or view with more than the maximum number of columns allowed.
Change your query so that the table or view you are creating will have less than 256 columns.
SQLCODE: -00602 Database: SQL/DS QMF Function: PQ
The &V1 column contains duplicate values.
You cannot create a &V1 column that contains duplicate values. One of the columns you named does so. If a column has a type of VARCHAR or VARGRAPHIC, two columns that differ only in the number of trailing blanks might cause duplication.
Change your CREATE statement so that it does not refer to a column with duplicate values, or else delete rows with duplicate values from the table.
SQLCODE: -00603 Database: SQL/DS QMF Function: PQ
You used a constant that exceeds maximum width allowed.
You specifies a constant that has a length, precision, or scale outside the data type limit. Some possible causes of the error are:
Change the constant specification to conform to the data type limit and run your query again. See the SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00604 Database: SQL/DS QMF Function: PQ
The table or column named does not exist or is owned by another user.
The table or column named in your COMMENT ON statement or LABEL ON statement does not exist or it is owned by another user. You can only use the statement(s) for tables you have created. You may COMMENT ON or LABEL ON another user's tables only if you have DBA authority.
Continue with another operation.
SQLCODE: -00606 Database: SQL/DS QMF Function: PQ
You cannot add more tables to this DBSPACE.
The maximum number of tables for a DBSPACE is 255.
Either create your table in a different DBSPACE, or drop a table in the named DBSPACE to free space for an entry.
SQLCODE: -00607 Database: SQL/DS QMF Function: PQ
DBSPACE not found.
If you used IN with a DBSPACE name, either
If you didn't use IN, either
Enter the name of a DBSPACE that you can use and run your SQL query again.
SQLCODE: -00608 Database: SQL/DS QMF Function: PQ
You cannot ALTER a SYSTEM DBSPACE.
No user can ALTER a SYSTEM DBSPACE. The information in this storage area is vital to the operation of the system and cannot be changed by the user.
Do not attempt this operation.
SQLCODE: -00609 Database: SQL/DS QMF Function: PQ
You cannot create a table in the specified DBSPACE.
You must have the proper authority to create a table in a DBSPACE owned by another user or by the system.
Use another DBSPACE to create your table. Follow your local procedures if you need authorization to use a DBSPACE owned by another user or by the system.
SQLCODE: -00610 Database: SQL/DS QMF Function: PQ
You cannot use NOT NULL with ALTER TABLE.
The ALTER TABLE statement adds one new column to a table. All existing rows are expanded with a null value for the new column. The NOT NULL option cannot be used.
Remove the NOT NULL option from your ALTER TABLE statement and run the query again.
SQLCODE: -00611 Database: SQL/DS QMF Function: PQ
You used column name &V1 twice.
A table cannot contain two columns with the same name. In CREATE TABLE, CREATE VIEW, or CREATE INDEX you used column name &V1 more than once. In ALTER TABLE, &V1 is already the name of a column in the table.
Choose another column name and run your query again.
SQLCODE: -00612 Database: SQL/DS QMF Function: PQ
Columns chosen cannot be indexed.
Under CMS, you cannot index a LONG VARCHAR or LONG VARGRAPHIC column.
Under TSO, you cannot index a VARCHAR column whose maximum allowable length is over 254 characters.
Under either CMS or TSO, you cannot index a group of columns if the sum of their internal lengths exceeds 255 characters.
Revise your index or primary key definition, either by omitting one or more of the columns or by replacing long columns with shorter ones.
SQLCODE: -00614 Database: SQL/DS QMF Function: PQ
The CREATE INDEX or PRIMARY KEY statement specifies to many columns.
The number or columns specified in the CREATE INDEX or PRIMARY KEY statement exceeds the maximum number of columns allowed.
Change your CREATE INDEX or PRIMARY KEY statement to conform to the column limit.
SQLCODE: -00617 Database: SQL/DS QMF Function: PQ
There is no private, recoverable DBSPACE available.
The DBSPACE name was not specified in the CREATE TABLE command, so a search was done to find a private DBSPACE owned by &V1..
Either there were no DBSPACEs found, they were full, or they were located in non-recoverable storage pools.
Either acquire a private DBSPACE, make room in an existing space, or explicitly specify the DBSPACE you want.
SQLCODE: -00620 Database: SQL/DS QMF Function: PQ
Graphic and Mixed data types are not supported by the current server.
Your SQL statement referenced the clause or scalar function, &V1, and the current server does not support it.
This may happen because:
Issue the SQL statement on a server that supports Mixed, Graphic and Vargraphic data types. If you use these data types at the current server, contact your QMF administrator to reset the system default CCSIDs.
SQLCODE: -00640 Database: SQL/DS QMF Function: PQ
UPDATE STATISTICS does not work with a view.
The UPDATE STATISTICS statement cannot be used with a view. It can only be used with one table.
Write queries to operate on the tables that make up the view and run the query again. Example:
UPDATE STATISTICS FOR TABLE PRICES
SQLCODE: -00657 Database: SQL/DS QMF Function: PQ
Invalid comparison with a column defined with a field procedure.
The value that is compared to a column defined with a field procedure does not have the same field type. The comparison is performed on the encoded form of the value in the column. For example, if the encoded value of the column is INTEGER, the data type of the value being compared must be identical. If they are strings, their data types must be compatible.
Correct the SQL statement and run the query again.
SQLCODE: -00687 Database: SQL/DS QMF Function: PQ
Space allocated for data in your DBSPACE is full.
Your query will not run because there is not enough space for data in your DBSPACE.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more data space and run the query again.
SQLCODE: -00701 Database: SQL/DS QMF Function: PQ
Space assigned for indexes in your DBSPACE is full.
Your query cannot be processed until more DBSPACE is added for indexes.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more index space and run the query again.
SQLCODE: -00702 Database: SQL/DS QMF Function: PQ
Space for header information in your DBSPACE is full.
The space allocated in your DBSPACE by the parameter NHEADER for header information is full. Your query cannot be processed unless additional DBSPACE space is obtained.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more header space and run the query again.
SQLCODE: -00703 Database: SQL/DS QMF Function: PQ
No DBSPACE available of the requested size and type.
Your ACQUIRE DBSPACE statement was not processed. One of the following has occurred:
If a storage pool was specified, verify that the storage pool exists by contacting your QMF administrator. If the storage pool exists, reduce the number of pages in your PAGES option or ask for another type of DBSPACE. If this does not work, contact your QMF administrator to request more DBSPACE and enter your ACQUIRE DBSPACE statement again when a DBSPACE has been added.
SQLCODE: -00704 Database: SQL/DS QMF Function: PQ
The value given for &V1 is invalid.
For an ACQUIRE or ALTER DBSPACE statement, the following values are used if the associated parameter is not specified:
NHEADER - 8 PAGES - 128
PCTFREE - 15 LOCK - PAGE
PCTINDEX - 33For CREATE INDEX or when adding a primary key to a table, a default of 10 is used for PCTFREE if it is not specified.
The maximum and minimum values for &V1 depend upon the application. Contact your QMF administrator for specific information.
Change the value of &V1 and rerun the query.
SQLCODE: -00705 Database: SQL/DS QMF Function: PQ
You cannot drop, lock, or alter a PUBLIC DBSPACE.
A PUBLIC DBSPACE can only be dropped, locked, or altered by a user with the proper authority.
Contact a user in your installation with the required authority and request the drop or alter action.
SQLCODE: -00708 Database: SQL/DS QMF Function: PQ
This DBSPACE contains system catalog tables.
No user can drop a DBSPACE containing system catalog tables.
Don't attempt to drop this DBSPACE.
SQLCODE: -00709 Database: SQL/DS QMF Function: PQ
The PRIVATE DBSPACE needed by your query is in use.
A PRIVATE DBSPACE can be accessed by only one user at any time. The table you requested in your query is in a PRIVATE DBSPACE now in use.
Run your query again when the PRIVATE DBSPACE is available.
SQLCODE: -00710 Database: SQL/DS QMF Function: PQ
There is not enough room in INTERNAL DBSPACEs to run the query.
QMF was not able to acquire sufficiently many, or sufficiently large, INTERNAL DBSPACEs. You may be able to simplify your query or break it up into two queries or more.
Ask your QMF administrator to acquire more INTERNAL DBSPACE for QMF.
SQLCODE: -00712 Database: SQL/DS QMF Function: PQ
An arithmetic operation in the SQL statement has resulted in an error.
You are trying to use a view, but an arithmetic operation in the subselect clause of the view definition has resulted in an error. The exception type is &V1, the operation type is &V2, and the data type is &V3.
Contact the owner of the view to examine the arithmetic operation and the columns within the subselect clause of the view to determine what data may be causing the program exception.
SQLCODE: -00801 Database: SQL/DS QMF Function: PQ
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: SQL/DS QMF Function: PQ
Duplicate value in a unique index column.
One of the columns into which you are inserting or updating a new value contains that same value already. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values.
Change the value so that it does not duplicate a value already existing. Run your query again.
SQLCODE: -00803 Database: SQL/DS QMF Function: PQ
The package &V1 is not found in the catalog table.
When SQL/DS tried to run the QMF program, it could not find the package in the catalog table SYSTEM.SYSACCESS. This can happen because:
Refer to the SQL/DS Messages and Codes manual for a detailed explanation and report this problem to your QMF administrator.
SQLCODE: -00805 Database: SQL/DS QMF Function: PQ
You do not have authorization to modify system catalogs.
You cannot modify system catalogs unless you have been granted authority. You may read the system catalogs and retrieve data using queries or DISPLAY commands.
Follow your QMF administrator procedures if authority is required.
SQLCODE: -00808 Database: SQL/DS QMF Function: PQ
Row is too long.
The result of your insert or update operation would be to create a row longer than is allowed. The maximum length is 4,070 positions, unless there are LONG VARCHAR or LONG VARGRAPHIC columns.
Change your query to create a shorter row, and run the query again.
SQLCODE: -00809 Database: SQL/DS QMF Function: PQ
A subquery produces more than one value.
A subquery should not produce values from more than one column of a table; in many cases it should not produce values from more than one row. Use ALL, ANY, EXISTS, or IN with a subquery that produces more than one value.
Examples: WHERE DEPT = ANY (SELECT DEPTNUMB FROM Q.ORG) HAVING AVG(X) > ALL (SELECT X FROM Y) WHERE EXISTS (SELECT * FROM X WHERE N1 = N2)
Change your query and run it again.
SQLCODE: -00810 Database: SQL/DS QMF Function: PQ
You cannot LOCK a view.
LOCK is used only to lock a table or dbspace. Views are not stored as tables are, and cannot be locked.
You may LOCK one or more of the tables that make up the view.
SQLCODE: -00813 Database: SQL/DS QMF Function: PQ
Cannot LOCK a system catalog table or a system DBSPACE.
Your LOCK statement attempted to LOCK a system catalog or a DBSPACE containing the system catalog tables. No user, regardless of authority, can LOCK these items.
If exclusive access to the systems catalogs is required, contact your QMF administrator and request exclusive use of the database. LOCK is not necessary if no other users are active.
SQLCODE: -00814 Database: SQL/DS QMF Function: PQ
CONNECT denied by accounting user exit routine.
Your attempt to connect to SQL/DS was rejected by your installation's accounting user exit routine.
See your QMF administrator.
SQLCODE: -00815 Database: SQL/DS QMF Function: PQ
You cannot perform this operation with a system catalog.
Your request specified a system catalog. Users cannot delete from a system catalog, add a primary or foreign key to a system catalog, or refer to a system catalog as a parent of a foreign key.
To drop the object "name1" from the database, give the command ERASE name1.
SQLCODE: -00823 Database: SQL/DS QMF Function: PQ
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00911 Database: SQL/DS QMF Function: PQ
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00912 Database: SQL/DS QMF Function: PQ
A CANCEL request has been issued.
The CANCEL could have been issued by the user or by the system. The CANCEL issued by the system is a result of reaching the limit on lock request blocks.
Redo your changes as necessary. If you did not issue the CANCEL request, and you continue to get SQLCODE -914, contact your system programmer about increasing the NLRBU or the NLRBS parameters when starting the application server.
SQLCODE: -00914 Database: SQL/DS QMF Function: PQ
Your query was not processed because of the system work load.
Your query cannot be processed now because of the work load on the database system.
Continue with another operation and try to run your query at a later time. Contact your QMF administrator for more details about the current system work load.
SQLCODE: -00915 Database: SQL/DS QMF Function: PQ
Your query was not processed because of operator action.
The system operator interrupted the processing of your query. This was not due to an error in the query.
Run the query again.
SQLCODE: -00916 Database: SQL/DS QMF Function: PQ
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00930 Database: SQL/DS QMF Function: PQ
The communications path to &V1. is not available.
You cannot access database &V1. for one of the following reasons:
Verify that the database name, &V1., is correct. If not, use a correct database name and retry your request.
The limit on the number of connections allowed to the SQL/DS virtual machine is set by the MAXCONN value in the SQL/DS virtual machine directory. If this limit has been exceeded, try your request later when the system activity is lighter. If this condition occurs frequently, contact your QMF administrator to get the MAXCONN value increased.
If the "CONNECT TO <location>" command is supported, QMF may have reconnected you to the current location. If so, you can continue to use QMF. If QMF cannot reconnect you, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00933 Database: SQL/DS QMF Function: PQ
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00939 Database: SQL/DS QMF Function: PQ
The database &V1 is not ready or cannot be found.
You cannot access the database for one of the following reasons:
Verify that the database name, &V1., is correct. If not, use a correct database name and retry your request.
If the "CONNECT TO <location>" command is supported, QMF may have reconnected you to the current location. If so, you can continue to use QMF. If QMF cannot reconnect you, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00940 Database: SQL/DS QMF Function: PQ
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00942 Database: SQL/DS QMF Function: PQ
The QMF virtual machine, &V2, cannot access database &V1..
The QMF virtual machine is not properly defined. The file ARISRMBT MODULE, on the QMF machine's A-disk, does not describe the database program that QMF is attempting to access.
Tell your QMF administrator about this message and wait for their response. There is nothing you can do until the QMF virtual machine is properly defined.
SQLCODE: -00943 Database: SQL/DS QMF Function: PQ
Your connection to SQL/DS was severed because of operator action.
The SQL/DS virtual-machine operator entered the FORCE command to cause ROLLBACK of the current logical unit of work and to sever your connection to the SQL/DS system. The userid, password, and database name are reset to their default values.
You can continue. Any explicit CONNECTs you have issued have been lost. You must issue another explicit CONNECT request, using the same USER ID, to reestablish your original connection.
SQLCODE: -00948 Database: SQL/DS QMF Function: PQ
Your SEARCH request contains too many columns or values.
Your search request could not be completed because:
Create a view which contains only those columns which you need to update, or specify fewer values for your search criteria.
SQLCODE: -00101 Database: SQL/DS QMF Function: Table Edit
Some character value is too long for the corresponding column.
One of the values you are trying to insert is longer than the width of the column you want to insert it into.
Change the value to fit the column and run the query again.
SQLCODE: -00102 Database: SQL/DS QMF Function: Table Edit
&V1 starts with a digit, but is not a valid number.
&V1 starts with a digit, but is not a valid integer, decimal, or floating-point number. If it is meant to be a...
Change &V1 and run the query again.
SQLCODE: -00103 Database: SQL/DS QMF Function: Table Edit
Non end-user SQLCODE returned from DBM.
The computer has detected an internal SQL error. The error code is shown at the bottom of this panel.
Report the error following your installation's procedures and check if your command executed correctly. You may continue to use QMF.
You used too many tables or columns in your query.
In your query, one of the following items exceeds the limits listed:
Table Names 15
Selected columns 255Correct your query to conform to the limits, then rerun it.
SQLCODE: -00129 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Insert or update value does not satisfy view definition.
Your &V1 command attempted to insert or update a view that uses the "WITH CHECK OPTION" clause. All attempts to insert or update rows into this view are checked to ensure that the results conform to the view definition. A value that you attempted to insert or update does not satisfy that definition.
Examine the view definition to determine why the change was rejected. Then, change the value that your &V1 command attempted to process.
SQLCODE: -00141 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
You cannot modify the specified object.
The specified object is a view based on more than one table. INSERT, DELETE, or UPDATE of a view is not permitted if the VIEW is based on more than one table.
Verify that the table/view name you specified is correct.
SQLCODE: -00149 Database: SQL/DS QMF Function: Table Edit
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00150 Database: SQL/DS QMF Function: Table Edit
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00151 Database: SQL/DS QMF Function: Table Edit
Invalid definition or use of view.
The operation violates one of these rules:
Make your command valid according to the rules on views and give it again.
SQLCODE: -00152 Database: SQL/DS QMF Function: Table Edit
Invalid definition or use of view.
The operation violates one of these rules:
Make your command valid according to the rules on views and give it again.
SQLCODE: -00153 Database: SQL/DS QMF Function: Table Edit
Invalid definition or use of view.
The operation violates one of these rules:
- data from more than one table - data selected by DISTINCT or GROUP BY
Make your command valid according to the rules on views and give it again.
SQLCODE: -00154 Database: SQL/DS QMF Function: Table Edit
Invalid definition or use of view.
The operation violates one of these rules:
Make your command valid according to the rules on views and give it again.
SQLCODE: -00155 Database: SQL/DS QMF Function: Table Edit
Invalid definition or use of view.
The operation violates one of these rules:
Make your command valid according to the rules on views and give it again.
SQLCODE: -00156 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00164 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00166 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00169 Database: SQL/DS QMF Function: Table Edit
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00170 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
The datetime value has invalid syntax.
The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
Correct the syntax for the datetime value and run the query again.
SQLCODE: -00180 Database: SQL/DS QMF Function: Table Edit
The datetime value is not a valid value.
The string representation of a datetime value contains a value which is out of range. The proper ranges for datetime values are as follows:
Years - 1 to 9999 Months - 1 to 12 Days - 1 to 31 Hours - 0 to 24 Minutes - 0 to 59 Seconds - 0 to 59
Correct the datetime value and run the query again.
SQLCODE: -00181 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
The mixed data consists of improper DBCS data value.
The mixed data may have a missing X'OE' (shift-out) or X'OF' (shift-in) or half of a DBCS character.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of this error with reason code &V1..
Verify that the referenced data values are correct. If not, make the necessary change and rerun the query.
SQLCODE: -00191 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
One or more characters could not be converted into a usable code for the current server.
Your SQL statement referenced a character string, which must be converted to a code suitable for the application server. However, due to a mismatch in data representation, this was not possible. The character string is incompatible with the corresponding column data type. Consequently, you cannot use the character string as specified.
Verify that the character columns and values you referenced are correct. If not, make the necessary change and try the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00330 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
A character string could not be converted due to incompatible CCSIDs.
Your SQL statement referenced a character string that has a coded character set ID(CCSID) &V1 in a coded character set that differs from the current one. To use this character string at the current server, it must be converted from the source CCSID &V1 to the target CCSID &V2. However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of this error with reason code &V3. Possible causes for this conversion error are:
Verify that the referenced character columns and values that you referenced are correct. If not, make the necessary change and rerun the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Invalid data type in position &V1..
Some SQL data types are not supported by the application requester. &V1 is the position of the first element with an invalid data type in the SQLDA. A common cause for this error is that the application requester has attempted to describe large object data residing at the application server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB, and DBLOB.
Remove the invalid data types and run the query again.
SQLCODE: -00351 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Some character value is too long for the corresponding column.
One of the values you are trying to insert is longer than the width of the column you want to insert it into.
Change the value to fit the column and run the query again.
SQLCODE: -00404 Database: SQL/DS QMF Function: Table Edit
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of
the column. For example,
if the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun your query.
SQLCODE: -00405 Database: SQL/DS QMF Function: Table Edit
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of
the column. For example,
if the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun your query.
SQLCODE: -00406 Database: SQL/DS QMF Function: Table Edit
You cannot update a NOT NULL column with a null value.
Some column you are updating does not allow NULL, and you want to update it with a null value. The null value could be from a subquery.
Remove the invalid NULL from your query and run it again.
SQLCODE: -00407 Database: SQL/DS QMF Function: Table Edit
A subquery returned an incompatible data type.
A value from a subquery used to update or insert was incompatible with the corresponding column. The subquery value and the corresponding column must have the same data type. For example, to update a numeric column, you must select only a numeric value in the subquery.
Change the subquery and run the query again.
SQLCODE: -00408 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
&V1 is not a valid numeric value.
Your query tried to assign &V1 to a numeric field. What it tried to assign is either a floating point constant of 31 characters or more, or a value containing non-numeric characters.
Change &V1 and run your query again.
SQLCODE: -00410 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Arithmetic overflow during change of data type.
The result of an arithmetic or insert operation is not valid because arithmetic overflow occurred. For example, you may have tried to INSERT values with a data type of INTEGER into a column with data type of SMALLINT. Conversion is possible so long as the INTEGER values are small enough. But a value larger than 32767 will cause arithmetic overflow.
Change your operation and run the query again.
SQLCODE: -00413 Database: SQL/DS QMF Function: Table Edit
LIKE requires character or graphic data, the column has numeric or datetime data.
You wrote something like this: LIKE '1%' or LIKE '%12.40.25', where LIKE compares a partial value to the values in some column. The column has a numeric or datetime data type and LIKE requires character or graphic data.
Correct your query and run it again. With numeric data, use a numeric comparison, like "n >= 1000 and n < 2000".
SQLCODE: -00414 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00511 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
The foreign key value is not valid.
An update or insert query specified a value for a foreign key. However, the value is not equal to any of the primary key values of the parent table.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Use a value for the foreign key that matches one of the primary key values.
SQLCODE: -00530 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
The row cannot be updated or deleted because of a dependent row.
The attempt to update or delete a parent row failed, because the parent row has a dependent row or cascades to a dependent row that has been restricted using the RESTRICT rule.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Make sure you selected the correct row. If you did, update or delete the dependent rows for which RESTRICT was specified. Then update or delete the parent row.
SQLCODE: -00532 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
You cannot create &V1 for the owner "SYSTEM".
For example, you cannot run a query that contains a statement like this:
CREATE TABLE SYSTEM.&V1 .....
Do not attempt this operation.
SQLCODE: -00550 Database: SQL/DS QMF Function: Table Edit
You do not have the authority to do this.
The authority you need depends on what you are doing:
See your QMF administrator to obtain the necessary authorization.
SQLCODE: -00551 Database: SQL/DS QMF Function: Table Edit
The specified object does not exist, or you lack needed authority.
The specified object does not exist, or it's a read-only view, or you lack some needed authority, as follows:
If you misnamed an existing object, use the correct name. If you lack needed authority, contact your QMF administrator.
SQLCODE: -00552 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
You cannot grant a privilege to yourself.
The database manager does not allow you to grant your own privileges or set your password even though you have been granted CONNECT authority implicitly through the command "GRANT CONNECT TO ALL USERS". You can only change your password after the DBA has granted CONNECT authority to you explicitly and set you initial password.
Correct the statement and run it again.
SQLCODE: -00554 Database: SQL/DS QMF Function: Table Edit
You cannot revoke a privilege from yourself.
Privileges can only be revoked by one user with the proper authority from another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you want any database privileges reduced.
SQLCODE: -00555 Database: SQL/DS QMF Function: Table Edit
You cannot revoke this privilege from &V1..
Either &V1 does not have the privilege you are trying to revoke, or it was granted by a user with a different authorization identifier from yours. You can revoke only privileges granted under your authorization identifier.
Proceed to another operation.
SQLCODE: -00556 Database: SQL/DS QMF Function: Table Edit
You cannot grant or revoke this combination of privileges.
One privilege you want to grant or revoke conflicts with the granting or revoking of another privilege in the same statement.
Break up your GRANT or REVOKE statement into separate statements and run the query again.
SQLCODE: -00557 Database: SQL/DS QMF Function: Table Edit
You cannot revoke a "special" privilege from a DBA.
Users cannot revoke "special" privileges , such as RESOURCE, from those with DBA authority.
Don't attempt this operation.
SQLCODE: -00558 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
You cannot use the database without CONNECT authority.
In order to use the database, you need CONNECT authority. If you have already used the database during this session, another user may have revoked your CONNECT authority while you were running.
Report your problem to your QMF administrator.
SQLCODE: -00561 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Statement references an invalid userid.
A SQL userid must begin with an alphabetic character and contain eight or fewer alphabetic or numeric characters. It must contain no embedded blanks or special characters.
The userids PUBLIC and SYSTEM can be used only in certain restricted contexts.
In particular, the special privileges (CONNECT, DBA, and RESOURCE) cannot be GRANTed to or REVOKEd from PUBLIC or SYSTEM.
Do not attempt this operation unless you can change the userid it names.
SQLCODE: -00564 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
The name of the object you are creating already exists.
The object you are creating or acquiring has a name that already exists.
Change the name to one that doesn't exist in the data base and run your query again.
SQLCODE: -00601 Database: SQL/DS QMF Function: Table Edit
Your table or view contains too many columns.
Your query would create a table or view with more than the maximum number of columns allowed.
Change your query so that the table or view you are creating will have less than 256 columns.
SQLCODE: -00602 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
You used a constant that exceeds maximum width allowed.
You specifies a constant that has a length, precision, or scale outside the data type limit. Some possible causes of the error are:
Change the constant specification to conform to the data type limit and run your query again. See the SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00604 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
The table or column named does not exist or is owned by another user.
The table or column named in your COMMENT ON statement or LABEL ON statement does not exist or it is owned by another user. You can only use the statement(s) for tables you have created. You may COMMENT ON or LABEL ON another user's tables only if you have DBA authority.
Continue with another operation.
SQLCODE: -00606 Database: SQL/DS QMF Function: Table Edit
You cannot add more tables to this DBSPACE.
The maximum number of tables for a DBSPACE is 255.
Either create your table in a different DBSPACE, or drop a table in the named DBSPACE to free space for an entry.
SQLCODE: -00607 Database: SQL/DS QMF Function: Table Edit
DBSPACE not found.
If you used IN with a DBSPACE name, either
If you didn't use IN, either
Enter the name of a DBSPACE that you can use and run your SQL query again.
SQLCODE: -00608 Database: SQL/DS QMF Function: Table Edit
You cannot ALTER a SYSTEM DBSPACE.
No user can ALTER a SYSTEM DBSPACE. The information in this storage area is vital to the operation of the system and cannot be changed by the user.
Do not attempt this operation.
SQLCODE: -00609 Database: SQL/DS QMF Function: Table Edit
You cannot create a table in the specified DBSPACE.
You must have the proper authority to create a table in a DBSPACE owned by another user or by the system.
Use another DBSPACE to create your table. Follow your local procedures if you need authorization to use a DBSPACE owned by another user or by the system.
SQLCODE: -00610 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Graphic and Mixed data types are not supported by the current server.
Your SQL statement referenced the clause or scalar function, &V1, and the current server does not support it.
This may happen because:
Issue the SQL statement on a server that supports Mixed, Graphic and Vargraphic data types. If you use these data types at the current server, contact your QMF administrator to reset the system default CCSIDs.
SQLCODE: -00640 Database: SQL/DS QMF Function: Table Edit
See DSQ31104
Follow the directions in the referenced message.
Non end-user SQLCODE returned from DBM.
The computer has detected an internal SQL error. The error code is shown at the bottom of this panel.
Report the error following your installation's procedures and check if your command executed correctly. You may continue to use QMF.
Space allocated for data in your DBSPACE is full.
Your query will not run because there is not enough space for data in your DBSPACE.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more data space and run the query again.
SQLCODE: -00701 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
This DBSPACE contains system catalog tables.
No user can drop a DBSPACE containing system catalog tables.
Don't attempt to drop this DBSPACE.
SQLCODE: -00709 Database: SQL/DS QMF Function: Table Edit
The PRIVATE DBSPACE needed by your query is in use.
A PRIVATE DBSPACE can be accessed by only one user at any time. The table you requested in your query is in a PRIVATE DBSPACE now in use.
Run your query again when the PRIVATE DBSPACE is available.
SQLCODE: -00710 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
There is not enough room in INTERNAL DBSPACEs to run the query.
QMF was not able to acquire sufficiently many, or sufficiently large, INTERNAL DBSPACEs. You may be able to simplify your query or break it up into two queries or more.
Ask your QMF administrator to acquire more INTERNAL DBSPACE for QMF.
SQLCODE: -00712 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
An arithmetic operation in the SQL statement has resulted in an error.
You are trying to use a view, but an arithmetic operation in the subselect clause of the view definition has resulted in an error. The exception type is &V1, the operation type is &V2, and the data type is &V3.
Contact the owner of the view to examine the arithmetic operation and the columns within the subselect clause of the view to determine what data may be causing the program exception.
SQLCODE: -00801 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Duplicate value in a unique index column.
One of the columns into which you are inserting or updating a new value contains that same value already. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values.
Change the value so that it does not duplicate a value already existing. Run your query again.
SQLCODE: -00803 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The package &V1 is not found in the catalog table.
When SQL/DS tried to run the QMF program, it could not find the package in the catalog table SYSTEM.SYSACCESS. This can happen because:
Refer to the SQL/DS Messages and Codes manual for a detailed explanation and report this problem to your QMF administrator.
SQLCODE: -00805 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
You do not have authorization to modify system catalogs.
You cannot modify system catalogs unless you have been granted authority. You may read the system catalogs and retrieve data using queries or DISPLAY commands.
Follow your QMF administrator procedures if authority is required.
SQLCODE: -00808 Database: SQL/DS QMF Function: Table Edit
Row is too long.
The result of your insert or update operation would be to create a row longer than is allowed. The maximum length is 4070 positions, unless there are LONG VARCHAR or LONG VARGRAPHIC columns.
Change your query to create a shorter row, and run the query again.
SQLCODE: -00809 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
You cannot LOCK a view.
LOCK is used only to lock a table or dbspace. Views are not stored as tables are, and cannot be locked.
You may LOCK one or more of the tables that make up the view.
SQLCODE: -00813 Database: SQL/DS QMF Function: Table Edit
Cannot LOCK a system catalog table or a system DBSPACE.
Your LOCK statement attempted to LOCK a system catalog or a DBSPACE containing the system catalog tables. No user, regardless of authority, can LOCK these items.
If exclusive access to the systems catalogs is required, contact your QMF administrator and request exclusive use of the database. LOCK is not necessary if no other users are active.
SQLCODE: -00814 Database: SQL/DS QMF Function: Table Edit
CONNECT denied by accounting user exit routine.
Your attempt to connect to SQL/DS was rejected by your installation's accounting user exit routine.
See your QMF administrator.
SQLCODE: -00815 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
You cannot perform this operation with a system catalog.
Your request specified a system catalog. Users cannot delete from a system catalog, add a primary or foreign key to a system catalog, or refer to a system catalog as a parent of a foreign key.
To drop the object "name1" from the database, give the command ERASE name1.
SQLCODE: -00823 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Sorry, your database changes have been lost.
Due to excessive locking or a locking conflict, the database manager has cancelled your database changes. Any additions, updates, or deletions to the table being edited have been lost.
End your Table Editor session and redo your changes at a later time.
SQLCODE: -00911 Database: SQL/DS QMF Function: Table Edit
Sorry, your database changes have been lost.
Due to excessive locking or a locking conflict, the database manager has cancelled your database changes. Any additions, updates, or deletions to the table being edited have been lost.
End your Table Editor session and redo your changes at a later time.
SQLCODE: -00912 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Sorry, your database changes have been lost.
A cancel request has been issued. The CANCEL could have been issued by you or by the system. The CANCEL issued by the system is a result of reaching the limit on lock request blocks.
Redo your changes as necessary. If you did not issue the CANCEL request, and you continue to get SQLCODE -914, contact your system programmer about increasing the NLRBU or the NLRBS parameters when starting the application server.
SQLCODE: -00914 Database: SQL/DS QMF Function: Table Edit
Sorry, your database changes have been lost.
Due to excessive locking or a locking conflict, the database manager has cancelled your database changes. Any additions, updates, or deletions to the table being edited have been lost.
End your Table Editor session and redo your changes at a later time.
SQLCODE: -00915 Database: SQL/DS QMF Function: Table Edit
Your query was not processed because of operator action.
The system operator interrupted the processing of your query. This was not due to an error in the query.
Run the query again.
SQLCODE: -00916 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00930 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The communications path to &V1. is not available.
You cannot access database &V1. for one of the following reasons:
Verify that the database name, &V1., is correct. If not, use a correct database name and retry your request.
The limit on the number of connections allowed to the SQL/DS virtual machine is set by the MAXCONN value in the SQL/DS virtual machine directory. If this limit has been exceeded, try your request later when the system activity is lighter. If this condition occurs frequently, contact your QMF administrator to get the MAXCONN value increased.
If the "CONNECT TO <location>" command is supported, QMF may have reconnected you to the current location. If so, you can continue to use QMF. If QMF cannot reconnect you, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00933 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00939 Database: SQL/DS QMF Function: Table Edit
The database &V1 is not ready or cannot be found.
You cannot access the database for one of the following reasons:
Verify that the database name, &V1., is correct. If not, use a correct database name and retry your request.
If the "CONNECT TO <location>" command is supported, QMF may have reconnected you to the current location. If so, you can continue to use QMF. If QMF cannot reconnect you, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00940 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00942 Database: SQL/DS QMF Function: Table Edit
The QMF virtual machine, &V2, cannot access database &V1..
The QMF virtual machine is not properly defined. The file ARISRMBT MODULE, on the QMF machine's A-disk, does not describe the database program that QMF is attempting to access.
Tell your QMF administrator about this message and wait for their response. There is nothing you can do until the QMF virtual machine is properly defined.
SQLCODE: -00943 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Your connection to SQL/DS was severed because of operator action.
The SQL/DS virtual-machine operator entered the FORCE command to cause ROLLBACK of the current logical unit of work and to sever your connection to the SQL/DS system. The userid, password, and database name are reset to their default values.
You can continue. Any explicit CONNECTs you have issued have been lost. You must issue another explicit CONNECT request, using the same USER ID, to reestablish your original connection.
SQLCODE: -00948 Database: SQL/DS QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
SQL error has been detected.
Refer to the DB2/400 Messages and Codes for a detailed explanation of this error.
The SQLCA is: &V1.
Argument of function too long.
The argument of a MIN or MAX function or the argument of a COUNT function is too long. The argument of a MIN or MAX column or scalar function cannot be more than 256 bytes. If the argument is graphic, then the argument cannot be longer than 128 DBCS characters. The argument of a COUNT function cannot be longer than 2000 bytes if DISTINCT is specified. If the argument is graphic, then the argument cannot be longer than 1000 DBCS characters.
Change the argument of the function so the length does not exceed the maximum. Try the request again.
ORDER BY or GROUP BY columns too long.
The maximum number of elements in an ORDER BY list is 10,000. The total length of all the ORDER BY elements cannot exceed 10,000 bytes. The maximum number of columns in a GROUP BY list is 120. The total length of all the GROUP BY columns cannot exceed 2,000 bytes. If the ORDER BY or GROUP BY list contains null capable columns, then an additional byte is required for each null capable column. If the ORDER or GROUP BY list contains variable length character columns, then the 2 byte length is included in the total length.
The statement must be changed so that the length of the ORDER BY or GROUP BY values does not exceed their limits. One or more column names must be removed from the clause. Try the request again.
Constraint type not valid for constraint &V1. in &V2..
An attempt was made to drop constraint &V1. in &V2. using an ALTER TABLE statement. The constraint was specified as UNIQUE, PRIMARY, or FOREIGN KEY and is not the same as the constraint found.
Verify the name and type of the constraint you want to drop. Try the request again.
&V1. in &V2. not valid in FOREIGN KEY clause.
View or table &V1. in &V2. was specified in the REFERENCES clause in the definition of a FOREIGN KEY referential constraint on a CREATE TABLE or an ALTER TABLE statement. Views and tables cannot be specified in a FOREIGN KEY clause.
Specify the base table that contains the parent key in the FOREIGN KEY clause. Try the request again.
ORDER BY expression is not valid.
The expression in the ORDER BY clause in position &V1. is not valid for reason code &V3..
Make the change listed for reason &V3. and try the request again:
See DSQ32001
Follow the directions in the referenced message.
Column attributes in your SELECT lists do not agree.
You connected two or more queries by UNION or UNION ALL. The SELECT lists in each query must have the same number of columns. Corresponding columns in each SELECT list must have comparable data definitions for the SELECT to succeed. If corresponding columns have field procedures, the columns must have the same field procedure and column CCSID value.
Rewrite your query with the SELECT lists of comparable columns, and rerun your query.
See DSQ32001
Follow the directions in the referenced message.
Update prevented by referential constraint &V1. in &V2..
Constraint &V1. in &V2. identifies the table being updated as the parent table in a relationship with dependent table &V3. in &V4., with an update rule of RESTRICT or NO ACTION. The update of a parent key is prevented when there are rows in the dependent table with matching values.
In order to perform this update, you must either drop the constraint, or delete the rows in the dependent table that are dependent on this row.
The FOREIGN key in constraint &V1. not same as the parent key.
The FOREIGN key in constraint &V1. in &V2. is not the same as the parent key of table &V3. in &V4.. The FOREIGN key must have the same number of columns as the parent key and the data type and attributes of the FOREIGN must be identical to the data type and attributes of the corresponding column of the parent key.
Correct the statement so that the description of the FOREIGN key conforms to that of the parent key of the specified table.
Table &V1..&V2 does not have a primary key.
You specified table &V1..&V2 as a parent table in a FOREIGN KEY clause, but it cannot be defined as a parent table because it does not have a primary key.
Define a primary key for the table using ALTER TABLE.
You lack the authorization necessary to run your command.
An operation was attempted on object &V1. in &V2.. This operation cannot be performed without the required authority.
Obtain the required authority from either the security officer or the object owner. Try the operation again.
Privilege not valid for table or view &V1. in &V2..
The specified privilege is not valid for one of the following reasons:
Specify a table or view that has the correct capability or remove the privilege that is not valid from the SQL statement.
&V1. in &V2. type &V3. already exists.
An attempt was made to create &V1. in &V2. or to rename a table, view, or index to &V1., but &V1. already exists. All tables, views, indexes, SQL packages, and constraints in the same library must have unique names. If the library name is *N, this is a CREATE COLLECTION statement, If this is a CREATE TABLE or ALTER TABLE statement and the type is *N, &V1. is a constraint.
Change &V1. to a name that does not exist, or delete, move, or rename the existing object. Try the request again.
Operation not allowed on system table &V1. in &V2..
The table or view &V1. in &V2. is a catalog or system table. Catalog and system tables cannot be changed or locked by the user.
Change the SQL statement to refer to a table that is not a system table. Try the request again.
&V1. in &V2. type &V3. cannot be dropped with RESTRICT.
An attempt was made to drop &V1. in &V2. with the RESTRICT option. &V1. cannot be dropped because a view, a constraint, or an index is dependent on it.
Specify CASCADE on the ALTER TABLE statement to drop &V1. and the views, constraints, or indexes that are dependent on it. Try the request again.
Table &V1. in &V2. already has a primary key.
An attempt was made to add a primary or unique key to table &V1. in &V2.. Either a primary key is already defined for this table, or the table has an access path which does not match the key being added. A table can only have one primary key. The constraint cannot be added.
Drop the primary key currently defined on the table or add the constraint as a UNIQUE constraint. If the table's access path does not match, make sure that the number of columns in the constraint match the number of columns in the access path. Try the request again.
SET NULL not allowed for referential constraint &V1..
SET NULL was specified in the REFERENCES clause for referential constraint &V1.. None of the columns in the foreign key allows null values.
Create the table so that at least one of the columns in the foreign key allows null values or specify a different default action on the ON DELETE clause. Try the request again.
Foreign key for referential constraint &V1. in &V2. too long.
The FOREIGN key cannot be created for constraint &V1. in &V2.. Either more than 120 columns were specified in a FOREIGN KEY clause or the sum of the lengths of the columns specified in the key exceeds the maximum of 2000 bytes. If the list contains null capable columns then an additional byte is required for the length of each null capable column. If the list contains variable length columns, then the 2-byte length of the column is included in the total length.
Remove some of the columns from the FOREIGN KEY clause. Try the request again.
Estimated query processing time &V1. exceeds limit &V2..
Estimated query processing time exceeds limit. The limit is &V2. seconds. An SQL query was about to be started which was estimated to require a longer elapsed time to run than that allowed by the query time limit attribute. The estimated elapsed time was &V1. seconds.
The following changes to the query could reduce the estimated elapsed time to be less than the query time limit.
See DSQ32001
Follow the directions in the referenced message.
Your command invoked a program not found in the current plan.
A remote request was attempted to &V3. for SQL package &V1. in &V2.. The SQL package was not found.
Check the invocation procedure. Perhaps you spelled the PLANID incorrectly.
Resource limit exceeded.
Resource limit type &V1. exceeded. A list of the limit types follows:
Do one of the following:
Row or object &V1. in &V2. type &V3. in use.
The requested object &V1. in &V2. type &V3. is either in use by another application process or a row in the object is in use by another application process.
Retry the operation later.
The database does not support three-part names.
The name you specified has a location qualifier "&V1". The database you are using does not support location qualifiers.
Remove the location qualifier "&V1" and retry your command. See your QMF administrator to make sure you are using the correct database.
Incorrect usage of &V1..
Some possibilities are:
Make the correction and continue.
&V1. &V2. was not found.
No routine was was found with compatible arguments for &V1. &V2..
This occurs when the database manager cannot find a routine it can use to implement the reference to &V1. &V2.. There are several reasons why this could occur:
Correct the statement and run the query again.
The specified combination of privileges cannot be granted or revoked.
One of the following occurred:
Correct the statement and run it again.
FOREIGN KEY &V1 is not valid.
FOREIGN KEY &V1 is not valid. The table cannot be defined as a dependent of table &V2 because of delete rule restrictions (reason code = &V3). A referential constraint cannot be defined because the object table of the CREATE TABLE or ALTER TABLE statement cannot be defined as a dependent of table &V2 for one of the following reason codes:
The delete rules of the existing relationships cause an error, not the delete rule specified in the FOREIGN KEY clause of the CREATE TABLE or ALTER TABLE statement. &V1 is the constraint name specified in the FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.
Eliminate the particular FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement and run the statement again.
The delete rule of FOREIGN KEY &V1 must be &V2..
The delete rule specified in a FOREIGN KEY clause of the CREATE TABLE or ALTER TABLE statement is not valid. Reason code &V3 was given. The indicated delete rule is required for one of the following reason codes:
&V1 is the constraint name specified in the FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.
Change the delete rule and run the statement again.
See DSQ33104
Follow the directions in the referenced message.
See DSQ33440
Follow the directions in the referenced message.
See DSQ33557
Follow the directions in the referenced message.
See DSQ33632
Follow the directions in the referenced message.
See DSQ33633
Follow the directions in the referenced message.
Character "&V1" in your query is invalid.
Your query cannot be processed because something is wrong with the character "&V1". It could be misplaced or invalid in the context in which it is being used.
Remove "&V1" or change it to a valid character.
SQLCODE: -00007 Database: DB2 QMF Function: PQ
Value needs an end quote.
Character constants must be enclosed in single quotes (like 'SANDERS'), and names of objects in the database, such as tables and columns, may be enclosed in double quotes (like "MYTABLE"). Without the final quote, there is no way to know where the constant or name is supposed to end. When a quote is used inside another quoted string, it must be shown as two consecutive quotes. For example:
Correct: ... WHERE NAME = 'O''CONNOR' Incorrect: ... WHERE NAME = 'O'CONNOR'
If the value is meant to be a character constant or double- quoted name, add an end quote or duplicate some quote inside it. Otherwise, remove the opening quote.
SQLCODE: -00010 Database: DB2 QMF Function: PQ
The &V1. value of &V2. is invalid.
Your query specifies a data type that has an incorrect &V1 specification of &V2.. The &V1 specification for that data type must not exceed the limit.
Some possible causes of your query error are:
Change the &V1 specification so that it is within the data type limit, and run the query again. See the SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00060 Database: DB2 QMF Function: PQ
The statement is not valid in this database manager.
The statement you just attempted to execute is not valid in DB2, though it may be valid with other database manager programs. A full list of SQL statements and options that are not allowed in DB2 is contained in the DB2 Reference Manual.
Use only DB2 statements while using this database manager.
SQLCODE: -00084 Database: DB2 QMF Function: PQ
Your query is too long.
The statement is too long or too complex to be interpreted. Your nesting of subqueries and correlated queries could be too complex for SQL processing.
Shorten your query or rewrite it as more than one query. If this problem continues, contact your QMF administrator.
SQLCODE: -00101 Database: DB2 QMF Function: PQ
Constant beginning '&V3.' &V1. is too long.
Reference line: ==>&V2.
The constant is longer than the maximum allowed. A character constant must be enclosed in quotes. If you omit a closing quote, your data could exceed the maximum length. Normally, character string length is 254 characters or 124 graphic characters if you use double byte character set; CURRENT SQLID value is 8 characters and CURRENT DEGREE value is 3 characters.
Correct the constant and run the query again.
SQLCODE: -00102 Database: DB2 QMF Function: PQ
&V1 is not a valid number.
&V1 starts with a digit, but is not a valid integer, decimal, or floating-point number. If it is meant to be a:
Change &V1 and run the query again.
SQLCODE: -00103 Database: DB2 QMF Function: PQ
Incorrect usage of &V1 or &V2..
Some possibilities are:
Make the correction and continue.
SQLCODE: -00104 Database: DB2 QMF Function: PQ
The statement contains an invalid string.
The statement contains an invalid string. Only a character string or a graphic string is valid.
Specify the correct format of string. For graphic data check for paired delimiters, the character G, and an even number of bytes within the string.
SQLCODE: -00105 Database: DB2 QMF Function: PQ
Name starting '&V1' is over &V2 characters long.
If this name specifies a column, table, view, index, alias, synonym, collection ID, or check constraints it cannot exceed 18 characters.
If this name specifies a location, it cannot exceed 16 characters .
If this name specifies a table, view qualifier, database, table space, storage group, bufferpool, referential constraint names specified in the CREATE or ALTER TABLE statement. or package ID, it cannot exceed 8 characters.
Use a shorter name and continue to use QMF.
SQLCODE: -00107 Database: DB2 QMF Function: PQ
&V1 is not valid in its context.
Some SQL keywords may not appear in some contexts. For example, ORDER BY, INTO, and FOR UPDATE may not be used with CREATE VIEW. INTO may not appear in any SELECT statement.
Correct the query and run it again.
SQLCODE: -00109 Database: DB2 QMF Function: PQ
Incorrect hexadecimal data found in value starting &V3.&V1..
Reference line: ==>&V2.
A single hexadecimal character is expressed by two letters or digits, so a hexadecimal value must be expressed by an even number of the digits 0 through 9 or the letters A, B, C, D, E, or F. The incorrect hexadecimal value either has an odd number of digits or letters, or contains an invalid letter or other character.
Correct the invalid value and run the query again.
SQLCODE: -00110 Database: DB2 QMF Function: PQ
A summary function must specify a column name.
You specified a summary function that contains an expression without a column name. A summary function must refer to a column name. Examples:
AVG(COMM + SALARY) is correct. AVG(1200 + 3498) is not correct.
Correct the expression of the summary function.
SQLCODE: -00111 Database: DB2 QMF Function: PQ
A summary function contains an invalid expression.
The summary functions are AVG, COUNT, MAX, MIN, and SUM. Any expressions used in a summary function cannot contain summary functions.
Correct: AVG(UNITS * PRICE) Incorrect: AVG(UNITS * MAX(PRICE))
Change your query so that the summary function has the correct expression.
SQLCODE: -00112 Database: DB2 QMF Function: PQ
Name &V3.&V1. contains an invalid character.
Reference line: ==>&V2.
The names for databases, storage groups, tablespaces, and bufferpools can contain only upper-case alphabetic, national (*, &, or @), or numeric characters. The first character must be alphabetic or a national character.
Correct the invalid character in name &V3. and run the query again.
SQLCODE: -00113 Database: DB2 QMF Function: PQ
Incorrect use of &V3.&V1..
Reference line: ==>&V2.
A simple comparison like '>' or '=' must not be followed by a list of items. ANY and ALL comparisons must be followed by a subselect, rather than an expression or a list of items. For Example:
Correct: WHERE SALARY > ALL (SELECT COMM
FROM Q.STAFF)
Incorrect: WHERE SALARY > ALL (10000)Change the usage of &V3. and run your query again.
SQLCODE: -00115 Database: DB2 QMF Function: PQ
The number of values does not match the number of columns.
In a statement like INSERT INTO Q.STAFF, you must provide a value for every column that was defined as NOT NULL.
If you do not give a list of columns after the table name, then give a value for every column in the table, after VALUES.
If you do give a list of columns after the table name, then give a value for every column in that list, after VALUES.
Example:
INSERT INTO Q.STAFF (ID, NAME, DEPT)
VALUES (400, 'HARRISON', 20)Provide a value for each column you want to INSERT INTO and run the query again.
SQLCODE: -00117 Database: DB2 QMF Function: PQ
You cannot modify a table used in a subquery.
"Modify" includes INSERT, UPDATE, and DELETE.
Incorrect: INSERT INTO Q.STAFF SELECT * FROM Q.STAFF WHERE YEARS > 7
The example tries to modify the table from which it is receiving data.
Change your query so that the same table used in the subquery is not modified or write a separate query to modify the table.
SQLCODE: -00118 Database: DB2 QMF Function: PQ
The grouping is inconsistent.
One of the following has occurred:
Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Correct: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)(If you use * after SELECT, list all column names after GROUP BY.
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6)Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Change the SQL statement and run your query again.
SQLCODE: -00119 Database: DB2 QMF Function: PQ
A built-in function or grouped column is used incorrectly.
You cannot use a built-in function (AVG, COUNT, MAX, MIN or SUM) after WHERE or SET except as part of a subquery.
Correct:
WHERE YEARS > (SELECT AVG(YEARS)
FROM Q.STAFF)
Incorrect:
WHERE YEARS > AVG(YEARS)If your query refers to a view, a column named after GROUP BY in the view definition cannot be used in a condition in your query. For example, if DEPT is used after GROUP BY in defining VIEW, then the following is
Incorrect: SELECT DEPT, SUMSALARY FROM VIEW WHERE DEPT = 20
Change your query and run it again. If your query uses a view, write a query to select from the table the view is based on.
SQLCODE: -00120 Database: DB2 QMF Function: PQ
You cannot modify a column twice in the same query.
"Modify" includes INSERT and UPDATE. For example, in the following invalid statement, the column 'YEARS' cannot be modified more than once.
Incorrect:
INSERT INTO Q.STAFF (ID, YEARS, JOB,
YEARS)
VALUES (400, 7, 'clerk', 8)Change the SQL statement so that there is only one modification and run it again.
SQLCODE: -00121 Database: DB2 QMF Function: PQ
The grouping is inconsistent.
One of the following has occurred:
Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Correct: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)(If you use * after SELECT, list all column names after GROUP BY.
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6)Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Change the SQL statement and run your query again.
SQLCODE: -00122 Database: DB2 QMF Function: PQ
The parameter in position &V1 must be a constant or keyword.
The parameter in position &V1 of the function &V2 is not a constant when it is required to be a constant or a keyword when it is required to be a keyword.
Correct the function call and run the query again.
SQLCODE: -00123 Database: DB2 QMF Function: PQ
The number in the SELECT list does not identify a column.
The column number in error may be 0, or it may be larger than the number of columns listed after SELECT.
Incorrect Examples:
ORDER BY 5 means ordering by the
fifth item in the
SELECT list; it won't
work if the SELECT
list has only four items.
ORDER BY 0 will never work.Change the column number following ORDER BY to agree with the SELECT list and run the query again.
SQLCODE: -00125 Database: DB2 QMF Function: PQ
DISTINCT cannot be used more than once in a query.
DISTINCT was used more than once in your query. DISTINCT is implied if you chose to keep a single copy of selected rows. You may have done that and also used DISTINCT in a summary function.
Use DISTINCT no more than once in your query.
SQLCODE: -00127 Database: DB2 QMF Function: PQ
Use NULL with IS or IS NOT.
NULL cannot be used as an item in a list following IN in a WHERE clause. For example
WHERE AMT IN (20,50,NULL) is wrong, but WHERE AMT IN (20,50) OR AMT IS NULL is OK.
Change the phrase with NULL and run your query again.
SQLCODE: -00128 Database: DB2 QMF Function: PQ
Query uses more than 15 table references.
One query may not make more than 15 references to tables.
Divide your query into two or more queries, each with 15 or fewer table references.
SQLCODE: -00129 Database: DB2 QMF Function: PQ
Statement with LIKE has incompatible data types.
If the column name to the left of LIKE or NOT LIKE is of type CHARACTER, the expression at the right must be of type CHARACTER. If the column name is of type GRAPHIC, the expression at the right must be of type GRAPHIC.
If the expression to the right of LIKE or NOT LIKE contains ESCAPE character, the data type of the ESCAPE character must be compatible with the type of the column name to the left.
Check the data type of every operand and run the query again.
SQLCODE: -00131 Database: DB2 QMF Function: PQ
LIKE is used incorrectly.
A condition written with LIKE is invalid. Follow LIKE by a character constant; you may use the symbols '%' and '_'.
Write NAME LIKE 'JO%' , where NAME is
a column name.Change the condition using LIKE and run your query again.
SQLCODE: -00132 Database: DB2 QMF Function: PQ
An expression is improperly used after a HAVING or WHERE clause.
You must use a column name, rather than an expression, as the argument of a built-in function, when that column is a correlated reference column in a WHERE or HAVING clause. For example:
SELECT DEPT,SUM(YEARS) FROM Q.STAFF VARX GROUP BY DEPT HAVING SUM(YEARS) > ANY (SELECT AVG(YEARS) FROM Q.STAFF GROUP BY DEPT HAVING MAX(YEARS) > MIN(1*VARX.YEARS))
is incorrect -- (1*VARX.YEARS) cannot be the argument of a built-in function MIN because it is an expression containing the correlated reference variable VARX.YEARS.
Correct your query and rerun it.
SQLCODE: -00133 Database: DB2 QMF Function: PQ
A wide character column is used incorrectly.
Several restrictions exist when using a column that has a character data type and a width greater than 254 characters. It cannot be selected in the Columns section of the query when the Duplicate Rows indicates to keep a single copy of each row. Some releases of the Relational Database manager do not allow it to be used in a Row Condition with an operator of Starting With, Ending With, or Containing.
Change your use of the wide character column or remove the Keep Single Copy line from the query.
SQLCODE: -00134 Database: DB2 QMF Function: PQ
Sort key length cannot exceed 4000 bytes.
The sort key is made up of the list of columns specified following DISTINCT, or in an ORDER BY or GROUP BY clause. If both DISINCT and ORDER BY or GROUP BY are present, the sort key is made from the combination of both column lists.
Change your statement so that the internal length of the sort key will not exceed 4000 bytes. One or more column names must be deleted from the ORDER BY or GROUP BY clause, or the list following the DISTINCT qualifier.
SQLCODE: -00136 Database: DB2 QMF Function: PQ
The result of concatenation is too long.
The length of the result of a concatenation (two vertical bars "||") exceeds 32,764 characters or 16,382 graphic characters.
Change your query to create a shorter string, and run the query again.
SQLCODE: -00137 Database: DB2 QMF Function: PQ
The second or third argument of the SUBSTR function is out of range.
SUBSTR(ARG1, ARG2, ARG3)
ARG1: must be a character or graphic
string
ARG2: must be an integer and
1 <= ARG2 <= L
ARG3: must be an integer and
0 <= ARG3 <= L-N+1
Where L : the length of ARG1
N : the value of ARG2Change the second or third argument of SUBSTR and run the query again.
SQLCODE: -00138 Database: DB2 QMF Function: PQ
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00150 Database: DB2 QMF Function: PQ
Column &V1 cannot be changed.
You cannot use INSERT, UPDATE, or DELETE (in SQL) or I., U., or D. (in QBE) to change a column in:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00151 Database: DB2 QMF Function: PQ
View columns defined by expressions or functions need names.
Your CREATE VIEW statement includes a column defined from an expression, such as UNITS * PRICE; a built-in function, such as AVG(YEARS); or a constant, such as 'JUNE 1'. You must supply names for those columns, and so you must have a name list with a name for each column.
Provide new names for all columns defined from functions or expressions in your CREATE VIEW query.
SQLCODE: -00153 Database: DB2 QMF Function: PQ
You cannot create a view that uses UNION or contains a remote object.
The definition of the view to be created uses the keyword UNION or contains a remote object. This is not permitted in the definition of a view.
Define the view in some other way.
SQLCODE: -00154 Database: DB2 QMF Function: PQ
A view defined by GROUP BY or HAVING is named after FROM.
One of the tables named after FROM in your query is a view defined by a query that uses a GROUP BY or HAVING clause. That view cannot be named after FROM along with any other table.
Rewrite your query so as not to name the view along with another table, after FROM. Run the query again.
SQLCODE: -00155 Database: DB2 QMF Function: PQ
Query does not identify a table.
ALTER TABLE, DROP TABLE, LOCK TABLE, or CREATE INDEX may be used only with tables. Names of a view or remote object cannot be used after these statements.
Be sure that the proper table name was used in the query. Do not use the name of a view or remote object after the statements listed above.
SQLCODE: -00156 Database: DB2 QMF Function: PQ
The CREATE VIEW and SELECT lists need the same number of columns.
There must be a column name in your SELECT list for every column name in the CREATE VIEW list. If you replace the list of names in the SELECT list with an asterisk (*), the view will contain the same column names as the original table.
Change the SELECT list column names to conform to the CREATE VIEW list and run the query again.
SQLCODE: -00158 Database: DB2 QMF Function: PQ
Name used is a table, not a view or an alias.
DROP VIEW is used only to drop a view. DROP ALIAS is used only to drop an alias. COMMENT ON ALIAS is used only to comment on an alias.
You cannot drop or comment on a table using DROP VIEW, DROP ALIAS or COMMENT ON ALIAS.
If you want to drop or comment on a table, use the DROP TABLE or COMMENT ON TABLE statement.
SQLCODE: -00159 Database: DB2 QMF Function: PQ
WITH CHECK cannot be used with this view.
The WITH CHECK option cannot be used if...
Continue with another operation.
SQLCODE: -00160 Database: DB2 QMF Function: PQ
Insert or update value does not satisfy view definition.
WITH CHECK OPTION was used in the definition of the view whose data you are trying to change. All attempts to insert or update rows in the view are checked to make sure that the results will conform to the definition of the view. Some value in your query does not satisfy a condition in that definition.
Examine the definition of the view to determine why the change was rejected, and change the value in the query.
SQLCODE: -00161 Database: DB2 QMF Function: PQ
You cannot create a view in another user's name.
Your query attempted to create a view with a qualified name (a name of the form USERID.TABLENAME), and the qualifier of the name was not your own DB2 authorization ID. You can only create a view using an authorization ID other than your own if you have "SYSADM" authority.
Correct the query and run it again or obtain the authorization needed to create a view for someone else.
SQLCODE: -00164 Database: DB2 QMF Function: PQ
The number of arguments specified for scalar function '&V1' is invalid.
The SQL statement has specified the scalar function &V1 with either too many or too few arguments. The supported scalar functions are:
DECIMAL, DIGITS, FLOAT, HEX, INTEGER, VARGRAPHIC, DATE, TIME, TIMESTAMP, DAYS, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, MICROSECOND, LENGTH, SUBSTR, and VALUE.
Examine the use of the scalar function &V1. Change the scalar function and run the query again.
SQLCODE: -00170 Database: DB2 QMF Function: PQ
Argument '&V1' of scalar function '&V2' is invalid.
The data type, length, or value specified for scalar function '&V2' is incorrect. Refer to SQL query publications for more information.
Change the data type, length, or value of '&V2' function and run the query again.
SQLCODE: -00171 Database: DB2 QMF Function: PQ
The datetime value &V1 is invalid.
The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
Correct the syntax for the datetime value and run the query again.
SQLCODE: -00180 Database: DB2 QMF Function: PQ
The datetime value is not a valid value.
The string representation of a datetime value contains a value which is out of range. The proper ranges for datetime values are as follows:
Years - 1 to 9999 Months - 1 to 12 Days - 1 to 31 Hours - 0 to 24 Minutes - 0 to 59 Seconds - 0 to 59
Correct the datetime value and run the query again.
SQLCODE: -00181 Database: DB2 QMF Function: PQ
An arithmetic expression with a datetime value is invalid.
The specified arithmetic expression contains an improperly used datetime value or simple duration. Some correct examples are:
SELECT STARTD + 10102433. FROM Q.PROJECT SELECT STARTD + 1 YEAR FROM Q.PROJECT
Correct the expression and run the query again.
SQLCODE: -00182 Database: DB2 QMF Function: PQ
An arithmetic operation on a date or timestamp has a result that is invalid.
The result of an arithmetic operation is a date or timestamp that is not within the valid range. Valid dates are between 0001-01-01 and 9999-12-31.
Correct the datetime value and run the query again.
SQLCODE: -00183 Database: DB2 QMF Function: PQ
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00184 Database: DB2 QMF Function: PQ
The date or time value cannot be formatted.
One of the following has occurred:
Either change your string representation of the date or time value to be one of the recognized formats, or contact your QMF administrator for assistance in making the local date or time routine available to the database.
SQLCODE: -00185 Database: DB2 QMF Function: PQ
Do not use qualified column names with ORDER BY.
When using ORDER BY with UNION or UNION ALL, do not use a qualified column name after the ORDER BY. Instead, use an unqualified name or a number that tells the position of the column in the list after SELECT.
Example 1: SELECT NAME, ID FROM Q.STAFF UNION SELECT NAME, TEMPID FROM Q.APPLICANT ORDER BY 1 Example 2: SELECT NAME, ID FROM Q.STAFF UNION SELECT NAME, TEMPID FROM Q.APPLICANT ORDER BY NAME
Change the statement so that qualified column names are not being used and run the query again.
SQLCODE: -00197 Database: DB2 QMF Function: PQ
The query is empty or contains only comments.
An empty query, or one containing only comments, contains no instructions to do anything. It cannot be run.
Write another query.
SQLCODE: -00198 Database: DB2 QMF Function: PQ
SQL error at or before &V1..
Some common errors that produce this message are:
Correct the query and run it again.
SQLCODE: -00199 Database: DB2 QMF Function: PQ
Column &V1 is in more than one table.
An unqualified column name is ambiguous if more than one table or view in the FROM clause has a column with that name, or if more than one column of a nested table expression has that name. A qualified column name is ambiguous only if the correlation name for the column name and for a nested table expression is not unique.
If the problem is caused by a non-unique column name in a nested table expression, change the nested table expression so that the column is unique. If the problem is caused by the use of an unqualified name, qualify it with a table, view or correlation name.
SQLCODE: -00203 Database: DB2 QMF Function: PQ
&V1 could not be found.
The query refers to &V1.. Nothing with this name exists in the database.
Check for a spelling error.
SQLCODE: -00204 Database: DB2 QMF Function: PQ
&V1 is not a column defined in a selected table.
&V1 has been specified as a column, and it could not be found in any of the tables you selected. You may have misspelled the name. If &V1 is intended to be a character constant, enclose it in single quotes.
You can use the command DISPLAY Q.COLUMN_LIST to display a table of information about all the columns in tables you are authorized to use. Verify the spelling of the column name, and then correct the column name or add the table containing column &V1 to the query.
SQLCODE: -00205 Database: DB2 QMF Function: PQ
Column &V1 is not in any table named in the query.
&V1 is not a column in any table or view named in the query. If it is intended to be a character constant, enclose it in single quotes.
Change the column name or add the table containing column &V1 to the query, and run the query again.
SQLCODE: -00206 Database: DB2 QMF Function: PQ
Use column numbers with ORDER BY, not column names.
When using ORDER BY with UNION, do not use a column name after ORDER BY. Instead, use a number that tells the position of the column in the list after SELECT.
Example: SELECT NAME, ID FROM Q.STAFF UNION SELECT NAME, TEMPID FROM Q.APPLICANT ORDER BY 1
Change the column names to column numbers and run the query again.
SQLCODE: -00207 Database: DB2 QMF Function: PQ
&V1 must be in the SELECT list.
&V1 follows ORDER BY. Either &V1 was not included in the SELECT list or it is misspelled after ORDER BY.
Add &V1 to the SELECT list; be sure it agrees with the column name after ORDER BY.
SQLCODE: -00208 Database: DB2 QMF Function: PQ
The location qualifier cannot be used.
The name you specified has a location qualifier. A three-part object name cannot be used until the local location name is defined.
Remove the location qualifier and retry your query. See your QMF administrator to make sure you are using the correct database, or to define the local location name.
SQLCODE: -00250 Database: DB2 QMF Function: PQ
&V1 is not a valid location name.
&V1 contains an alphabetic extender (#, @, $). Alphabetic extenders are not allowed in location names.
Correct the location name and try again.
SQLCODE: -00251 Database: DB2 QMF Function: PQ
Function is not supported (reason code = &V1).
The statement cannot be processed because it violates a restriction as indicated by the following reason codes:
The action corresponding to the reason code is:
SQLCODE: -00270 Database: DB2 QMF Function: PQ
Invalid use of colon (:).
Your query uses a name preceded by a colon, as in "WHERE NAME = :NAME (That usage has a meaning in a query submitted to the preprocessor program, but not in a query in QMF.)
Correct your query. Use names of tables, columns, or views, or else character constants enclosed in single quotes.
SQLCODE: -00312 Database: DB2 QMF Function: PQ
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00313 Database: DB2 QMF Function: PQ
A character string could not be converted due to undefined CCSIDs.
Your SQL statement referenced a character string with a coded character set ID(CCSID) &V1 in a coded character set that differs from the current one. To use this character string at the current server, this character string must be translated from the source CCSID &V1 to the target CCSID &V2. However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Verify that the character columns and values you referenced are correct. If not, make the necessary change and try the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: DB2 QMF Function: PQ
Invalid use of the ON clause.
The ON clause is being used incorrectly for one of the following reasons:
Correct the syntax of the ON clause and run the query again.
SQLCODE: -00338 Database: DB2 QMF Function: PQ
Invalid data type in position &V1..
Some SQL data types are not supported by the application requester. &V1 is the position of the first element with an invalid data type in the SQLDA. A common cause for this error is that the application requester has attempted to describe large object data residing at the application server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB, and DBLOB.
Remove the invalid data types and run the query again.
SQLCODE: -00351 Database: DB2 QMF Function: PQ
Data of different types cannot be mixed or compared.
Either an expression mixes numeric with non-numeric data, an attempt is made to compare numeric and non-numeric data, or an attempt is made to compare character and graphic data.
Assuming SALARY is a numeric column and NAME is non-numeric, the following examples are invalid:
SALARY - NAME - is an invalid
expression
NAME/2 - is an invalid
expression
If NAME Is Equal
To SALARY - is an invalid
conditionChange your expression so that it does not mix data of different types.
SQLCODE: -00401 Database: DB2 QMF Function: PQ
Numeric data is required.
You used non-numeric data with a numeric operator or function. Two examples are:
NAME AVG(NAME)
where NAME is column name not defined as numeric.
Change your query to use only numeric data with the arithmetic expression or function.
SQLCODE: -00402 Database: DB2 QMF Function: PQ
Value given is too long for column &V1..
The maximum width of column &V1 is less than the number of characters you are trying to put into it.
Change the value to fit the column and run the query again.
SQLCODE: -00404 Database: DB2 QMF Function: PQ
Numeric value &V1 is outside the allowable range for your column.
&V1 is outside the range of values allowed for the associated column.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of the
column. For example, if
the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change &V1 and continue.
SQLCODE: -00405 Database: DB2 QMF Function: PQ
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of the
column. For example, if
the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun the query.
SQLCODE: -00406 Database: DB2 QMF Function: PQ
Column &V1 cannot contain a NULL value.
The update or insert value for column &V1 was NULL. However, column &V1 was made NOT NULL in the table definition. If you are inserting a row, the failure to specify a value for a column implies that you want to insert NULL in it.
Enter a value for column &V1..
SQLCODE: -00407 Database: DB2 QMF Function: PQ
New value has wrong data type for column &V1..
The data type of the new value in column &V1 does not agree with the data type of the column. Both must be numbers, character strings, graphic strings, dates, times, or time stamps.
Enter some other value for column &V1 and run the query again.
SQLCODE: -00408 Database: DB2 QMF Function: PQ
DISTINCT must be used in the expression of a COUNT summary function.
In prompted query, the function COUNT can be used only with DISTINCT and a column name. Example of usage:
COUNT(DISTINCT column name)
gives the number of different values in the column.
Change your use of COUNT.
SQLCODE: -00409 Database: DB2 QMF Function: PQ
Value starting '&V1' is longer than 30 characters.
A floating-point constant cannot be more than 30 characters long.
Round &V1 so that it can be written with 30 characters or fewer.
SQLCODE: -00410 Database: DB2 QMF Function: PQ
Use of USER, CURRENT DATE/TIME, or CURRENT SQLID is invalid.
USER is not valid in Prompted Query. The CURRENT DATE/TIME or CURRENT SQLID is used in a way that is invalid for its data type:
Change your query to conform to the above rules.
SQLCODE: -00411 Database: DB2 QMF Function: PQ
Use only one column after SELECT in the subquery.
When SELECT is used in a subquery, (except after INSERT), it can select only one column name.
Incorrect: (SELECT PARTNO, PRICE.......)
Change the SELECT list in your subquery and run the query again.
SQLCODE: -00412 Database: DB2 QMF Function: PQ
Arithmetic overflow during change of data type.
The result of an arithmetic or insert operation is not valid because arithmetic overflow occurred. For example, you may have tried to INSERT values with a data type of INTEGER into a column with data type of SMALLINT. Conversion is possible so long as the INTEGER values are small enough. But a value larger than 32,767 will cause arithmetic overflow.
Change your operation and run the query again.
SQLCODE: -00413 Database: DB2 QMF Function: PQ
LIKE requires character or graphic data, the column has numeric or datetime data.
You wrote something like this: LIKE '1%' or LIKE '%12.40.25', where LIKE compares a partial value to the values in some column. The column has a numeric or datetime data type and LIKE requires character or graphic data.
Correct your query and run it again. With numeric data, use a numeric comparison, like "n >= 1000 and n < 2000".
SQLCODE: -00414 Database: DB2 QMF Function: PQ
Column attributes in your SELECT lists do not agree.
You connected two or more queries by UNION or UNION ALL. The SELECT lists in each query must have the same number of columns. Corresponding columns in each SELECT list must have comparable data definitions for the SELECT to succeed. If corresponding columns have field procedures, the columns must have the same field procedure and column CCSID value.
Rewrite your query with the SELECT lists of comparable columns, and rerun your query.
SQLCODE: -00415 Database: DB2 QMF Function: PQ
Wide character columns cannot be used with UNION.
A column with data type LONG VARCHAR, or with a width greater than 254, cannot be listed after SELECT in a query that uses UNION. Columns with these data types can be used: INTEGER, SMALLINT, DECIMAL, FLOAT, CHAR. A VARCHAR column can be used if its width is less than 255.
Remove any column wider than 254 characters from the SELECT list of any query used with UNION.
SQLCODE: -00416 Database: DB2 QMF Function: PQ
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00417 Database: DB2 QMF Function: PQ
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00418 Database: DB2 QMF Function: PQ
Decimal division is not possible with the values used.
Either the precision of the numerator or the scale of the denominator is too large for decimal division.
Change the precision or scale of your decimal division values and run the query again. Note that an integer or small integer value may have been converted to decimal for this calculation.
SQLCODE: -00419 Database: DB2 QMF Function: PQ
An invalid character string argument was used with the &V1 function.
A character string argument did not conform to the requirements of the function. For example, a character string passed to the DECIMAL function did not conform to the rules for forming an SQL integer or decimal constant.
Change the value of the argument so that it conforms to the requirements of the function.
SQLCODE: -00420 Database: DB2 QMF Function: PQ
SELECT lists do not have the same number of columns.
You connected two or more queries by UNION. The SELECT lists in each query must have the same number of columns.
Correct the query and run it again.
SQLCODE: -00421 Database: DB2 QMF Function: PQ
Invalid use of DISTINCT or ALL with &V1..
The keyword DISTINCT or ALL was detected within the parentheses in a reference to the function &V1.. This function was recognized as a scalar function.
If a scalar function is being used then remove the keyword DISTINCT or ALL. It is invalid for a scalar function.
If a column function is being used, then there is a problem with function resolution. Check the value of special register CURRENT FUNCTION PATH. Also check the spelling of the function name and the number and types of parameters in both the query and the system catalog.
SQLCODE: -00441 Database: DB2 QMF Function: PQ
The function &V1 has too many arguments.
Too many arguments were specified in the reference to function &V1. The maximum allowable is 90.
Correct the statement by ensuring the correct number of arguments was used and run the query again.
SQLCODE: -00442 Database: DB2 QMF Function: PQ
This query exceeds a DB2 cost estimate limit.
DB2 has determined that the cost estimate for this query exceeds a limit specified in the Resource Limit Facility (DB2 governor) preventing the query from being run.
The details of the cost estimate for the query statement are:
If the cost category value is 'B', seek the assistant of your DB2 administrator, the DB2 catalog statistics or resource limit specification tables (RLST) might need updating.
If the SQL statement is consuming too much processor time, rewrite the statement to perform more efficiently and run the query again.
Things to check might be:
Some queries can be made simpler by removing the GROUP BY clause from the query and using the GROUP usage code in the QMF FORM instead.
Some queries will perform better by using advanced SQL syntax, such as Outer Join or the CASE expression,
For advanced analysis the EXPLAIN SQL statement can be used to gather information about the structure and execution performance of a query.
Refer to the SQL Reference for more information on Queries and the EXPLAIN statement.
Refer to the DB2 Administration manual for more information on tuning queries and writing efficient predicates and subqueries.
SQLCODE: -00495 Database: DB2 QMF Function: PQ
The query reference to a remote object is invalid.
One of the following invalid conditions exists:
Refer to the DB2 SQL Reference manual for more information on using remote objects.
SQLCODE: -00512 Database: DB2 QMF Function: PQ
The alias name &V1 cannot be defined on another local or remote alias.
The object indicated by &V1 exist at the location indicated. However, It is defined as an alias at at that location.
Modify the query to ensure that all object references are to tables or views at the indicated location.
SQLCODE: -00513 Database: DB2 QMF Function: PQ
Table &V1 has no primary index for the primary key.
You cannot use table &V1.. It has a primary key, but no primary index.
Define a primary index for the table before you refer to it.
SQLCODE: -00540 Database: DB2 QMF Function: PQ
&V3 does not exist, or you lack the necessary authority.
&V3 does not exist, or it is a read-only view, or you (the &V1 ID) lack the &V2 authority. The possible causes of the authorization failure are:
If you misnamed an existing object, use the correct name. If the &V1 ID lacks needed authority, contact your QMF administrator.
SQLCODE: -00551 Database: DB2 QMF Function: PQ
The specified object does not exist, or you lack needed authority.
The specified object does not exist, or it's a read-only view, or you lack some needed authority, as follows:
If you misnamed an existing object, use the correct name. If you lack needed authority, contact your QMF administrator.
SQLCODE: -00552 Database: DB2 QMF Function: PQ
You cannot grant a privilege to yourself.
Privileges can only be granted from one user with the proper authority to another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you need additional privileges.
SQLCODE: -00554 Database: DB2 QMF Function: PQ
You cannot revoke a privilege from yourself.
Privileges can only be revoked by one user with the proper authority from another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you want any database privileges reduced.
SQLCODE: -00555 Database: DB2 QMF Function: PQ
You cannot revoke this privilege from &V1..
Either &V1 does not have the privilege you are trying to revoke, or it was granted by a user with a different authorization identifier from yours. You can revoke only privileges granted under your authorization identifier.
Proceed to another operation.
SQLCODE: -00556 Database: DB2 QMF Function: PQ
GRANT and REVOKE cannot be run now.
The authorization portion of the system is temporarily disabled. GRANT and REVOKE queries cannot be run.
Run your query again when the authorization portion of the system is running. Contact your QMF administrator for more details.
SQLCODE: -00559 Database: DB2 QMF Function: PQ
&V1 is the name of an existing &V2..
You tried to CREATE an object named &V1 when a &V2 of that name already exists.
Either DROP &V2 &V1 before running the query, or choose another name for &V1..
SQLCODE: -00601 Database: DB2 QMF Function: PQ
The CREATE INDEX or PRIMARY KEY statement specifies to many columns.
The number or columns specified in the CREATE INDEX or PRIMARY KEY statement exceeds the maximum number of columns allowed.
Change your CREATE INDEX or PRIMARY KEY statement to conform to the column limit.
SQLCODE: -00602 Database: DB2 QMF Function: PQ
The specified unique index column has duplicate values.
You cannot create an unique index on the specified columns because the table already contains rows that have duplicate values on the column. If a column has a type of VARCHAR or VARGRAPHIC, two columns that differ only in the number of trailing blanks might cause duplication.
Change your CREATE statement so that it does not refer to a column with duplicate values, or else delete rows with duplicate values from the table.
SQLCODE: -00603 Database: DB2 QMF Function: PQ
You used a constant that exceeds maximum width allowed.
You specifies a constant that has a length, precision, or scale outside the data type limit. Two possible causes of the error are the precision or scale for a DECIMAL constant exceeded the data type limit, and the length for a CHAR, FLOAT, GRAPHIC, VARCHAR or VARGRAPHIC constant exceeded the data type limit.
Change the constant specification to conform to the data type limit and run your query again. See the DB2 SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00604 Database: DB2 QMF Function: PQ
&V1 cannot be used with this catalog object.
You cannot use INSERT, UPDATE, or DELETE with the catalog object specified in the SQL statement. You cannot use the DEFER YES option for indexes on catalog tables SYSINDEXES, SYSKEYS, and SYSINDEXPART.
Do not attempt this operation.
SQLCODE: -00607 Database: DB2 QMF Function: PQ
You used column name &V1 twice.
A table cannot contain two columns with the same name. In CREATE TABLE, CREATE VIEW, or CREATE INDEX you used column name &V1 more than once. In ALTER TABLE, &V1 is already the name of a column in the table.
Choose another column name and run your query again.
SQLCODE: -00612 Database: DB2 QMF Function: PQ
Columns chosen cannot be indexed.
Under CMS, you cannot index a LONG VARCHAR or LONG VARGRAPHIC column.
Under TSO, you cannot index a VARCHAR column whose maximum allowable length is over 254 characters.
Under either CMS or TSO, you cannot index a group of columns if the sum of their internal lengths exceeds 255 characters.
Revise your index or primary key definition, either by omitting one or more of the columns or by replacing long columns with shorter ones.
SQLCODE: -00614 Database: DB2 QMF Function: PQ
You cannot drop &V2; other objects depend on it.
&V2 cannot be dropped because the &V3 named &V4 refers to it.
If you want to drop &V2, first drop all objects that depend on it.
SQLCODE: -00616 Database: DB2 QMF Function: PQ
&V1 cannot be performed on system databases.
System databases cannot be the object of certain types of operations, including &V1..
Do not attempt this operation.
SQLCODE: -00618 Database: DB2 QMF Function: PQ
Table &V1 can have only one CLUSTER index.
The CREATE INDEX statement would create a second CLUSTER index on table &V1.. But a table may have only one CLUSTER index.
Determine the identity and validity of the existing CLUSTER index. Consider creating the new index without the CLUSTER definition.
SQLCODE: -00623 Database: DB2 QMF Function: PQ
The partitioning keys for partition &V1 are not specified in ascending or descending order.
Your query creates a CLUSTER index for a partitioned table (a table in a partitioned tablespace). The key values in the limit-key-value specifications must be given in ascending or descending order.
Correct the limit-key-value specifications so that the values for successive partitions are in strictly ascending or descending order.
SQLCODE: -00636 Database: DB2 QMF Function: PQ
Invalid value for &V1 in &V2 query.
The value given for &V1 in the &V2 query is not a permitted value.
Refer to the SQL Help for information about allowable values for &V1 in &V2 queries.
SQLCODE: -00644 Database: DB2 QMF Function: PQ
Table space &V2 already contains a table.
Table space &V2, named in the CREATE TABLE query, is a partitioned or default table space that already contains an existing table. Only one table can be contained in a partitioned or default table space.
Be sure you used the correct table space in the query. Do not attempt to create more than one table in a partitioned or default table space.
SQLCODE: -00646 Database: DB2 QMF Function: PQ
Bufferpool &V1 must be activated.
Bufferpool &V1, named in your CREATE or ALTER query for a table space or index space, is not activated. The bufferpool has NUMPAGES = 0.
Table spaces and index spaces can only be assigned (or re-assigned) to bufferpools currently activated.
Be sure that the proper bufferpool was named in the create or alter statement. If it was, activate the bufferpool and execute the statement again.
SQLCODE: -00647 Database: DB2 QMF Function: PQ
Procedure &V1 rejects the result.
&V1 is a procedure defined by your installation to edit or validate the results of queries. The result of your query did not meet some requirement of this procedure.
See your QMF administrator for descriptions of your installation's edit and validation procedures.
SQLCODE: -00652 Database: DB2 QMF Function: PQ
Table &V1 has no partitioned index.
A partitioned table (a table in a partitioned tablespace) cannot be referenced until the CLUSTER index for that table has been created. Table &V1 has no CLUSTER index.
Be sure that the correct table was specified in the statement. If it was, create a CLUSTER index for that table and execute your statement again.
SQLCODE: -00653 Database: DB2 QMF Function: PQ
The maximum size of a table object has been exceeded.
One or more of the objects that make up a table has reached its maximum size. The storage objects that make up a table are:
Once a storage object has grown to its maximum size, it cannot be extended further.
To make existing space within the object available to store new data, you can:
SQLCODE: -00659 Database: DB2 QMF Function: PQ
&V1 is not partitioned.
Your CREATE INDEX query contains PART specifications, but tablespace &V1 is not a partitioned tablespace.
Be sure that the proper table is specified in the statement. If it was, the table must be partitioned before a partitioned index can be created.
SQLCODE: -00662 Database: DB2 QMF Function: PQ
Wrong number of key limit values for &V1..
The number of limit-key-values in at least one PART specification is either zero or greater than the number of columns in the index key.
Change the number of limit-key-values and continue.
SQLCODE: -00663 Database: DB2 QMF Function: PQ
Limit-key fields of index &V1 are too long.
The total length of the keys for a partitioned index may not exceed 40 bytes internally.
Reduce the total number of columns used in key fields of your index.
SQLCODE: -00664 Database: DB2 QMF Function: PQ
The PART clause of an ALTER statement is omitted or invalid.
The ALTER statement is invalid for one of the following reasons:
Determine whether the table space or index you want to alter is partitioned. If it is partitioned, specify a PART clause that identifies the partition you want to alter. If it is not partitioned, do not use a PART clause.
SQLCODE: -00665 Database: DB2 QMF Function: PQ
A utility, the Resource Limit Facility, or the Distributed Data Facility is running.
If a system utility is running, it must complete execution before your query can be run. If the Resource Limit Facility is running, it must be stopped or switched to a different resource limit control table before your query can be run. If the Distributed Data Facility is running, it must be stopped before an object in the communications database can be dropped.
Wait for the utility to finish, or wait until the Resource Limit Facility stops or switches to a different resource limit control table, then run your query again. Or wait until the Distributed Data Facility stops, then drop the object.
SQLCODE: -00666 Database: DB2 QMF Function: PQ
The index cannot be removed by the DROP INDEX statement.
The DROP INDEX statement attempted to drop one of the following indexes:
Neither of these indexes can be explicitly dropped. They can only be removed implicitly by dropping another object.
To remove a cluster index for a table in a partitioned table space, drop the associated partitioned table space.
To remove a unique index defined on a ROWID column with the GENERATED BY DEFAULT attribute, drop the associated table.
SQLCODE: -00667 Database: DB2 QMF Function: PQ
This table has an edit procedure: you cannot ALTER.
If a table has an edit procedure, no columns can be added to it. The ALTER statement was not executed.
Be sure that the correct table was specified in the ALTER statement. Do not attempt to ALTER the definition of a table that has an installation-written edit procedure.
SQLCODE: -00668 Database: DB2 QMF Function: PQ
You cannot use DROP with this table.
The table you want to drop is in a partitioned tablespace. In order to drop such a table, you must drop the entire tablespace.
Do not attempt this operation.
SQLCODE: -00669 Database: DB2 QMF Function: PQ
Rows are longer than tablespace page size.
The length of the rows in a table cannot exceed the page size of the tablespace containing the table.
For CREATE TABLE, either ...
For ALTER TABLE, reduce the width of the new column. If the table already has the maximum row length, no new column can be added.
SQLCODE: -00670 Database: DB2 QMF Function: PQ
ALTER TABLESPACE cannot change the page size.
The attempted change to the bufferpool value would change the page size of the tablespace, from 4K to 32K or from 32K to 4K.
If the tablespace uses one of the 4K bufferpools (BP0, BP1, or BP2), it may be re-assigned to one of the other 4K bufferpools. (If it is assigned to BP32K, it cannot be altered.)
SQLCODE: -00671 Database: DB2 QMF Function: PQ
32K bufferpools cannot be used for indexes.
Your CREATE INDEX query named a bufferpool with a page size of 32K. Only the 4K bufferpools BP0, BP1, and BP2 can be used for indexes.
Name a different bufferpool.
SQLCODE: -00676 Database: DB2 QMF Function: PQ
Not enough storage to expand bufferpools.
Several situations could cause this message:
Contact your QMF administrator.
SQLCODE: -00677 Database: DB2 QMF Function: PQ
Value for limit-key doesn't match column &V3..
The limit-key value given for column &V3 does not have the same data type as the column.
If the value should have a character data type, enclose it in single quotes.
SQLCODE: -00678 Database: DB2 QMF Function: PQ
Your table or view contains too many columns.
Your query would create a table or view with more than the maximum number of columns allowed.
Change your query so that the number of columns in the table or view you are creating will not exceed the database limit.
SQLCODE: -00680 Database: DB2 QMF Function: PQ
Column &V1 violates installation defined field procedure. RT: &V2, RS: &V3, MSG: &V4..
A field procedure error has occurred on column &V1. Use return code (RT) to determine the problem:
4 Invalid value on encode or decode or
invalid column definition.
8 Invalid parameter value.
12 Field procedure error on any
function.Use reason code (RS) and message (MSG) token for additional information.
If it is not a field procedure error, determine the requirements imposed by the field procedure. If it is a field procedure error, examine the field procedure.
SQLCODE: -00681 Database: DB2 QMF Function: PQ
FIELDPROC, SBCS, BIT or MIXED data cannot be used on column &V1..
Either FIELDPROC, SBCS, BIT or MIXED data was specified on column &V1. This is invalid because these data types cannot be specified for a numeric, date, time, long string, or non-null default value column.
Correct the SQL statement and rerun the query.
SQLCODE: -00683 Database: DB2 QMF Function: PQ
The length of the parameter list beginning &V1 is too long.
FIELDPROC program-name (parameter list)
The parameter list is optional for FIELDPROC. The number of parameters and data type of each are determined by the field procedure. The maximum length of the parameter list is 254 bytes, including commas but excluding insignificant blanks and the delimiting parentheses.
Correct the SQL statement and run the query again.
SQLCODE: -00684 Database: DB2 QMF Function: PQ
A column defined with a field procedure cannot be compared to another column with a different field procedure.
If a column with a field procedure is compared to another column, the two columns must have the same field procedure.
Correct the SQL statement and run the query again.
SQLCODE: -00686 Database: DB2 QMF Function: PQ
Column field types incomparable.
If a column with a field procedure is compared to another column, they must have the same field procedure and same field type. The comparison is performed on the encoded form of the values in the columns. For example, if the encoded values are numeric, their data types must be identical; if they are strings, their data types must be compatible.
Correct the SQL statement and run the query again.
SQLCODE: -00687 Database: DB2 QMF Function: PQ
Database &V1 is not a shared database on the owning subsystem.
You are trying to access an object in the database identified by &V1. That database is defined as ROSHARE READ on the subsystem that you are accessing. However, the database is not defined as ROSHARE OWNER on the owning subsystem. Therefore, the object cannot be accessed.
Verify that the correct object was specified.
SQLCODE: -00735 Database: DB2 QMF Function: PQ
The definition for the table is incomplete.
An attempt was made to access or reference a table with one or more LOB columns, however, one of the following conditions exist.
Perform as many of the steps listed below as needed.
Run the query again.
SQLCODE: -00747 Database: DB2 QMF Function: PQ
DB2 auxiliary table cannot be referenced directly.
Data in an auxiliary table cannot be accessed by specifying the auxiliary table name. Data in an auxiliary table can only be accessed through operations on the base table.
Use the corresponding base table and re-run the query.
SQLCODE: -00766 Database: DB2 QMF Function: PQ
Division by zero was attempted.
The processing of a column or arithmetic expression resulted in division by zero.
Correct the statement and run the query again.
SQLCODE: -00801 Database: DB2 QMF Function: PQ
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: DB2 QMF Function: PQ
Duplicate value in a unique index column.
One of the columns into which you are inserting or updating a new value contains that same value already. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values.
Change the value so that it does not duplicate a value already existing. Run your query again.
SQLCODE: -00803 Database: DB2 QMF Function: PQ
A program is not found in the current plan.
QMF executed the application plan &V2, which needs the program &V1..
If you are accessing remote data, the name of your plan may have been changed to DISTSERV.
This program was not found in the plan &V2.. The following are some causes of this error:
Refer to the DB2 Messages and Codes manual for a detailed explanation and report this problem to your QMF administrator.
SQLCODE: -00805 Database: DB2 QMF Function: PQ
A subquery produces more than one value.
A subquery should not produce values from more than one column of a table; in many cases it should not produce values from more than one row. Use ALL, ANY, EXISTS, or IN with a subquery that produces more than one value.
Examples: WHERE DEPT = ANY (SELECT DEPTNUMB FROM Q.ORG) HAVING AVG(X) > ALL (SELECT X FROM Y) WHERE EXISTS (SELECT * FROM X WHERE N1 = N2)
Change your query and run it again.
SQLCODE: -00811 Database: DB2 QMF Function: PQ
A subquery using a GROUP BY or HAVING clause needs ALL, ANY, EXISTS, or IN.
A subquery that uses a GROUP BY or HAVING clause can be expected to produce more than one value. It should be preceded by one of the keywords ALL, ANY, EXISTS, or IN.
Change the query and run the query again.
SQLCODE: -00815 Database: DB2 QMF Function: PQ
Your Prompted Query is too complex for the database.
An internal QMF query needed to build or run the Prompted Query failed. This situation can occur if the internal query was too long or too complex, or if the total number of columns for all tables used exceeded a database limit. Your query cannot be completed or run using Prompted Query.
Shorten your query or rewrite it as more than one query.
SQLCODE: -00840 Database: DB2 QMF Function: PQ
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00900 Database: DB2 QMF Function: PQ
Unsuccessful execution caused by an unavailable resource. Reason code &V1, type of resource &V2, and resource name &V3..
The request could not be executed because the resource '&V3' of type '&V2' was not available at this time for the reason indicated by '&V1'. See DB2 Messages and Codes manual for a detailed explanation of the reason code &V1..
This may be a temporary condition.
Some common causes for this condition are:
If you have access to the MVS JES log information, browse the log records for this unavailable resource error.
If you need to refer to a local object, but you are currently connected to a remote location, you can connect to the local location and then reference the local object.
If the resource is temporarily unavailable, issue your query again.
If DDF is stopped and the Lost Connection prompt is displayed, you may only be able to reconnect to the local DB2.
If the error condition persists, contact your QMF administrator for assistance.
SQLCODE: -00904 Database: DB2 QMF Function: PQ
Unsuccessful execution because DB2 resource limit was exceeded. Resource name = &V1., limit = &V2..
The execution of the SQL statement was terminated because a DB2 resource limit was exceeded.
To avoid exceeding the DB2 resource limit, consider simplifying the SQL statement, restructuring the tables and indexes, or changing the resource limits. For further assistance, contact your QMF administrator.
SQLCODE: -00905 Database: DB2 QMF Function: PQ
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00911 Database: DB2 QMF Function: PQ
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00913 Database: DB2 QMF Function: PQ
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00918 Database: DB2 QMF Function: PQ
There is not enough storage available to process the statement.
A request was made to the database manager that required another memory page but no more pages are available to the database manager. Some possible causes are:
Correct the problem and run the query again.
SQLCODE: -00930 Database: DB2 QMF Function: PQ
You cannot access remote data while DDF is inactive.
Your query attempted to access data at the remote database, but Distributed Data Facility is not started. Your query is rolled back.
You may continue using QMF. If the problem persists, contact your QMF administrator.
SQLCODE: -00948 Database: DB2 QMF Function: PQ
See DSQ31649
Follow the directions in the referenced message.
Character "&V1" in your query is invalid.
Your query cannot be processed because something is wrong with the character "&V1". It could be misplaced or invalid in the context in which it is being used.
Remove "&V1" or change it to a valid character.
SQLCODE: -00007 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The statement is not valid in this database manager.
The statement you just attempted to execute is not valid in DB2, though it may be valid with other database manager programs. A full list of SQL statements and options that are not allowed in DB2 is contained in the DB2 Reference Manual.
Use only DB2 statements while using this database manager.
SQLCODE: -00084 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Your SEARCH request contains too many columns or values.
Your search request could not be completed because:
Create a view which contains only those columns which you need to update, or specify fewer values for your search criteria.
SQLCODE: -00101 Database: DB2 QMF Function: Table Edit
Constant beginning '&V3.' &V1. is too long.
Reference line: ==>&V2.
The constant is longer than the maximum allowed. A character constant must be enclosed in quotes. If you omit a closing quote, your data could exceed the maximum length. Normally, character string length is 254 characters or 124 graphic characters if you use double byte character set; CURRENT SQLID value is 8 characters and CURRENT DEGREE value is 3 characters.
Correct the constant and run the query again.
SQLCODE: -00102 Database: DB2 QMF Function: Table Edit
&V3.&V1. is not a valid number.
Reference line: ==>&V2.
&V3. starts with a digit, but is not a valid integer, decimal, or floating-point number. If it is meant to be a:
Change &V3. and run the query again.
SQLCODE: -00103 Database: DB2 QMF Function: Table Edit
Incorrect usage of &V1 or &V2..
Some possibilities are:
Make the correction and continue.
SQLCODE: -00104 Database: DB2 QMF Function: Table Edit
The statement contains an invalid string.
The statement contains an invalid string. Only a character string or a graphic string is valid.
Specify the correct format of string. For graphic data check for paired delimiters, the character G, and an even number of bytes within the string.
SQLCODE: -00105 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Name starting '&V3.' &V1. is over &V4. characters long.
Reference line: ==>&V2.
If this name specifies a column, table, view, index, alias, synonym, collection ID, or check constraint it should not exceed 18 characters. For DB2/400, the collection ID should not exceed 10 characters.
If this name specifies a location, it should not exceed 16 characters.
If this name specifies a table, view qualifier, database, table space, storage group, bufferpool, referential constraint specified in the CREATE or ALTER TABLE statements, or package ID, it should not exceed 8 characters.
Specify a shorter name and continue to use QMF.
SQLCODE: -00107 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Name &V3.&V1. contains an invalid character.
Reference line: ==>&V2.
The names for databases, storage groups, tablespaces, and bufferpools can contain only upper-case alphabetic, national (*, &, or @), or numeric characters. The first character must be alphabetic or a national character.
Correct the invalid character in name &V3. and run the query again.
SQLCODE: -00113 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The number of values doesn't match the number of columns.
In a statement like INSERT INTO Q.STAFF, you must provide a value for every column that was defined as NOT NULL.
If you do not give a list of columns after the table name, then give a value for every column in the table, after VALUES.
If you do give a list of columns after the table name, then give a value for every column in that list, after VALUES.
Example:
INSERT INTO Q.STAFF (ID, NAME, DEPT)
VALUES (400, 'HARRISON', 20)Provide a value for each column you want to INSERT INTO and run the query again.
SQLCODE: -00117 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00150 Database: DB2 QMF Function: Table Edit
Column &V1 cannot be changed.
You cannot use INSERT, UPDATE, or DELETE (in SQL) or I., U., or D. (in QBE) to change a column in:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00151 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Insert or update value does not satisfy view definition.
WITH CHECK OPTION was used in the definition of the view whose data you are trying to change. All attempts to insert or update rows in the view are checked to make sure that the results will conform to the definition of the view. Some value in your query does not satisfy a condition in that definition.
Examine the definition of the view to determine why the change was rejected, and change the value in the query.
SQLCODE: -00161 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
You cannot create a view in another user's name.
Your query attempted to create a view with a qualified name (a name of the form USERID.TABLENAME), and the qualifier of the name was not your own DB2 authorization ID. You can only create a view using an authorization ID other than your own if you have "SYSADM" authority.
Correct the query and run it again or obtain the authorization needed to create a view for someone else.
SQLCODE: -00164 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The datetime value &V1 is invalid.
The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
Correct the syntax for the datetime value and run the query again.
SQLCODE: -00180 Database: DB2 QMF Function: Table Edit
The datetime value is not a valid value.
The string representation of a datetime value contains a value which is out of range. The proper ranges for datetime values are as follows:
Years - 1 to 9999 Months - 1 to 12 Days - 1 to 31 Hours - 0 to 24 Minutes - 0 to 59 Seconds - 0 to 59
Correct the datetime value and run the query again.
SQLCODE: -00181 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The query is empty or contains only comments.
An empty query, or one containing only comments, contains no instructions to do anything. It cannot be run.
Write another query.
SQLCODE: -00198 Database: DB2 QMF Function: Table Edit
SQL error at or before &V3. &V1..
Reference line: ==>&V2.
Some common errors that produce this message are:
The line below lists one or more symbols that might have been correct, based on the context so far, though they might not all work with the whole query.
The list of alternate symbols are only suggestions. Some of the symbols might not be legal statements for the database manager being used. Those symbols might be correct for statements sent to other database management systems. &V4.
Correct the query and run it again.
SQLCODE: -00199 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Column &V1 is in more than one table.
An unqualified column name is ambiguous if more than one table or view in the FROM clause has a column with that name, or if more than one column of a nested table expression has that name. A qualified column name is ambiguous only if the correlation name for the column name and for a nested table expression is not unique.
If the problem is caused by a non-unique column name in a nested table expression, change the nested table expression so that the column is unique. If the problem is caused by the use of an unqualified name, qualify it with a table, view or correlation name.
SQLCODE: -00203 Database: DB2 QMF Function: Table Edit
&V1 could not be found.
The query refers to &V1.. Nothing with this name exists in the database.
Check for a spelling error.
SQLCODE: -00204 Database: DB2 QMF Function: Table Edit
&V1 is not a column defined in a selected table.
&V1 has been specified as a column, and it could not be found in any of the tables you selected. You may have misspelled the name. If &V1 is intended to be a character constant, enclose it in single quotes.
You can use the command DISPLAY Q.COLUMN_LIST to display a table of information about all the columns in tables you are authorized to use. Verify the spelling of the column name, and then correct the column name or add the table containing column &V1 to the query.
SQLCODE: -00205 Database: DB2 QMF Function: Table Edit
Column &V1 is not in any table named in the query.
&V1 is not a column in any table or view named in the query. If it is intended to be a character constant, enclose it in single quotes.
Change the column name or add the table containing column &V1 to the query, and run the query again.
SQLCODE: -00206 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The location qualifier cannot be used.
The name you specified has a location qualifier. A three-part object name cannot be used until the local location name is defined.
Remove the location qualifier and retry your query. See your QMF administrator to make sure you are using the correct database, or to define the local location name.
SQLCODE: -00250 Database: DB2 QMF Function: Table Edit
&V2 is not a valid location name.
One of the following has occurred:
Correct the location name and try again.
SQLCODE: -00251 Database: DB2 QMF Function: Table Edit
Function is not supported (reason code = &V1).
The statement cannot be processed because it violates a restriction as indicated by the following reason codes:
The action corresponding to the reason code is:
SQLCODE: -00270 Database: DB2 QMF Function: Table Edit
A character string could not be converted due to undefined CCSIDs.
Your SQL statement referenced a character string with a coded character set ID(CCSID) &V1 in a coded character set that differs from the current one. To use this character string at the current server, this character string must be translated from the source CCSID &V1 to the target CCSID &V2. However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Verify that the character columns and values you referenced are correct. If not, make the necessary change and try the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Invalid data type in position &V1..
Some SQL data types are not supported by the application requester. &V1 is the position of the first element with an invalid data type in the SQLDA. A common cause for this error is that the application requester has attempted to describe large object data residing at the application server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB, and DBLOB.
Remove the invalid data types and run the query again.
SQLCODE: -00351 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
A ROWID column has an invalid value.
An attempt to insert an invalid value into a ROWID column was made.
Only ROWID values previously generated by DB2 can be used as values for insertion into a ROWID column. Alternatively, insert the row specifying the keyword DEFAULT for the ROWID column value or remove the ROWID column from the insert column-list.
SQLCODE: -00399 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Value given is too long for column &V1..
The maximum width of column &V1 is less than the number of characters you are trying to put into it.
Change the value to fit the column and run the query again.
SQLCODE: -00404 Database: DB2 QMF Function: Table Edit
Numeric value &V3.&V1. is outside the allowable range for your column.
Reference line: ==>&V2.
&V3. is outside the range of values allowed for the associated column. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT .... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .. -2147483648 to 2147483647
SMALLINT . -32768 to 32767
DECIMAL .. The range depends on the
precision and scale of the
column. For example, if
the value is being specified
for a decimal column defined
with precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value and rerun the query.
SQLCODE: -00405 Database: DB2 QMF Function: Table Edit
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of the
column. For example, if
the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun the query.
SQLCODE: -00406 Database: DB2 QMF Function: Table Edit
Column &V1 cannot contain a NULL value.
The update or insert value for column &V1 was NULL. But column &V1 was made NOT NULL in the table definition. If you are inserting a row, the failure to specify a value for a column implies that you want to insert NULL in it.
Enter a value for column &V1..
SQLCODE: -00407 Database: DB2 QMF Function: Table Edit
New value has wrong data type for column &V1..
The data type of the new value in column &V1 does not agree with the data type of the column. Both must be numbers, character strings, graphic strings, dates, times, or time stamps.
Enter some other value for column &V1 and run the query again.
SQLCODE: -00408 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Value starting '&V1' is longer than 30 characters.
A floating-point constant cannot be more than 30 characters long.
Round &V1 so that it can be written with 30 characters or fewer.
SQLCODE: -00410 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
Arithmetic overflow during change of data type.
The result of an arithmetic or insert operation is not valid because arithmetic overflow occurred. For example, you may have tried to INSERT values with a data type of INTEGER into a column with data type of SMALLINT. Conversion is possible so long as the INTEGER values are small enough. But a value larger than 32767 will cause arithmetic overflow.
Change your operation and run the query again.
SQLCODE: -00413 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
This query exceeds a DB2 cost estimate limit.
DB2 has determined that the cost estimate for this query exceeds a limit specified in the Resource Limit Facility (DB2 governor) preventing the query from being run.
The details of the cost estimate for the query statement are:
If the cost category value is 'B', seek the assistant of your DB2 administrator, the DB2 catalog statistics or resource limit specification tables (RLST) might need updating.
If the SQL statement is consuming too much processor time, rewrite the statement to perform more efficiently and run the query again.
Things to check might be:
Some queries can be made simpler by removing the GROUP BY clause from the query and using the GROUP usage code in the QMF FORM instead.
Some queries will perform better by using advanced SQL syntax, such as Outer Join or the CASE expression,
For advanced analysis the EXPLAIN SQL statement can be used to gather information about the structure and execution performance of a query.
Refer to the SQL Reference for more information on Queries and the EXPLAIN statement.
Refer to the DB2 Administration manual for more information on tuning queries and writing efficient predicates and subqueries.
SQLCODE: -00495 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00511 Database: DB2 QMF Function: Table Edit
The query reference to a remote object is invalid.
One of the following invalid conditions exists:
Refer to the DB2 SQL Reference manual for more information on using remote objects.
SQLCODE: -00512 Database: DB2 QMF Function: Table Edit
The alias name &V1 cannot be defined on another local or remote alias.
The object indicated by &V1 exist at the location indicated. However, It is defined as an alias at at that location.
Modify the query to ensure that all object references are to tables or views at the indicated location.
SQLCODE: -00513 Database: DB2 QMF Function: Table Edit
See DSQ31649
Follow the directions in the referenced message.
The foreign key value is not valid.
An update or insert query specified a value for a foreign key. However, the value is not equal to any of the primary key values of the parent table.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Use a value for the foreign key that matches one of the primary key values.
SQLCODE: -00530 Database: DB2 QMF Function: Table Edit
The primary key &V1 in a parent row cannot be updated.
Your update request specifies a value for the primary key of the table being updated, but the row identified by that primary key value has dependent rows associated with it. The value of a primary key in a parent row cannot be updated if the parent row has any dependent rows.
Make sure you selected the correct row to be updated. Before a primary key value in a parent row can be updated, the parent row must not have any dependent rows.
SQLCODE: -00531 Database: DB2 QMF Function: Table Edit
The row cannot be deleted because of a RESTRICT delete rule.
The delete operation attempted to delete a parent row. However, the row cannot be deleted because a delete rule of RESTRICT is associated with tables that can be affected by this deletion. Either the row has a dependent in a relationship with a delete rule of RESTRICT, or the deletion cascades to a row that is a dependent in a relationship with a delete rule of RESTRICT.
Make sure you selected the correct row to be deleted. If you did, delete any dependent rows with a delete rule of RESTRICT. Then delete the parent row.
SQLCODE: -00532 Database: DB2 QMF Function: Table Edit
Non end-user SQLCODE returned from DBM.
The computer has detected an internal SQL error. The error code is shown at the bottom of this panel.
Report the error following your installation's procedures and check if your command executed correctly. You may continue to use QMF.
The primary key in the table cannot be updated.
The table you are editing contains a primary key. Columns that are part of a primary key cannot be updated or deleted using the Table Editor.
Create or use a view that contains only the columns you need updated. Do not include any columns that are part of a primary key. If you want to update the primary key, you can do it using SQL or QBE, provided that the primary key does not have any dependant rows.
SQLCODE: -00535 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Table &V1 has no primary index for the primary key.
You cannot use table &V1.. It has a primary key, but no primary index.
Define a primary index for the table before you refer to it.
SQLCODE: -00540 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
You do not have the authority to do this.
The authority you need depends on what you are doing:
See your QMF administrator to obtain the necessary authorization.
SQLCODE: -00551 Database: DB2 QMF Function: Table Edit
The specified object does not exist, or you lack needed authority.
The specified object does not exist, or it's a read-only view, or you lack some needed authority, as follows:
If you misnamed an existing object, use the correct name. If you lack needed authority, contact your QMF administrator.
SQLCODE: -00552 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
You cannot grant a privilege to yourself.
Privileges can only be granted from one user with the proper authority to another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you need additional privileges.
SQLCODE: -00554 Database: DB2 QMF Function: Table Edit
You cannot revoke a privilege from yourself.
Privileges can only be revoked by one user with the proper authority from another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you want any database privileges reduced.
SQLCODE: -00555 Database: DB2 QMF Function: Table Edit
You cannot revoke this privilege from &V1..
Either &V1 does not have the privilege you are trying to revoke, or it was granted by a user with a different authorization identifier from yours. You can revoke only privileges granted under your authorization identifier.
Proceed to another operation.
SQLCODE: -00556 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
GRANT and REVOKE cannot be run now.
The authorization portion of the system is temporarily disabled. GRANT and REVOKE queries cannot be run.
Run your query again when the authorization portion of the system is running. Contact your QMF administrator for more details.
SQLCODE: -00559 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Remote update is disallowed in a READ-ONLY environment.
You have attempted to update, insert or delete data at a remote location, but your current operating environment allows remote read only. For example, you cannot update remote data in a CICS operating environment if server database does not support two-phase commit.
To access remote data in a READ-ONLY operating environment, you can use one of the following:
You can continue to use QMF. If you need to update remote data, switch to an operating environment that supports it; otherwise, contact your QMF administrator.
SQLCODE: -00571 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
&V1 is the name of an existing &V2..
You tried to CREATE an object named &V1 when a &V2 of that name already exists.
Either DROP &V2 &V1 before running the query, or choose another name for &V1..
SQLCODE: -00601 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
You used a constant that exceeds maximum width allowed.
You specifies a constant that has a length, precision, or scale outside the data type limit. Some possible causes of the error are:
Change the constant specification to conform to the data type limit and run your query again. See the SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00604 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
&V1 cannot be used with this catalog object.
You cannot use INSERT, UPDATE, or DELETE with the catalog object specified in the SQL statement. You cannot use the DEFER YES option for indexes on catalog tables SYSINDEXES, SYSKEYS, and SYSINDEXPART.
Do not attempt this operation.
SQLCODE: -00607 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
You cannot drop &V2; other objects depend on it.
&V2 cannot be dropped because the &V3 named &V4 refers to it.
If you want to drop &V2, first drop all objects that depend on it.
SQLCODE: -00616 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
&V1 cannot be performed on system databases.
System databases cannot be the object of certain types of operations, including &V1..
Do not attempt this operation.
SQLCODE: -00618 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Invalid value for &V1 in &V2 query.
The value given for &V1 in the &V2 query is not a permitted value.
Refer to the SQL Help for information about allowable values for &V1 in &V2 queries.
SQLCODE: -00644 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Table space &V2 already contains a table.
Table space &V2, named in the CREATE TABLE query, is a partitioned or default table space that already contains an existing table. Only one table can be contained in a partitioned or default table space.
Be sure you used the correct table space in the query. Do not attempt to create more than one table in a partitioned or default table space.
SQLCODE: -00646 Database: DB2 QMF Function: Table Edit
Bufferpool &V1 must be activated.
Bufferpool &V1, named in your CREATE or ALTER query for a table space or index space, is not activated. The bufferpool has NUMPAGES = 0.
Table spaces and index spaces can only be assigned (or re-assigned) to bufferpools currently activated.
Be sure that the proper bufferpool was named in the create or alter statement. If it was, activate the bufferpool and execute the statement again.
SQLCODE: -00647 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Procedure &V1 rejects the result.
&V1 is a procedure defined by your installation to edit or validate the results of queries. The result of your query did not meet some requirement of this procedure.
See your QMF administrator for descriptions of your installation's edit and validation procedures.
SQLCODE: -00652 Database: DB2 QMF Function: Table Edit
Table &V1 has no partitioned index.
A partitioned table (a table in a partitioned tablespace) cannot be referenced until the CLUSTER index for that table has been created. Table &V1 has no CLUSTER index.
Be sure that the correct table was specified in the statement. If it was, create a CLUSTER index for that table and execute your statement again.
SQLCODE: -00653 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
The maximum size of a table object has been exceeded.
One or more of the objects that make up a table has reached its maximum size. The storage objects that make up a table are:
Once a storage object has grown to its maximum size, it cannot be extended further.
To make existing space within the object available to store new data, you can:
SQLCODE: -00659 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
&V1 is not partitioned.
Your CREATE INDEX query contains PART specifications, but tablespace &V1 is not a partitioned tablespace.
Be sure that the proper table is specified in the statement. If it was, the table must be partitioned before a partitioned index can be created.
SQLCODE: -00662 Database: DB2 QMF Function: Table Edit
Wrong number of key limit values for &V1..
The number of limit-key-values in at least one PART specification is either zero or greater than the number of columns in the index key.
Change the number of limit-key-values and continue.
SQLCODE: -00663 Database: DB2 QMF Function: Table Edit
Limit-key fields of index &V1 are too long.
The total length of the keys for a partitioned index may not exceed 40 bytes internally.
Reduce the total number of columns used in key fields of your index.
SQLCODE: -00664 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
A utility, the Resource Limit Facility, or the Distributed Data Facility is running.
If a system utility is running, it must complete execution before your query can be run. If the Resource Limit Facility is running, it must be stopped or switched to a different resource limit control table before your query can be run. If the Distributed Data Facility is running, it must be stopped before an object in the communications database can be dropped.
Wait for the utility to finish, or wait until the Resource Limit Facility stops or switches to a different resource limit control table, then run your query again. Or wait until the Distributed Data Facility stops, then drop the object.
SQLCODE: -00666 Database: DB2 QMF Function: Table Edit
The index cannot be removed by the DROP INDEX statement.
The DROP INDEX statement attempted to drop one of the following indexes:
Neither of these indexes can be explicitly dropped. They can only be removed implicitly by dropping another object.
To remove a cluster index for a table in a partitioned table space, drop the associated partitioned table space.
To remove a unique index defined on a ROWID column with the GENERATED BY DEFAULT attribute, drop the associated table.
SQLCODE: -00667 Database: DB2 QMF Function: Table Edit
This table has an edit procedure: you cannot ALTER.
If a table has an edit procedure, no columns can be added to it. The ALTER statement was not executed.
Be sure that the correct table was specified in the ALTER statement. Do not attempt to ALTER the definition of a table that has an installation-written edit procedure.
SQLCODE: -00668 Database: DB2 QMF Function: Table Edit
You cannot use DROP with this table.
The table you want to drop is in a partitioned tablespace. In order to drop such a table, you must drop the entire tablespace.
Do not attempt this operation.
SQLCODE: -00669 Database: DB2 QMF Function: Table Edit
Rows are longer than tablespace page size.
The length of the rows in a table cannot exceed the page size of the tablespace containing the table.
For CREATE TABLE, either ...
For ALTER TABLE, reduce the width of the new column. If the table already has the maximum row length, no new column can be added.
SQLCODE: -00670 Database: DB2 QMF Function: Table Edit
ALTER TABLESPACE cannot change the page size.
The attempted change to the bufferpool value would change the page size of the tablespace, from 4K to 32K or from 32K to 4K.
If the tablespace uses one of the 4K bufferpools (BP0, BP1, or BP2), it may be re-assigned to one of the other 4K bufferpools. (If it is assigned to BP32K, it cannot be altered.)
SQLCODE: -00671 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
32K bufferpools cannot be used for indexes.
Your CREATE INDEX query named a bufferpool with a page size of 32K. Only the 4K bufferpools BP0, BP1, and BP2 can be used for indexes.
Name a different bufferpool.
SQLCODE: -00676 Database: DB2 QMF Function: Table Edit
Not enough storage to expand bufferpools.
Several situations could cause this message:
Contact your QMF administrator.
SQLCODE: -00677 Database: DB2 QMF Function: Table Edit
Value for limit-key doesn't match column &V3..
The limit-key value given for column &V3 does not have the same data type as the column.
If the value should have a character data type, enclose it in single quotes.
SQLCODE: -00678 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Your table or view contains too many columns.
Your query would create a table or view with more than the maximum number of columns allowed.
Change your query so that the number of columns in the table or view you are creating will not exceed the database limit.
SQLCODE: -00680 Database: DB2 QMF Function: Table Edit
Column &V1 violates installation defined field procedure. RT: &V2, RS: &V3, MSG: &V4..
A field procedure error has occurred on column &V1. Use return code (RT) to determine the problem:
4 Invalid value on encode or decode or
invalid column definition.
8 Invalid parameter value.
12 Field procedure error on any
function.Use reason code (RS) and message (MSG) token for additional information.
If it is not a field procedure error, determine the requirements imposed by the field procedure. If it is a field procedure error, examine the field procedure.
SQLCODE: -00681 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
FIELDPROC, SBCS, BIT or MIXED data cannot be used on column &V1..
Either FIELDPROC, SBCS, BIT or MIXED data was specified on column &V1. This is invalid because these data types cannot be specified for a numeric, date, time, long string, or non-null default value column.
Correct the SQL statement and rerun the query.
SQLCODE: -00683 Database: DB2 QMF Function: Table Edit
The length of the parameter list beginning &V1 is too long.
FIELDPROC program-name (parameter list)
The parameter list is optional for FIELDPROC. The number of parameters and data type of each are determined by the field procedure. The maximum length of the parameter list is 254 bytes, including commas but excluding insignificant blanks and the delimiting parentheses.
Correct the SQL statement and run the query again.
SQLCODE: -00684 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Database &V1 is not a shared database on the owning subsystem.
You are trying to access an object in the database identified by &V1. That database is defined as ROSHARE READ on the subsystem that you are accessing. However, the database is not defined as ROSHARE OWNER on the owning subsystem. Therefore, the object cannot be accessed.
Verify that the correct object was specified.
SQLCODE: -00735 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
The definition for the table is incomplete.
An attempt was made to access or reference a table with one or more LOB columns, however, one of the following conditions exist:
Perform as many of the steps listed below as needed.
Run the query again.
SQLCODE: -00747 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
DB2 auxiliary table cannot be referenced directly.
Data in an auxiliary table cannot be accessed by specifying the auxiliary table name. Data in an auxiliary table can only be accessed through operations on the base table.
Use the corresponding base table and re-run the query.
SQLCODE: -00766 Database: DB2 QMF Function: Table Edit
Attempted to insert a value into ROWID GENERATED ALWAYS column.
When inserting into a table, a value was specified for a ROWID GENERATED ALWAYS column &V1.. GENERATED ALWAYS columns should not be specified in the column-list for an insertion unless the corresponding entry in the VALUES list is DEFAULT.
Remove the ROWID column from the column-list or specify DEFAULT for the ROWID identifier column in the VALUES clause.
SQLCODE: -00798 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Division by zero was attempted.
The processing of a column or arithmetic expression resulted in division by zero.
Correct the statement and run the query again.
SQLCODE: -00801 Database: DB2 QMF Function: Table Edit
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: DB2 QMF Function: Table Edit
Duplicate value in a unique index column.
One of the columns into which you are inserting or updating a new value contains that same value already. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values.
Change the value so that it does not duplicate a value already existing. Run your query again.
SQLCODE: -00803 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
A program is not found in the current plan.
QMF executed the application plan &V2, which needs the program &V1..
If you are accessing remote data, the name of your plan may have been changed to DISTSERV.
This program was not found in the plan &V2.. The following are some causes of this error:
Refer to the DB2 Messages and Codes manual for a detailed explanation and report this problem to your QMF administrator.
SQLCODE: -00805 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Remote update is disallowed in a READ-ONLY environment.
You have attempted to update, insert or delete data at a remote location, but your current operating environment allows remote read only. For example, you cannot update remote data in a CICS operating environment if server database does not support 2-phase commit.
To access remote data in a READ-ONLY operating environment, you can use one of the following:
You can continue to use QMF. If you need to update remote data, switch to an operating environment that supports it; otherwise, contact your QMF administrator.
SQLCODE: -00817 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Your query uses too many columns.
You cannot select or insert more than the maximum number of columns allowed by the database from any table or set of tables in a single query.
Rewrite the query to use fewer columns. If the query is in SQL, check statements like "SELECT * FROM A, B, C", which selects every column from each of tables A, B, and C.
SQLCODE: -00840 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00900 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Unsuccessful execution caused by an unavailable resource. Reason code &V1, type of resource &V2, and resource name &V3..
The request could not be executed because the resource '&V3' of type '&V2' was not available at this time for the reason indicated by '&V1'. See DB2 Messages and Codes manual for a detailed explanation of the reason code &V1..
This may be a temporary condition.
Some common causes for this condition are:
If you have access to the MVS JES log information, browse the log records for this unavailable resource error.
If you need to refer to a local object, but you are currently connected to a remote location, you can connect to the local location and then reference the local object.
If the resource is temporarily unavailable, issue your query again.
If DDF is stopped and the Lost Connection prompt is displayed, you may only be able to reconnect to the local DB2.
If the error condition persists, contact your QMF administrator for assistance.
SQLCODE: -00904 Database: DB2 QMF Function: Table Edit
Unsuccessful execution because DB2 resource limit was exceeded. Resource name = &V1., limit = &V2..
The execution of the SQL statement was terminated because a DB2 resource limit was exceeded.
To avoid exceeding the DB2 resource limit, consider simplifying the SQL statement, restructuring the tables and indexes, or changing the resource limits. For further assistance, contact your QMF administrator.
SQLCODE: -00905 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Unable to determine if the updates made at a remote location were successful or not.
A system error occurred at the remote location where the updates were made, or a communication failure with the remote location occurred. The error occurred after the request to commit the updates was sent to the remote location. The error prevents DB2 from determining whether or not the commit operation succeeded. If the commit succeeded, updates will appear in the database. If the commit failed, the updates will have been backed out.
After communication has been reestablished with the remote location, query the data to determine whether or not the commit operation was successful.
SQLCODE: -00907 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Sorry, your database changes have been lost.
Due to excessive locking or a locking conflict, the database manager has cancelled your database changes. Any additions, updates, or deletions to the table being edited have been lost.
End your Table Editor session and redo your changes at a later time.
SQLCODE: -00911 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
Sorry, your database changes have been lost.
Due to excessive locking or a locking conflict, the database manager has cancelled your database changes. Any additions, updates, or deletions to the table being edited have been lost.
End your Table Editor session and redo your changes at a later time.
SQLCODE: -00913 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00918 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
There is not enough storage available to process the statement.
A request was made to the database manager that required another memory page but no more pages are available to the database manager. Some possible causes are:
Correct the problem and run the query again.
SQLCODE: -00930 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.
You cannot access remote data while DDF is inactive.
Your query attempted to access data at the remote database, but Distributed Data Facility is not started. Your query is rolled back.
You may continue using QMF. If problem persists, contact your QMF administrator.
SQLCODE: -00948 Database: DB2 QMF Function: Table Edit
See DSQ36533
Follow the directions in the referenced message.