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 33263
Action: See error#33263
https://support.oracle.com/
http://www.oracle.com/
ORA-33267: (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
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
Action: Remove the fine-grained access control
ORA-33265: (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number
Cause: The blocksize of the containing tablespace didn't match database cache size
Action: Change either size to make them consistent, or set olap_page_pool_size to 0 to allow automatic OLAP pool management when compatibility is greater than 10.2
ORA-33263: Could not create analytic workspace string
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
Action: There should be another error on the error stack. Consult it to determine what is causing the problem and remove that table
ORA-33262: (DBERR01) Analytic workspace string does not exist
Cause: The analytic workspace requested does not seem to be in the current database
Action: Check that you are in the correct schema and have access to the requested AW
ORA-33261: (DBERRLEN) Analytic workspace string extension number truncated at number bytes while trying to read at number
Cause: Either an internal error or a mistaken user has truncated the AW
Action: Export any data if possible and restore from backup
ORA-33247: (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object
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
Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE, or either of the duplicate values could be changed to make them UNIQUE
ORA-33223: (CMOVE03) You cannot move a session-only dimension value
Cause: The user named a SESSION dimension value in the MAINTAIN MOVE command
Action: Do not try to MAINTAIN MOVE session-only dimension values
ORA-33219: (CINSERT05) %K cannot be added to workspace object because it is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object
Cause: A value cannot be added to a dimension if it conflicts with an existing value in a unique concat dimension containing this dimension
Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE, or either of the duplicate values could be renamed to make them UNIQUE
ORA-33218: (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places
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)
Action: Use a smaller number for the dimension value, or define a new dimension with a larger precision and replace the old dimension with the new one