ORA-37176: argument string is not valid for the sparsity advisor

ORA-37176: argument string is not valid for the sparsity advisor

Cause: An invalid argument was passed to the advisor

Action: Specify a TABLE, VIEW or SELECT statement instead

ORA-37175: column string is not a column of source data

ORA-37175: column string is not a column of source data

Cause: A dimension column was specified which did not exist in the input data

Action: Specify one of the columns of the input data

ORA-37174: source SQL must be a SELECT statement

ORA-37174: source SQL must be a SELECT statement

Cause: The user specified an INSERT, UPDATE, DELETE or other type of SQL statement

Action: Specify a SQL SELECT statement instead

ORA-37173: null dimension source data

ORA-37173: null dimension source data

Cause: The user specified NULL for one of the members of the dimension sources argument

Action: Specify a value

ORA-37172: illegal dimension type

ORA-37172: illegal dimension type

Cause: The user specified an invalid member of the DIMTYPE field in the dimension sources argument

Action: Specify one of the valid enumerated values in DBMS_AW

ORA-37171: dimension sources not specified

ORA-37171: dimension sources not specified

Cause: The user passed an empty or null collection to DBMS_AW.ADVISE_ SPARSITY

Action: Specify a valid set of dimension sources

ORA-37158: Bad clob or varray IN-args: (case string)

ORA-37158: Bad clob or varray IN-args: (case string)

Cause: When in clob or varray mode, the PL or SQL mappings of OLAP API s IDL interface methods were executed blindly with null clob or varray or non-null clob or varray containing garbages.

Action: Do not blindly execute them as doing so does not make sense unless you understand how OLAP API works internally.

ORA-37157: MDX syntax error was found in MDX query string but error text was missing

ORA-37157: MDX syntax error was found in MDX query string but error text was missing

Cause: This happened because the message file was missing.

Action: Make sure that the message file xsous.msb is located in $ORACLE_ HOME or olap or mesg and rerun your MDX query.

ORA-37156: (string)

ORA-37156: (string)

Cause: unknown

Action: Check the error message details.

ORA-37155: OLAP API bootstrap error: (case string)

ORA-37155: OLAP API bootstrap error: (case string)

Cause: OLAP API bootstraping failed.

Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Support Services.

ORA-37154: OLAP API initialization error: (case string)

ORA-37154: OLAP API initialization error: (case string)

Cause: OLAP API initialization failed.

Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Support Services.

ORA-37153: unknown exception caught: (case string)

ORA-37153: unknown exception caught: (case string)

Cause: An unknown exception was caught while MDX query was processed.

Action: Please report it to Oracle Support Services.

ORA-37152: MDX query error: (string)

ORA-37152: MDX query error: (string)

Cause: An exception occurred while MDX query was processed.

Action: Check the error message details and try again.

ORA-37151: MDX parser initialization error

ORA-37151: MDX parser initialization error

Cause: MDX parser initialization failed

Action: Please report this to Oracle Support Services.

ORA-37150: line string, column string, string

ORA-37150: line string, column string, string

Cause: MDX syntax error was found in MDX query string.

Action: Check the error message details and make the corrections.

ORA-37145: (XSTTS_PLAT) Cannot transport analytic workspace across platforms.

ORA-37145: (XSTTS_PLAT) Cannot transport analytic workspace across platforms.

Cause: The user attempted to transport a tablespace containing an analytic workspace from one platform to another.

Action: Use export or import to move an analytic workspace across platforms.

ORA-37144: (MDQUERY01) string is not a valid metadata object type for MDQUERY.

ORA-37144: (MDQUERY01) string is not a valid metadata object type for MDQUERY.

Cause: The user specified an unrecognized first argument to MDQUERY

Action: Specify a recognized object type (CUBE or DIMENSION)

ORA-37143: (XSSQLMDQ03) string is not a valid analytic workspace name.

ORA-37143: (XSSQLMDQ03) string is not a valid analytic workspace name.

Cause: The user specified an analytic workspace name not qualified by a schema name, or one or both components of the name exceed the maximum length

Action: Specify a schema-qualified analytic workspace name with components no longer than 30 characters long.

ORA-37142: (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.

ORA-37142: (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.

Cause: The user specified a host variable that was not of the correct type.

Action: Choose a different host variable.

ORA-37141: (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.

ORA-37141: (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.

Cause: The schema and analytic workspace name for the MDQUERY cursor declaration were incorrectly specified.

Action: Specify the schema and awname as a host variable name preceded by a colon, or as a text literal string of the form SCHEMA.AWNAME or *.* (quotes optional).

ORA-37140: (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace object using AGGMAP workspace object because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension.

ORA-37140: (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace object using AGGMAP workspace object because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension.

Cause: The user tried to run aggregate on a partitioned variable with a partition dimension that is a base of a COMPRESSED COMPOSITE.

Action: Repartition the data, drop the partition dimension from the aggmap, or don t use COMPRESSED COMPOSITES.

ORA-37139: (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.

ORA-37139: (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.

Cause: The user tried to AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE with an AGGMAP that included a PROTECT clause.

Action: Modify the aggmap or create a new aggmap that does not include a PROTECT clause and reaggregate.

ORA-37138: (XSCCOMP13) You cannot delete values from workspace object because it is an aggregated COMPRESSED COMPOSITE.

ORA-37138: (XSCCOMP13) You cannot delete values from workspace object because it is an aggregated COMPRESSED COMPOSITE.

Cause: The user tried to MAINTAIN DELETE from an aggregated COMPRESSED COMPOSITE.

Action: In order to perform this sort of maintenance the composite must first be cleared. This can be done by running the CLEAR AGGREGATES command on the variable dimensioning the composite. Note that this will remove all data computed during the last AGGREGATE command.

ORA-37137: (XSCCOMP12) You cannot CHGDFN workspace object because it is a COMPRESSED COMPOSITE.

ORA-37137: (XSCCOMP12) You cannot CHGDFN workspace object because it is a COMPRESSED COMPOSITE.

Cause: The user tried to CHGDFN a compressed composite

Action: If the change is desired then delete the old composite and create a new one.

ORA-37136: (XSCCOMP11) Cannot ROLLUP dimension workspace object which is a base of COMPRESSED COMPOSITE workspace object, use AGGREGATE instead.

ORA-37136: (XSCCOMP11) Cannot ROLLUP dimension workspace object which is a base of COMPRESSED COMPOSITE workspace object, use AGGREGATE instead.

Cause: The user ran ROLLUP on a variable dimensioned by a COMPRESSED COMPOSITE.

Action: Instead of using ROLLUP, generate an aggmap and use AGGREGATE

ORA-37135: (XSCCOMP10) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. The RELATION statement for dense dimension workspace object must precede RELATION statements over the bases of the COMPRESSED COMPOSITE.

ORA-37135: (XSCCOMP10) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. The RELATION statement for dense dimension workspace object must precede RELATION statements over the bases of the COMPRESSED COMPOSITE.

Cause: The user ran AGGREGATE on a variable dimensioned by a COMPRESSED COMPOSITE using an illegal AGGMAP. The AGGMAP contained a RELATION statement over some base of the COMPRESSED COMPOSITE followed by a RELATION over some other dimension of the variable.

Action: Change the order of the RELATION statements in the AGGMAP.

ORA-37134: (XSCCOMP09) You cannot add new values to workspace object because it includes positions for precomputed aggregate values.

ORA-37134: (XSCCOMP09) You cannot add new values to workspace object because it includes positions for precomputed aggregate values.

Cause: The user attempted to create a new position in a compressed composite, either directly (using MAINTAIN MERGE or MAINTAIN ADD) or by storing a value into the variable dimensioned by the compressed composite. This is not allowed when the variable has been precomputed using the AGGREGATE command. Once the AGGREGATE command is run on a variable dimensioned by a compressed composite, the compressed composite becomes read-only until the computed values are removed with the CLEAR command.

Action: Run the CLEAR AGGREGATES command to remove the computed values from the variable and then rerun the failed operation. Note that CLEAR AGGREGATES will remove all the data computed during the last AGGREGATE command on this variable.

ORA-37133: (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.

ORA-37133: (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.

Cause: The user attempted to store a value into to a variable dimensioned by a compressed composite, and the variable had previously been precomputed using the AGGREGATE command. Once the AGGREGATE command is run on a variable dimensioned by a compressed composite, it becomes read-only until the computed values are removed with the CLEAR command.

Action: Run the CLEAR AGGREGATES command to remove the computed values from the variable and then rerun the failed operation. Note that CLEAR AGGREGATES will remove all the data computed during the last AGGREGATE command on this variable.

ORA-37132: (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE.

ORA-37132: (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE.

Cause: The status of the specified dimension did not include all detail cells.

Action: Add all detail cells to the status of the dimension and reissue the AGGREGATE command.

ORA-37131: (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE.

ORA-37131: (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE.

Cause: The user specified an aggregation OPERATOR that is not supported by COMPRESSED COMPOSITES.

Action: Use a MODEL for the calculation, or use an uncompressed COMPOSITE.

ORA-37130: (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.

ORA-37130: (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.

Cause: A PRECOMPUTE clause was specified in the AGGMAP for a RELATION over a base of a COMPRESSED COMPOSITE, but AGGINDEX was ON

Action: Remove the PRECOMPUTE clause from the AGGMAP, or add AGGINDEX OFF

ORA-37129: (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.

ORA-37129: (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.

Cause: The AGGMAP was defined with a MODEL statement after a RELATION statement over a base of the COMPRESSED COMPOSITE.

Action: Change the AGGMAP so that the MODEL statements appear before the RELATION statements.

ORA-37128: (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE.

ORA-37128: (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE.

Cause: The user attempted to use a base of a COMPRESSED COMPOSITE as a partitioning dimension.

Action: Choose a dense dimension as the partition base.

ORA-37127: (XSCCOMP02) The COMPRESSED COMPOSITE workspace object must be last in the dimension list.

ORA-37127: (XSCCOMP02) The COMPRESSED COMPOSITE workspace object must be last in the dimension list.

Cause: The user attempted to DEFINE a variable dimensioned by a COMPRESSED COMPOSITE, but gave a slower varying dimension in the dimension list.

Action: Put the COMPRESSED COMPOSITE last in the dimension list when defining the VARIABLE.

ORA-37126: (XSCCOMP01) The COMPRESSED COMPOSITE workspace object can only be used as a base of a single variable.

ORA-37126: (XSCCOMP01) The COMPRESSED COMPOSITE workspace object can only be used as a base of a single variable.

Cause: The user attempted to DEFINE a variable dimensioned by a COMPRESSED COMPOSITE, but that COMPRESSED COMPOSITE is already being used by another VARIABLE.

Action: Create a second COMPRESSED COMPOSITE for the second VARIABLE or add a measure dimension to the first variable.

ORA-37122: AW Session cache disabled

ORA-37122: AW Session cache disabled

Cause: A SQL Spreadsheet was attempted while the AW Session cache was disabled.

Action: Enable the session cache and perform the query again.

ORA-37121: AW Spreadsheet invalidated

ORA-37121: AW Spreadsheet invalidated

Cause: While this cursor was open, a command was issued that changed the underlying data to become inconsistent.

Action: Perform the query again, avoid performing dimension maintenance and cache clears during spreadsheet processing.

ORA-37120: MDX string is null

ORA-37120: MDX string is null

Cause: MDX parser received a null string for syntax analysis.

Action: Prepare a non-null and well-formed MDX query string and try again.

ORA-37119: Incompatible OLAP API library load address

ORA-37119: Incompatible OLAP API library load address

Cause: The OLAP API session was executing in a process in which the OLAP API sharable library was loaded which was at a different address than the process in which the OLAP API session originated.

Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to ALWAYS, restart the instance, and try again.

ORA-37118: The OLAP API library was not preloaded.

ORA-37118: The OLAP API library was not preloaded.

Cause: In shared-server mode, the OLAP API library should be loaded during process initialization to ensure that the C++ virtual table addresses are identical in all shared-server processes. The OLAP API session was executing in a process in which the library had not been loaded.

Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to SHARED_ SERVER or ALWAYS, restart the instance, and try again.

ORA-37117: olapi history retention has been disabled

ORA-37117: olapi history retention has been disabled

Cause: Under certain circumstances, for example, when the database is read only, olapi history retention is not possible because it requires updating persistent tables from time to time. If olapi history retention has been disabled, setting _olapi_ history_retention parameter to true has no effect.

Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support.

ORA-37116: OLAP API table function error: (string)

ORA-37116: OLAP API table function error: (string)

Cause: OLAP API table function failed.

Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support.

ORA-37115: New OLAP API history is not allowed

ORA-37115: New OLAP API history is not allowed

Cause: If there are active OLAP API sessions, it is not allowed to start a new OLAP API history by setting _olapi_history_retention parameter to true.

Action: Wait until all active OLAP API sessions terminate before resetting _olapi_ history_retention parameter to true.

ORA-37114: OLAP API bootstrap error: (string)

ORA-37114: OLAP API bootstrap error: (string)

Cause: OLAP API bootstrapping failed.

Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support.

ORA-37113: OLAP API initialization error: (string)

ORA-37113: OLAP API initialization error: (string)

Cause: OLAP API initialization failed.

Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support.

ORA-37112: OLAP API requires Oracle 9.2 or later

ORA-37112: OLAP API requires Oracle 9.2 or later

Cause: The version of the OLAP API jar files that you used requires Oracle version 9.2 or later.

Action: Ensure that the URL with which the JDBC connection was opened is correct. If the RDBMS instance is running in compatibility mode for a version older than 9.2, it must be upgraded to at least 9.2.0.0.0 to be used with this version of the OLAP API.

ORA-37111: Unable to load the OLAP API sharable library: (string)

ORA-37111: Unable to load the OLAP API sharable library: (string)

Cause: This happens if: (1) the OLAP API sharable library is missing. (2) a sharable library upon which the OLAP API sharable library depends is missing. (3) the OLAP API sharable library is the wrong version.

Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support.

ORA-37108: (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.

ORA-37108: (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.

Cause: An attempt was made to add a partition to a partitioned variable. Either the partition was defined WITH AGGCOUNT and the partitioned variable was not, or the partitioned variable was defined WITH AGGCOUNT and the partition was not.

Action: Use CHGDFN ADD AGGCOUNT or CHGDFN DROP AGGCOUNT to either add or remove an AGGCOUNT from either the partition or the partitioned variable.

ORA-37107: (XSVPART07) Attempt to write to non-existent partition of workspace object.

ORA-37107: (XSVPART07) Attempt to write to non-existent partition of workspace object.

Cause: Some action attempted to write data to a partitioned variable, but the variable didn t have a partition for that data. This can result from a partition template that does not assign all possible dimension values to some subcube, or from a partitioned variable that does not have a partition for one of the partitions defined by the partition template.

Action: Make sure that the cell being written is assigned to some partition by the partition template, and that the variable has an actual partition associated with the partition of the template. Use the CHGDFN template DEFINE... command to define new partitions within the template, and the CHGDFN variable ADD... command to add new partitions to the variable. Alternatively, the PARTWRITEERR can be set to false, in which case data being written to a non-existent partition will be silently discarded.

ORA-37106: (XSVPART06) Invalid partition name number.

ORA-37106: (XSVPART06) Invalid partition name number.

Cause: The user gave an invalid partition name.

Action: Supply a valid partition name.

ORA-37105: (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions.

ORA-37105: (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions.

Cause: User attempted to create an external partition on a partitioned variable, but the variable was dimensioned by a RANGE or LIST partition template.

Action: Declare the partition INTERNAL instead of EXTERNAL, or use a CONCAT partition template in place of the RANGE or LIST partition template.

ORA-37104: (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.

ORA-37104: (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.

Cause: User attempted to define a partitioned variable with more than one partition templates, or a partition template and one or more other dimensions, in the dimension list.

Action: Use only a partition template in the dimension list of the variable. All dimensions of the variable must be included in the definition of the partition template.

ORA-37103: (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.

ORA-37103: (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.

Cause: User attempted to define a partitioned variable with an external partition, but the target of the external partition had incorrect dimensionality or datatype.

Action: Pick a different target variable. The target variable must be dimensioned by exactly the same dimensions, composites, and partition templates, in the same order, as are specified in the partition template, and must have the exact same datatype (including width, precision, and scale) as the partitioned variable itself.

ORA-37102: (XSVPART02) Invalid partition name string.

ORA-37102: (XSVPART02) Invalid partition name string.

Cause: The user gave an invalid partition name. When defining a partitioned variable, this message indicates that the partition name does not exist in the partition template. In any other context, it indicates that the partitioned variable or partition template does not have a partition with the given name.

Action: Supply a valid partition name.

ORA-37101: (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.

ORA-37101: (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.

Cause: User attempted to define or reference an AW object with the all internal phrase or internal or external partition list, but the object was not a variable, was not dimensioned by a partition template, or was an already existing target of an external partition.

Action: Eliminate phrases specific to partitioned variables from the definition string, or dimension the variable by a partition template.

ORA-37100: (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.

ORA-37100: (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.

Cause: The user has attempted to shut down OLAP, but they have active analytic workspaces whose changes have not been saved.

Action: Issue the commit command. ---- 37101 - 37110 are reserved for partitioned variables ---

ORA-37086: %s is not a valueset

ORA-37086: %s is not a valueset

Cause: An operation was attempted that supports only valuesets as precompute expressions in an aggmap, yet a different kind of precompute expression was used.

Action: Replace this limit expression with an equivalent valueset and retry the operation. General precompute expressions are deprecated.

ORA-37084: Output valueset string must match string s dimensionality

ORA-37084: Output valueset string must match string s dimensionality

Cause: A request was made for advice for a relation with different dimensionality from the output valueset.

Action: Request using objects that have the same dimensionality.

ORA-37083: Invalid object string

ORA-37083: Invalid object string

Cause: A request was made for advice with an illegal object name.

Action: Request using valid object names.

ORA-37082: Invalid percent

ORA-37082: Invalid percent

Cause: A request was made for advice with an illegal percent value.

Action: Request between 0 and 100 percent precomputation.