ORA-34164: (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.

ORA-34164: (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.

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

Action: This is an internal error that should be referred to Oracle technical support.

ORA-34145: (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.

ORA-34145: (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.

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

Action: To assign a value to a SURROGATE in a FILEREAD, SQL FETCH or SQL SELECT command, use the ASSIGN keyword.

ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.

ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.

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.

Action: Do not attempt to assign values to an INTEGER surrogate. Values will automatically appear and disappear from the INTEGER surrogate as positions are added to or removed from the underlying dimension.

ORA-34141: (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.

ORA-34141: (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.

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

Action: To create a new dimension value in a FILEREAD, SQL FETCH or SQL SELECT command, use the APPEND keyword.

ORA-34061: (MSEXECUT11) Session-only values cannot be added to non-unique concat dimension workspace object, or any of its base dimensions.

ORA-34061: (MSEXECUT11) Session-only values cannot be added to non-unique concat dimension workspace object, or any of its base dimensions.

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

Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry.

ORA-34059: (MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension workspace object.

ORA-34059: (MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension workspace object.

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

Action: Only use MAINTAIN DELETE to remove SESSION values from a concat dimension.

ORA-34021: (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.

ORA-34021: (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.

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.

Action: Specify the partition: maintain (template) add to partition (partitionname) (values) or maintain (template) delete from partition (partitionname) (values)

ORA-34019: (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.

ORA-34019: (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.

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

Action: Partitioning in a RANGE or CONCAT partition template cannot be changed using the MAINTAIN command.

ORA-34001: (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.

ORA-34001: (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.

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).

Action: Do not specify overlapping concat dimensions, or any leaves of specified concat dimensions.

ORA-34000: (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.

ORA-34000: (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.

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

Action: Use either of the two surrogates in the DIMENSION statement of the model, but not both.

ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.

ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.

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

Action: Use either the dimension or the surrogate in the DIMENSION statement of the model, but not both.

ORA-33922: (MAKEDCL35) You cannot define a surrogate of dimension workspace object because it is a time dimension.

ORA-33922: (MAKEDCL35) You cannot define a surrogate of dimension workspace object because it is a time dimension.

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

Action: Do not attempt to define a surrogate on this dimension.

ORA-33920: (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.

ORA-33920: (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.

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

Action: Specify the data type (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the definition of the surrogate.

ORA-33918: (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.

ORA-33918: (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.

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

Action: Do not attempt to define a surrogate on this dimension.

ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.

ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.

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.

Action: Make sure that the database is running in the appropriate compatibility mode, and upgrade the AW.

ORA-33883: (MAKEDCL36) You cannot use the string attribute when you define an EXTERNAL partition with an existing target.

ORA-33883: (MAKEDCL36) You cannot use the string attribute when you define an EXTERNAL partition with an existing target.

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

Action: Any storage characteristics of the external partition are determined by the target variable. These attributes should be set when the target is defined, not when the external partition is defined.

ORA-33625: (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.

ORA-33625: (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.

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

Action: APPENDing a value to one of the CONCATs leaves automatically appends to the CONCAT.

ORA-33558: (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.

ORA-33558: (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.

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

Action: SET LOCK_LANGUAGE_DIMS to NO and retry the MAINTAIN or LIMIT.

ORA-33557: (MAINTCHK01) You cannot string values of dimension workspace object during a loop over it.

ORA-33557: (MAINTCHK01) You cannot string values of dimension workspace object during a loop over it.

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.

Action: Move the dimension maintenance or QDR-based variable assignment outside the dimension loop.

ORA-33468: (ESDREAD13) Discarding compiled code for workspace object because number is no longer a surrogate of dimension workspace object.

ORA-33468: (ESDREAD13) Discarding compiled code for workspace object because number is no longer a surrogate of dimension workspace object.

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.

Action: No action needed; program automatically recompiles.

ORA-33462: (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.

ORA-33462: (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.

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

Action: None needed.

ORA-33460: (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.

ORA-33460: (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.

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

Action: None needed.

ORA-33458: (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled.

ORA-33458: (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled.

Cause: The type of the specified object has changed.

Action: None needed.

ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.

ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.

Cause: The type of the specified object has changed.

Action: None needed.

ORA-33454: (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.

ORA-33454: (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.

Cause: The specified object has changed.

Action: None needed.

ORA-33452: (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled.

ORA-33452: (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled.

Cause: The dimensionality of the specified object has changed.

Action: None needed.

ORA-33450: (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.

ORA-33450: (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.

Cause: The dimensionality of the specified object has changed.

Action: None needed.

ORA-33449: (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.

ORA-33449: (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.

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.

Action: None needed.

ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.

ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.

Cause: The datatype of the specified variable has changed.

Action: None needed.

ORA-33447: (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.

ORA-33447: (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.

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.

Action: None needed.

ORA-33445: (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.

ORA-33445: (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.

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.

Action: None needed.

ORA-33443: (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached.

ORA-33443: (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached.

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

Action: No action necessary. The program will be automatically recompiled. It is likely that the recompile will fail with an appropriate exception code, in which case the signaled condition should be corrected and the program re-run.

ORA-33429: (EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT.

ORA-33429: (EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT.

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

Action: No action needed.

ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.

ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.

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

Action: No action needed.

ORA-33425: (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.

ORA-33425: (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.

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.

Action: If the user is certain that the contents of the NTEXT object can be represented in the specified character set, then no action is necessary. Otherwise, the user can add nls_charset UTF8 to the EXPORT command string. This will result in the EIF file being written in UTF8 Unicode, which can represent all the data contained in NTEXT objects.

ORA-33413: (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction.

ORA-33413: (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction.

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.

Action: Either set the base dimensions statuses to ALL and remove their PERMIT READ programs, or export using the NOAGGR keyword.

ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.

ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.

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

Action: Specify an analytic workspace other than EXPTEMP.

ORA-33336: (DSSEXIST04A) Analytic workspace string is not attached.

ORA-33336: (DSSEXIST04A) Analytic workspace string is not attached.

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

Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name .

ORA-33334: (DSSEXIST04) Analytic workspace string is not attached.

ORA-33334: (DSSEXIST04) Analytic workspace string is not attached.

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

Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name .

ORA-33332: (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.

ORA-33332: (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.

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

Action: Execute an AW ATTACH or AW CREATE command to establish an active workspace.

ORA-33315: (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.

ORA-33315: (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.

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

Action: Delete the object outside of a loop over the dimension.

ORA-33313: (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.

ORA-33313: (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.

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.

Action: DELETE the partitioned variable or CHGDFN DROP PARTITION the the external partition from the partitioned variable, then delete the target variable.

ORA-33309: (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)

ORA-33309: (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)

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

Action: Export and recreate the analytic workspace.

ORA-33308: (DBVALID04) SEVERE ERROR: Record number used but not allocated

ORA-33308: (DBVALID04) SEVERE ERROR: Record number used but not allocated

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

Action: Export and recreate the analytic workspace.

ORA-33306: (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string.

ORA-33306: (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string.

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

Action: Attach the analytic workspace read or write and try again.

ORA-33305: (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)

ORA-33305: (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)

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

Action: Either nothing, or export and recreate the analytic workspace

ORA-33304: (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.

ORA-33304: (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.

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

Action: Either nothing, or export and recreate the analytic workspace

ORA-33302: (DBVALID01) SEVERE ERROR: Record number multiply used.

ORA-33302: (DBVALID01) SEVERE ERROR: Record number multiply used.

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

Action: Export what you can of the analytic workspace.

ORA-33298: (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting

ORA-33298: (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting

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

Action: If upgrading the Analytic Workspace is necessary, upgrade the database instance and then re-run DBMS_AW.CONVERT. If the new features offered by upgrading the Analytic Workspace are not required, then no action is needed.

ORA-33297: (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string.

ORA-33297: (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string.

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

Action: Either create a new analytic workspace or try using a version of OLAP Services compatible with the one that created this analytic workspace.

ORA-33292: (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.

ORA-33292: (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.

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

Action: Ask the owner of the schema or OLAP DBA to grant you sufficient permissions to access the {SCHEMA}.AW${AWNAME} table (for example, SCOTT.AW$FOO table).

ORA-33290: (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.

ORA-33290: (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.

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

Action: Wait until the conflicting user is done.

ORA-33288: (DBERR15) Another user has incompatible access to analytic workspace string, and the wait timeout has expired.

ORA-33288: (DBERR15) Another user has incompatible access to analytic workspace string, and the wait timeout has expired.

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

Action: Wait until the conflicting user is done.

ORA-33284: (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.

ORA-33284: (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.

Cause: The AW is stored in 9i format.

Action: Convert the AW to a later format

ORA-33282: (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.

ORA-33282: (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.

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

Action: Release an analytic workspace that some other user might be waiting for before proceeding to attach this analytic workspace in this mode.

ORA-33280: (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.

ORA-33280: (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.

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.

Action: Either try attaching the workspace is RO, RW, or EXCLUSIVE mode or commit or roll back the transaction before trying to attach the workspace in MULTI mode.

ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.

ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.

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

Action: Either try attaching the workspace is RO or MULTI mode or commit or roll back the transaction before trying to attach the workspace in RW or EXCLUSIVE mode.

ORA-33274: (DBERR07) Timed out while trying to lock analytic workspace string for string.

ORA-33274: (DBERR07) Timed out while trying to lock analytic workspace string for string.

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.

Action: If another session is stopped, resume that session to let it release the lock. If another session has crashed, wait for a few minutes while PMON or SMON process is recovering that lock. Contact Oracle OLAP Support if none of the situations above apply.

ORA-33270: (DBERR05) Analytic workspace string already exists.

ORA-33270: (DBERR05) Analytic workspace string already exists.

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

Action: Specify a different name.

ORA-33269: while operating on string

ORA-33269: while operating on string

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 33,263

Action: See error#33263