Oracle 12c R2 Error Codes and Solution Suggestions from ORA-18200 to ORA-19000
- ORA-18201: The input MDX string is empty.
Cause: The input MDX (MultiDimensional eXpression) string was empty.
Action: Correct the input MDX (MultiDimensional eXpression) string.
Cause: The input MDX (MultiDimensional eXpression) query had invalid syntax.
Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
Cause: The input MDX (MultiDimensional eXpression) query contained an unsupported feature.
Action: Modify the MDX (MultiDimensional eXpression) query to use only supported features.
Cause: The delimited identifier had no closing right bracket (]) character.
Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
Cause: The function had invalid arguments.
Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
Cause: The MDX (MultiDimensional eXpression) query had the wrong type.
Action: Use an expression with a valid type.
Cause: An argument had different hierarchies.
Action: Use uniform hierarchies.
Cause: A hierarchy was repeated.
Action: Use disjoint hierarchies.
Cause: More than one hierarchy existed for dimension.
Action: Specify the hierarchy with the dimension.
Cause: The cube identifier was specified incorrectly.
Action: Specify a valid cube identifier.
Cause: An argument of the function had the wrong type.
Action: Use an argument with a valid type.
Cause: The hierarchy in one argument did not exist in the SET argument.
Action: Use an expression with the hierarchy from the set in the SET argument.
Cause: The index was out of range.
Action: Use an index within the range.
- ORA-18228: The set of argument string of string contains multiple hierarchies. Only one hierarchy is expected.
Cause: The set argument had more than one hierarchy.
Action: Use a SET argument that contains only one hierarchy.
Cause: The hierarchy was used more than once.
Action: Use arguments that contain different hierarchies.
Cause: The member identifier could not be resolved.
Action: Use a valid member identifier.
Cause: The StrToMember argument was not a member identifier and CONSTRAINED was specified.
Action: Replace the argument with a member identifier or remove the CONSTRAINED option.
Cause: More than one set was defined with the same name.
Action: Rename the set so that it has a unique name within the WITH clause of the multidimensional expression (MDX) query.
Cause: The set definition referenced itself either directly or indirectly using another referenced set.
Action: Change the definition of the set so that it does not directly or indirectly refer to itself.
Cause: The name specified for the calculated member identified another member in the hierarchy.
Action: Change the name of the calculated member so that it is unique within the specified hierarchy.
Cause: The calculated member identifier either was not a valid member identifier or does not contain a hierarchy qualification.
Action: Change the calculated member identifier so that it is a valid member identifier qualifying the hierarchy.
Cause: The calculated member referenced itself either directly or indirectly using another referenced calculated member.
Action: Change the definition of the calculated member so that it does not directly or indirectly refer to itself.
Cause: More than one calculated member was defined with the same name.
Action: Rename the calculated member so that it has a unique name within the WITH clause of the multidimensional expression (MDX) query.
Cause: The input parameter to the PL/SQL function was invalid.
Action: Correct the input parameter to the PL/SQL function.
Cause: Either an MDX (MultiDimensional eXpression) query was not executed or all executed queries were closed.
Action: Execute an MDX (MultiDimensional eXpression) query.
Cause: The MDX (MultiDimensional eXpression) query did not exist in the session with the given queryID.
Action: Specify a valid queryID obtained by calling dbms_mdx_odbo.execute.
Cause: The size of the cellRange sequence was not 2 times the number of axes.
Action: Specify a cellRange that has the correct number of elements.
Cause: The start was greater than end for a particular axis in the cellRange.
Action: Specify start less than or equal to end for each axis in the cellRange.
Cause: The axisIndex was out of range.
Action: Specify an axisIndex greater than or equal to 0 and less than the number of axes.
Cause: The classification value was invalid for MultiDimensional eXpression.
Action: Replace the Classification value.
Cause: The set defining the Slicer resulted in more than one row.
Action: Correct the Slicer portion of the MultiDimensional eXpression query.
Cause: The MDX (MultiDimensional eXpression) Schema Rowset type was not a valid value.
Action: Valid MDX (MultiDimensional eXpression) schema Rowset types are between 1 and 10.
Cause: The MultiDimensional eXpression Schema Rowset Restrictions array and the Empty array were not the same size.
Action: Correct the sizes of the Restriction and Empty arrays.
Cause: The given TREE_OP restriction value was invalid.
Action: Provide a valid TREE_OP restriction value.
Cause: A value in the given empty list was invalid.
Action: Provide a valid empty value.
Cause: The object name and log number combination did not match the value returned by DBMS_HIERARCHY.VALIDATE_HIERARCHY or VALIDATE_CUBE.
Action: Provide a valid combination of object name and log number and reexecute.
Cause: The ‘queryProperties’ sequence had an odd number of elements.
Action: Ensure that the ‘queryProperties’ sequence is either empty or contains an even number of elements.
- ORA-18265: fact table key column (string) with value (‘string‘) not in dimension star table key column
Cause: There was a row in the fact table with a key column value that was not in the corresponding dimension star table key column.
Action: Ensure that each fact table key column value has a corresponding row in the dimension star table key column.
- ORA-18266: analytic view key (string) with value (‘string‘) does not determine hierarchy lowest level key
Cause: The attribute references found on the analytic view keys could not determine the level key column values of the lowest level in the hierarchy.
Action: Ensure that the attribute references found on the analytic view keys determine the level key column values of the lowest level in the hierarchy.
- ORA-18267: key (string) with value (string) for level “string” does not determine all level attributes
Cause: There were rows with the level key column value where the number of distinct values of every attribute column and alternate key attribute were not zero or one.
Action: Ensure that the number of distinct values of every attribute column and alternate key attribute is zero or one for each level key column value.
- ORA-18268: alternate key (string) with value (string) for level “string” does not determine level key column value
Cause: There were rows with the alternate key attribute that had non-unique level key values.
Action: Ensure that the alternate key attribute rows all have the same level key value.
Cause: A level key column value was defined as NULL when it should be NOT NULL.
Action: Do not define a level key column value to NULL when it should be the NOT NULL value.
- ORA-18270: key or alternate key attributes “string” and “string” for level “string” have string mismatched NULL values
Cause: There was a mismatch in the number of NULL values for a SKIP WHEN NULL level.
Action: Ensure that for each SKIP WHEN NULL level, either all level key column values and alternate key attributes are NULL, or all of the level key column values and alternate key attributes are not NULL.
Cause: A non-integer value, a negative value, or a value greater than 2 was specified for the VisualMode query property.
Action: Specify an integer value of 0, 1, or 2 for the VisualMode query property.
Cause: An analytic view join key did not determine all rows in the dimension star table.
Action: Ensure that the analytic view join key determines all rows in the dimension star table.
Cause: An attempt was made to create a materialized view SQL statement for an analytic view that did not contain a cache.
Action: Modify the analytic view to contain a cache or specify an analytic view with a cache.
Cause: The specified analytic view cache index was invalid.
Action: Specify a valid cache index.
Cause: The column size of the table did not match with the default log table.
Action: Ensure that the table provided has a correct column definition.
Cause: There was a mismatch in the log table format that corresponds with an older version of the table.
Action: Call DBMS_HIERARCHY.UPGRADE_VALIDATE_LOG_TABLE in order to upgrade to the latest format and retry the operation.
Cause: The REFERENCES clause specified for the analytic view dimension was invalid.
Action: Correct the REFERENCES clause for the analytic view dimension.
Cause: A cyclic reference for a calculated measure was detected.
Action: Correct the cyclic reference for the calculated measure.
Cause: An invalid join condition was detected.
Action: Ensure that each side of the join condition comes from a different source.
Cause: An invalid join path reference was detected.
Action: Ensure that the join path on the hierarchy refers to a join path on the attribute dimension.
Cause: Invalid join paths were detected on the attribute dimension.
Action: Ensure that every dimension source is reachable starting with any source and applying join paths of the visited sources.
Cause: Invalid join paths were detected on the hierarchy.
Action: Ensure that every join path contains a single unique path and includes every dim source of every level in the hierarchy exactly once.
- ORA-18286: invalid SKIP WHEN NULL specification on a calculation expression detected on hierarchy string
Cause: An invalid SKIP WHEN NULL specification was detected on the calculation expression.
Action: Ensure that SKIP WHEN NULL is only specified on skip level hierarchies.
Cause: An invalid level name specification was detected on the calculation expression.
Action: Ensure the level exists on the hierarchy specified in the calculation expression.
Cause: A parent-child hierarchy was detected on the calculation expression level specification.
Action: Ensure the level specifcation on the calculation expression does not reference a parent-child hierarchy.
Cause: A parent-child member literal expression was detected for a level-based hierarchy.
Action: Ensure that the parent-child member literal expression is used with a parent-child hierarchy.
- ORA-18290: positional member key mismatch detected between member literal expression and hierarchy level “string” on hierarchy “string“
Cause: The number of member keys on the member literal expression did not match those on the corresponding level.
Action: Ensure that the number of member keys on the member literal expression match those on the corresponding level.
- ORA-18291: named member key mismatch detected between member literal expression and hierarchy level “string” on hierarchy “string“
Cause: The member keys on the member literal expression did not match those on the corresponding level.
Action: Ensure that the member keys on the member literal expression match those on the corresponding level.
Cause: An invalid data type was detected on an attribute.
Action: Ensure that the attributes are not of LOB, BFILE, or LONG data type.
Cause: The same cube hierarchy was named more than once in the calculation expression.
Action: Specify each cube hierarchy only once in the calculation expression.
Cause: An ambiguously defined hierarchy was detected in a calculation expression.
Action: Resolve the ambiguity on the hierarchy used in the calculation expression.
- ORA-18297: invalid data type detected on base measure “string” for use with aggregation operator “string“
Cause: An invalid data type was detected on a base measure for use with its specified aggregation operator.
Action: Ensure that the data type of the base measure is valid with the aggregation operator on the base measure.
- ORA-18298: The REFERENCES clause for the analytic view dimension “string” does not determine the lowest level of every hierarchy.
Cause: The REFERENCES clause specified for the analytic view dimension was invalid.
Action: Correct the REFERENCES clause for the analytic view dimension.
Cause: The specified hierarchical attribute of the specified level had an invalid data type.
Action: Ensure that all attributes of the specified type are character expressions using the same character set.
Cause: The specified hierarchical attribute of the specified level used a character set that did not match the character set of other levels.
Action: Ensure that all attributes of the specified type are character expressions using the same character set. An explicit ALL clause may need to be specified if the default character set of the ALL attributes does not match the character set used in other levels.
Cause: The attribute dimension did not exist or the user did not have the required privileges.
Action: Check the spelling of the attribute dimension and ensure that the required privileges are granted.
Cause: The hierarchy did not exist or the user did not have the required privileges.
Action: Check the spelling of the hierarchy and ensure that the required privileges are granted.
- ORA-18303: The REFERENCES clause for the analytic view dimension “string” refers to a level key where the level is marked as SKIP WHEN NULL.
Cause: The REFERENCES clause specified for the analytic view dimension was invalid.
Action: Correct the REFERENCES clause for the analytic view dimension or remove the SKIP WHEN NULL from the attribute dimension level.
Cause: A non-measure was referenced in a calculated measure.
Action: Ensure that only a measure is referenced in a calculated measure.
Cause: A non-aggregation user-defined function was specified for a window calculated measure.
Action: Ensure that a valid user-defined aggregation function is specified for a window calculated measure.
Cause: An invalid depth expression was specified in a hier ancestor calculated measure.
Action: Ensure that the depth expression of the hier ancestor evaluates to a positive integer no greater than the number of levels in the hierarchy.
Cause: The analytic view did not exist or the user did not have the required privileges.
Action: Check the spelling of the analytic view and ensure that the required privileges are granted.
Cause: The attribute dimension did not have a level specification.
Action: Specify at least one level in the attribute dimension.
Cause: Either the MATERIALIZED or DYNAMIC keyword was missing.
Action: Specify the MATERIALIZED or DYNAMIC keyword for this level group.
Cause: Analytic View (AV) dynamic caching initialization parameter was not set.
Action: Enable Dynamic AV caching using the appropriate initialization parameter.
Cause: The level key did not reference a valid attribute in the dimension.
Action: Reference an existing attribute in the level key.
Cause: The determined attribute did not reference a valid attribute in the dimension.
Action: Reference an existing attribute in the level.
Cause: The level did not have a member name.
Action: Specify a member name for this multi-attribute key level.
Cause: The default measure did not reference a valid measure in the cube.
Action: Reference an existing measure in the cube.
Cause: The attribute was named using a reserved word.
Action: Use a name for the attribute that is not a reserved word.
Cause: A duplicate metadata object was specified.
Action: Remove or rename the duplicate metadata object specification.
Cause: Another default cube hierarchy was specified within the same cube dimension.
Action: Set only one default cube hierarchy within a cube dimension.
Cause: A duplicate level key was specified.
Action: Remove or replace the duplicate level key specification.
Cause: The hierarchical attribute was named using an invalid word.
Action: Use a valid name for the hierarchical attribute.
Cause: The attribute dimension was defined with an invalid skip level specification.
Action: At least one level on the attribute dimension must be NOT NULL.
Cause: The ORDER BY attribute did not reference a valid attribute in the dimension.
Action: Reference an existing attribute in the level.
Cause: A cyclic-determined attribute reference for a level was detected.
Action: Correct the cyclic-determined attribute reference for the level.
Cause: An invalid expression was detected on a calculated measure.
Action: An offset expression or member key expression cannot contain a column expression or be an analytic view SQL calculation expression.
Cause: An invalid ALL member name was detected on a hierarchy dimension.
Action: Ensure that the ALL member name is a constant expression.
Cause: A duplicate level was found in the level list for an Analytic View Cache Level Group.
Action: Ensure that each Analytic View Cache Level Group contains a distinct list of levels.
Cause: A duplicate measure was found in the measure list for an Analytic View Cache Level Group.
Action: Ensure that each Analytic View Cache Level Group contains a distinct list of measures.
Cause: A hierarchy specified in the level list for an Analytic View Cache Level Group was not found.
Action: Ensure that each specified hierarchy in the Analytic View Cache Level Group is defined within the Analytic View.
Cause: A dimension specified in the level list for an Analytic View Cache Level Group was not found.
Action: Ensure that each specified dimension in the Analytic View Cache Level Group is defined within the Analytic View.
Cause: Multiple levels for the same hierarchy were found in the level list for an Analytic View Cache Level Group.
Action: Ensure that each Analytic View Cache Level Group contains only one level per hierarchy.
Cause: A duplicate Analytic View Cache Level Group and Measure List combination was found in the Analytic View Cache.
Action: Ensure that for each Measure List the Analytic View Cache Level Group Lists are unique.
Cause: The level type was inconsistent with the dimension type.
Action: Ensure the level type is consistent with the dimension type.
Cause: One key was a subset of another key at the same level.
Action: Ensure that no key is a subset of another key at the same level.
Cause: Invalid syntax was specified for a calculated measure.
Action: Ensure that the syntax is correct.
Cause: An invalid aggregation function was specified for a window calculated measure.
Action: Ensure that a valid aggregation function is specified for a window calculated measure.
Cause: A HIERARCHIES clause was used on a table or other non-cube object.
Action: Remove the HIERARCHIES clause.
Cause: Cube hierarchies may only be qualified by dimension in the HIERARCHIES clause.
Action: Remove the additional qualification.
Cause: Illegal syntax was found in the HIERARCHIES clause.
Action: Ensure that the HIERARCHIES clause only contains a comma delimited list of cube hierarchies enclosed in parentheses.
Cause: No hierarchy was specified in the HIERARCHIES clause.
Action: Specify at least one hierarchy in the HIERARCHIES clause enclosed in parentheses.
Cause: The same cube hierarchy was named more than once in the HIERARCHIES clause.
Action: Specify each cube hierarchy only once in the HIERARCHIES clause.
Cause: A cube column was referenced in an ANSI NATURAL JOIN or USING clause.
Action: Use the ANSI ON clause or Oracle join syntax.
Cause: A hierarchy or analytic view was specified in an incorrect location in a statement.
Action: Ensure that the name is correct or remove it.
Cause: A comment for a column of an analytic view object was specified.
Action: Do not define comments for columns of analytic views. Use classifications instead.
Cause: Calculated measures were not allowed in the cache measure list.
Action: Remove calculated measures from the cache measure list.
Cause: Illegal syntax was found in the query hint session parameter.
Action: Ensure that the hint syntax provided is a valid SQL hint syntax.
Cause: Illegal syntax was found in the query hint session parameter.
Action: Ensure that the hint syntax provided is a valid SQL hint syntax.
Cause: Illegal syntax was found in the query hint session parameter.
Action: Ensure that the hint syntax provided is a valid SQL hint syntax.
Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.
Action: Supply the RELATIONAL keyword in the storage clause