My Oracle Support Banner

Cloned Olap Database Gets ORA-01578 Nologging (Doc ID 374036.1)

Last updated on NOVEMBER 08, 2022

Applies to:

Oracle OLAP - Version and later
Information in this document applies to any platform.


NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

You made an  image copy of the data files from your production instance (PROD). Moved the files to a test server and restored/renamed the database to TEST.
The schema's and AW should be the same in TEST since it's a recovered version of
the same database/instance.

You get the following error message when you try to  attach the AW using Analytic Workspace

java.sql.SQLException: ORA-33272: (DBERR06) Analytic workspace TEST_USER.TESTAW
cannot be opened.

ORA-01578: ORACLE data block corrupted (file # 15, block # 59216)
ORA-01110: data file 15: '<DIR>/test_04.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
ORA-06512: at "SYS.DBMS_AW", line 18
ORA-06512: at line 1




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.