A reader, November 18, 2021 - 7:14 am UTC
Thank you for the answer. There are indeed nologging objects in this database. Do you know any cases where nologging objects are not avoidable or can be tolerated?
November 19, 2021 - 12:43 am UTC
There is nothing wrong with NOLOGGING as long as you understand the implications.
You've already seen with RMAN that it can tell you about such operations. In a nutshell, the reason NOLOGGING operations are best tracked carefully is that ideally you want to backup the impacted datafile(s) as quickly as possible after the NOLOGING operation has been done (to ensure you don't lose data in the event of a disaster).
For example, I've worked on a data warehouse system where all bulk load operations will done in nologging mode, with some automation that monitored v$datafile and the like to launch backups via RMAN.
My "default" position is always have logging until you can't :-)
"alter database force logging" is the easiest way to do that
A reader, November 19, 2021 - 3:39 pm UTC
Thank you very much for the answer!
November 22, 2021 - 2:07 am UTC
Glad we could help