18 ORA-33000 to ORA-37999

Cause: The AGGMAP was already compiled by a more recent version of the product than was being used to execute this command.

Cause: The user specified a floor argument greater than the ceiling argument.

Cause: The user tried to specify a dimension in a dataflow-related clause in an aggmap which is already in another RELATION statement, DIMENSION statement, or possibly dimensioning the AGGMAP, or they specified a composite or conjoint dimension, or an object which is not a dimension

Cause: A RELATION clause in the AGGMAP named a workspace object that is not a relation.

Cause: The user specified something that was not a valid dimension or relation on a BREAKOUTDIM line in an aggmap. This might be because the object was not a valid relation, was not over the specified dimension or was multidimensional

Cause: A relation was named in a RELATION clause of the AGGMAP that is not a self-relation.

Cause: A relation was named in a RELATION clause of the AGGMAP that is not a relation for a base dimension of the AGGMAP.

Cause: PRECOMPUTE was specified both as a line in the AGGMAP and on at least one of the RELATION lines, or it was specified more than once as a line of the AGGMAP.

Cause: Two RELATION statements in the AGGMAP reference the same relation object.

Cause: A line in the AGGMAP contains invalid syntax.

Cause: Operator variables cannot have the rollup dimension as one of their base dimensions.

Cause: An invalid argument was supplied to the OPERATOR clause in the relation statement.

Cause: An operator variable was supplied whose data type is not TEXT.

Cause: A MEASUREDIM was supplied in the AGGMAP that was not acceptable.

Cause: The aggmap contains multiple instances of a clause that can only be specified once.

Cause: The AGGMAP either specified multiple PROTECT statements not on a RELATION line, or specified PROTECT statements both independently and on RELATION lines.

Cause: An ARGS value had a non-text data type.

Cause: The AGGMAP contained multiple SCREENBY clauses.

Cause: The AGGMAP contains incompatible RELATION statements.

Cause: The user attempted to aggregate a variable in another analytic workspace.

Cause: The user attempted to aggregate a variable with different dimensions than the AGGMAP. This is only possible with undimensioned AGGMAPs.

Cause: The user specified an invalid ERRORMASK value.

Cause: The user specified an ERRORLOG MAX of 0 or a negative number.

Cause: The user specified an invalid hierarchy dimension qualified data reference.

Cause: The user specified an invalid qualified data reference for the hierarchy dimension.

Cause: The user specified an invalid qualified data reference for the hierarchy dimension.

Cause: The user specified two conflicting hierarchy dimension qualified data references.

Cause: Multiple dimensions share the same hierarchy dimension, but it is only qualified within a subset of the AGGMAP relations.

Cause: The hierarchy dimension offset is an invalid dimension position.

Cause: The hierarchy dimension offset is an invalid dimension position.

Cause: The user specified an invalid qualified data reference for the hierarchy dimension.

Cause: The user included both RELATION and DIMENSION statements in the AGGMAP referring to the same AGGMAP.

Cause: The VALUESET statement specified a scalar valueset but did not include a qualified data reference to specify the parent.

Cause: The VALUESET line referred to a dimensioned valueset.

Cause: The specified AGGMAP was dimensioned by a conjoint dimension.

Cause: An invalid model name was attached to an AGGMAP.

Cause: formulas likely refer to each other recursively or with a great deal of depth.

Cause: An inappropriate value was specified for the named option.

Cause: An inappropriate value was specified for the named option.

Cause: The user specified a BEFORE or AFTER clause specifying a position in the range of SESSION dimension values.

Cause: The dimension has too many values.

Cause: The user tried to add a SESSION dimension value while a spreadsheet spreadsheet cursor was open.

Cause: Only UNIQUE concat dimensions can have custom member values.

Cause: The user attempted to insert a value that had too many digits into a NUMBER dimension. For instance, the user might have tried to insert the value 99999 (5 digits) into a dimension with data type NUMBER(4).

Cause: A value cannot be added to a dimension if it conflicts with an existing value in a unique concat dimension containing this dimension.

Cause: The user named a SESSION dimension value in the MAINTAIN MOVE command.

Cause: A value cannot be renamed in a dimension if the new value conflicts with an existing value in a unique concat dimension containing this dimension.

Cause: Either an internal error or a mistaken user has truncated the AW

Cause: The analytic workspace requested does not seem to be in the current database

Cause: A serious error was encountered while trying to set up the tables for the named analytic workspace. Possibilities include a tablespace that can"t be written to, corrupted metadata about which AWs exist, bogus tables with names the code expects to be able to use, or the remains of a partially removed AW.

Cause: The blocksize of the containing tablespace didn"t match database cache size.

Cause: An attempt was made to access the specified analytic workspace"s LOB table. The OLAP option detected the table had fine-grained security applied to it. The OLAP option requires full access to this table to operate correctly.

Cause: Error is raised to inform user what object was being worked on when an error occurred during the creation of an AW. It should always be signaled with 33263

Cause: The AW CREATE command was passed the name of an analytic workspace that already exists

Cause: A lock operation that was supposed to happen very quickly was taking too long. It can be due to another session being stopped while holding that lock, another session crashing while holding that lock, or an internal error.

Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in MULTI mode.

Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in RW or EXCLUSIVE mode.

Cause: Trying to wait for the workspace to become available caused a deadlock.

Cause: The AW is stored in 9i format.

Cause: An attempt to access an analytic workspace conflicted with another user"s access, and the timeout specified has elapsed.

Cause: An attempt to access an analytic workspace conflicted with another user"s access, and no timeout was specified

Cause: You do not have sufficient permissions to access this analytic workspace in the desired mode.

Cause: The user attempted to attach an old OLAP Services analytic workspace that cannot be converted by this version of OLAP Services.

Cause: User ran the DBMS_AW.CONVERT procedure on an Analytic Workspace that was created in or previously upgraded to the current compatibility mode.

Cause: The AW VALIDATE command has detected an error in the structure of the analytic workspace. This error will result in the corruption of one or more objects

Cause: This is a benign message. The AW VALIDATE command found an analytic workspace has some inaccessible space.

Cause: This is a benign message. The AW VALIDATE command found an analytic workspace has some inaccessible space.

Cause: The AW VALIDATE command does not support read-only access.

Cause: The AW VALIDATE command has detected a problem that will result in corruption of the analytic workspace. There is no corruption yet.

Cause: The AW VALIDATE command has detected a problem that will result in corruption of the analytic workspace. There is no corruption yet.

Cause: User attempted to delete a variable, but some partitioned variable was defined to use that variable as the target of one of its external partitions.

Cause: While looping over the named anonymous composite, an attempt was made to delete an object which is dimensioned by it.

Cause: There is no currently active analytic workspace. The command that generated the error requires an active analytic workspace to operate on.

Cause: The specified analytic workspace is currently not attached to the session, or the name is misspelled.

Cause: The specified analytic workspace is currently not attached to the session, or the name is misspelled.

Cause: The command requires a non-temporary analytic workspace to operate on.

Cause: Export of a compressed composite to an EIF file or lob failed because one or more of the bases had some values that were not in the current status. This can be caused either by a LIMIT command or a PERMIT READ restriction on the dimension.

Cause: The user exported an object with data type NTEXT, but the EIF file that will result from the EXPORT command is not written in Unicode. Because no non-Unicode file can represent all possible Unicode data, it is possible that some data will be lost when converting from the Unicode NTEXT object to the EIF file. The EIF file will be written in the character set indicated by the "nls_charset" argument of the EXPORT command, or, if no such argument is present, in the database character set.

Cause: User attempted to export an object whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The object will be exported as a TEXT object instead.

Cause: User attempted to export an expression whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The expression will be exported as a TEXT object instead.

Cause: A program used an analytic workspace name in a qualified object name. The named analytic workspace is not attached at program run time.

Cause: Two variables are "partition-dependent" if they share any external partition target variables, or if one is the target of an external partition of the other. If object names referred to non-partition-dependent variables at compile time but refer to partition-dependent variables in the run-time context, the OLAP DML program, formula, or model will be automatically recompiled.

Cause: Two variables are "partition-dependent" if they share any external partition target variables, or if one is the target of an external partition of the other. If object names referred to partition-dependent variables at compile time but refer to non-partition-dependent variables in the run-time context, the OLAP DML program, formula, or model will be automatically recompiled.

Cause: The datatype of the specified variable has changed.

Cause: The partitioning method (LIST, RANGE, or CONCAT) or the partition dimension of the partition template is sufficiently different from what it was when the code was compiled that the code must be recompiled.

Cause: The dimensionality of the specified object has changed.

Cause: The dimensionality of the specified object has changed.

Cause: The specified object has changed.

Cause: The type of the specified object has changed.

Cause: The type of the specified object has changed.

Cause: The specified object is not in the same analytic workspace it was in when the compiled object was compiled.

Cause: The specified object was not in the same analytic workspace it was when the compiled object was compiled

Cause: When the compiled code was saved, the specified object was a surrogate of a certain dimension. Now the specified object is a surrogate of a different dimension.

Cause: User tried to insert or delete a value of the specified dimension while some loop over that dimension was active. The loop could be an explicit FOR or ACROSS loop, or a natural expression evaluation or OLAP_TABLE loop. Also, it could be a loop over the dimension itself or over a derived dimension (like a composite or partition template) or dimension alias that includes it. The insert or delete could be explicitly caused by the MAINTAIN command. It is also possible that the user attempted to assign a value to a variable or partition dimensioned by a composite during a loop over that composite using a qualified data reference (QDR), and that the exception was generated by the engine"s attempt to insert a new position in the composite to hold the new value.

Cause: A LIMIT or MAINTAIN was attempted on the named language dimension while the boolean option LOCK_LANGUAGE_DIMS was set to YES.

Cause: User used the APPEND keyword on a CONCAT target in a FILEREAD, SQL FETCH or SQL SELECT command.

Cause: User gave the TEMPORARY keyword in the definition of an external partition whose target variable was previously defined.

Cause: User attempted to define an object that requires a certain compatibility setting in an AW that has not been upgraded to that compatibility level.

Cause: Not all kinds of dimensions can have surrogates. The user attempted to define a surrogate of a prohibited kind of dimension.

Cause: The user attempted to define a surrogate without specifying a valid data type.

Cause: The user attempted to define a surrogate on a dimension that has type DAY, WEEK, MONTH, or YEAR.

Cause: The user attempted to include both a dimension and its surrogate in the DIMENSION statement of a model.

Cause: The user attempted to include two dimension surrogates of the same dimension in the DIMENSION statement of a model.

Cause: Either two concat dimensions which share a common leaf dimension, or a concat and one of its leaves where both specified in the DIMENSION statement(s).

Cause: User attempted to MAINTAINT ADD or DELETE a list value from a RANGE or CONCAT partition template.

Cause: User attempted to MAINTAINT ADD or DELETE a list value from a LIST partition template, but didn"t specify which partition to add to or delete from.

Cause: The user tried to apply MAINTAIN DELETE to a non-SESSION value.

Cause: Only UNIQUE concat dimensions can have custom member values.

Cause: User used the ASSIGN keyword on a DIMENSION target in a FILEREAD, SQL FETCH or SQL SELECT command.

Cause: The user attempted to assign a value to a dimension surrogate whose data type is INTEGER. INTEGER surrogates, like INTEGER dimensions, cannot have values assigned to them. They can only be referenced by position.

Cause: User used the APPEND keyword on a SURROGATE target in a FILEREAD, SQL FETCH or SQL SELECT command.

Cause: A local relation or valueset has become invalid, most probably because an object used by the currently executing program has been deleted.

Cause: User attempted to CHGDFN DELETE a partition template, but some partitioned variable had data in the partition specified for deletion.

Cause: User specified an object that is not a partition template where a partition template is required.

Cause: User specified an object that is not a partitioned variable in a place where a partitioned variable is required.

Cause: User attempted to ADD a partition that already existed to a partitioned variable.

Cause: The user attempted to redefine a conjoint dimension as a composite, but the conjoint has one or more surrogates defined. A dimension that has surrogates cannot be redefined as a composite.

Cause: User supplied the COMPRESSED keyword when defining an object that was not a COMPOSITE.

Cause: The user attempted to use a COMPOSITE in the dimension list of an object that does not allow for such dimensions.

Cause: The user attempted to use NUMBER(Precision) or NUMBER(Precision, Scale) as the datatype in a definition for some object other than a DIMENSION or VARIABLE, such as a FORMULA or PROGRAM. This error can also be produced in cases where a NUMBER data type is not allowed at all.

Cause: The CONCAT keyword was used incorrectly.

Cause: User specified a dimension composite, conjoint, or partition template in a place where that kind of dimension is not allowed. For instance, a relation cannot be dimensioned by a composite, and only a variable can dimensioned by a partition template.

Cause: The user attempted to define a NUMBER dimension without specifying a precision. The proper format for declaring a number dimension is NUMBER(Precision) or NUMBER(Precision, Scale). NUMBER with no precision or scale is not allowed.

Cause: This is an informational message that reminds you that you may not save changes to the specified analytic workspace.

Cause: The command attempted to operate on an analytic workspace that is not currently attached, or the name of the analytic workspace is misspelled.

Cause: The specified analytic workspace is an internal workspace and may not be detached by the user.

Cause: The command attempted to operate on an internal analytic workspace used by the system.

Cause: The specified analytic workspace is currently in use.

Cause: User attempted to use AW UNALIAS on a non-existent alias.

Cause: Used for AW LIST output formatting when %d > 1

Cause: User included the same name twice in the alias list of an AW ALIAS or AW UNALIAS command.

Cause: Used for AW LIST output formatting when %d > 1

Cause: Used for AW LIST output formatting when %d == 1

Cause: Used for AW LIST output formatting when %d == 1

Cause: User attempted to use the MAINTAIN command with some keyword other than ADD or DELETE on a partition template.

Cause: The specified MAINTAIN operation can only be applied to UNQUE concats.

Cause: The user attempted to use the MAINTAIN command on a dimension surrogate. The MAINTAIN command can only be used with real dimensions, not surrogates.

Cause: The user attempted an invalid operation.

Cause: A SQL UPDATE or DELETE statement tried to use the CURRENT of <cursor name> syntax with a WHERE clause containing multiple conditions.

Cause: When character set conversion happens between TEXT and NTEXT either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.

Cause: Some operation required a string to be converted into a different character set, but the string contained characters that didn"t exist in the new character set.

Cause: Some operation required a string to be converted into a different character set. The string required more bytes in the new encoding, and exceeded some byte limit on its allowable length, causing some characters to be removed from the end of the string.

Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces was called. The current operation is aborted, and the Analytic Workspace detached.

Cause: An attempt was made to declare the option with the wrong datatype.

Cause: An attempt was made to declare the option without the READONLY attribute.

Cause: Execution of a PERMIT command revealed a permanent dimension or surrogate value having the same name as the SESSION value.

Cause: There must be at least one name for each month. Not enough names were provided.

Cause: There is at least one blank line in the string populating the MONTHNAMES option. We do not allow blank month names.

Cause: There must be at least one name for each day. Not enough names were provided.

Cause: There is at least one blank line in the string populating the DAYNAMES option. We do not allow blank day names.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF f