Oracle Error Messages: 06/10/12

Sunday 10 June 2012

ORA-36681: (XSDPART19) Partitions string and string are out of order.

ORA-36681: (XSDPART19) Partitions string and string are out of order.

Cause: In the definition of a range partition template, a partition with a lower range boundary was listed after a partition with a higher range boundary.

Action: Alter the order of the partition definition list.

ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.

ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.

Cause: In the definition of a partition template, one of the partitions was dimensioned by a dimension that was not given in the dimension list of the partition template.

Action: Remove the offending dimension from the partition s dimension list, or add it to the partition template s dimension list.

ORA-36679: (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.

ORA-36679: (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.

Cause: In the definition of a CONCAT partition template, one of the partitions was dimensioned by a dimension that is concat-related to a partition dimension, meaning it shares some leaves with the partition dimension, but it contained some leaves that are not in the partition dimension.

Action: Either modify the dimensionality of the partition template to include a concat dimension that contains all the desired leaves, or pick a different dimension for the partition.

ORA-36678: (XSDPART16) workspace object is missing from one or more partition dimension lists.

ORA-36678: (XSDPART16) workspace object is missing from one or more partition dimension lists.

Cause: In the definition of a partition template, one of the partitions had a dimension list that did not contain all the dimensions of the partition template.

Action: Add the offending dimension to the partition s dimension list, or delete it from the partition template s dimension list. If using CONCAT partitioning and the missing dimension is a partition dimension, add to the partition dimension list any leaf of the partition dimension or any concat of leaves of the partition dimension.

ORA-36677: (XSDPART15) Duplicate value in value lists of number and number

ORA-36677: (XSDPART15) Duplicate value in value lists of number and number

Cause: In a LIST PARTITION TEMPLATE definition, a value appeared in more than one value list, or more than once within a single value list.

Action: List each value only once.

ORA-36676: (XSDPART14) Missing dimension list for string.

ORA-36676: (XSDPART14) Missing dimension list for string.

Cause: User attempted to define a CONCAT partition template, and didn t supply a list of dimensions for one of the partition definitions.

Action: Give a dimension list for each partition.

ORA-36674: (XSDPART12) Invalid dimension value starting at string.

ORA-36674: (XSDPART12) Invalid dimension value starting at string.

Cause: When defining a RANGE or LIST partition template, the user specified an invalid value in a VALUES LESS THAN or VALUES clause. An invalid value can be one of two things: a value whose datatype does not match the partition dimension s datatype, or a non-constant value.

Action: Modify the offending VALUES LESS THAN or VALUES phrase.

ORA-36673: (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the lamp;lt;lamp;nbsp;LEAF: VALUElamp;gt; format.

ORA-36673: (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the lamp;lt;lamp;nbsp;LEAF: VALUElamp;gt; format.

Cause: When defining a RANGE partition template with a concat dimension for the partition dimension, the user attempted to define a range using the lamp;lt;lamp;nbsp;LEAF: VALUElamp;gt; format of a concat dimension value.

Action: Use just the leaf value. Instead of VALUES LESS THAN lamp;lt;lamp;nbsp;leaf: valuelamp;gt; , just say, VALUES LESS THAN value .

ORA-36672: (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.

ORA-36672: (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.

Cause: User attempted to define a RANGE or LIST partition template with more than one partition dimension.

Action: Remove all but one of the dimensions from the PARTITION BY RANGE(...) or PARTITION BY LIST(...) clause of the partition template definition.

ORA-36671: (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.

ORA-36671: (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.

Cause: User attempted to define a range partition template with a concat partition dimension, and the concat had two leaf dimensions with different datatypes.

Action: Pick a different partition dimension.

ORA-36670: (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.

ORA-36670: (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.

Cause: User attempted to define a partition template partitioned by an INTEGER or NTEXT dimension or a concat containing an NTEXT leaf.

Action: Either pick a different partition dimension, or redefine the dimension to use a different datatype.

ORA-36669: (XSDPART07) string is not a legal LIST partition.

ORA-36669: (XSDPART07) string is not a legal LIST partition.

Cause: User attempted to use RANGE or CONCAT syntax in defining a LIST partition template.

Action: Use LIST partition syntax.

ORA-36668: (XSDPART06) string is not a legal RANGE partition.

ORA-36668: (XSDPART06) string is not a legal RANGE partition.

Cause: User attempted to use CONCAT or LIST syntax in defining a RANGE partition template.

Action: Use RANGE partition syntax.

ORA-36667: (XSDPART05) string is not a legal CONCAT partition.

ORA-36667: (XSDPART05) string is not a legal CONCAT partition.

Cause: User attempted to use RANGE or LIST syntax in defining a CONCAT partition template.

Action: Use CONCAT partition syntax.

ORA-36666: (XSDPART04) workspace object is not a concat dimension.

ORA-36666: (XSDPART04) workspace object is not a concat dimension.

Cause: User tried to define a partition template with PARTITION BY CONCAT(... dim ...) where dim is not a concat dimension.

Action: Only concat dimensions can serve as partition dimensions with CONCAT partitioning. Choose a different partition dimension.

ORA-36665: (XSDPART03) workspace object is not in the dimension list of the PARTITION TEMPLATE.

ORA-36665: (XSDPART03) workspace object is not in the dimension list of the PARTITION TEMPLATE.

Cause: While defining a partition template, user attempted to specify a partition dimension that is not a dimension of the partition template itself.

Action: Choose a partition dimension from among the dimensions of the partition template.

ORA-36664: (XSDPART02) You must specify a partitioning method and one or more partition dimensions when defining a PARTITION TEMPLATE.

ORA-36664: (XSDPART02) You must specify a partitioning method and one or more partition dimensions when defining a PARTITION TEMPLATE.

Cause: User tried to define a PARTITION TEMPLATE without a PARTITION BY clause.

Action: Add a PARTITION BY clause.

ORA-36652: (XSDUNION11) workspace object is not a string type dimension.

ORA-36652: (XSDUNION11) workspace object is not a string type dimension.

Cause: The CHGDFN BASE ADD command is only valid for concat dimensions.

Action: none

ORA-36650: (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.

ORA-36650: (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.

Cause: Unique concat base dimensions cannot contain duplicate values.

Action: Use MAINTAIN RENAME to change one of the duplicate values and retry.

ORA-36648: (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.

ORA-36648: (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.

Cause: Attempt to change a concat dimension to UNIQUE, but it is already UNIQUE.

Action: none

ORA-36646: (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension.

ORA-36646: (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension.

Cause: UNIQUE keyword was used with an invalid object.

Action: Retry without the UNIQUE keyword.

ORA-36644: (XSDUNION07) Concat dimension workspace object contains a previously detected leaf dimension.

ORA-36644: (XSDUNION07) Concat dimension workspace object contains a previously detected leaf dimension.

Cause: Concat dimension contains a previously detected leaf dimension.

Action: none

ORA-36643: (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.

ORA-36643: (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.

Cause: Only UNIQUE concat dimensions can have custom member values or base dimensions which contain custom member values.

Action: Remove all custom member values from the concat and all of its bases, and retry.

ORA-36642: (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.

ORA-36642: (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.

Cause: Duplicate concat leaf dimension was found.

Action: Remove duplicate concat base dimensions and retry.

ORA-36641: (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.

ORA-36641: (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.

Cause: The UNIQUE keyword was not specified in the concat dimension definition, and is required if any of its base dimensions contain custom member values.

Action: Define the concat as UNIQUE, or remove all base custom member values.

ORA-36640: (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.

ORA-36640: (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.

Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.

Action: none

ORA-36639: (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.

ORA-36639: (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.

Cause: Unique concat base dimensions cannot contain duplicate values.

Action: Use MAINTAIN RENAME to change one of the duplicate values and retry.

ORA-36638: (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.

ORA-36638: (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.

Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat.

Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry.

ORA-36637: (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.

ORA-36637: (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.

Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat.

Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry.

ORA-36636: (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.

ORA-36636: (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.

Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat.

Action: CHGDFN any dependent unique concat dimensions to NOT UNIQUE and retry.

ORA-36635: (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition.

ORA-36635: (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition.

Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.

Action: Specify a valid list of dimensions when defining a unique concat dimension.

ORA-36634: (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.

ORA-36634: (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.

Cause: The user cannot specify INTEGER base dimensions when defining a concat dimension.

Action: Change the datatype of the INTEGER base dimension, or omit it from the concat.

ORA-36632: (XSDUNION01) The concat dimension workspace object is not currently defined as UNIQUE.

ORA-36632: (XSDUNION01) The concat dimension workspace object is not currently defined as UNIQUE.

Cause: Attempt was made to CHGDFN a concat, which is already non-unique, to NOT UNIQUE.

Action: Since the concat is already non-unique, this command is unnecessary.

ORA-36630: (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.

ORA-36630: (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.

Cause: An empty concat dimension list was specified.

Action: Specify a valid list of dimensions when defining a concat dimension.

ORA-36628: (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.

ORA-36628: (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.

Cause: The dimension of the model must match a hierarchy of the aggmap.

Action: Add a RELATION statement to the AGGMAP for that dimension.

ORA-36618: (XSAGMODDIM00) workspace object is not a valid model for AGGMAP ADD.

ORA-36618: (XSAGMODDIM00) workspace object is not a valid model for AGGMAP ADD.

Cause: The model failed one of the following tests: 1) only one dimension (aside from LAG or LEAD dimensions); 2) assignment to dimension values only; 3) a single simple solution block; 4) no time-series functions with variable step values.

Action: Edit the model so that it conforms to the above requirements.

ORA-36612: (XSLMS01) invalid OLAP message number: value

ORA-36612: (XSLMS01) invalid OLAP message number: value

Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace attempted to retrieve a non-existent message.

Action: Contact support.

ORA-36610: (XSLMS00) Unable to locate a message file for OLAP message: value

ORA-36610: (XSLMS00) Unable to locate a message file for OLAP message: value

Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace failed to retrieve a user message.

Action: Contact support.

ORA-36608: (XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow.

ORA-36608: (XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow.

Cause: The depth of the hierarchies that are part of a composite exceeded 4 billion levels during the merge.

Action: Reduce the number of levels in the hierarchies, reduce the number of dimensions in the composite, or do not aggregate over all dimensions at once.

ORA-36410: (VCACHE03) number is an invalid value for the $VARCACHE property. The only permissible values are DEFAULT , SESSION , VARIABLE, and NONE .

ORA-36410: (VCACHE03) number is an invalid value for the $VARCACHE property. The only permissible values are DEFAULT , SESSION , VARIABLE, and NONE .

Cause: The user tried to assign an invalid value to the $VARCACHE property on a variable

Action: Assign one of the valid values

ORA-36406: (VCACHE00) number is an invalid value for the VARCACHE option. The only permissible values are SESSION , VARIABLE , and NONE .

ORA-36406: (VCACHE00) number is an invalid value for the VARCACHE option. The only permissible values are SESSION , VARIABLE , and NONE .

Cause: The user tried to assign an invalid value to the VARCACHE option

Action: Assign one of the valid values

ORA-36405: (XSSPROP05) Property ignored for object workspace object:

ORA-36405: (XSSPROP05) Property ignored for object workspace object:

Cause: A property was ignored during import.

Action: Refer to the message that follows this one and correct the error it describes.

ORA-36404: (XSSPROP04) Property string cannot be applied to an undimensioned (scalar) TEMPORARY variable.

ORA-36404: (XSSPROP04) Property string cannot be applied to an undimensioned (scalar) TEMPORARY variable.

Cause: The user applied a reserved property name to an incorrect object type

Action: Apply the property to the correct object

ORA-36403: (XSBADSPROP) number is an illegal value for system-reserved property string on workspace object.

ORA-36403: (XSBADSPROP) number is an illegal value for system-reserved property string on workspace object.

Cause: The user tried to specify an illegal value for a special property

Action: Specify a legal value.

ORA-36402: (XSSPROP03) The property $string requires a leading $ because it is a system-reserved property name.

ORA-36402: (XSSPROP03) The property $string requires a leading $ because it is a system-reserved property name.

Cause: The user tried to specify a property name which is reserved, but did not use a leading $

Action: Either add a leading $ or choose another property name

ORA-36401: (XSSPROPOTYPE) Property string may only be applied to objects of type string.

ORA-36401: (XSSPROPOTYPE) Property string may only be applied to objects of type string.

Cause: The user applied a reserved property name to an incorrect object type

Action: Apply the property to the correct object

ORA-36400: (XSSPROP02) workspace object is not a valid variable name.

ORA-36400: (XSSPROP02) workspace object is not a valid variable name.

Cause: Not a valid variable name

Action: Change to a valid variable name

ORA-36399: (XSSPROPDTYPE) The data type of property string must be string.

ORA-36399: (XSSPROPDTYPE) The data type of property string must be string.

Cause: The used tried to set a system-reserved property on an OLAP object to a value with an illegal datatype

Action: Set the property with the proper datatype

ORA-36398: (XSSPROP01) Property name number is invalid because only system-reserved property names can begin with $ .

ORA-36398: (XSSPROP01) Property name number is invalid because only system-reserved property names can begin with $ .

Cause: The user attempted to add a property which starts with $ but is not a reserved property name

Action: Remove the $ from the property name

ORA-36394: (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.

ORA-36394: (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.

Cause: The user attempted to CLEAR an AGGMAP using a directive other than CACHE

Action: Amend the CLEAR line to only use the CACHE keyword with AGGMAPs.

ORA-36393: (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.

ORA-36393: (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.

Cause: The user didn t use the ALL keyword when using CHANGES or CACHE

Action: Specify the ALL keyword

ORA-36392: (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.

ORA-36392: (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.

Cause: The user didn t specify an AGGMAP with the CLEAR command

Action: Specify the AGGMAP used to aggregate the variable being cleared

ORA-36391: (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.

ORA-36391: (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.

Cause: The user specified objects whose dimensionality didn t match

Action: Break up the CLEAR command into multiple commands where the dimensionality of the objects matches

ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.

ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.

Cause: The user is attempting to use partitions as a means of sparsity control, however they have set up their partitions in a manner that simply makes no sense. It is a simple fact that during aggregation data becomes more dense, not less dense, and yet their partitions indicate the opposite.

Action: Modify the partition template add the specified dimension into the source composite, or removing it from the target composite.

ORA-36380: (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.

ORA-36380: (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.

Cause: A model, NATRIGGER, or other object called the AGGREGATE function or command while another AGGREGATE function or command was already in progress.

Action: Modify your objects so that they do not need to have two AGGREGATE commands or functions executing at once.

ORA-36378: (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.

ORA-36378: (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.

Cause: While running AGGREGATE in threaded mode, you attempted to specify a WEIGHT variable in another analytic workspace.

Action: Use a weight variable from the same analytic workspace as the aggmap and rollup variable.

ORA-36376: (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.

ORA-36376: (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.

Cause: A calculation in the current AGGREGATE command attempted to divide by zero as a result of an AVERAGE, WAVERAGE, HAVERAGE or HWAVERAGE operation.

Action: Either fix the data, or set DIVIDEBYZERO to YES to return NA instead of signaling an error.

ORA-36342: (SNSYN200) The format of the CLEAR command is: CLEAR ( ALL | STATUS ( ( AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ( FROM var1 (var2, var3...( (USING aggmap(

ORA-36342: (SNSYN200) The format of the CLEAR command is: CLEAR ( ALL | STATUS ( ( AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ( FROM var1 (var2, var3...( (USING aggmap(

Cause: The syntax for the CLEAR command was invalid.

Action: Modify your syntax using the correct format.

ORA-36341: (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)

ORA-36341: (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)

Cause: Bad syntax

Action: Correct syntax

ORA-36316: (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another.

ORA-36316: (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another.

Cause: The user specified an invalid relation while attempting to use the PHYSICAL command

Action: Specify a valid relation