Database Administration (MOSC)

MOSC Banner

Impact of force logging statement on the database

edited Apr 15, 2009 2:12AM in Database Administration (MOSC) 4 commentsAnswered
Hi

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.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center