ORA-37080: Advice requested for hierarchy with too many levels

ORA-37080: Advice requested for hierarchy with too many levels

Cause: A request was made for advice on a hierarchy with more levels than are supported.

Action: Only request advice for hierarchies with less than 32 levels.

ORA-37079: (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.

ORA-37079: (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.

Cause: The current aggmap may be for ALLOCATE

Action: Choose the correct aggmap for AGGREGATE only.

ORA-37078: (XSMCSESS06) The dimension being maintained (workspace object) cannot also be used as a step dimension.

ORA-37078: (XSMCSESS06) The dimension being maintained (workspace object) cannot also be used as a step dimension.

Cause: The dimension being maintained was named as a step dimension.

Action: Remove this dimension from the list of step dimensions.

ORA-37077: (XSMCSESS05) Object workspace object is specified more than once.

ORA-37077: (XSMCSESS05) Object workspace object is specified more than once.

Cause: The same object name was given more than once in the apply clause or in the step dimension list.

Action: Remove the repetitions.

ORA-37076: (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.

ORA-37076: (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.

Cause: The user tried to add a SESSION value to a dimension type that does not support SESSION values.

Action: Use a dimension of one of the listed types.

ORA-37075: (XSMCSESS03) You cannot rename a session-only dimension value.

ORA-37075: (XSMCSESS03) You cannot rename a session-only dimension value.

Cause: The user tried to apply MAINTAIN RENAME to a SESSION value.

Action: Delete the old value and add a new one with the desired name.

ORA-37074: (XSMCSESS02) Variable workspace object has no default aggmap.

ORA-37074: (XSMCSESS02) Variable workspace object has no default aggmap.

Cause: The applied variable has no default aggmap

Action: Use variable with the default aggmap or aggmap directly

ORA-37073: (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.

ORA-37073: (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.

Cause: Applied relation has the different dimension from the dimension currently being maintained

Action: Maintain relation dimension

ORA-37072: (XSMCSESS00) Object workspace object has the wrong type.

ORA-37072: (XSMCSESS00) Object workspace object has the wrong type.

Cause: The object is not of the object type specified in the APPLY clause

Action: Specify the correct object type

ORA-37071: You may not execute a parallel OLAP operation against updated but uncommitted AW string.

ORA-37071: You may not execute a parallel OLAP operation against updated but uncommitted AW string.

Cause: The user attempted to use a parallel feature against an AW which they updated but which has not been committed

Action: Commit the current changes

ORA-37070: You may not execute OLAP DML programs in a parallel query session.

ORA-37070: You may not execute OLAP DML programs in a parallel query session.

Cause: The user attempted to execute a DML program inside of a parallel query session, perhaps in parallel aggregate

Action: Adjust the job so that a program does no need to be executed, or disable parallelism

ORA-37069: You may not execute a parallel OLAP operation against the EXPRESS AW.

ORA-37069: You may not execute a parallel OLAP operation against the EXPRESS AW.

Cause: A parallel OLAP command attempted to execute against EXPRESS.

Action: Contact Oracle support. Users should not see this message.

ORA-37060: (XSMCSESS08) number is not a valid custom member in dimension workspace object.

ORA-37060: (XSMCSESS08) number is not a valid custom member in dimension workspace object.

Cause: No custom member or invalid custom member

Action: Create the custom member or use the correct custom member

ORA-37050: (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.

ORA-37050: (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.

Cause: One cannot use the RELATION command on objects in an analytic workspace attached in MULTI mode.

Action: Change the default relation when the analytic workspace is attached in RW or Exclusive mode.

ORA-37044: (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync.

ORA-37044: (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync.

Cause: Could not acquire the object without resync because another user has committed a newer version of it already.

Action: Try to acquire this object with resync parameter

ORA-37043: (XSACQUIRE_DEP_OLDGEN) Composite, concat, dimension map, or internal partition workspace object cannot be locked since another user has committed a new one already.

ORA-37043: (XSACQUIRE_DEP_OLDGEN) Composite, concat, dimension map, or internal partition workspace object cannot be locked since another user has committed a new one already.

Cause: Some object required locking a composite, concat, dimension map, or internal partition in the present generation, which is not possible since a newer generation already exists.

Action: Try to acquire the main object with resync

ORA-37042: (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object since doing so would cause a deadlock.

ORA-37042: (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object since doing so would cause a deadlock.

Cause: Some object required locking a composite, concat, dimension map, or internal partition, which would cause a deadlock

Action: Release some other object that another user is waiting for and try to acquire this object again.

ORA-37041: (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.

ORA-37041: (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.

Cause: Some object required locking a composite, concat, dimension map, or internal partition, which could not be locked for a while since it is locked by another user

Action: Try to acquire this object later

ORA-37040: (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.

ORA-37040: (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.

Cause: Some object required locking a composite, concat, dimension map, or internal partition, which is locked by another user

Action: Try to acquire this object later

ORA-37039: (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.

ORA-37039: (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.

Cause: One cannot use TRIGGER command on objects in an analytic workspace attached in MULTI mode.

Action: Do all persistent object maintenance in read-write mode.

ORA-37038: (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.

ORA-37038: (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.

Cause: One cannot used CHGDFN command on objects in an analytic workspace attached in MULTI mode.

Action: Do all persistent object maintenance in read-write mode.

ORA-37037: (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.

ORA-37037: (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.

Cause: One cannot rename objects in an analytic workspace attached in MULTI mode.

Action: Do all persistent object maintenance in read-write mode.

ORA-37036: (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode.

ORA-37036: (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode.

Cause: One cannot delete objects in an analytic workspace attached in MULTI mode.

Action: Do all object in read-only or read-write mode.

ORA-37035: (XSMLTDCL01) You can only DEFINE SESSION objects in analytic workspace string because it is attached in MULTI mode.

ORA-37035: (XSMLTDCL01) You can only DEFINE SESSION objects in analytic workspace string because it is attached in MULTI mode.

Cause: Persistent object definition in multiwriter mode is not allowed.

Action: Do all persistent object definitions in read-write mode.

ORA-37032: (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.

ORA-37032: (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.

Cause: User attempted to add or remove values from a LIST partition template s lists while the AW containing the partition template was attached in multiwriter mode.

Action: Do the maintenance in read only or read-write mode.

ORA-37031: (XSMLTMAINT02) You cannot DELETE values of dimension workspace object in MULTI mode.

ORA-37031: (XSMLTMAINT02) You cannot DELETE values of dimension workspace object in MULTI mode.

Cause: DELETE is allowed in multiwriter mode only for SESSION dimension members

Action: Attach the AW in a R or W mode and perform the DELETE operation

ORA-37030: (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.

ORA-37030: (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.

Cause: One cannot maintain a dimension in a multiwriter AW if it is not acquired.

Action: Acquire the dimension first.

ORA-37028: (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.

ORA-37028: (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.

Cause: When one resyncs an object that is dimensioned by a dimension map, the dimension map is resynced automatically, dropping all changes. This cannot be done, however, if the automatic resync of the dimension map might cause data in an object that shares the dimension map to become NA.

Action: Resync both objects together. Alternatively, you can try to acquire the other object (that will ensure that the dimensions map is locked in the latest generation and will not be resynced when resyncing the first object), resync the first object, and release the other object.

ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.

ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.

Cause: When one resyncs an object that is dimensioned by a composite dimension, the composite dimension is resynced automatically, dropping all new tuples. This cannot be done, however, if the automatic resync of the composite dimension might cause data in an object that shares the composite dimension to become NA.

Action: Resync both objects together. Alternatively, you can try to acquire the other object (that will ensure that the composite dimension is locked in the latest generation and will not be resynced when resyncing the first object), resync the first object, and release the other object.

ORA-37026: (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.

ORA-37026: (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.

Cause: One cannot resync an object if it is dimensioned by a maintained dimension without updating that dimension or if the object is a relation and the dimension is its target.

Action: Include the maintained dimension in the update list

ORA-37023: (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.

ORA-37023: (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.

Cause: One cannot update an object if it is dimensioned by a maintained dimension without updating that dimension or if the object is a relation and the dimension is its target.

Action: Include the maintained dimension in the update list

ORA-37021: (XSMULTI02) Object workspace object is not acquired.

ORA-37021: (XSMULTI02) Object workspace object is not acquired.

Cause: The object must be acquired for this multiwriter operation

Action: Do not use this multiwriter operation on an object that is not acquired

ORA-37020: (XSMULTI01) Analytic workspace string is not in MULTI mode.

ORA-37020: (XSMULTI01) Analytic workspace string is not in MULTI mode.

Cause: The workspace for an object is not in multiwriter mode. Hence, no multiwriter operations are allowed on the objects in the workspace

Action: Attach the workspace in the multiwriter mode or do not use multiwriter commands with it.

ORA-37018: (XSACQUIRE03) Multiwriter operations are not supported for object workspace object.

ORA-37018: (XSACQUIRE03) Multiwriter operations are not supported for object workspace object.

Cause: Multiwriter presently does not work for this object type

Action: Attach the AW in RW or EXCLUSIVE modes to modify this object.

ORA-37016: (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE command.

ORA-37016: (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE command.

Cause: A list of objects to acquire with or without resync is missing

Action: Specify the list of objects to acquire

ORA-37015: (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.

ORA-37015: (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.

Cause: The object is listed in with resync list and no resync list. Such usage is ambiguous as to the user s intent on preserving or not preserving private changes.

Action: Do not list the object both with and without RESYNC

ORA-37014: (XSACQUIRE_ACQUIRED) Object workspace object is already acquired.

ORA-37014: (XSACQUIRE_ACQUIRED) Object workspace object is already acquired.

Cause: The object is already acquired

Action: Do not try to acquire this object again

ORA-37013: (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.

ORA-37013: (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.

Cause: Waiting to acquire the object would cause a deadlock

Action: Release some other object that another user is waiting for and try to acquire this object again.

ORA-37012: (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.

ORA-37012: (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.

Cause: Could not acquire (or acquire consistent) the object for a while since it is locked by another user

Action: Try to acquire this object later

ORA-37011: (XSACQUIRE_LOCKED) Object workspace object is locked by another user.

ORA-37011: (XSACQUIRE_LOCKED) Object workspace object is locked by another user.

Cause: Could not acquire (or acquire consistent) the object since it is locked by another user

Action: Try to acquire this object later

ORA-37010: (XSACQUIRE_DIFFAW) When using the CONSISTENT WITH clause, all objects must come from the same analytic workspace.

ORA-37010: (XSACQUIRE_DIFFAW) When using the CONSISTENT WITH clause, all objects must come from the same analytic workspace.

Cause: The ACQUIRE command cannot keep objects from several workspaces consistent with each other

Action: Omit the CONSISTENT WITH clause or make sure all objects being acquired belong to the same analytic workspace.

ORA-37008: (AWLISTALL06) number writers

ORA-37008: (AWLISTALL06) number writers

Cause: used in AW(LISTALL) output formatting when %d is lamp;gt; 1

Action: none

ORA-37007: (AWLISTALL05) number writer

ORA-37007: (AWLISTALL05) number writer

Cause: used in AW(LISTALL) output formatting when %d is 1

Action: none

ORA-37006: (AWLISTALL04) number writers

ORA-37006: (AWLISTALL04) number writers

Cause: used in AW(LISTALL) output formatting when %d is 0

Action: none

ORA-37005: (AWLISTALL03) number readers

ORA-37005: (AWLISTALL03) number readers

Cause: used in AW(LISTALL) output formatting when %d is lamp;gt; 1

Action: none

ORA-37004: (AWLISTALL02) number reader

ORA-37004: (AWLISTALL02) number reader

Cause: used in AW(LISTALL) output formatting when %d is 1

Action: none

ORA-37003: (AWLISTALL01) number readers

ORA-37003: (AWLISTALL01) number readers

Cause: used in AW(LISTALL) output formatting when %d is 0

Action: none

ORA-37002: Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.

ORA-37002: Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.

Cause: A severe error occurred while initializing OLAP.

Action: Contact support (and possibly OLAP development) for help in debugging the issue.

ORA-37001: You have one or more attached but unupdated analytic workspaces.

ORA-37001: You have one or more attached but unupdated analytic workspaces.

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

Action: Either issue the update command to update the AWs, or pass TRUE as the force parameter to dbms_aw.shutdown()

ORA-37000: (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.

ORA-37000: (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.

Cause: The user specified an object which is not alias dimension of the first dimension

Action: Specify an alias dimension of the first dimension

ORA-36999: (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id.

ORA-36999: (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id.

Cause: use variable or relation gid without providing the source relation

Action: use the surrogate or provide the source relation

ORA-36998: (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.

ORA-36998: (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.

Cause: either level order valueset or level relation has wrong level dimension.

Action: choose the correct level dimension

ORA-36997: (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.

ORA-36997: (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.

Cause: no level relation exists with level order valueset.

Action: provide the level relation.

ORA-36996: (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.

ORA-36996: (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.

Cause: Valueset doesn t match the dimension

Action: Change the valueset s dimension

ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.

ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.

Cause: more than 1 hierarchies in the current computing scope.

Action: use inhierarchy to limit

ORA-36994: (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.

ORA-36994: (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.

Cause: The surrogate dimension is not numeric

Action: Change the surrogate dimension as numeric

ORA-36993: (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.

ORA-36993: (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.

Cause: not a surrogate dimension, or the surrogate dimension is not based on the level dimension.

Action: modify or change the surrogate dimension.

ORA-36992: (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.

ORA-36992: (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.

Cause: A level relation was not specified.

Action: Specify a level relation.

ORA-36991: (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.

ORA-36991: (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.

Cause: There is a conflict between the hierarchy or level relation and the level order valueset.

Action: Choose objects that do not conflict.

ORA-36990: (XSRELGID07) The level relation workspace object should be dimensioned by a level dimension.

ORA-36990: (XSRELGID07) The level relation workspace object should be dimensioned by a level dimension.

Cause: The level relation is not dimensioned by a level dimension.

Action: Redefine the level relation or choose another relation with the correct dimensionality.