Bookshelf Home | Contents | Index | Search | PDF |
Siebel Analytics Message Reference > Siebel Analytics Messages >
Join and UDML Generation Messages
This category contains message numbers 30xxx - 32xxx.
30002
The join info part vector is empty.
Cause. The vector passed to the underlying layer is empty.
Response. Contact Siebel Systems technical support for assistance.
31001
(@1%s): Multiple matches found in the current repository.
Cause. The repository contains multiple matches.
Response. Review the repository definitions and make the appropriate modifications. Use the Check Consistency command in the Administration Tool to check for repository compilation errors. Correct any other problems and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.
32001
The object @1%s of type `@2%s`: is missing a role. Two roles are required for a relationship.
Cause. The repository is not set up correctly. The named object is missing a role.
Response. Review the repository definitions and make the appropriate modifications. Use the Check Consistency command in the Administration Tool to check for repository compilation errors. Correct any other problems and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.
32002
The object @1%s of type `@2%s`: is missing an object of type `@3%s`.
Cause. The repository is not set up correctly. The named object definition is invalid.
Response. Review the repository definitions and make the appropriate modifications. Use the Check Consistency command in the Administration Tool to check for repository compilation errors. Correct any other problems and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.
32003
The object @1%s of type `@2%s`: is missing a list of type `@3%s`.
Cause. The repository is not set up correctly. The named object definition is invalid.
Response. Review the repository definitions and make the appropriate modifications. Use the Check Consistency command in the Administration Tool to check for repository compilation errors. Correct any other problems and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.
32004
The object @1%s of type `@2%s`: is missing a table in the join graph.
Cause. The repository is not set up correctly. The named object is missing a table in the join graph.
Response. Review the repository definitions and make the appropriate modifications. Use the Check Consistency command in the Administration Tool to check for repository compilation errors. Correct any other problems and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.
32005
The object @1%s of type `@2%s`: is missing a foreign key or a complex join in the join graph.
Cause. The repository is not set up correctly. The named object is missing a foreign key or complex join in the join graph.
Response. Review the repository definitions and make the appropriate modifications. Use the Check Consistency command in the Administration Tool to check for repository compilation errors. Correct any other problems and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.
32006
The object @1%s of type `@2%s`: missing a driving table.
Cause. The repository is not set up correctly. The named object is missing a driving table.
Response. Review the repository definitions and make the appropriate modifications. Use the Check Consistency command in the Administration Tool to check for repository compilation errors. Correct any other problems and retry the action. If the problem persists, contact Siebel Systems technical support for assistance.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Analytics Message Reference Published: 18 April 2003 |