Lucent Technologies CentreVu Call Management System Custom Reports Manual

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-13
Table 5-1: Phase 1 Error Messages (Contd)
Message:keyword AVG invalid in where clause
Cause:You cannot use the keyword AVG in row search criteria.
Solution:Remove the keyword AVG from the row search criteria.
Message:keyword BETWEEN invalid for real-time
Cause:You cannot use the keyword BETWEEN in row search 
criteria for a real-time report.
Solution:Remove the keyword BETWEEN from the row search 
criteria.
Message:keyword COUNT invalid in where clause
Cause:You cannot use the keyword COUNT in row search criteria.
Solution:Remove the keyword COUNT from the row search criteria.
Message:keyword MAX invalid in where clause.
Cause:You cannot use the keyword MAX in row search criteria.
Solution:Remove the keyword MAX from the row search criteria.
Message:keyword MIN invalid in where clause.
Cause:You cannot use the keyword MIN in row search criteria.
Solution:Remove the keyword MIN from the row search criteria.
Message:keyword SUM invalid in where clause.
Cause:You cannot use 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 cannot use the keyword SYN in row search criteria.
Solution:Remove the keyword SYN from the row search criteria. 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-14
Phase 2 
Historical 
Error Codes
5
This section contains the INFORMIX* error codes most likely to appear for 
CentreVu 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: 
In addition, a circumflex (^) may appear in the listed Select statement(s) to 
mark the location of an error.
*INFORMIX is a registered trademark of Informix Software, Inc.
NoteIf an error code appears that is not listed in this document, see the 
INFORMIX SQL Relational Database Management System 
Reference Guide
 for INFORMIX SQL Version 4.10.
Table 5-2:  Phase 2 Historical Error Codes 
—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
—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. Check that you have not 
included a number with a fractional portion or a number 
outside the acceptable range. Check 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: Check that you have not inadvertently entered a 
letter in place of a number (for example, 125p3 instead of 
125.03). 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-15
—206 Description: The specified table name is not in the 
database.
Solution: Check 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. Check for 
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: Must include a FROM clause in the query. Check 
that you do not have an illegal character ($, #, &, etc., 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 less. Table 5-2:  Phase 2 Historical Error Codes  — 
Continued 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-16
—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 
less 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: Check 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 less the number of 
nonaggregate database items that are assigned the same 
row search ID as that assigned to an aggregate function.
—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. Table 5-2:  Phase 2 Historical Error Codes  — 
Continued 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-17
—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 appear 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: Check the spelling of the database item.
—367 Description: Sums and averages cannot be computed for 
character columns.
Solution: Check that you have not included a database 
item of a string type (VDN, LOGID, etc.) 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. Table 5-2:  Phase 2 Historical Error Codes  — 
Continued 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-18
—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. Table 5-2:  Phase 2 Historical Error Codes  — 
Continued 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-19
Phase 2 Real-
Time Error 
Codes
5
This section contains the Real-Time Database Manager error codes. Each 
code includes a description of the error and a recommended solution.
These errors are reported in the following format:
CMS Database Manager error: 
In addition, a circumflex (^) appears in the listed Select statement(s) to mark 
the location of an error.
Table 5-3:  Phase 2 Real-Time Error Codes 
—1 Description: A syntax error has occurred.
 Solution: Check the select for misspelled keywords or 
keywords that are out of order.
—2 Description: An illegal character has been found in the select 
statement.
 Solution: Remove the illegal character (often a nonprintable 
control character).
—3 Description: The specified table name is invalid.
 Solution: Check the spelling of the table name and for required 
commas in the From tables field.
—4 Description: An invalid column has been specified (it is not 
found in any of the specified tables).
Solution: Check the spelling of the column names.
—5 Description: A mixture of aggregates and nonaggregates are 
being selected, and this is not allowed in real-time reports. (This 
error code can also mean mismatched types in comparison.)
Solution: Create two identical row search conditions, and apply 
one to the aggregate columns and one to the nonaggregate 
columns.
—6 Description: Bad column in the order by clause.
Solution: Check that the column name in the order by clause is 
spelled correctly and that it is being selected by one of the fields 
included in this row search. 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Running Custom Reports5-20
Running Custom Reports5
You run custom reports using steps similar to steps you use to run standard 
reports. However, you run custom reports from the Custom Reports Main 
Menu option. Also, the Report Input window shows input fields you defined 
on the Define Input window for the report. For real-time reports, the Report 
Input window also automatically shows a Refresh rate in seconds  —7 Description: Bad index in order by clause.
Solution: Order by clause has to have a column in the “select” 
clause or a number that indicates a position of the column in the 
“select” clause.
—8 Description: Bad argument given to an aggregate function. For 
example, you cannot take the SUM or AVG of a character 
column.
Solution: Check the arguments for the aggregates and be sure 
that data type is appropriate.
—9 Description: In the “Select” of one of the fields associated with 
this row search, an action is being performed with the wrong 
data types. For example, you cannot use arithmetic with 
character fields.
Solution: Check for these types of errors in the fields 
associated with the row search.
—10 Description: Error with subquery. 
Solution: There may be a subquery in the “where” clause that 
CMS does not support. Check the subqueries. This typically 
happens with an Agent Group report (a “select” embedded 
within a “select”).
—11 Description: CMS system error.
Solution: Check the error logs.
—12 Description: Memory allocation error.
Solution: Check the error logs.
—13 Description: Query cannot select more than one table.
Solution: Check the error logs. Table 5-3:  Phase 2 Real-Time Error Codes  — 
Continued 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Running Custom Reports5-21
field. For historical reports, the Report Input window automatically shows 
report destination fields.
1.Select the Custom Reports 
Main Menu option.®
The Custom Reports submenu 
appears.
2.Select either the Real-time or 
Historical submenu option.®A submenu of custom reports, 
either real-time or historical, 
appears. The list includes all 
existing global reports and your 
private reports.
3.Select the desired report.®The Report Input window for 
the report appears.
NoteIf more than 20 custom reports are available, you may need to 
scroll the submenu to find the report you want. Scroll down with 
the down arrow (¯). Scroll up with the up arrow (­).
4.Complete the fields of the Report 
Input window, and select Run.®Working 
appears on the 
Report Input window status 
line. If the destination is the 
terminal, the report appears. If 
the destination is a printer or 
file, 
Successful appears. 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Running Custom Reports5-22