It's possible to limit redo generation for specific operations on Oracle databases, which provide higher performance. These operations include bulk inserts, creation of tables as select operations, and index creations. When we work using the
NOLOGGING clause, redo will not include all the changes to data on the related segments. This means if we perform a restore/recovery of the related datafile, or of the whole database after the
NOLOGGING operations, it'll not be possible to recover the data created with the
The same problem exists with Data Guard. When the
NOLOGGING operation is executed in the primary database, Data Guard is not able to reflect all the data changes in the standby ...