Impact of force logging statement on the database
I would like to start a discussion on database force logging and nologging operations.
1. Nologging operations will limit the generated redo rather than eliminating it completely. so the objects are recoverable from the archived redo logs.
2. Can we write a database trigger where in we can raise an alert or stop the activity if any session tries to do a nologging operation.
3. Given the situation , a physical standby database is configured for a primary database which is in force logging mode , Will a nologging operation on the primary database affect the recovery on the standby database .
4. What are the changes that takes place when alter database force logging command is fired in a database. What are the implications on the current workload of the database, how to calculate the percentage of increase on the I/O subsystem for this change.