Siebel Analytics Message Reference > Siebel Analytics Messages >

Request Generation Messages


This category contains message numbers 42xxx.

42001

Missing repository object with ID=@1%s.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42002

Corrupt repository object with ID=@1%s.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42003

Expression object (Name=@1%s, ID=@2%s) has illegal type @3%ld.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42004

Logical element @1%s (ID=@2%s) has no physical data link.

Cause.  The specified repository object is incorrectly defined.

Response.  Use the Check Consistency command in the Administration Tool to check for repository compilation errors. Correct any problems and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

42005

Attribute @1%s (ID=@2%s) is not part of an entity.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42006

Column @1%s (ID=@2%s) is not part of a table.

Cause.  The named column is not defined correctly. It is not part of a table.

Response.  Verify the definition of the named column and use the Administration Tool to perform a consistency check on the repository. Correct any errors and try the action again. If the problem persists, contact Siebel Systems technical support for assistance.

42007

Table @1%s (ID=@2%s) is not part of a database.

Cause.  The named table is not associated with a known data source.

Response.  Verify the definition of the named table and use the Administration Tool to perform a consistency check on the repository. Correct any errors and try the action again. If the problem persists, contact Siebel Systems technical support for assistance.

42008

Cannot find database definition for @1%s.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42009

Operation @1%s has no implementation.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42010

@1%s is not a conditional expression.

Cause.  The specified expression is not a valid conditional expression.

Response.  Use the Expression Editor in the Administration Tool to review the expression. Correct any problems and try the action again. If the problem persists, contact Siebel Systems technical support for assistance.

42011

Foreign key object, @1%s, is not completely specified.

Cause.  The foreign key specification for the named object is invalid.

Response.  Use the Administration Tool to review foreign key specifications for the named object. Correct any problems and try the action again. If the problem persists, contact Siebel Systems technical support for assistance.

42012

Incorrect foreign key specification for object @1%s.

Cause.  The foreign key specification for the named object is invalid.

Response.  Use the Administration Tool to review foreign key specifications for the named object. Correct any problems and try the action again. If the problem persists, contact Siebel Systems technical support for assistance.

42013

Unsupported fiscal extract operation.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42014

Improperly defined qualified entity attribute object: @1%s (ID=@2%s).

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42015

Cannot function ship the following expression: @1%s.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42016

Check database specific features table. Must be able to push at least a single table reference to a remote database.

Cause.  The database features table contains an invalid setting. The features table may have been modified in error.

Response.  Siebel Analytics Server uses the features table to determine what kinds of queries it can send to the underlying databases. The features table contains default settings for each database type that have been tested with that database. Use the Administration Tool to restore the features table for the database to the tested default settings and try the action again. If the problem persists, contact Siebel Systems technical support for assistance.

42017

Query refers to @1%ld catalog(s). A request can only refer to tables from a single catalog.

Cause.  The query is invalid because it refers to tables from multiple catalogs.

Response.  Review the query and correct any problems. If necessary, use the Administration Tool to modify the Catalog Folder in the Presentation Layer of the repository. If the problem persists, contact Siebel Systems technical support for assistance.

42018

Unknown logical query request translation failure. Notify technical support.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

42019

Join condition, @1%s, contains predicates that are currently not supported for outer joins across multiple databases.

Cause.  The query contains an invalid join.

Response.  Use the Administration Tool to review defined joins, correct any problems, and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

42020

GROUP BY clause, @1%s, is inconsistent with the projected columns in the SQL query request.

Cause.  The specified GROUP BY clause is invalid.

Response.  Review the query, correct any problems, and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

42021

The query does not reference any tables.

Cause.  The query is invalid because it does not reference any tables.

Response.  Review the query, correct any problems, and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

42022

The query contains a self join. This is a non-supported operation.

Cause.  The query contains an invalid join.

Response.  Use the Administration Tool to review defined joins, correct any problems, and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

42023

Illegal aggregate nesting in query.

Cause.  The query is invalid because it contains illegal aggregate nesting.

Response.  Review the query, correct any problems, and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

42024

Regular aggregates cannot be nested.

Cause.  The query is invalid because it contains nested aggregates.

Response.  Review the query, correct any problems, and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

42025

The value of N for TopN, BottomN, Mavg, and NTile must be a constant.

Cause.  The second operand of the aggregate in the SQL statement does not evaluate to a numeric constant.

Response.  Change the second operand of the aggregate in the SQL statement to use a numeric constant and resubmit the query.

42026

Navigator for subject area: @1%s could not be accessed.

Cause.  The named subject area could not be accessed. The subject area in the Business Model and Mapping Layer may not be correctly defined.

Response.  Check the repository for the validity of the named subject area. Correct any problems, and retry the action.

42027

Subquery within a predicate must project out 1 column only.

Cause.  The subquery is invalid.

Response.  Modify the subquery so that only one column is projected out.

42028

The current drill-down implementation requires the catalog to be specified in the FROM clause.

Cause.  The FROM clause does not explicitly specify the catalog.

Response.  Modify the query so that the catalog is explicitly specified in the FROM clause.

42029

Subquery contains too many values for the IN predicate.

Cause.  The subquery is invalid.

Response.  Strengthen the filtering within the subquery so that it returns fewer values.

42030

FROM clause cannot contain both atomic tables and embedded queries.

Cause.  The FROM clause is invalid.

Response.  Nest the atomic tables in an embedded query.

42031

Empty join condition specified for an outer join.

Cause.  An outer join has an invalid search condition specified.

Response.  Specify the correct search condition for the outer join.

42032

Parameters are not supported in the select list.

Cause.  The query select list includes parameters.

Response.  Remove all parameters from the query select list and resubmit the query.

42033

Improperly defined presentation column object: @1%s (ID=@2%s).

Cause.  The named presentation column is improperly defined.

Response.  Use the Administration Tool to review the named presentation column definition. Correct any problems, and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.


 Siebel Analytics Message Reference 
 Published: 18 April 2003