Skip Headers
Oracle® Database Error Messages
11g Release 2 (11.2)
Part Number E17766-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
Mobi · ePub

120 XOQ-00101 to XOQ-02535

XOQ-00101: unknown error
Cause: An unexpected internal error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00102: system failure
Cause: An unexpected internal error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00103: An OLAP API method failed.
Cause: An unexpected internal error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00104: not implemented
Cause: An OLAP API query was issued that requires an unimplemented feature.
Action: Check the classes and methods in the OLAP API Java documentation for alternative ways to construct the query.
XOQ-00105: unknown error
Cause: An unexpected internal error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00106: SQL query failed: "(string)"
Cause: A SQL query generated by the OLAP component failed to execute.
Action: Examine the error message to determine the possible cause of failure, or contact Oracle Support Services.
XOQ-00107: current operation cancelled
Cause: An Oracle operation was interrupted by CTRL+C or another cancelling operation.
Action: Continue with the next operation.
XOQ-00201: error opening connection
Cause: An error occurred while initializing the connection for the OLAP API.
Action: Ensure that Oracle Database is properly installed with the OLAP option. If the problem persists, then contact Oracle Support Services.
XOQ-00203: error retrieving connection information for the server
Cause: An error occurred while retrieving the connection parameter information.
Action: Ensure that Oracle Database is properly installed with the OLAP option. If the problem persists, then contact Oracle Support Services.
XOQ-00204: error initializing second DataProvider on a JDBC connection
Cause: The Java client tried to open multiple DataProviders over one JDBC connection.
Action: Close the first DataProvider before initializing the second DataProvider.
XOQ-00223: error executing an OLAP DML command
Cause: A syntactic or referential error in the commmand string prevented execution of an OLAP DML command.
Action: Correct the syntax of the OLAP DML command.
XOQ-00225: error closing the connection
Cause: An error occurred while closing the connection for the OLAP API.
Action: Report this error to Oracle Support Services.
XOQ-00229: cannot retrieve information for the connection
Cause: An error occurred while preparing OLAP API connection information.
Action: Report this error to Oracle Support Services.
XOQ-00232: error sharing the session
Cause: An unexpected error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00233: error obtaining the system
Cause: An unexpected error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00234: error obtaining the module version
Cause: An unexpected error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00251: Default database is not set.
Cause: An unexpected error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00286: error creating a definition manager
Cause: An error occurred while preparing an OLAP API query for use.
Action: Examine the ErrorStack for more detail about the reason for the failure.
XOQ-00287: error adding analytic workspace "(string)" to branch (string)
Cause: An unexpected error occurred while adding an analytic workspace to a branch.
Action: Report this error to Oracle Support Services.
XOQ-00288: unable to commit transaction string
Cause: An error occurred while trying to commit changes to a cube or dimension.
Action: Examine the error stack for more detail about the reason for the failure.
XOQ-00400: failed to map CWM object "(string))" to XML or IDL
Cause: An error occurred while preparing a metadata object to return to the client.
Action: Check the metadata object for unusual characteristics, such as extremely long text attributes, unusual characters in text attributes,
XOQ-00401: unexpected class type for object "(string)": expected string, found string
Cause: An error occurred while processing the metadata. This could indicate inconsistencies in the metadata or multiple objects with the same name or ID.
Action: Check the metadata object for inconsistencies. If multiple objects have the same name or ID, then rename one of the objects so its ID is unique.
XOQ-00402: unexpected class type for object "(string)": expected string
Cause: An unexpected error occurred while processing the metadata. This could indicate inconsistencies in the metadata, or multiple objects with the same name or ID.
Action: Check the metadata object for inconsistencies. If there are multiple objects with the same name or ID, rename one of the objects so that its ID is unique.
XOQ-00500: no metadata provider "(string)" available
Cause: A MetadataProvider could not be found for the specified type of metadata.
Action: Ensure that your code requests metadata type CWM.
XOQ-00501: table "(string)" and/or column "(string)" not found
Cause: A metadata object was mapped to a table or column that does not exist.
Action: Run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any reported problems with the metadata object.
XOQ-00502: cannot create more than one CursorManager for a source
Cause: An attempt was made to create a second CursorManager for a source in a transaction.
Action: Use only one CursorManager or upgrade to newer OLAP API jar files.
XOQ-00503: cannot create server cursor
Cause: An error occurred while executing the SQL for an OLAP API query.
Action: Examine the ErrorStack for details about the failure.
XOQ-00504: cannot execute the query
Cause: An error occurred while executing the SQL for an OLAP API query.
Action: Examine the ErrorStack for details about the failure.
XOQ-00505: The number of cursor inputs (string) does not match the number of bind sources (string).
Cause: The bind source specified in the cursor manager did not have matching cursor input.
Action: Specify a cursor input for each bind source.
XOQ-00506: cannot parse XML string from the client
Cause: An error occurred while parsing query or metadata definitions sent by the client.
Action: Examine the error output for details about the failure.
XOQ-00507: source definition not found with ID "(string)"
Cause: The query referred to a source definition that did not exist.
Action: Examine the error output for details about the failure.
XOQ-00508: metadata object not found with ID "(string)"
Cause: The query referred to a metadata object that did not exist.
Action: Correct the query so it refers to existing metadata objects.
XOQ-00509: Invalid value string "(string)" is used for a value of dimension "(string)".
Cause: The query contained an incorrectly formatted value string. The accepted formats are "HIERARCHY::LEVEL::VALUE" in hierarchy-qualified value mode, or "[Dimension].[Hierarchy].[Level].[Value]" in ODBO compatibility mode.
Action: Correct the value string used in the query, or select values using the localValue attribute. For example, dimensionSource.select(dimension.getLocalValueAttribute().getSource().eq("value"));
XOQ-00510: NULL key found in hierarchy
Cause: The hierarchy was not identified as a skip-level hierarchy, although it contained NULL values.
Action: Correct the metadata for the hierarchy to mark it as a skip-level hierarchy.
XOQ-00511: Query will result in a Cartesian product.
Cause: An incorrect join condition was used in the query.
Action: Examine the mappings for the metadata objects and correct the query.
XOQ-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
Cause: A process encountered an exceptional condition. This is the generic internal error number for Oracle program exceptions.
Action: Report as a bug. The first argument is the internal error number.
XOQ-00603: Fatal error occurred: unwise to proceed.
Cause: An Oracle session was in an unrecoverable state.
Action: Log in to Oracle again so a new session is created automatically. Examine the session trace file for more information.
XOQ-00699: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
Cause: An internal inconsistency was detected that did not end the process.
Action: Report a bug and include the internal error, which is the first argument in the error message.
XOQ-00700: error compiling OLAP DML command
Cause: A syntactic or referential error in the OLAP DML command caused a compilation error.
Action: Correct the syntax of the OLAP DML command. The error stack may provide more detail about the error. Before trying again, enable the OLAP DML BADLINE option to get more detailed messages.
XOQ-00701: error compiling OLAP DML expression
Cause: A syntactic or referential error in the OLAP DML expression caused a compilation error.
Action: Correct the syntax of the OLAP DML expression. The error stack may provide more detail about the error. Before trying again, enable the OLAP DML BADLINE option to get more detailed messages.
XOQ-00702: no OLAP DML code to compile
Cause: SPLExecutor:executeCommand was called with an empty command string.
Action: Ensure that an OLAP DML command is passed to SPLExecutor::executeCommand.
XOQ-00703: error executing OLAP DML command "(string)"
Cause: A syntactic or referential error in the commmand string prevented the execution of an OLAP DML command.
Action: Examine the error stack for more detail about the error. Correct the OLAP DML command and try again.
XOQ-00704: error evaluating OLAP DML expression
Cause: A syntactic or referential error in the expression string prevented the evaluation of an OLAP DML expression.
Action: Examine the error stack for more detail about the error. Correct the OLAP DML expression and try again.
XOQ-00705: no OLAP DML expression to evaluate
Cause: An SPLExecutor::evaluateExpression method was called with an empty expression string.
Action: Ensure that an OLAP DML command is passed to the SPLExecutor::evaluateExpression method.
XOQ-00850: cannot create fundamental snapshot: definition id "(string)" not recognized
Cause: A cursor could not be created because the source referred to an unrecognized metadata object.
Action: If the source uses an MdmDimension or MdmMeasure that is created with an MdmCustomObjectFactory, then ensure that the Mtm definition is complete and refers only to existing objects.
XOQ-00851: cannot create Mdm property: definition id "(string)" not recognized
Cause: A cursor was not created because the source referred to an unrecognized metadata object.
Action: If the source uses an MdmDimension or MdmMeasure that is created with an MdmCustomObjectFactory, then ensure that the Mtm definition is complete and refers only to existing objects.
XOQ-01000: A portion of the query results in an empty selection and a 0-extent cursor.
Cause: The selection for one or more dimensions of a source yielded no members, so no data was retrieved for the source.
Action: Check the dimension selections to ensure that all references to hierarchies, levels, and members are correct. Evaluate each dimension query separately to identify the faulty one.
XOQ-01100: Query is not supported by the current generator.
Cause: The source involved a construct that was syntactically correct but is not currently supported.
Action: Check the source for unsupported constructs. For example, some releases require that a measure source be joined to sources for hierarchies and not to sources for dimensions.
XOQ-01150: unknown problem with OLAP Catalog
Cause: An error occurred while reading the OLAP Catalog.
Action: Run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01151: OCI error: string
Cause: An exception was raised by Oracle Call Interface.
Action: Correct the problems identified in the error message.
XOQ-01200: metadata problem for MdmAttribute "string"
Cause: Metadata for the MdmAttribute was incomplete or inconsistent. Possible causes are: 1) The MdmAttribute did not have an associated MtmAttributeMap. 2) The MtmAttributeMap existed, but there was no mapped expression for a requested MtmDimensionMap.
Action: If the MdmAttribute is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MdmAttribute is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01201: metadata problem for MdmMeasure "string"
Cause: Metadata for the MdmMeasure was incomplete or inconsistent. Possible causes are: 1) The MdmMeasure did not have an associated MtmMeasureMap. 2) The MtmMeasureMap existed, but there was no mapped expression for a requested MtmBaseCube. 3) The MtmMeasureMap existed, but had no associated MtmCube.
Action: If the MdmMeasure is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MdmMeasure is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01202: metadata problem for MdmLevel "string"
Cause: Metadata for the MdmLevel was incomplete or inconsistent. The MdmLevel did not have an associated MtmLevelMap.
Action: If the MdmLevel is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MdmLevel is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01203: metadata problem for MdmHierarchy "string"
Cause: Metadata for the MdmHierarchy was incomplete or inconsistent. The MdmHierarchy did not have an associated MtmHierarchyMap.
Action: If the MdmHierarchy is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MdmHierarchy is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01204: metadata problem for MdmListDimension "string"
Cause: Metadata for the MdmListDimension was incomplete or inconsistent.
Action: If the MdmListDimension is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MdmListDimension was read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01205: metadata problem for MdmPrimaryDimension "string"
Cause: Metadata for the MdmPrimaryDimension was incomplete or inconsistent. The MdmPrimaryDimension (also known as MdmUnionHierarchy) did not have an associated MtmPrimaryDimensionMap.
Action: If the MdmPrimaryDimension is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MdmPrimaryDimension is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01206: metadata problem for cube "string"
Cause: Metadata for the cube was incomplete or inconsistent. This happened for one of the following reasons: 1) No MtmBaseCube was associated with a requested hierarchy combination. 2) One of the MtmMeasureMaps associated with an MtmCube was NULL. 3) Something was wrong with an MtmCubeDimensionality associated with an MtmBaseCube.
Action: If the hierarchy combination, measure map, or cube is created or modified using the OLAP Metadata API, then ensure that the objects are created and mapped correctly. If the attribute hierarchy combination, measure map, or cube is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01207: metadata problem for hierarchy combination "string"
Cause: Metadata for the hierarchy combination was incomplete or inconsistent.
Action: If the hierarchy combination is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the hierarchy combination is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01208: metadata problem for MtmBaseCube "string"
Cause: Metadata for the MtmBaseCube was incomplete or inconsistent. An MtmBaseCube had no associated MtmTabularSource.
Action: If the MtmBaseCube is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MtmBaseCube is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01209: metadata problem for attributes on dimension "string"
Cause: Metadata for the attributes on the dimension was incomplete or inconsistent.
Action: If the attributes or dimension is created or modified using the OLAP Metadata, then ensure that the objects are created and mapped correctly. If the attributes or dimension are read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01210: metadata problem for table map for list dimension "string"
Cause: Metadata for the table map for the list dimension was incomplete or inconsistent.
Action: If the table map or dimension is created or modified using the OLAP Metadata API, then ensure that the objects are created and mapped correctly. If the table map or dimension is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01211: metadata problem for MdmValueHierarchy "string"
Cause: Metadata for the MdmValueHierarchy was incomplete or inconsistent. Possible causes are: 1) The MtmValueLevelHierarchyMap for the MdmValueHierarchy did not have an associated MtmSolvedLevelHierarchyMap. 2) The MtmValueLevelHierarchyMap for the MdmValueHierarchy was invalid.
Action: If the MdmValueHierarchy or MtmValueLevelHierarchyMap is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MdmValueHierarchy or MtmValueLevelHierarchyMap is read from the OLAP Catalog, run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01212: aggregation metadata problem for cube "string"
Cause: Aggregation metadata for the cube was incomplete or inconsistent.
Action: If the cube is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the cube is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01213: metadata problem for MdmLevelHierarchy "string"
Cause: Metadata for the table mapping for the MdmLevelHierarchy was incomplete or inconsistent. The MtmLevelHierarchyMap for the MdmLevelHierarchy had no associated MtmTabularSource.
Action: If the MdmLevelHierarchy is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MdmLevelHierarchy is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01214: metadata problem with dimension order specification for "string"
Cause: Metadata for the custom sort column was incomplete or inconsistent. An MtmDimensionOrderSpecification had no associated OrderByExpression.
Action: If the MtmDimensionOrderSpecification is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the MtmDimensionOrderSpecification is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01215: metadata problem with mapped RDBMS column "string"
Cause: Metadata for the mapped RDBMS column was incomplete or inconsistent. There was a problem identifying the RDBMS table that owns the associated RDBMS column.
Action: If the RDBMS column is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the RDBMS column is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01216: metadata problem with mapping for snowflake hierarchy "string"
Cause: Mapping metadata for the snowflake hierarchy was incomplete or inconsistent. There was a problem identifying a mapping for the associated snowflake hierarchy.
Action: If the hierarchy is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the hierarchy is read from the OLAP Catalog, run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01217: metadata problem with mapping for hierarchy "string"
Cause: Mapping metadata for the hierarchy was incomplete or inconsistent. A mapping for the associated hierarchy could not be identified. The problem may be the way the dimension was mapped in one of the cubes and may be in the GID column.
Action: If the hierarchy is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the hierarchy is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01218: metadata problem with mapping for hierarchy "string"
Cause: Mapping metadata for the hierarchy was incomplete or inconsistent. A mapping for the associated hierarchy could not be identified, possibly because of the way the dimension was mapped in one of the cubes.
Action: If the hierarchy is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the hierarchy is read from the OLAP Catalog, run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01219: metadata problem with mapping for hierarchy "string"
Cause: Mapping metadata for the hierarchy was incomplete or inconsistent. The ET column for the associated hierarchy could not be identified.
Action: If the hierarchy is created or modified using the OLAP Metadata API, then ensure that the object is created and mapped correctly. If the hierarchy is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01300: invalid dimension member value "(string)"
Cause: An invalid dimension value was specified as part of an MdmCustomMember.
Action: Check the values passed to the MdmCustomMembers. All dimension members must be in unique value form. The problem could be in the memberValue, the parentValue, an attributeExpression, or the measureExpression.
XOQ-01301: invalid measure expression in MdmCustomMember "(string)"
Cause: A measure expression in an MdmCustomMember was invalid.
Action: Ensure that the measure expression in each MdmCustomMember is valid. Ensure that any square brackets are balanced.
XOQ-01302: query not supported in local value mode
Cause: Some feature of the query required unique value mode to be enabled.
Action: Either enable unique value mode, or rewrite the query to remove any features that depend on unique value mode. MdmCustomMembers require unique value mode.
XOQ-01303: incorrect cube dimensionality
Cause: The metadata that defines the dimensionality of a cube was incorrect.
Action: Check the metadata for the dimensionality of the cubes being queried. Ensure that the number of join columns on the fact table matches the number of join columns on the dimension table.
XOQ-01304: Custom members feature is not supported.
Cause: The query included custom members that could not be processed.
Action: Check if any solved cubes are in GROUPING SET or ROLLUP form in the query. Rewrite them in ET form.
XOQ-01305: invalid model assignment
Cause: The definition of a model assignment was invalid.
Action: Ensure that all assignments are defined so the assigned source does not have a qualified source as an input. The assignment may have been created explicitly, or it may have been created implicitly from a custom member definition.
XOQ-01306: cannot generate cursor manager for MdmValueHierarchy
Cause: A cursor manager could not be created on a query containing an MdmValueHierarchy, because the hierarchy had no LevelExpressions and was not compiled in an analytic workspace.
Action: Either add LevelExpressions to the SolvedValueHierarchyMap of the MdmValueHierarchy, or create a AWPrimaryDimensionOrganization on the hierarchy's MdmPrimaryDimension. Build the dimension using a COMPILE command.
XOQ-01307: Cannot generate MdmCubeMap "string" on MdmCube "string". The MdmCubeMap contains no MdmCubeDimensionalityMap for dimension "string".
Cause: The MdmCubeMap was missing an MdmCubeDimensionalityMap for the specified dimension.
Action: Ensure that the MdmCubeMap has an MdmCubeDimensionalityMap for each dimension of the MdmCube.
XOQ-01308: Primary dimension "string" on cube "string" has multiple dimension levels but no hierarchy.
Cause: A PrimaryDimension had more than one DimensionLevel, but no hierarchies and no MemberListMap.
Action: Add a Hierarchy or MemberListMap to the PrimaryDimension.
XOQ-01400: invalid metadata objects
Cause: One or more Mdm or Mtm metadata objects was invalid. A list of the invalid objects follows this error.
Action: Examine the list of invalid metadata objects and correct the errors reported for each object. For objects created or modified using the OLAP Metadata API, make the necessary changes on the client. For objects created from the OLAP Catalog, either modify the metadata tables or modify the Mdm and Mtm objects using the OLAP Metadata API.
XOQ-01401: validation error
Cause: An error occurred while validating an Mdm or Mtm metadata object, but the cause of the error could not be determined.
Action: Check the metadata object and its dependencies for inconsistencies.
XOQ-01411: attribute mapping not defined for hierarchy "(string)"
Cause: An MtmAttributeMap had no mapping for a requested MtmDimensionMap, and it had no default value.
Action: Use the OLAP Metadata API to create an expression that provides the attribute value for the required MtmDimensionMap. Add it to the MtmAttributeMap as a mapping for the given MtmDimensionMap. If the attribute is read from the OLAP Catalog, then correct the attribute mapping in the OLAP Catalog tables.
XOQ-01421: A hierarchy must contain at least one level.
Cause: An MdmHierarchy was defined without any levels.
Action: Add a level to the requested MdmHierarchy using the OLAP Metadata API. If the hierarchy is read from the OLAP Catalog, then add a level to the hierarchy in the catalog table, or remove the hierarchy from the table if it is no longer relevant.
XOQ-01422: Hierarchy does not match hierarchy map: hierarchy map does not contain level map for "(string)".
Cause: The levels contained in an MdmHierarchy were inconsistent with the level maps contained in the corresponding MtmHierarchyMap.
Action: Use the OLAP Metadata API to correct the hierarchy or hierarchy map so they are consistent.
XOQ-01423: Hierarchy does not match hierarchy map: hierarchy does not contain level "(string)".
Cause: The levels contained in an MdmHierarchy are inconsistent with the level maps contained in the corresponding MtmHierarchyMap.
Action: Use the OLAP Metadata API to correct the hierarchy or hierarchy map so they are consistent.
XOQ-01424: Hierarchy must be declared skip-level, because it contains level expressions that can be null.
Cause: One of the MtmLevelMaps of an MdmHierarchy was defined by a level expression that can be null. Hierarchies containing levels with nullable expressions must be declared skip-level.
Action: Either set the MtmHierarchyMap to be skip-level using the OLAP Metadata API, or declare the expression for the MtmLevelMap as not nullable.
XOQ-01431: Primary dimension must have at least one hierarchy.
Cause: An MdmPrimaryDimension was defined without any hierarchies.
Action: Add a hierarchy to the requested MdmPrimaryDimension using the OLAP Metadata API. If the primary dimension is read from the OLAP Catalog, then add a hierarchy to the primary dimension in the catalog table, or remove the primary dimension from the table if it is no longer relevant.
XOQ-01432: Primary dimension and union hierarchy map are inconsistent: union hierarchy map does not contain hierarchy map for "(string)".
Cause: The hierarchies contained in an MdmPrimaryDimension were inconsistent with the hierarchy maps contained in the corresponding MtmPrimaryDimensionMap.
Action: Use the OLAP Metadata API to correct the MdmPrimaryDimension or MtmPrimaryDimensionMap so they are consistent.
XOQ-01433: Primary dimension and union hierarchy map are inconsistent: primary dimension does not contain hierarchy "(string)".
Cause: The hierarchies contained in an MdmPrimaryDimension were inconsistent with the hierarchy maps contained in the corresponding MtmPrimaryDimensionMap.
Action: Use the OLAP Metadata API to correct the MdmPrimaryDimension or MtmPrimaryDimensionMap so they are consistent.
XOQ-01434: Time dimension must have EndDate and TimeSpan attributes.
Cause: A time dimension did not have an EndDate or a TimeSpan attribute.
Action: Create an EndDate and a TimeSpan attribute using the OLAP Metadata API, and add them to the time dimension using the appropriate functions. If the time dimension already has an EndDate and a TimeSpan attribute, then ensure that they have been added to the time dimension. If the time dimension is read from the OLAP Catalog, then define the EndDate and TimeSpan attributes in the catalog.
XOQ-01441: Measure does not contain cube dimension "(string)".
Cause: An MdmMeasure and its associated MtmPartitionedCube contained different sets of dimensions.
Action: Use the OLAP Metadata API to correct the MdmMeasure or the MtmPartitionedCube so they are consistent. If the measure and cube are read from the OLAP Catalog, then ensure that the dimensions are consistent in the catalog.
XOQ-01442: Measure contains dimension "(string)", which does not exist on the cube.
Cause: An MdmMeasure and its associated MtmPartitionedCube contained different sets of dimensions.
Action: Use the OLAP Metadata API to correct the MdmMeasure or the MtmPartitionedCube so they are consistent. If the measure and cube are read from the OLAP Catalog, then ensure that the dimensions are consistent in the catalog.
XOQ-01443: Measure contains dimension "(string)", which is not a primary dimension.
Cause: An MdmMeasure referred to dimensions that were not primary dimensions.
Action: Use the OLAP Metadata API to change the MdmMeasure to refer to primary dimensions. If the measure is read from the OLAP Catalog, then change the catalog so the MdmMeasure refers only to primary dimensions.
XOQ-01444: Cube is not partitioned.
Cause: An MtmMeasureMap referred to an MtmBaseCube instead of an MtmPartitionedCube.
Action: Use the OLAP Metadata API to change the MtmMeasureMap to refer to an MtmPartitionedCube. If the measure is read from the OLAP Catalog, then change the catalog so the MtmMeasureMap refers to the MtmPartitionedCube.
XOQ-01445: Measure is not a member of its partitioned cube.
Cause: An MtmMeasureMap referred to an MtmPartitionedCube as its owner, but the MtmPartitionedCube does not include the MtmMeasureMap among its measures.
Action: Use the OLAP Metadata API to add the MtmMeasureMap as a member to its MtmPartitionedCube. If the measure is read from the OLAP Catalog, then correct the catalog so the MtmPartitionedCube refers to the MtmMeasureMap.
XOQ-01446: Measure has no mapping for cube "(string)".
Cause: An MtmMeasureMap contained no mapped expressions for the requested MtmBaseCube, and it did not have a default mapped expression.
Action: Use the OLAP Metadata API to create an expression that provides the measure value for the required MtmBaseCube. Add the expression to the MtmMeasureMap as a mapping for the given MtmBaseCube. If the measure is read from the OLAP Catalog, then correct the measure mapping in the OLAP Catalog tables.
XOQ-01461: Partitioned cube has no base cube for hierarchy combination ("(string)").
Cause: A partitioned cube had no base cube for the requested hierarchy combination.
Action: Use the OLAP Metadata API to create a base cube for the required hierarchy combination. If the cube is read from the OLAP Catalog, then add a base cube to the partitioned cube in the OLAP Catalog tables.
XOQ-01462: Partitioned cube does not contain measure "(string)".
Cause: A partitioned cube and one of its base cubes referred to different sets of measure maps.
Action: Use the OLAP Metadata API to add or remove measure maps as necessary to make the partitioned cube consistent with all of its base cubes. If the cube is read from the OLAP Catalog, then correct the cube in the OLAP Catalog tables.
XOQ-01463: Base cube does not contain measure "(string)".
Cause: A partitioned cube and one of its base cubes referred to different sets of measure maps.
Action: Use the OLAP Metadata API to add or remove measure maps as necessary to make the partitioned cube consistent with all of its base cubes. If the cube is read from the OLAP Catalog, then correct the base cube in the OLAP Catalog tables.
XOQ-01464: Partitioned cube does not contain dimension "(string)".
Cause: A partitioned cube and one of its base cubes referred to different sets of dimension maps.
Action: Use the OLAP Metadata API to add or remove dimension maps as necessary to make the partitioned cube consistent with all of its base cubes. If the cube is read from the OLAP Catalog, then correct its dimensions in the OLAP Catalog tables.
XOQ-01465: Base cube does not contain dimension "(string)".
Cause: A partitioned cube and one of its base cubes referred to different sets of dimension maps.
Action: Use the OLAP Metadata API to add or remove dimension maps as necessary to make the partitioned cube consistent with all of its base cubes. If the cube is read from the OLAP Catalog, then correct its dimensions in the OLAP Catalog tables.
XOQ-01466: Base cube does not contain dimension for dimensionality "(string)".
Cause: A base cube's dimensionalities contained a set of dimension maps that was inconsistent with the base cube's set of dimension maps.
Action: Use the OLAP Metadata API to add or remove dimension maps or dimensionalities as necessary to make the sets of dimension maps consistent. If the cube is read from the OLAP Catalog, then correct its dimensionalities in the OLAP Catalog tables.
XOQ-01467: Base cube does not contain dimensionality for dimension "(string)".
Cause: A base cube's dimensionalities contained a set of dimension maps that was inconsistent with the base cube's set of dimension maps.
Action: Use the OLAP Metadata API to add or remove dimension maps or dimensionalities as necessary to make the sets of dimension maps consistent. If the cube is read from the OLAP Catalog, then correct its dimensionalities in the OLAP Catalog tables.
XOQ-01468: Base cube solved status does not match dimensionality "(string)" solved status.
Cause: A base cube was solved, but one of its dimensionalities was unsolved, or the reverse.
Action: Use the OLAP Metadata API to correct the inconsistency. If the cube is read from the OLAP Catalog, then correct its dimensionalities in the OLAP Catalog tables.
XOQ-01481: Dimension "(string)" appears in multiple aggregation steps.
Cause: Every dimension in the cube must appear in one and only one aggregation step.
Action: Use the OLAP Metadata API to remove the extraneous aggregation steps from the cube. If the cube is read from the OLAP Catalog, then correct its aggregation specification in the OLAP Catalog tables.
XOQ-01482: no aggregation step found for dimension "(string)"
Cause: A dimension did not have an aggregation step. Every dimension in the cube must appear in one and only one aggregation step.
Action: Use the OLAP Metadata API to add an appropriate aggregation step to the cube. If the cube is read from the OLAP Catalog, then correct its aggregation specification in the OLAP Catalog tables.
XOQ-01483: Invalid aggregation step for dimension "(string)": Dimension is not part of the cube.
Cause: An aggregation step referred to a dimension that was not a dimension of the cube.
Action: Use the OLAP Metadata API to remove the extraneous aggregation steps from the cube. If the cube is read from the OLAP Catalog, then correct its aggregation specification in the OLAP Catalog tables.
XOQ-01484: Cannot modify "string" while in a branch in a way that invalidates its materialized view.
Cause: A change was attempted in a branch to an object that had an associated materialized view. The change would invalidate that materialized view.
Action: Disable the materialized view on the object before creating the branch.
XOQ-01485: Cannot modify "string" in the branch, because its analytic workspace is not in the branch.
Cause: A modification was attempted on an object whose analytic workspace had not been added to the branch.
Action: Add the associated analytic workspace to the branch.
XOQ-01486: Consistent solve has two aggregation steps over dimension "string".
Cause: A consistent solve had more than one aggregation steps over the dimension.
Action: Modify the consistent solve to remove or replace one of the aggregation steps.
XOQ-01487: Consistent solve has two precompute models over dimension "string".
Cause: A consistent solve had more than one precompute model over the dimension.
Action: Modify the consistent solve to remove or replace one of the precompute models.
XOQ-01488: Consistent solve has two dynamic models over dimension "string".
Cause: A consistent solve had more than one dynamic model over the dimension.
Action: Modify the consistent solve to remove or replace one of the dynamic models.
XOQ-01489: Consistent solve has a model "string" with invalid explicit dimension "string".
Cause: An explicit dimension of a model in a consistent solve was not a dimension of the cube and measure.
Action: Modify the consistent solve to remove or replace this model.
XOQ-01490: Consistent solve has a model "string" with invalid base dimension "string".
Cause: The base dimension of a model in a consistent solve was not a dimension of the cube and measure.
Action: Modify the consistent solve to remove or replace this model.
XOQ-01491: Consistent solve has an invalid aggregation step over dimension "string".
Cause: The aggregation step for a consistent solve was not over a dimension of the cube and measure.
Action: Modify the consistent solve to remove or replace this aggregation step.
XOQ-01492: invalid order of steps for consistent solve
Cause: A consistent solve did not list precompute models first, then aggregation steps, and dynamic models last.
Action: Reorder the steps in the consistent solve or remove some of the steps.
XOQ-01493: Invalid specification for dimension "string" in precompute condition for cube "string"
Cause: The precompute condition contained an invalid specification. When a precompute percent is also specified, the precompute condition can specify only that the last dimensions in the cube's consistent solve specification are not precomputed.
Action: Remove the cube's precompute condition or precompute percent, or rewrite the cube's precompute condition so that it specifies only NONE for dimensions at the end of the cube's consistent solve specification.
XOQ-01494: invalid target dimension or attribute "string"
Cause: The attribute and its target dimension or attribute were in different analytic workspaces.
Action: Remove the attribute's target, or specify a target dimension or attribute that is in the same analytic workspace.
XOQ-01495: cannot specify both a target attribute "string" and a target dimension "string"
Cause: The attribute has both a target dimension and a target attribute.
Action: Remove either the attribute's target dimension or its target attribute.
XOQ-01496: loaded data incompatible with data type "string"
Cause: A data type change could not be made because data loaded for the object could not be represented by the data type.
Action: Clear the data prior to making the data type change.
XOQ-01497: Data type "string" is not allowed for an indexed attribute.
Cause: An invalid data type was specified for an indexed attribute.
Action: Either change the data type or set CreateIndex to False, set PopulateLineage to False, remove any target attributes or target dimensions from the attribute, and remove the attribute from the list of UniqueKeyAttributes in all dimension levels.
XOQ-01498: Calculation model "string" specifies invalid explicit dimension "string".
Cause: A dimension calculation model specified the owning dimension as an explicit dimension.
Action: Remove the owning dimension from the calculation model's explicit dimensions.
XOQ-01499: Measure folder "string" cannot appear twice in a sequence of nested folders.
Cause: A measure folder was nested under itself as a subfolder.
Action: Remove the nested subfolder.
XOQ-01600: string XOQ-01600: OLAP DML error while executing DML "string"
Cause: An OLAP DML expression in an analytic workspace failed.
Action: This is an unexpected error. Examine the rest of the error stack for more details.
XOQ-01601: error while loading data for string "string" into the analytic workspace
Cause: An error occurred while executing a generated SQL statement and loading the result into the analytic workspace. The error could be caused by bad SQL or bad data.
Action: Examine the rest of the error stack for more details. If build logging is enabled, the SQL will be displayed in the OUTPUT column of the cube build log.
XOQ-01700: Cube "string" is not part of an analytic workspace.
Cause: The cube was not built because it was not deployed in an analytic workspace.
Action: Remove the cube from the list of objects in the build process, or deploy the cube in an analytic workspace.
XOQ-01701: Dimension "string" is not part of an analytic workspace.
Cause: The dimension was not built because it is not deployed in an analytic workspace.
Action: Remove the dimension from the list of objects in the build process, or deploy the dimension in an analytic workspace.
XOQ-01702: Objects from multiple analytic workspaces cannot be built in a single process.
Cause: A single build process contained objects from more than one analytic workspace.
Action: Change the build process to include objects in only a single analytic workspace.
XOQ-01703: error during parse of build process script: "string", "string"
Cause: The current build process failed because of an error in the build script.
Action: Correct the error in the script.
XOQ-01704: unknown model "string"
Cause: The current build process failed because the model in the build script does not exist.
Action: Change the build script to refer to an actual model.
XOQ-01705: CLEAR command cannot run on a dimension.
Cause: A CLEAR command is in a build specification for a dimension.
Action: Remove the CLEAR command.
XOQ-01706: An unexpected condition occurred during the build: "string".
Cause: An internal error occurred during the build.
Action: Report this error to Oracle Support Services.
XOQ-01707: Oracle job "string" failed while executing slave build "string" with error "string".
Cause: of the failure.
Action: Examine the trace file for the slave build to determine the
XOQ-01708: SOLVE command cannot run on a dimension.
Cause: A SOLVE command was in a build specification for a dimension.
Action: Remove the SOLVE command.
XOQ-01709: string command cannot run on a cube.
Cause: An invalid build command was in a build specification for a cube.
Action: Remove the invalid build command.
XOQ-01710: unknown build item "string"
Cause: A build item was not a cube or a dimension.
Action: Check the list of build items to ensure that they are all valid.
XOQ-01711: Aggregation path for hierarchies on dimension "string" is inconsistent.
Cause: The definition of parents was ambiguous among hierarchies, or a loop was defined within a hierarchy.
Action: Fix the mappings or delete the hierarchies.
XOQ-01712: "string" failed validation as a level hierarchy.
Cause: A member of the hierarchy had one of these problems: 1) The member's level was not part of the hierarchy. 2) The member's parent was at the same or a lower level of the hierarchy.
Action: Redefine the hierarchy as a value hierarchy or fix the level mappings.
XOQ-01713: "string" failed validation as a non-skip-level hierarchy.
Cause: A member of the hierarchy had one of these problems: 1) The member had no parent but was not in the top level of the hierarchy. 2) The member's parent was two or more levels above in the hierarchy.
Action: Mark the hierarchy as a skip-level hierarchy or fix the level mappings.
XOQ-01714: "string" failed validation as a non-ragged hierarchy.
Cause: A member of the hierarchy had no children but was not in the lowest level of the hierarchy.
Action: Mark the hierarchy as a ragged hierarchy or fix the level mappings.
XOQ-01715: Hierarchy "string" has no members for some levels.
Cause: No members existed for some levels defining this hierarchy.
Action: Fix the mappings or the hierarchy definition.
XOQ-01716: Definition of a hierarchy "string" does not allow raggedness.
Cause: Leaf members of a hierarchy were on different levels.
Action: Fix the mappings or the hierarchy definition.
XOQ-01717: illegal parent for calculated member "string"
Cause: The parent for this member was not a member of a dimension or hierarchy.
Action: Fix the calculated member parent data.
XOQ-01718: A calculated member "string" and its parent have inconsistent level definitions.
Cause: Levels of a calculated member and its parent are inconsistent with the current hierarchy.
Action: Fix level data for a calculated member or its parent.
XOQ-01719: incorrect level for a calculated member "string"
Cause: The level of a calculated member was invalid, or it was not in this hierarchy level.
Action: Fix the level data for the calculated member.
XOQ-01720: Calculated members in hierarchy "%(1)" cannot be organized.
Cause: A loop existed among calculated members.
Action: Fix the parent data for calculated members to remove the loop.
XOQ-01721: ValueHierarchy "string" does not have unique keys.
Cause: AddUniqueKeyPrefix was set to True on an AWPrimaryDimensionOrganization, and a load was attempted on a ValueHierarchy.
Action: Do one of the following: 1) Perform the load on DimensionLevels. 2) If the keys are in fact unique, then set AddUniqueKeyPrefix on the AWPrimaryDimensionOrganization to False.
XOQ-01722: Cube "string" mapping to "string" is invalid. Cubes must map to DimensionLevels for PrimaryDimensions whose keys are not unique.
Cause: AddUniqueKeyPrefix was set to True on an AWPrimaryDimensionOrganization, and a cube was not mapped to a DimensionLevel.
Action: Either map the cube to a DimensionLevel or, if the keys are in fact unique, set AddUniqueKeyPrefix on the AWPrimaryDimensionOrganization to False.
XOQ-01723: CLEAR AGGREGATES command cannot run within a FOR...BUILD group.
Cause: A CLEAR AGGREGATES command was found within a FOR...BUILD group as part of a build.
Action: Change the command to CLEAR VALUES or remove it from the FOR...BUILD group.
XOQ-01724: invalid USING clause
Cause: An invalid USING clause was specified on a cube or cube dimension with an associated materialized view.
Action: Specify a valid USING clause or omit the USING clause.
XOQ-01725: unknown named build specification "string"
Cause: A USING clause specified an unknown named build specification."
Action: Ensure that the name in the USING clause is correct.
XOQ-01726: The partition dimension "string" in cube "string" is missing an ET view.
Cause: The partition dimension was missing an embedded totals view. This may have been caused by using EIF import to create the analytic workspace."
Action: Ensure that the partition dimension has an ET view.
XOQ-01727: Specified refresh method "string" is invalid.
Cause: An invalid refresh method was specified for a build.
Action: Specify a valid refresh method.
XOQ-01728: Atomic refresh is not supported.
Cause: Multiple objects were specified in the build script, or the add_dimensions flag was set to true. Atomic refresh is not supported for builds involving two or more cube materialized views.
Action: Specify the atomic parameter as false, or build the objects individually.
XOQ-01729: Explicit SCN build is not allowed.
Cause: A build involving cube materialized views specified AS OF SCN for a build.
Action: Remove explicit SCN from the build script.
XOQ-01730: Refresh method "string" requires a suitable materialized view.
Cause: The cube was not associated with a FAST or REWRITE materialized view, as required by the specified refresh method.
Action: Change the refresh method or the type of materialized view associated with the cube.
XOQ-01731: Atomic build is not supported in a branch.
Cause: An atomic build was requested while there was an active branch in the session.
Action: Either run the build without the atomic setting or close the branch.
XOQ-01732: Object "string" cannot build in a branch because it has a materialized view.
Cause: A build was attempted in a branch on an object that has an associated materialized view.
Action: Turn off the materialized view on the object before creation of a branch.
XOQ-01733: Invalid cube map "string" is specified in a LOAD command.
Cause: A FROM clause was specified in a LOAD command that does not correspond to any cube map in the build cube.
Action: Remove the FROM clause or specify a valid cube map.
XOQ-01734: Time dimension "string" is specified in a COMPILE command, but attribute "string" on level "string" has no mapping.
Cause: One of the following attributes was specified but not mapped: END_DATE, START_DATE, or TIMESPAN.
Action: Define a mapping for the unmapped attribute.
XOQ-01735: Cube cannot be refreshed because dimension "string" is stale.
Cause: An attempt was made to refresh a cube with a materialized view when one of the cube's dimensions has a stale materialized view.
Action: Refresh the dimension's materialized view before refreshing the cube.
XOQ-01736: Cube "string" cannot be aggregated because it is compressed.
Cause: An attempt was made to run a nonconsistent solve aggregation on a compressed cube. This is not supported.
Action: Redefine the cube to be noncompressed or do not attempt to run the aggregation.
XOQ-01737: FAST_SOLVE cannot be used to build cube "string". Build must use COMPLETE.
Cause: An attempt was made to use FAST_SOLVE build on a cube that must use a COMPLETE build (for example, an initial build).
Action: Use a FORCE or a COMPLETE build on the cube.
XOQ-01738: Level of dimension member "string" cannot change from "string" to "string" within a single load.
Cause: A dimension member was mapped to more than one level.
Action: Change the mapping so each dimension member is mapped to only one level.
XOQ-01739: Unknown or invalid measure "string" is specified in an assignment.
Cause: The target of an assignment was specified as a measure that was not part of the cube being built.
Action: Specify a valid measure of the cube as the assignment target.
XOQ-01740: Unknown or invalid dimension "string" is specified in an assignment.
Cause: The target of an assignment was qualified by a dimension that was not part of the cube or attribute being built.
Action: Specify a valid dimension of the cube or attribute.
XOQ-01741: unsupported assignment qualification for dimension "string"
Cause: The target of an assignment was qualified by something other than a literal text value.
Action: Specify a literal text value for the qualified dimension member.
XOQ-01742: NO COMMIT option cannot be specified on build "string".
Cause: The NO COMMIT option was specified on a build that includes cubes backed by materialized views or that has non zero parallelism.
Action: Do not specify the NO COMMIT option for this build.
XOQ-01743: Cannot apply automatic order because circular dependency exists between build objects "string" and "string".
Cause: The build objects contained two or more metadata objects that depend on each other.
Action: Either do not specify automatic order, or remove one of the properties that cause the circular dependency.
XOQ-01744: The LOAD PRUNE command cannot be used with cube "string".
Cause: A build specification contained a LOAD PRUNE command for a cube that did not support the PRUNE option. To be compatible with the LOAD PRUNE command, a cube must have exactly one CubeMap; the CubeMap must contain a CubeDimensionalityMap for the partition dimension; the CubeDimensionalityMap for the partition dimension must specify a MappedDimension; and the MappedDimension object must contain a DimensionMap.
Action: Remove the PRUNE option from the LOAD command.
XOQ-01745: Unknown or invalid hierarchy "string" is specified in a maintain dimension command.
Cause: The hierarchy specified in a maintain dimension command was not part of the dimension being built.
Action: Specify a valid hierarchy of the dimension in the maintain dimension command.
XOQ-01746: Unknown or invalid level "string" is specified in a maintain dimension command.
Cause: The level specified in a maintain dimension command was not part of the dimension being built.
Action: Specify a valid level of the dimension in the maintain dimension command.
XOQ-01747: Dimension member "string" is not a valid member of dimension "string".
Cause: The member specified in the maintain dimension command was not a valid member of the dimension.
Action: Specify a valid member in the maintain dimension command.
XOQ-01748: Dimension member "string" is already a member of dimension "string".
Cause: The member specified in the dimension insert command was already a member of the dimension.
Action: Change the dimension insert command to a dimension merge command.
XOQ-01749: Dimension member "string" is not a member of dimension "string".
Cause: The member specified in the dimension update or dimension delete command was not a member of the dimension.
Action: Specify an existing member of the dimension in the dimension update or dimension delete command.
XOQ-01750: Dimension member "string" is already a member of hierarchy "string".
Cause: The member specified in the dimension insert command was already a member of the hierarchy.
Action: Change the dimension insert command to a dimension merge command.
XOQ-01751: Dimension member "string" is not a member of hierarchy "string".
Cause: The member specified in the dimension update or dimension delete command was not a member of the hierarchy.
Action: Specify an existing member of the hierarchy in the dimension update or dimension delete command.
XOQ-01752: Member "string" appears both in level "string" and in level "string" of dimension "string".
Cause: A modification to a dimension member was attempted that would cause the member to belong to two different levels.
Action: Change the maintain dimension command to modify the level of all hierarchies to which the dimension member belongs.
XOQ-01753: Unknown or invalid attribute "string" is specified in an assignment.
Cause: The target of an assignment was specified as an attribute that was not part of the dimension being built.
Action: Specify a valid attribute of the dimension as the assignment target.
XOQ-01754: SOLVE command cannot run on a subset of cube measures when sparse type is COMPRESSED and measure storage is INDEPENDENT.
Cause: The build specification contains a partial list of cube measures with COMPRESSED cube sparsity and INDEPENDENT measure storage.
Action: Correct the build specification in one of these ways: Remove the SOLVE command, list all measures of the cube, or build the entire cube.
XOQ-01799: unspecified error
Cause: A mismatch existed between the C++ and the OLAP DML versions of the code.
Action: Verify the installation of the product.
XOQ-01800: ALTER privilege is required on object "string" in schema "string".
Cause: An attempt was made to modify a metadata object without having the ALTER privilege on that object.
Action: Request the ALTER privilege on the object from the DBA.
XOQ-01801: CREATE privilege is required for object "string" in schema "string".
Cause: An attempt was made to create a new metadata object without the necessary privileges.
Action: Request the CREATE ANY privilege to create the object in any schema or the CREATE privilege to create it only in your own schema.
XOQ-01802: DROP privilege is required for object "string" in schema "string".
Cause: An attempt was made to delete a metadata object without the DROP privilege on that object.
Action: Request the DROP privilege on the object from the DBA.
XOQ-01803: SELECT privilege is required for object "string" in schema "string".
Cause: An attempt was made to read a metadata object without the SELECT privilege on that object.
Action: Request the SELECT privilege on the object from the DBA.
XOQ-01900: The dimension level has invalid or no unique key attributes.
Cause: The dimension level had an associated materialized view, but it had no unique key attributes.
Action: Create at least one unique key attribute.
XOQ-01901: No measures or dimensionalities are in the cube.
Cause: Measures and dimensionalities were not added to the cube.
Action: Add at least one measure or dimensionality to the cube.
XOQ-01902: No analytic workspace is specified in the analytic workspace primary dimension organization.
Cause: An analytic workspace was not added to the analytic workspace primary dimension organization.
Action: Add an analytic workspace to the analytic workspace primary dimension organization.
XOQ-01903: The unique key attribute has no corresponding base attribute.
Cause: A dimension level whose primary dimension had an associated materialized view contained a unique key attribute that did not have an associated base attribute.
Action: Create a base attribute that corresponds to the unique key attribute.
XOQ-01904: The dimension level has no base attributes.
Cause: A dimension level whose primary dimension had an associated materialized view did not have base attributes.
Action: Create base attributes that correspond to the unique key attributes of the dimension level.
XOQ-01905: GenerateRefreshMV is not specified in AWCubeOrganization.
Cause: The AWCubeOrganization was not marked for a refresh materialized view, but it was marked for rewrite materialized view.
Action: Set GenerateRefreshMV on the AWCubeOrganization if it has been marked for GenerateRewriteMV.
XOQ-01906: The analytic workspace referenced by the AWCubeOrganization does not match that of analytic workspace primary dimension organization "string".
Cause: The analytic workspace referred to by the AWCubeOrganization did not match that of its corresponding analytic workspace primary dimension organization.
Action: Set the analytic workspace of the AWCubeOrganization to match that of its corresponding analytic workspace primary dimension organization.
XOQ-01907: The AWCubeOrganization is marked for GenerateRefreshMV, but analytic workspace primary dimension organization "string" is not.
Cause: The AWCubeOrganization was marked for GenerateRefreshMV.
Action: If the AWCubeOrganization is marked for GenerateRefreshMV, then mark the analytic workspace primary dimension organization also.
XOQ-01908: The cube has no dimensionalities.
Cause: The AWCubeOrganization was marked for GenerateRefreshMV, but there were no dimensionalities.
Action: Add dimensionalities to the cube and mark the analytic workspace primary dimension organization for GenerateRefreshMV.
XOQ-01909: The hierarchy level has an invalid or no associated dimension level.
Cause: Either a dimension level was not created on the primary dimension, or the primary dimension on the dimension level was not the same as the primary dimension on the hierarchy.
Action: Assure that the hierarchy level is associated with exactly one dimension level in the same primary dimension.
XOQ-01910: The level hierarchy has no hierarchy levels.
Cause: Hierarchy levels were not created on the level hierarchy.
Action: Create at least one level for the hierarchy.
XOQ-01911: The specified default hierarchy does not exist.
Cause: A default hierarchy was specified, but it was not created.
Action: Create a hierarchy on the primary dimension, then set it as the default hierarchy.
XOQ-01912: The cube has no organization.
Cause: Neither an AWCubeOrganization nor a ROLAP cube organization existed on the cube.
Action: Create either an AWCubeOrganization or ROLAP cube organization on the cube.
XOQ-01913: The base measure has an invalid or no data type specified.
Cause: A SQL data type on the base measure was either not specified or invalid.
Action: Create a valid SQL data type on the base measure.
XOQ-01914: The primary dimension has no organization.
Cause: Neither an analytic workspace primary dimension organization nor a ROLAP primary dimension organization existed on the primary dimension.
Action: Create either an analytic workspace primary dimension organization or ROLAP primary dimension organization on the primary dimension.
XOQ-01915: The hierarchy level has no hierarchy level map.
Cause: A hierarchy level map did not exist on the hierarchy level.
Action: Create a hierarchy level map for the hierarchy levels of dimensions with associated materialized views.
XOQ-01916: The AWCubeOrganization has no analytic workspace.
Cause: An analytic workspace was not specified for the AWCubeOrganization.
Action: Create an analytic workspace for AWCubeOrganization in which the cube will be deployed.
XOQ-01917: The base attribute has an invalid or no data type specified.
Cause: A SQL data type on the base attribute was either not specified or invalid.
Action: Create a valid SQL data type on the base attribute.
XOQ-01918: The sparse type must be COMPRESSED when the AWCubeOrganization is marked for GenerateRefreshMV.
Cause: When the AWCubeOrganization was marked for GenerateRefreshMV, the sparse type was not COMPRESSED.
Action: Set the sparse type to COMPRESSED on the AWCubeOrganization.
XOQ-01919: The sparse dimensions of the AWCubeOrganization must contain all dimensions or none.
Cause: The sparse dimensions did not contain either all dimensions or none, although the AWCubeOrganization was marked for GenerateRefreshMV.
Action: Set sparse dimensions on the AWCubeOrganization to include all the dimensions or none.
XOQ-01920: Sparse dimensions of the AWCubeOrganization must be specified with a subset of the cube dimensionalities.
Cause: The sparse dimensions did not specify a subset of the cube dimensionalities, although the AWCubeOrganization was not marked for GenerateRefreshMV.
Action: Set sparse dimensions on the AWCubeOrganization to include a subset of the cube dimensionalities.
XOQ-01921: The dimensionality does not reference a primary dimension.
Cause: A primary dimension was not specified on the dimensionality.
Action: Set the primary dimension on the dimensionality.
XOQ-01922: The dimension referenced in dimensionality "string" is specified more than once in this cube.
Cause: Duplicate dimensions were specified in the dimensionality of the cube.
Action: Remove duplicate dimensionality specifications.
XOQ-01923: Assignment "string" has no member expression and does not correspond to a custom member.
Cause: An expression or a custom member was missing in the assignment.
Action: Specify an expression for the assignment, or check that its name corresponds to a known custom member.
XOQ-01924: Custom member "string" has no member expression.
Cause: An expression was missing in the custom member.
Action: Specify an expression for the custom member.
XOQ-01925: PrecomputePercent cannot be used with this cube.
Cause: PrecomputePercent can be used only with a compressed cube.
Action: Remove the PrecomputePercent property from this cube.
XOQ-01926: PrecomputePercentTop cannot be used with this cube.
Cause: PrecomputePercentTop can be used only with a compressed partitioned cube.
Action: Remove the PrecomputePercentTop property from this cube.
XOQ-01927: invalid PrecomputePercent value
Cause: PrecomputePercent value was not in the valid range. A PrecomputePercent value must be between 0 and 100, and if the cube has a secondary partition level then the PrecomputePercent value cannot be 0.
Action: Change the PrecomputePercent value.
XOQ-01928: invalid PrecomputePercentTop value
Cause: PrecomputePercentTop value was not in the valid range between 0 and 100.
Action: Change the PrecomputePercentTop value.
XOQ-01929: incompatible values for PrecomputePercent and PrecomputePercentTop
Cause: A PrecomputePercentTop value can be greater than 0 only when the PrecomputePercent value is greater than 0.
Action: Change the PrecomputePercent value or the PrecomputePercentTop value.
XOQ-01930: The cube dimensionality map has no mapped dimension.
Cause: A mapped dimension was not specified for the cube dimensionality map.
Action: Specify a mapped dimension on the cube dimensionality map. The mapped dimension must be the dimension or hierarchy level that corresponds to the mapped data.
XOQ-01931: MeasureStorage is incompatible with MVoption.
Cause: MeasureStorage was defined as SHARED.
Action: Specify MeasureStorage as INDEPENDENT.
XOQ-01932: NullStorage is incompatible with MVoption.
Cause: NullStorage was defined as GENERIC.
Action: Specify NullStorage as MV_READY.
XOQ-01933: invalid list of sparse dimensions
Cause: List of sparse dimensions was not contiguous among all cube dimensions.
Action: Change the order of the cube dimensions.
XOQ-01934: Sparse dimensions are not last.
Cause: Sparse dimensions were not last in the list cube dimensions, as required for compressed cubes.
Action: Change the order of the cube dimensions.
XOQ-01935: invalid definition of SPARSE_GLOBAL cube
Cause: SPARSE_GLOBAL cube must have at least two dimensions, at least one sparse dimension, and partitions.
Action: Change the definition of the cube.
XOQ-01936: invalid partition dimension for SPARSE_GLOBAL cube
Cause: SPARSE_GLOBAL cube cannot have a sparse partition dimension.
Action: Change the definition of the cube.
XOQ-01937: incompatible HierarchyConsistencyRule and MVOption
Cause: HierarchyConcistencyRule must be set to STAR_CONSISTENT for this MVOption.
Action: Change the HierarchyConsistencyRule.
XOQ-01938: PrecomputeCondition cannot be used with this cube.
Cause: PrecomputeCondition was used with a compressed cube, but it requires an uncompressed cube.
Action: Remove PrecomputeCondition property from this cube.
XOQ-01939: MappedDimension "string" specified for a CubeDimensionalityMap is not mapped.
Cause: The MappedDimension property of a CubeDimensionalityMap pointed to a dimension that was not mapped.
Action: Change the MappedDimension property to reference a dimension that is mapped, or add a map to the current MappedDimension. For example, if MappedDimension points to a DimensionLevel, then the DimensionLevel must contain a MemberListMap.
XOQ-01940: BaseAttribute "string" is specified on a DimensionLevel as both a UniqueKeyAttribute and a VisibleAttribute.
Cause: A BaseAttribute on a DimensionLevel can be specified as either a UniqueKeyAttribute or a VisibleAttribute, but not both.
Action: Remove either the Visible or the UniqueKey setting for the attribute.
XOQ-01941: The HierarchyLevelMap for HierarchyLevel "string" must contain a KeyExpression and a Query.
Cause: HierarchyLevelMap missing a KeyExpression, Query, or both.
Action: Specify a KeyExpression and Query for the HierarchyLevelMap.
XOQ-01942: A BaseAttribute cannot be removed while it is a UniqueKeyAttribute on DimensionLevel "string".
Cause: The BaseAttribute is a UniqueKeyAttribute of a DimensionLevel.
Action: Remove the attribute as a UniqueKeyAttribute.
XOQ-01943: An AttributeMap refers to a nonexistent attribute.
Cause: An AttributeMap referred to a nonexistent attribute.
Action: Ensure all AttributeMaps point to an existing attribute.
XOQ-01944: BaseAttribute "string" already exists on this dimension object.
Cause: A BaseAttribute was added to a dimension object more than once.
Action: Do not add the same BaseAttribute to a dimension object.
XOQ-01945: The cube dimensionality map has no join condition.
Cause: A join condition was not specified for the CubeDimensionalityMap.
Action: Specify a join condition on the cube dimensionality map.
XOQ-01946: BaseAttribute "string" is mapped by more than one attribute map.
Cause: A BaseAttribute was mapped more than once.
Action: Do not map the same BaseAttribute more than once.
XOQ-01947: Measure "string" is mapped by more than one MeasureMap.
Cause: A measure was mapped more than once.
Action: Do not map the same measure more than once.
XOQ-01948: CubeDimensionality "string" is mapped by more than one CubeDimensionalityMap.
Cause: A cube dimensionality was mapped more than once.
Action: Do not map the same cube dimensionality more than once.
XOQ-01949: The AWCubeOrganization for cube "string" is marked as DENSE but contains SPARSE dimensions.
Cause: The AWCubeOrganization was marked as DENSE but contained SPARSE dimensions.
Action: Either mark the cube as SPARSE, or remove the SPARSE dimensions.
XOQ-01950: The AWCubeOrganization for cube "string" contains multiple BuildSpecifications with the same name.
Cause: The AWCubeOrganization contains multiple BuildSpecifications with the same name.
Action: Ensure all BuildSpecifications on an AWCubeOrganization are named uniquely.
XOQ-01951: A time dimension requires at least two of the following attributes: END_DATE, START_DATE and TIMESPAN.
Cause: A time dimension was created without the required attributes.
Action: Add the required attributes and mark them as the appropriate type.
XOQ-01952: The CubeMap for cube "string" must contain either a query or a From clause.
Cause: The CubeMap did not have a query or From clause.
Action: Specify a query or From clause for the CubeMap.
XOQ-01953: cannot commit changes to CWM or AWXML metadata
Cause: The transaction contained changes to metadata objects stored in CWM or AWXML format.
Action: Use the DBMS_CUBE.UPGRADE function to upgrade the metadata objects to a format that supports changes.
XOQ-01954: Object cannot be renamed to "string" because that name is already being used by an existing object.
Cause: The transaction attempted to change an object name to a name that was already taken.
Action: Change the object name to a different name and commit the transaction again.
XOQ-01955: Cannot rename object to "string" because that name is invalid.
Cause: The transaction attempted to change an object name to a name that was either too long or contained invalid characters.
Action: Change the object name to a different name, and commit the transaction again.
XOQ-01956: The object cannot be renamed.
Cause: The transaction attempted to change the name of a database object such as a table or a column. This object cannot be renamed through the OLAP API client. It must be renamed with a DDL statement such as RENAME or ALTER TABLE.
Action: Restore the object name to its previous value or rollback the transaction containing the rename. Then use an appropriate DDL statement to rename the object.
XOQ-01957: A cube cannot have both rewrite materialized views and either a ragged or a skip-level hierarchy. The hierarchy is "string".
Cause: The cube had rewrite materialized views and either a ragged or a skip-level hierarchy.
Action: Either mark the cube to exclude rewrite materialized views, or adjust the hierarchy so it is neither ragged nor skip-level.
XOQ-01958: The derived measure has an invalid data type or no data type.
Cause: Either a valid SQL data type was not specified on the derived measure, or the data type could not be derived from the expression.
Action: Create a valid SQL data type on the derived measure.
XOQ-01959: The derived measure has a missing or invalid expression.
Cause: An expression on the derived measure was either not specified or invalid.
Action: Create a valid expression on the derived measure.
XOQ-01960: Circular dependency exists between string "string" and string "string".
Cause: The OLAP API transaction contained two or more metadata objects that depend on each other.
Action: Remove either one or both of the properties that cause the circular dependency.
XOQ-01961: Object string "string" cannot be dropped while it is still a dependency of string "string".
Cause: An attempt was made to drop a metadata object that was referenced by another metadata object.
Action: Remove the reference to the metadata object being dropped.
XOQ-01962: Object "string" has an invalid name.
Cause: An attempt was made to create an object with a name that was too long or contained invalid characters.
Action: Use a valid name and commit the transaction again.
XOQ-01963: MappedDimension "string" does not match CubeDimensionality "string" specified for a CubeDimensionalityMap.
Cause: The MappedDimension property of a CubeDimensionalityMap did not point to a dimension or subdimension that had the same dimensionality as the CubeDimensionalityMap.
Action: Change the MappedDimension property to reference a dimension with the same dimensionality as the CubeDimensionalityMap.
XOQ-01964: Cannot drop MappedDimension "string" of the CubeDimensionalityMap.
Cause: An attempt was made to drop a dimension that is a MappedDimension of a CubeDimensionalityMap.
Action: Remove the reference to the dimension being dropped from the CubeDimensionalityMap.
XOQ-01965: Missing Cube Dimensionality Map for Cube Dimensionality "string".
Cause: A CubeDimensionalityMap was not found for a CubeDimensionality.
Action: Add a CubeDimensionalityMap for the CubeDimensionality.
XOQ-01966: Cannot drop PartitionLevel "string" of AWCubeOrganization.
Cause: An attempt was made to drop a dimension that is a PartitionLevel of an AWCubeOrganization Map.
Action: Remove the reference to the dimension being dropped from the AWCubeOrganization.
XOQ-01967: Attribute "string" is invalid.
Cause: An attempt was made to commit a dimension with an invalid attribute.
Action: Correct the attribute or delete it from the dimension.
XOQ-01968: UniqueKey attribute "string" has an invalid multilingual flag set.
Cause: The attribute had the multilingual flag set. An attribute cannot have this flag set and be a unique key.
Action: Remove this flag on the attribute or do not make the attribute a unique key.
XOQ-01969: Attribute cannot be both multilingual and indexed.
Cause: An indexed attribute had the multilingual flag set.
Action: Unset the createIndex flag on the analytic workspace attribute organization or unset the populate lineage flag on the attribute.
XOQ-01970: Attribute "string" has no attribute map.
Cause: The attribute had no corresponding attribute map on the hierarchy level.
Action: Create an attribute map on the attribute.
XOQ-01971: A dependency cannot be added on the organizationalSchema to the cube because measure "string" is invalid.
Cause: An attempt was made to commit an organizationalSchema that contained an invalid measure.
Action: Correct the measure.
XOQ-01972: A dependency cannot be added on the organizationalSchema to the cube because the cube has been deleted.
Cause: An attempt was made to commit an organizationalSchema that contained a deleted cube.
Action: Remove the cube reference from the organizationalSchema.
XOQ-01973: UniqueKey attribute "string" on the dimension level is invalid.
Cause: The uniqueKey attribute was invalid.
Action: Correct the uniqueKey attribute or delete it from the dimension level.
XOQ-01974: Attribute map "string" is invalid.
Cause: An attribute on the attribute map was invalid.
Action: Correct the attribute or delete it from the dimension.
XOQ-01975: The DimensionMap for Dimension "string" must contain either a query or a From clause
Cause: The DimensionMap did not have a query or From clause.
Action: Specify a query or From clause for the DimensionMap.
XOQ-01976: No key expression is defined on this dimension map owned by "string".
Cause: A key expression was not defined on the dimension map.
Action: Define a key expression on the dimension map.
XOQ-01977: Measure "string" does not exist in cube "string".
Cause: The measure associated with the measure map did not exist in the cube.
Action: Correct the measure map or add the measure to the cube.
XOQ-01978: The number of dimensionalities on cube "string" does not match the number of cube dimensionality maps on the cube map.
Cause: The number of cube dimensionalities did not equal the number of cube dimensionality maps on the cube map.
Action: Correct the cube dimensionality mappings.
XOQ-01979: Measure map "string" refers to an invalid measure, "string".
Cause: The measure was invalid.
Action: Correct the measure or delete it from the cube.
XOQ-01980: Dimension "string" is created before the attribute cube GID relation is added.
Cause: The dimension was created before the attribute cube GID relation was added.
Action: Add the attribute cube GID relation.
XOQ-01981: A generic metadata validation error has occurred.
Cause: An attempt was made to commit with invalid metadata.
Action: Correct the metadata.
XOQ-01982: A generic metadata validation error occurred against "string".
Cause: An attempt was made to commit with invalid metadata.
Action: Correct the metadata.
XOQ-01983: The dimension "string" is referenced more than once in the precompute list of the AWCubeOrganization.
Cause: Duplicate dimensions were specified in the precompute list of the AWCubeOrganization.
Action: Remove duplicate dimensions from the precompute list.
XOQ-01984: The dimension "string" referenced in the precompute list of the AWCubeOrganization is not part of cube "string".
Cause: A dimension specified in the precompute list of the AWCubeOrganization is not part of the cube.
Action: Remove the dimension from the precompute list.
XOQ-01985: The ET attribute prefix of "string" specified for dimension "string" of cube "string" is invalid.
Cause: The ET attribute prefix was invalid. The ET attribute prefix: 1) Must be fewer than six characters 2) Cannot be a substring of any MdmDimensionality or MdmMeasure colummn names.
Action: Correct the ET attribute prefix, or omit the prefix to use the default value.
XOQ-01986: The LevelHierarchy "string" contains more than one HierarchyLevel for DimensionLevel "string".
Cause: If HierarchyConsistencyRule is CONSISTENT or STAR_CONSISTENT, then a DimensionLevel within a LevelHierarchy can have only one HierarchyLevel.
Action: Correct the HierarchyLevels in the LevelHierarchy.
XOQ-01987: A subset of the following HierarchyLevels is ordered inconsistently in PrimaryDimension "string": "string".
Cause: If HierarchyConsistencyRule is CONSISTENT or STAR_CONSISTENT, then HierarchyLevels cannot form loops between LevelHierarchies.
Action: Eliminate the loop.
XOQ-01988: name conflict between string "string" and string "string"
Cause: Two metadata objects with the same parent had the same name. This duplication was allowed in Oracle Database 10 Release 2 (10.2) and earlier, but it is not valid for metadata objects in Oracle Database 11 Release 1 (11.1) and later.
Action: Run DBMS_CUBE.INITIALIZE_CUBE_UPGRADE which will populate a table (default name CUBE_UPGRADE_INFO) with new names to resolve the conflicts.
XOQ-01989: Level "string" is not uniquely mapped.
Cause: More than one level was mapped to the same expression. If a dimension has materialized views, it cannot have more than one level mapped to the same expression.
Action: Uniquely map all levels or create the dimension without materialized views.
XOQ-01990: Cube "string" cannot override the aggregation maps for this measure.
Cause: The consistent solve specification was invalid on the measure.
Action: Modify the cube so it is uncompressed with independent measure storage.
XOQ-01991: The data type of this measure in cube "string" or its mapped expression is incompatible with materialized views.
Cause: The data type of a numeric measure in a cube with a materialized view had restricted scale or precision.
Action: Change the data type to NUMBER without any qualifications.
XOQ-01992: The OLAP DML data type cube storage qualifications "string" in cube "string" are incompatible with materialized views.
Cause: The cube storage data type of the AWCubeOrganization with a materialized view had restricted scale or precision.
Action: Remove precision and scale restrictions on the NUMBER data type from the cube storage.
XOQ-01993: The data type of base attribute "string" or its mapped expression is incompatible with materialized views.
Cause: The data type of the attribute or its mapped expression is not supported by materialized views.
Action: Change the data type of the attribute or its mapped expression.
XOQ-01994: Primary dimension "string" and the cube have incompatible organizations.
Cause: The organizations of the primary dimension and of the cube were incompatible. If a cube has an AWCubeOrganization, then all of its primary dimensions must have analytic workspace primary dimension organizations.
Action: Create an analytic workspace primary dimension organization on the primary dimension.
XOQ-01995: Object "string" does not exist.
Cause: A cube or dimension was defined in terms of an object that does not exist.
Action: Create the missing object or redefine the cube or dimension.
XOQ-01996: The object cannot be renamed.
Cause: An attempt was made to rename an object without the necessary permissions to alter all of the dependent objects.
Action: Do not attempt to rename the object.
XOQ-01997: A partition level of the cube is invalid.
Cause: The hierarchy level specified as a partition level of the cube was invalid.
Action: Remove the partition level from the cube or specify a valid hierarchy level.
XOQ-01998: cannot partition a cube by two different dimensions: "string" and "string"
Cause: The cube was defined with partitioning by levels from different dimensions.
Action: Ensure that all partition levels for the cube belong to the same dimension.
XOQ-01999: More than one ORDER BY element is specified in the CUSTOMORDER clause.
Cause: The CUSTOMORDER contained more than one ORDER BY element.
Action: Specify only one ORDER BY element in the CUSTOMORDER clause.
XOQ-02000: PrimaryDimension "string" is not a valid TimeDimension for the time series expression.
Cause: PrimaryDimension was not a TimeDimension.
Action: Specify a TimeDimension for the time series expression.
XOQ-02001: table "string" not found
Cause: A table used to map a cube or dimension does not exist. It may have been deleted after the original mapping.
Action: Create the table or remap to a different table.
XOQ-02002: Table "string" does not contain column "string".
Cause: A column used to map a cube or dimension does not exist. It may have been deleted after the original mapping.
Action: Create the column or remap to a different column.
XOQ-02003: Expression "string" is only valid within a model.
Cause: The expression can only be specified as the right hand side of a model assignment.
Action: Redefine the expression to remove all model-specific features.
XOQ-02004: object string "string" not found
Cause: The referenced object may have been deleted.
Action: Specify an existing object.
XOQ-02005: The string "string" referenced from object "string" is not found.
Cause: The referenced object was not found. It may have been deleted.
Action: Specify an existing object.
XOQ-02006: invalid reference to table "string" in mapping "string"
Cause: An expression in a mapping object referred to a table that is not part of the mapping query.
Action: Make sure that all expressions in the mapping object refer only to columns from the mapping query.
XOQ-02007: cannot parse OLAP syntax string
Cause: The OLAP syntax string was invalid and could not be parsed.
Action: Replace the syntax with a valid syntax string.
XOQ-02008: cannot parse OLAP syntax string "string": string
Cause: The OLAP syntax string was invalid and could not be parsed.
Action: Replace the syntax with a valid syntax string.
XOQ-02009: Function "string" is not supported by the analytic workspace.
Cause: A function was specified that is not supported by the OLAP DML language.
Action: Remove the unsupported function from the expression.
XOQ-02010: Data type "string" is not supported by the analytic workspace.
Cause: A data type was specified that is not supported by the OLAP DML language.
Action: Use a supported data type.
XOQ-02011: invalid column expression "string"
Cause: The OLAP DML expression was invalid in this context.
Action: Replace the expression with a valid syntax string.
XOQ-02012: missing expression in object "string"
Cause: A mapping object did not contain all the expressions needed to perform the requested action.
Action: Add the necessary expressions to the mapping object.
XOQ-02013: Missing query and From clause in object "string".
Cause: A mapping object contained neither a query nor a From clause.
Action: Add the necessary query or From clause to the mapping object.
XOQ-02014: missing condition in object "string"
Cause: A mapping object did not contain all the conditions that were needed to perform the requested action.
Action: Add the necessary conditions to the mapping object.
XOQ-02015: Dimension or hierarchy has too many Grouping ID columns.
Cause: The number of Grouping ID columns exceeded the maximum allowed columns. Possible causes are: 1) Attribute spreading was enabled for some attributes in the dimension. 2) There were too many levels defined for the dimension or hierarchy.
Action: Do one of the following: 1) Disable attribute spreading for some or all of the attributes. 2) Eliminate some attributes. 3) Eliminate some levels.
XOQ-02016: cannot add a dynamic model to the cube's consistent solve specification.
Cause: An attempt was made to add a dynamic model to a consistent solve specification that did not contain any aggregation commands.
Action: Add an aggregation command to the consistent solve specification.
XOQ-02100: cannot parse server XML string
Cause: An internal error occurred while parsing query or metadata definitions.
Action: Examine the error output for more detail about the reason for the failure.
XOQ-02101: Invalid object type is used for object reference with id "string".
Cause: An object of the wrong type was specified as an object reference in the XML document.
Action: Correct the XML document to reference an object of the correct type.
XOQ-02102: cannot find object "string"
Cause: An object that does not exist was referenced in the XML document.
Action: Create the referenced object or correct the XML document to reference an existing object.
XOQ-02103: invalid XML attribute "string" for element "string" and object "string"
Cause: An XML attribute in the XML document was invalid.
Action: Correct the invalid attribute in the XML document.
XOQ-02104: invalid XML element "string"
Cause: An XML element in the XML document was invalid.
Action: Correct the invalid element in the XML document.
XOQ-02105: invalid XML element "string" for object "string"
Cause: An XML element in the XML document was invalid.
Action: Correct the invalid element in the XML document.
XOQ-02106: invalid property "string" with value "string" for object "string" in XML document
Cause: The XML document did not specify the object property correctly.
Action: Correct the invalid property in the XML document.
XOQ-02107: invalid property "string" with key::value "string" for object "string" in XML document
Cause: The XML document did not specify the object property correctly.
Action: Correct the invalid property in the XML document.
XOQ-02108: invalid XML document: string at line string
Cause: An internal error occurred while parsing the XML document.
Action: Examine the error output for more detail about the reason for the failure.
XOQ-02109: Top level object "string" already exists.
Cause: An attempt was made through the XML to create an object that already exists.
Action: Drop the existing object before recreating it.
XOQ-02110: Object of type "string" with ID "string" cannot be created because another object with that ID already exists.
Cause: An attempt was made through the XML to create an object with an ID that was already used on an existing object.
Action: Rename the new object or delete the existing one.
XOQ-02111: Object type "string" is invalid for export.
Cause: An attempt was made to export an object of an inappropriate type. Only objects of type analytic workspace, database schema, cube, cube dimension, measure folder, and cube build process are allowed for export.
Action: If the object is a subobject of a cube or cube dimension, then call the export procedure passing the cube or cube dimension as an argument instead of the object itself.
XOQ-02112: invalid XML attribute "string" with value "string" for element "string"
Cause: An XML attribute in the XML document was invalid.
Action: Correct the invalid attribute in the XML document.
XOQ-02113: Unable to parse XML because the compatibility setting is below the minimum setting of 11.0.0.0.0.
Cause: The compatibility setting was below the minimum for parsing XML.
Action: Set the compatibility to 11.0.0.0.0 or higher.
XOQ-02114: Unable to write XML because the compatibility setting is below the minimum setting of 11.0.0.0.0.
Cause: The compatibility setting was below the minimum for writing XML.
Action: Set the compatibility to 11.0.0.0.0 or higher.
XOQ-02115: Metadata object type "string" cannot be renamed on import.
Cause: The object type in the rename table was not a leaf object type, or the leaf object type could not be renamed.
Action: Enter a valid object type in the rename table.
XOQ-02116: Metadata object id "string" is not valid.
Cause: The object id in the rename table was null or contained invalid characters.
Action: Enter a valid object id in the rename table.
XOQ-02117: The new name "string" for object "string" is not valid.
Cause: The new name in the rename table was either null or empty.
Action: Enter a valid new name in the rename table.
XOQ-02118: Two new names for object "string" with type "string" are in the rename table.
Cause: The rename table contained two different new names for the same object.
Action: Remove one of the rows from the rename table.
XOQ-02200: cannot upgrade object "string"
Cause: The object could not be upgraded.
Action: Apply the modifications suggested by the other error messages that typically accompany this one. Then attempt the upgrade again. If you cannot correct the error, try exporting the XML definition for the object using DBMS_CUBE.EXPORT_XML, and reimporting the object into a different schema.
XOQ-02201: object "string" not found
Cause: The upgrade command referred to an object that did not exist.
Action: Correct the object identifier and try again.
XOQ-02202: Object "string" cannot be upgraded because its name is the same as an existing object.
Cause: The upgrade failed because the object name was the same as the name of an existing object. In earlier versions of Oracle Database, a cube, dimension, or measure folder could have the same name as a database table. In Oracle Database 11g and later, cubes, dimensions, measure folders, and RDBMS tables must all have different names.
Action: Change the object name and try the upgrade again.
XOQ-02203: Analytic workspace "string" cannot be upgraded because it contains customization "string".
Cause: The upgrade failed because the analytic workspace contained a customization. Customizations are not supported in releases after Oracle Database 10g.
Action: Remove the customization and attempt the upgrade again. To remove all customizations, call the upgrade procedure with the DeleteCustomizations option set to YES.
XOQ-02204: Cannot upgrade object "string": only analytic workspaces and database schemas are valid arguments to the UPGRADE command.
Cause: The identified argument of the UPGRADE command was an object that was neither type oracle.olapi.metadata.mdm.MdmDatabaseSchema nor type oracle.olapi.metadata.deployment.AW.
Action: If the object is in an analytic workspace or a database schema, call the UPGRADE command and use the analytic workspace or the database schema as an argument instead of the object.
XOQ-02205: Cannot upgrade analytic workspace "string": the analytic workspace version is too old.
Cause: An attempt was made to upgrade an analytic workspace that was formatted for Oracle Database 10.1.0.2 or earlier. Only analytic workspaces from Oracle Database 10.1.0.3 and later can be upgraded using DBMS_CUBE.UPGRADE.
Action: Upgrade the analytic workspace to release 10.1.0.3 or later using methods described in the OLAP documentation for Oracle 10.1.0.3. Then use DBMS_CUBE.UPGRADE to upgrade the analytic workspace to Release 11g.
XOQ-02206: Cannot upgrade object "string": the metadata is already using the current version.
Cause: An attempt was made to upgrade an analytic workspace that is already formatted correctly for the current version.
Action: Do not use the DBMS_CUBE.UPGRADE facility for this analytic workspace.
XOQ-02207: cannot process mapping "string": string
Cause: An object stored in an Oracle Database 10g analytic workspace contained an invalid mapping.
Action: Replace the mapping with a valid one. If the problem persists, set the IgnoreMappingErrors option to YES in the UPGRADE or COMMIT options.
XOQ-02208: Object contains multiple mappings.
Cause: A dimension or measure stored in an Oracle OLAP 10g analytic workspace contained multiple mappings. This is not supported in releases after Oracle Database 10g.
Action: Modify the object to use only one mapping. If the problem persists, set the IgnoreMappingErrors option to YES in the UPGRADE or COMMIT options.
XOQ-02209: cannot process aggregation "string": string
Cause: An object stored in an Oracle Database 10g analytic workspace contained an invalid aggregation.
Action: Replace the aggregation with a valid one. If the problem persists, set the IgnoreMappingErrors option to YES in the UPGRADE or COMMIT options.
XOQ-02210: Legacy metadata contains invalid mappings.
Cause: An object stored in an Oracle Database 10g analytic workspace contained mappings that could not be converted to post-10g format.
Action: Examine the list of invalid mappings and correct the errors reported for each object using Analytic Workspace Manager in 10g compatibility mode. If the problem persists, set the IgnoreMappingErrors option to YES in the UPGRADE or COMMIT options.
XOQ-02211: The MdmPrimaryDimension cannot be upgraded because a compile step failed with this message: "string".
Cause: A dimension could not be compiled.
Action: Correct the compilation errors in the analytic workspace. If the problem persists, set the IgnoreCompileErrors option to YES in the UPGRADE options. This allows other objects in the analytic workspace to be upgraded. Then fix and recompile the problem dimension so you can use it.
XOQ-02212: The expression for this MdmMeasure cannot be read. Analytic workspace "string" was not attached when the connection was opened.
Cause: The Oracle Database 10g analytic workspace contained a derived measure. Derived measures can only be upgraded if the analytic workspace is attached before the first call to DataProvider.createSession or DataProvider.initialize.
Action: Attach the analytic workspace before calling DataProvider.createSession or DataProvider.initialize. Alternatively, set the IgnoreMappingErrors option to YES in the UPGRADE or COMMIT options to suppress this error message. The derived measure will become an MdmBaseMeasure after the upgrade.
XOQ-02213: cannot read legacy metadata
Cause: The database contained metadata stored in an Oracle Database 10g analytic workspace or in CWM format. The metadata could not be converted to post-10g format because of problems in the stored metadata.
Action: Examine the list of errors and make corrections to the metadata using Analytic Workspace Manager in 10g compatibility mode. If the problem persists and is preventing you from accessing 11g metadata, set the MetadataReaderMode option to 11_ONLY in the connection properties.
XOQ-02214: error reading legacy metadata object: string
Cause: One of the metadata objects, which was stored in either an Oracle Database 10g analytic workspace or CWM format, could not be converted to post-10g format.
Action: Make corrections to the metadata using Analytic Workspace Manager in 10g compatibility mode. If the problem persists and is preventing you from accessing post-10g metadata, set the MetadataReaderMode option to 11_ONLY in the connection properties.
XOQ-02300: Build completed with warnings.
Cause: The build completed successfully, but some of the data may be incorrect due to inconsistencies in the metadata or input data.
Action: If cube build logging is enabled, examine the OUTPUT column of the cube build log for more details.
XOQ-02500: Derived attribute "string" is not a DIM_KEY.
Cause: The derived attribute specified in the CUSTOMORDER clause was not the DIM_KEY. A derived attribute in a CUSTOMORDER clause can only be the DIM_KEY.
Action: Specify the DIM_KEY or use a base attribute in the CUSTOMORDER clause.
XOQ-02501: Attribute "string" is not part of the primary dimension.
Cause: The attribute specified in the CUSTOMORDER clause was not part of the primary dimension. An attribute in the CUSTOMORDER clause must be part of the primary dimension.
Action: Specify an attribute of the CUSTOMORDER clause that is part of the primary dimension.
XOQ-02502: Attribute "string" is not a visible attribute of the hierarchy.
Cause: The attribute specified in the CUSTOMORDER clause was not a visible attribute of the hierarchy. An attribute in the CUSTOMORDER clause of a hierarchy must be a visible attribute of the hierarchy.
Action: Specify a visible attribute in the CUSTOMORDER clause of the hierarchy.
XOQ-02503: No attribute is specified for the CUSTOMORDER clause.
Cause: The object specified in the CUSTOMORDER clause was not an attribute. Only an attribute can be specified in the CUSTOMORDER clause.
Action: Specify an attribute in the CUSTOMORDER clause.
XOQ-02504: The object contains multiple descriptions of type "string" for the language "string".
Cause: An object contained multiple descriptions for the same type on the same language.
Action: Ensure there is only one description on an object for each type for each language.
XOQ-02505: The CubeMap for cube "string" contains both a query and a From clause.
Cause: The CubeMap had a query and a From clause.
Action: Specify either a query or a From clause for the CubeMap but not both.
XOQ-02506: The DimensionMap for dimension "string" contains both a query and a From clause.
Cause: The DimensionMap had a query and a From clause.
Action: Specify either a query or From clause for the DimensionMap but not both.
XOQ-02507: The DimensionMap for dimension "string" contains a From clause with duplicate queries.
Cause: The DimensionMap had a From clause with duplicate queries.
Action: Remove the duplicate queries in the From clause for the DimensionMap.
XOQ-02508: The CubeMap for cube "string" contains a From clause with duplicate queries.
Cause: The CubeMap had a From clause with duplicate queries.
Action: Remove the duplicate queries in the From clause for the CubeMap.
XOQ-02509: Analytic workspace "string" has an invalid name.
Cause: An attempt was made to create an analytic workspace with an invalid name. Analytic workspace names cannot contain lower-case letters.
Action: Change the analytic workspace name to a valid name, and commit the transaction.
XOQ-02510: The SolvedMap for Object "string" contains a From Clause with multiple queries
Cause: The SolvedMap had a From Clause with multiple queries.
Action: Remove multiple queries in the From Clause for the SolvedMap.
XOQ-02511: The cube storage DATE data type is incompatible with materialized views.
Cause: The AWCubeOrganization had a cube storage data type of DATE, which was incompatible with materialized views.
Action: Either change the cube storage data type to DATETIME or create the cube without materialized views.
XOQ-02512: string XOQ-02512: OLAP DML error while compiling formula for measure "string"
Cause: The measure expression in the derived measure could not be compiled.
Action: Redefine the measure expression for the derived measure.
XOQ-02513: A rewrite materialize view cannot be created for cube "string" because the aggregation from the consistent solve specification is incompatible.
Cause: The consistent solve specification specified an aggregation that was not uniform over all dimensions and hierarchies or was not one of the supported aggregation operators.
Action: Change the aggregation on the consistent solve specification to be uniform and one of the supported aggregation types.
XOQ-02514: The attribute "string" is mapped to different expressions on the two HierarchyLevels "string" and "string".
Cause: An attribute was mapped to different expressions on two different HierarchyLevels that have the same DimensionLevel.
Action: Change the attribute mappings so that the target expression is the same on all HierarchyLevels having the same DimensionLevel.
XOQ-02515: The MVCreationOptions of REFRESH ON COMMIT, REFRESH START WITH, and REFRESH NEXT are not supported.
Cause: The MVCreationOptions of either an AWPrimaryDimensionOrganization or an AWCubeOrganization contained unsupported settings.
Action: Ensure that the MVCreationOptions of AWPrimaryDimensionOrganizations and AWCubeOrganizations do not set REFRESH ON COMMIT and do not specify REFRESH START WITH or REFRESH NEXT.
XOQ-02516: The MdmValueHierarchy has no value hierarchy map.
Cause: The MdmValueHierarchy did not contain a value hierarchy map.
Action: Add a SolvedValueHierarchyMap to all value hierarchies contained in dimensions with associated materialized views.
XOQ-02517: The data type "string" of the base attribute or base measure is different from the mapped expression "string".
Cause: Either the base attribute or base measure with the mapped expression was set to an inconsistent data type, or it was mapped to an expression of a different data type from its fixed data type.
Action: When changing a mapped expression for a base attribute or base measure, ensure that the expression has the same data type; otherwise, set the data type of the base attribute or base measure to NULL first. When a base attribute or a base measure has an existing mapped expression, do not set it to a different data type.
XOQ-02518: Object cannot be renamed to "string" because that name is already being used by an existing object.
Cause: A row in the CUBE_UPGRADE_INFO table had a value in the NEW_NAME column that was not unique.
Action: Fix the CUBE_UPGRADE_INFO table by using an UPDATE command or running DBMS_CUBE.INTIALIZE_CUBE_UPGRADE.
XOQ-02519: The mapped dimension in the cube dimensionality map of a cube materialized view must be either a dimension level or a hierarchy level.
Cause: "The mapped dimension in the cube dimensionality map of a cube materialized view was a primary dimension."
Action: "Change the mapped dimension in the cube dimensionality map of a cube materialized view to a dimension level or a hierarchy level."
XOQ-02520: The mapped dimension in the cube dimensionality map of a query-rewrite-enabled cube materialized view must be the lowest hierarchy level on all hierarchies in the dimension.
Cause: "The mapped dimension in the cube dimensionality map of a query-rewrite-enabled cube materialized view was not the lowest hierarchy level on a hierarchy in the dimension."
Action: "Change the mapped dimension in the cube dimensionality map of a query-rewrite-enabled cube materialized view to a hierarchy level or a dimension level that is the lowest hierarchy level on all hierarchies in the dimension."
XOQ-02521: The object description of type "string" for language "string" was truncated to the maximum number of characters (string).
Cause: An object had a description that was too long. The description was shortened automatically.
Action: No action is necessary. Consider rephrasing the description to make it fit within the maximum length.
XOQ-02522: The values for attribute "string" in level "string" must be unique.
Cause: The IsLevelUnique flag was set to true for the attribute, but the attribute values in the given level were not unique.
Action: Either set the IsLevelUnique flag to false, or load unique values into the attribute.
XOQ-02523: unsupported data type "string"
Cause: The data type specified for cube storage was invalid or not supported.
Action: Specify a supported SQL data type.
XOQ-02524: A SQL data type and an OLAP DML data type have both been specified and/or modified for cube storage. The OLAP DML cube storage data type specification will be ignored
Cause: The data type for cube storage was specified in both SQL and in OLAP DML resulting in the use of the SQL data type.
Action: Specify a supported data type in either SQL or OLAP DML format.
XOQ-02525: A mismatch exists between the measure data type "string" and cube storage data type "string"
Cause: Measure storage was defined as SHARED and the data type for the measure was not an exact match to that of the cube storage type. This may result in data inconsistencies.
Action: Either set the IsLevelUnique flag to false, or load unique values into the attribute.
XOQ-02526: UniqueKey attribute "string" has an invalid populate lineage flag set.
Cause: The attribute had the populate lineage flag set. This flag does not need to be set on a unique key attribute.
Action: Optionally remove this flag on the attribute or do not make the attribute a unique key.
XOQ-02527: The unique key attributes "string" and "string" are on different levels of a primary dimension but are mapped to the same expression.
Cause: Two different unique key attributes on different levels of a primary dimension were mapped to the same expression. Such mappings are not allowed if the dimension is part of a query-rewrite-enabled cube.
Action: Uniquely map the unique key attributes or create the cube without a REWRITE materialized view.
XOQ-02528: The derived measure "string" cannot be designated as the default measure for the cube.
Cause: A derived measure was designated as the default measure on a cube that has materialized views.
Action: To designate a default measure for the cube, choose a measure that is not derived, or remove the materialized views from the cube.
XOQ-02529: The base attribute "string" of dimension "string" cannot be given an NVL expression because it is indexed.
Cause: An NVL expression was specified for a base attribute that is indexed. An attribute is indexed if it is explicitly marked as indexed by the user, or if it is a unique key attribute, or if the populate lineage flag is set.
Action: Remove the NVL expression or change the attribute so that it is not indexed, is not a unique key, and does not have the populate lineage flag set.
XOQ-02530: A maintain dimension command cannot be specified as part of a default build specification or named build specification.
Cause: Either a named build specification or the default build specification for a cube or dimension specified a maintain dimension command.
Action: Remove the maintain dimension command from the default build specification or named build specification.
XOQ-02531: The sparse type must be COMPRESSED or SPARSE when a secondary partition level is specified.
Cause: A secondary partition level was specified for the AWCubeOrganization when its sparse type was not COMPRESSED or SPARSE.
Action: Set the sparse type to COMPRESSED or SPARSE on the AWCubeOrganization, or remove all secondary partition levels.
XOQ-02532: cannot specify a secondary partition level without also specifying a (primary) partition level.
Cause: A secondary partition level was specified for an AWCubeOrganization that had no (primary) partition level.
Action: Specify a (primary) partition level before specifying additional secondary partition levels.
XOQ-02533: The cube dimensionality map has neither a join condition nor an expression.
Cause: Neither a join condition nor an expression were specified for the CubeDimensionalityMap.
Action: Specify either a join condition, an expression, or both on the cube dimensionality map.
XOQ-02534: The data type "string" of the base attribute or base measure "string" is different from the mapped expression "string".
Cause: Either the base attribute or base measure with the mapped expression was set to an inconsistent data type, or it was mapped to an expression of a different data type from its fixed data type.
Action: When changing a mapped expression for a base attribute or base measure, ensure that the expression has the same data type; otherwise, set the data type of the base attribute or base measure to NULL first. When a base attribute or a base measure has an existing mapped expression, do not set it to a different data type.
XOQ-02535: The view name "string" defined on the object "string" is not unique.
Cause: The user-defined view name was already in use.
Action: Ensure that all user-defined view names are unique.
Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us