Oracle Database Errors or Warnings from Error ORA-36998 to ORA-37010

SQLServerF1

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-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/relation gid without providing the source relation
Action: use the surrogate or provide the source relation
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-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-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-37003: (AWLISTALL01) number readers
Cause: used in AW(LISTALL) output formatting when %d is 0
Action: None
ORA-37004: (AWLISTALL02) number reader
Cause: used in AW(LISTALL) output formatting when %d is 1
Action: None
ORA-37005: (AWLISTALL03) number readers
Cause: used in AW(LISTALL) output formatting when %d is > 1
Action: None

ORA-37006: (AWLISTALL04) number writers
Cause: used in AW(LISTALL) output formatting when %d is 0
Action: None
ORA-37007: (AWLISTALL05) number writer
Cause: used in AW(LISTALL) output formatting when %d is 1
Action: None
ORA-37008: (AWLISTALL06) number writers
Cause: used in AW(LISTALL) output formatting when %d is > 1
Action: None
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.

Above are list of Oracle Database Errors or Warnings from Error ORA-36998 to ORA-37010 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *