Hello All,
-- Summary: trying to fix "ORA-26040: Data block was loaded using the NOLOGGING option" at physical standby database.
-- Problem description:
For physical standby database, simulated several no logging operations on primary side, received "ORA-26040: Data block was loaded using the NOLOGGING option" at the standby side.
-- Action:
I'm trying to follow "The Gains and Pains of Nologging Operations (Doc ID 290161.1)" to fix the issue, in the solution section of the doc, it lists several steps:
1. stop Redo Apply (recover managed standby database cancel)
2. offline corresponding datafile(s) (alter database datafile <NAME> offline drop;)
3. start Redo Apply (recover managed standby database disconnect)
4. copy the appropriate backup datafiles over from the primary database (e.g. use RMAN to backup datafiles and copy them)
5. stop Redo Apply (recover managed standby database cancel)
6. online corresponding data files (alter database datafile <NAME> online;)
7. start Redo Apply (recover managed standby database disconnect)
Question:
For step 4, if using OS file system, I think it's good enough. But we use ASM&OMF, standby and primary have different ASM group and path. Does anyone have detailed instruction how to perform this? And no recovery is needed?
Thanks,
Janet