Siebel Analytics Message Reference > Siebel Analytics Messages >

General Administration Tool Messages

This category contains message numbers 34xxx - 40xxx.

34001

Cannot convert repository query to desired target format.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34002

Unknown Siebel Analytics repository object construction error.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34003

Unknown repository object type. Check for missing metadata DLL(s).

Cause.  An internal error occurred. The installation may be incomplete.

Response.  Contact Siebel Systems technical support for assistance.

34004

Unknown repository implementation type. Check for missing metadata DLL(s).

Cause.  An internal error occurred. The installation may be incomplete.

Response.  Contact Siebel Systems technical support for assistance.

34005

Missing executable file. Check installation or system configuration.

Cause.  The installation or the system configuration may be incomplete.

Response.  Complete installation and system configuration. If the problem persists, contact Siebel Systems technical support for assistance.

34006

Error when accessing executable file. Check file permissions.

Cause.  The installation or the system configuration may be incomplete.

Response.  Complete installation and system configuration. Verify permissions for the Siebel Analytics folders. If the problem persists, contact Siebel Systems technical support for assistance.

34007

Not licensed to access all metadata objects.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34008

Internal error: cannot cast from @1%s to @2%s.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34009

Missing repository object: @1%s.

Cause.  The named repository object is missing. The installation or system configuration may be incomplete or corrupted.

Response.  Complete installation and system configuration. Verify permissions for the Siebel Analytics folders. If the problem persists, contact Siebel Systems technical support for assistance.

34010

Cannot convert to string: check that the value of reserved system session property (either user or group) is of type string.

Cause.  An internal conversion error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34011

Cannot convert session property value to an integer.

Cause.  An internal conversion error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34012

Cannot convert session property value to a float.

Cause.  An internal conversion error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34013

Cannot convert session property value to a date.

Cause.  An internal conversion error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34014

Cannot convert session property value to a date time.

Cause.  An internal conversion error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34015

Cannot convert session property value to a time.

Cause.  An internal conversion error occurred.

Response.  Contact Siebel Systems technical support for assistance.

34016

Administrator is concurrently updating object @1%s(@2%s).

Cause.  The named object is currently being updated by the Siebel Analytics Server administrator.

Response.  Try the update later. If the problem persists, contact Siebel Systems technical support for assistance.

34017

The repository publishing directory `@1%s' is not a directory.

Cause.  The REPOSITORY_PUBLISHING_DIRECTORY parameter in the Siebel Analytics Server configuration file (NQSConfig.ini) references some object, such as a file, that exists but is not a directory.

Response.  Specify a valid directory for the REPOSITORY_PUBLISHING_DIRECTORY in the NQSConfig.ini file.

34018

The repository publishing directory `@1%s' is not accessible.

Cause.  The repository publishing directory specified in the Siebel Analytics Server configuration file does not exist or is not accessible. More detailed error messages which may be helpful in diagnosing the problem sometimes accompany this message.

Response.  Verify the REPOSITORY_PUBLISHING_DIRECTORY parameter in the NQSConfig.ini file on the reporting machine, and make any needed corrections. If the specification was correct, determine why the directory is inaccessible and remedy the problem. If necessary, contact Siebel Systems technical support for assistance.

34019

The server is terminating because an error was encountered accessing the repository publishing directory or some file within it.

Cause.  The REQUIRE_PUBLISHING_DIRECTORY parameter in the NQSConfig.ini file requests that the server not be started if errors are encountered while accessing the repository publishing directory so the server is being stopped. More detailed error messages which may be helpful in diagnosing the problem accompany this message.

Response.  Either fix the problem detected by the server or set the value of the REQUIRE_PUBLISHING_DIRECTORY parameter in the NQSConfig.ini file to "NO" and restart the server. (Note that this change may result in the reporting server using an outdated version of one or more repositories.) If necessary, contact Siebel Systems technical support for assistance.

34020

An error was encountered while attempting to locate or access a published version of repository file `@1%s`.

Cause.  An error prevented the Siebel Analytics Server from determining if an updated version of the specified repository is available in the publishing directory or from accessing a published version. The local version of the repository will be used unless the REQUIRE_PUBLISHING_DIRECTORY parameter in the NQSConfig.ini file indicates that the server should be stopped in response to this condition. More detailed error messages which may be helpful in diagnosing the problem generally accompany this message.

Response.  Verify that the repository publishing directory, and the files in it, are accessible from the reporting server. If necessary, contact Siebel Systems technical support for assistance.

34021

The repository file `@1%s` was located but is not an ordinary file.

Cause.  The specified name must be a repository file but the filesystem object with that name is not an ordinary file (for example, it may be the name of a directory).

Response.  Update the NQSConfig.ini file to specify the correct repository file and restart the server.

34022

An attempt to access the repository file `@1%s` resulted in an error.

Cause.  The specified repository file could not be accessed. More detailed error messages which may be helpful in diagnosing the problem may accompany this message.

Response.  Either modify the reporting server's NQSConfig.ini file to specify a valid repository file or fix the access problem by altering the environment and restart the server. If necessary, contact Siebel Systems technical support for assistance.

34023

An attempt to upgrade repository file `@1%s` from a published version failed.

Cause.  A different version of the specified repository was located in the repository publishing directory but attempts to replace the local repository with the published one failed. If the REQUIRE_PUBLISHING_DIRECTORY parameter in the NQSConfig.ini file does not specify that this is a fatal error, the server will attempt to continue processing with the local copy, if any, of the repository. Generally this message is preceded by other messages which provide additional detail.

Response.  Examine other messages logged about the specified repository file, remedy the situations indicated in those messages, and restart the server. If necessary, contact Siebel Systems technical support for assistance.

34024

An attempt to copy the published version of repository file `@1%s` from the publishing directory to the local repository directory failed.

Cause.  A more detailed error messages which may be helpful in diagnosing the problem may accompany this message.

Response.  Examine other messages logged about the specified repository file, remedy the situations indicated in those messages, and restart the server. If necessary, contact Siebel Systems technical support for assistance.

34025

The repository file `@1%s` was successfully updated from published repository file `@2%s`.

Cause.  The local version of the repository did not match the published version so it was replaced with the most recent published version.

Response.  This is an informational message. No action is required.

34026

The repository file `@1%s` has been published to the other clustered Siebel Analytics Servers.

Cause.  The specified file was saved to the local repository directory and a copy was also made to the repository publishing directory where it will be available to other Siebel Analytics Servers in the cluster the next time they restart.

Response.  This is an informational message. No action is required.

34027

Attempt to publish repository file `@1%s` failed.

Cause.  The publish phase of saving the specified repository was not completed due to an error. Generally, other messages providing additional detail accompany this message. The repository was successfully saved to the Master Server's local repository directory and will be available to the Master Server. However, the new repository will not be available to any of the other servers in the cluster.

NOTE:  When this message is displayed in the Siebel Analytics Server Administration Tool, all filesystems and directories specified in the accompanying messages are relative to the machine running the master Siebel Analytics Server, not the machine running the Siebel Analytics Server Administration Tool.

Response.  The Siebel Analytics Server administrator should examine the accompanying messages to determine the source of the problem and resolve the problem. After the problem has been resolved, use the Siebel Analytics Administration Tool to load, modify, and save the repository, forcing it to be published to the other servers in the cluster. Contact Siebel Systems technical support for assistance if necessary.

34028

Attempt to purge obsolete published repository file `@1%s` failed.

Cause.  A new version of the repository was published and an attempt to delete obsolete published versions failed. Generally, other messages providing additional detail accompany this message. The initiating repository publishing operation was completed successfully. This is only a warning message.

Response.  If this message is reported infrequently and the repository publishing directory contains only versions of the referenced repository that were published recently (based on modification date), no action is required. Otherwise, examine the accompanying messages to assist in determining and resolving the problem. Contact Siebel Systems technical support if needed.

34029

Cannot convert to string vector: check that the value of the multi- row session variable (row-wise initialization) is of type string.

Cause.  An internal conversion error occurred.

Response.  Contact Siebel Systems technical support for assistance.

35001

Invalid file name specified.

Cause.  The file name is invalid.

Response.  Contact Siebel Systems technical support for assistance.

35002

Write operation on change log failed.

Cause.  There may be insufficient space on the disk.

Response.  Verify that there is sufficient disk space available. If the problem persists, contact Siebel Systems technical support for assistance.

35003

Rename of change log from @1%s to @2%s failed while recovering.

Cause.  A file rename operation failed during recovery. The file may already exist.

Response.  Contact Siebel Systems technical support for assistance.

36001

Unable to load the dll @1%s.

Cause.  The named dll failed to load due to an internal error.

Response.  Contact Siebel Systems technical support for assistance.

36002

Failed to recover the repository. Restore earlier version of repository archive.

Cause.  An unknown error caused repository recovery to fail.

Response.  Restore an earlier version of the repository. If necessary, contact Siebel Systems technical support for assistance.

36003

Failed to sync up with master server this round.

Cause.  An unknown error occurred.

Response.  This is an informational message. No action is required.

36004

Object @1%s is already checked out or temporarily locked.

Cause.  Another Siebel Analytics administration tool is running and has this object checked out.

Response.  Undo the checkout from the other administration tool or wait for several minutes.

36005

Failed to get exclusive lock on @1%s. It is checked out or temporarily locked.

Cause.  Another Siebel Analytics administration tool is running and has this object checked out.

Response.  Undo the checkout from the other administration tool or wait for several minutes.

36007

Loading repository @1%s.

Cause.  This is only informational.

Response.  This message will appear in the log file.

36010

Server version @1%d cannot read the newer version @2%d of the repository @3%s.

Cause.  The repository is from a newer version of Siebel Analytics Server.

Response.  Upgrade to a newer version of Siebel Analytics Server.

37001

Could not connect to the Siebel Analytics Server instance.

Cause.  The Siebel Analytics Server may not be running, or the network is temporarily unavailable.

Response.  Verify that the Siebel Analytics Server is running and is available through the network, and then retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

37002

Admin procedure request failed. The server may be down.

Cause.  The Siebel Analytics Server may not be running, or the network is temporarily unavailable.

Response.  Verify that the Siebel Analytics Server is running and is available through the network, and then retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

37003

Data fetch failed for output parameters. The server may be down.

Cause.  The Siebel Analytics Server may not be running, or the network is temporarily unavailable.

Response.  Verify that the Siebel Analytics Server is running and is available through the network, and then retry the action. If the problem persists, contact Siebel Systems technical support for assistance.

37004

Invalid repository handle.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance.

37005

Transactional update failed.

Cause.  Repository may not be consistent.

Response.  Verify in offline mode that repository is consistent. If the problem persists, contact Siebel Systems technical support for assistance.

38001

Logical column @1%s.@2%s has no physical data source mapping.

Cause.  The named logical column is not mapped to any physical data source.

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

38002

Expression validation error: check logical table sources.

Cause.  The expression could not be validated. There may be a problem with the logical table sources.

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

38003

Key @1%s in logical table @2%s has no columns. A valid key must have at least one column.

Cause.  The repository contains a definition error or inconsistency.

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

38004

Foreign key @1%s in logical table @2%s has no columns. A valid key must have at least one column.

Cause.  The repository contains a definition error or inconsistency.

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

38005

Empty level key definition: @1%s.@2%s.

Cause.  The repository contains a definition error or inconsistency.

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

38006

Logical table @1%s is associated to multiple dimensions: @2%s and @3%s.

Cause.  The repository contains a definition error or inconsistency.

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

38007

Level @1%s associated to logical table @2%s does not belong to a dimension.

Cause.  The repository contains a definition error or inconsistency.

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

38008

Content filter in table source @1%s of logical table @2%s refers to an unknown object.

Cause.  The repository contains a definition error or inconsistency.

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

38009

No table source exists for logical table @1%s.

Cause.  The repository contains a definition error or inconsistency.

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

38010

Presentation table @1%s has an invalid logical table @2%s associated with it.

Cause.  The repository contains a definition error or inconsistency.

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

38011

Logical tables from multiple subject areas associated, @1%s and @2%s.

Cause.  The repository contains a definition error or inconsistency.

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

38012

Logical column @1%s.@2%s does not have a physical data type mapping, nor is it a derived column.

Cause.  The repository contains a definition error or inconsistency.

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

38013

Dimension table @1%s does not have any joins!

Cause.  The repository contains a definition error or inconsistency.

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

38014

Logical tables @1%s and @2%s have multiple joins.

Cause.  The repository contains a definition error or inconsistency.

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

38015

Physical tables @1%s and @2%s have multiple joins. Delete new foreign key object if it is a duplicate of existing foreign key.

Cause.  The repository contains a definition error or inconsistency.

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

38016

Physical table @1%s has a self join.

Cause.  The repository contains a definition error or inconsistency.

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

38017

Logical table @1%s has a self join.

Cause.  The repository contains a definition error or inconsistency.

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

38018

Subject area @1%s does not have corresponding Presentation Catalog.

Cause.  The repository contains a definition error or inconsistency.

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

38019

Where clause in table source @1%s of logical table @2%s refers to unmapped table @3%s.

Cause.  The repository contains a definition error or inconsistency.

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

38020

Column @1%s mapping in table source @2%s of logical table @3%s refers to unmapped table @4%s.

Cause.  The repository contains a definition error or inconsistency.

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

38021

Group @1%s has privilege setting on a missing (deleted) object @2%s. Please update the group privileges.

Cause.  Group privileges exist for an object that is no longer in the repository.

Response.  Use the Administration Tool to correct the privilege setting, or correct the repository definition to restore the missing object. If the problem persists, contact Siebel Systems technical support for assistance.

38022

User @1%s has privilege setting on a missing (deleted) object @2%s. Please update the user privileges.

Cause.  User privileges exist for an object that is no longer in the repository.

Response.  Use the Administration Tool to correct the privilege setting, or correct the repository definition to restore the missing object. If the problem persists, contact Siebel Systems technical support for assistance.

38023

Complex join @1%s refers to the column @2%s. Please update or delete the complex join first.

Cause.  The repository contains a definition error or inconsistency.

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

38024

Session Variable Block @1%s is not associated with a valid connection pool or LDAP server.

Cause.  The repository contains a definition error or inconsistency.

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

38025

Object @1%s has invalid dynamic name.

Cause.  The repository contains a definition error or inconsistency.

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

38026

Logical column @1%s is not mapped properly.

Cause.  The repository contains a definition error or inconsistency.

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

38027

Catalog folder @1%s has the same name or alias as that of presentation table @2%s.

Cause.  The repository contains a definition error or inconsistency.

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

38028

Logical column @1%s.@2%s does not have a valid data type.

Cause.  The repository contains a definition error or inconsistency.

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

38029

Primary key of level @1%s does not match the primary key of table @2%s.

Cause.  The repository contains a definition error or inconsistency.

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

38030

Dimension @1%s is associated with table @2%s, which is also associated with another dimension. Use multiple hierarchies in the same dimension instead.

Cause.  The repository contains a definition error or inconsistency.

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

38031

The presentation table @1%s is corrupted. Please regenerate the repository using script tools.

Cause.  An internal error occurred.

Response.  Contact Siebel Systems technical support for assistance. (The repository must be regenerated using scripts like nqudmlgen and nqudmlexec.)

38033

The join @1%s is not properly defined.

Cause.  An internal error occurred.

Response.  Define the join properly.

38034

@1%s is name reserved for system session variable. It is defined in this repository as repository variable.

Cause.  The repository contains a definition error.

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

38035

Repository variable @1%s is defined more than once. Name of the variable has to be unique. Please redefine/remove one instance.

Cause.  The repository contains a definition error.

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

38036

Repository variable @1%s is defined more than once. Name of the variable has to be unique. Please redefine/remove one instance.

Cause.  The repository contains a definition error.

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

38037

Logical join @1%s is invalid.

Cause.  The repository contains an invalid logical join.

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

38038

Level @1%s is invalid.

Cause.  The repository contains an invalid level.

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

38039

User @1%s is defined more than once. Name of the user has to be unique. Please remove one instance.

Cause.  The repository contains a definition error.

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

38040

Group @1%s is defined more than once. Name of the group has to be unique. Please remove one instance.

Cause.  The repository contains a definition error.

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

38041

Query privilege @1%s is invalid.

Cause.  The repository contains invalid query privilege.

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

38042

Privilege package @1%s is invalid.

Cause.  The repository contains invalid privilege package.

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

39001

Logical table @1%s has no defined key.

Cause.  The repository contains a definition error or inconsistency.

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

39002

Level @1%s has no defined key to uniquely identify members.

Cause.  The repository contains a definition error or inconsistency.

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

39003

Missing functional dependency association for column: @1%s.@2%s.

Cause.  The repository contains a definition error or inconsistency.

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

39004

Source expressions @1%s and @2%s have incompatible types.

Cause.  The repository contains a definition error or inconsistency.

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

39005

Source expression @1%s is non-nullable, but a nullable source was found.

Cause.  The repository contains a definition error or inconsistency.

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

39006

Source expression @1%s is smaller in length than the max length @2%d from other sources.

Cause.  The repository contains a definition error or inconsistency.

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

39007

The source expressions @1%s is not binary, while other binary sources exist.

Cause.  The repository contains a definition error or inconsistency.

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

39008

Logical dimension table @1%s has a source @2%s that does not join to any fact source.

Cause.  The repository contains a definition error or inconsistency.

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

39009

Logical fact table @1%s has an aggregate source @2%s that does not join to a @3%s source at the proper level of detail.

Cause.  The repository contains a definition error or inconsistency.

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

39010

Disabled join in logical table source @1%s.@2%s. Please verify.

Cause.  The repository contains a definition error or inconsistency.

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

39011

Key @1%s in logical table @2%s is a superset or subset of another key in this table. Any redundant table key should be removed.

Cause.  The repository contains a definition error or inconsistency.

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

39012

Logical join @1%s is invalid and has been removed.

Cause.  The repository contained an invalid logical join.

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

39013

Query privilege @1%s is invalid and has been removed.

Cause.  The repository contained invalid query privilege.

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

39014

Privilege package @1%s is invalid and has been removed.

Cause.  The repository contained invalid privilege package.

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

39015

The name @1%s has leading or trailing space(s) in it.

Cause.  The name has leading or trailing space(s).

Response.  Please remove the leading or trailing space(s) using the Administration Tool.

39016

The alias "@1%s" of @2%s has leading or trailing space(s) in it.

Cause.  The alias has leading or trailing space(s).

Response.  Please remove the leading or trailing space(s) using the Administration Tool.

40001

Source object types are different.

Cause.  A drag and drop error occurred.

Response.  Select objects with matching source object types and try the action again.

40002

This kind of drag and drop is not supported at this time.

Cause.  A drag and drop error occurred.

Response.  Perform a support drag and drop operation, or use menu selections to perform the needed actions.

40003

Only tables from the subject area @1%s may be dragged to this catalog folder.

Cause.  A drag and drop error occurred.

Response.  Drag and drop a table from the named subject area, or choose a valid catalog folder.


 Siebel Analytics Message Reference 
 Published: 18 April 2003