Oracle Database Errors or Warnings from Error ORA-33223 to ORA-33270


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-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-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-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-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-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-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-33268: (DBERRTHW) Analytic workspace string cannot be attached with the THAW option because it was frozen with the NOTHAW option
Cause: An attempt to attach the AW using the thaw option was made; the AW was frozen using the NOTHAW option.
Action: Either attempt the command again without the THAW option.
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
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.

Above are list of Oracle Database Errors or Warnings from Error ORA-33223 to ORA-33270 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.

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 *