This content has been marked as final. Show 5 replies
ABauer wrote:INSERT /*+ APPEND */
every time we do an rman clone from production we get
ORA-01110: data file 13: '***.dbs'
ORA-26040: Data block was loaded using the NOLOGGING option
But there are no tables or indexes that have nologging switched on. We've checked the according v$ tables.
We also checked that there are no Informatica ETLat the clone timestamp.
Are there any scenarios that can unintentionally switch on nologging?
You can also consider putting your production database in FORCED LOGGING mode.
You will never have to worry about this problem again.
alter database force logging ;
It may happen for sure like when you insert /*+ append */ into table values ('abc'); and create index idx . . . nologging;
To enable force logging:
ALTER TABLESPACE users FORCE LOGGING;
ALTER DATABASE force logging;
The following operations can make use of the NOLOGGING option:
direct load with SQL*Loader
direct load INSERT (using APPEND)
alter table...split partition
alter table...move partition
create table...as select
alter index...split partition
alter index...rebuild partition
ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING - Error explanation and solution [ID 794505.1]
Are there any scenarios that can unintentionally switch on nologging?No. NOLOGGING is a result of deliberate decisions.
Create a Table with NOLOGGING
Use Direct Path Insert into a NOLOGGING Table
Rebuild an Index with NOLOGGING
Oracle, by iteslf, doesn't execute NOLOGGING operations unless it is directed to.
Hemant K Chitale