historical error codes

Phase 2 historical error codes contains the INFORMIX¹ error codes most likely to be displayed for CMS historical reports. Each code includes a description of the error and the recommended corrective action.

These errors are reported in the following format:

INFORMIX error: <error number>

In addition, a circumflex (^) may be displayed in the listed Select statements to mark the location of an error.

Note:

If an error code is displayed that is not listed in this document, see the INFORMIX SQL Relational Database Management System Reference Guide for INFORMIX SQL Version 4.10.

Phase 2 historical error codes

Message: keyword SUM invalid in where clause.

Cause: You used the keyword SUM in row search criteria.

Solution: Remove the keyword SUM from the row search criteria.

Message: keyword SYN invalid in where clause.

Cause: You used the keyword SYN in row search criteria.

Solution: Remove the keyword SYN from the row search criteria.

1 INFORMIX is a registered trademark of Informix Software, Inc.

—201 Description: A syntax error has occurred.

Solution: Check that you have not misspelled an RDSQL statement, placed key words out of sequence, or included an INFORMIX-SQL reserved word in your query.

—202 Description: An illegal character has been found in the statement.

Solution: Remove the illegal character (often a

nonprintable control character) and resubmit the statement

Test Design Error Messages

—203 Description: An illegal integer has been found in the statement.

Solution: Integers must be whole numbers from

-2,147483,647 to +2,147,483,647. Verify that you have not included a number with a fractional portion or a number outside the acceptable range. Verify also that you have not inadvertently entered a letter in place of a number (for example, 125p3 instead of 12503).

—204 Description: An illegal floating-point number has been found in the statement.

Solution: Verify that you have not inadvertently entered a letter in place of a number (for example, 125p3 instead of 125.03).

—206 Description: The specified table name is not in the database.

Solution: Verify the spelling of the table name in your statement.

—217 Description: Column column-name not found in any table in the query.

Solution: Correct the spelling of the database item and ensure that the item exists in the database table. Verify the presence of required commas and quotes.

—219 Description: Wildcard matching may not be used with noncharacter types.

Solution: Wildcards (*, ?) and characters enclosed in brackets [ ] can be used only with CHAR data types. Check the data type for the offending column.

—220 Description: There is no FROM clause in the query.

Solution: You must include a FROM clause in the query.

Check that you do not have an illegal character ($, #, &, e-mail, or a CONTROL character) in the line prior to the FROM keyword.

—223 Description: Duplicate table name table-name in the FROM clause.

Solution: Remove the redundant table name from the statement or use an alias to rename one of the tables.

—228 Description: cannot have negative characters.

Solution: Check that you have not included a negative CHAR data type (for example, -a or -p) in your statement.

—278 Description: Too many ORDER BY columns; maximum is

eight.

Solution: Reduce the number of columns included in the ORDER BY clause to eight or fewer.

—280 Description: Total size of ORDER BY columns exceeds 120 bytes.

Solution: Reduce the number of columns included in the ORDER BY clause so that the total number of characters is fewer than or equal to 120 (perhaps delete a CHAR column of 30 or more characters).

—282 Description: Found a quote for which there is no matching quote.

Solution: Verify that all quoted strings are properly terminated with a quote.

—284 Description: A subquery has not returned exactly one value.

Solution: Check data for the subquery. Restructure the subquery by adding more components in the WHERE clause so that only one value is returned.

—297 Description: The SELECT list may not contain a subquery.

Solution: Remove the subquery from the SELECT list in the statement.

—300 Description: There are too many GROUP BY columns (maximum is eight).

Solution: Reduce to eight or fewer the number of

nonaggregate database items that are assigned the same row search ID as that assigned to an aggregate function.

Test Design Error Messages

—301 Description: The total size of the GROUP BY columns exceeds 120 characters.

Solution: The total number of characters in all columns listed in the GROUP BY list exceeds 120 characters.

Reduce the number of nonaggregate database items that are assigned to a row search ID that is also assigned to an aggregate function.

—303 Description: Expression mixes columns with aggregates.

Solution: Restructure your query so that columns and aggregates are not included in the same expression.

—309 Description: ORDER BY database item must be included in a report field to which the row search ID is assigned.

Solution: Check that database items included in the ORDER BY clause is displayed in the report and are assigned to row search ID.

—324 Description: Ambiguous database item.

Solution: A database item in your row search criteria exists in more than one table also cited in your row search criteria.

Prepend each database item with the appropriate table name.

—352 Description: Database item not found.

Solution: Verify the spelling of the database item.

—367 Description: Sums and averages cannot be computed for character columns.

Solution: Verify that you have not included a database item of a string type (VDN, LOGID, e-mail) in the aggregate function statement.

—522 Description: A database item in a field/bar does not exist in the table specified in the field’s row search ID.

Solution: Check the Select statement that has the error.

The database item that does not exist in the table will be marked with a circumflex (^). Change or delete the

database item or change the table in the field’s row search ID.

—809 Description: RDSQL syntax error has occurred.

Solution: Check that you have not misspelled an RDSQL statement, placed key words out of sequence, or included an INFORMIX SQL reserved word in your query.

—1202 Description: An attempt was made to divide by zero.

Solution: Check that you are not attempting to divide a numerical column type by a character column type (for example. 16/Jones) or that the value of the divisor does not equal zero.

—1203 Description: Values used in a MATCH must both be type CHARACTER.

Solution: Check that the values included in your MATCH condition are both CHAR types. Use an alternate

comparison condition for nonCHAR types.

—1204 Description: Invalid year in date.

Solution: Acceptable years are 0001 to 9999. If two digits are used, RDSQL assumes the year is 19xx. Check the value entered in the date field.

—1205 Description: Invalid month in date.

Solution: Months must be represented as the number of the month (1 through 12). Check the value entered in the date field.

—1206 Description: Invalid day in date.

Solution: Days must be represented as the number of the day (01 through 31). Check the value entered in the date field.

—1226 Description: Decimal or money value exceeds maximum precision.

Solution: Increase the precision of the DECIMAL or MONEY field.

Test Design Error Messages