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
https://support.oracle.com/
http://www.oracle.com/
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
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
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
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
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
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
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
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
Cause: The AW CREATE command was passed the name of an analytic workspace that already exists
Action: Specify a different name