dev_dba
asked on
logging
why we are using force logging while dataguard setup..
chaau
Do you realise that the person who interviews you may have an account at EE?
ASKER
There is no interview ,
I ask when I cannot find satisfied answers from google.
I hope you can understand,
I ask when I cannot find satisfied answers from google.
I hope you can understand,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Could any other experts answer my question..
What answer are you looking for? I can reword slightwv's answer, but it would be the same answer.
ASKER
Keeping going if any other experts...
The answer is what I posted. There is no other answer.
I suppose other Experts can make something up that sounds reasonable and you can accept that?
I suppose other Experts can make something up that sounds reasonable and you can accept that?
Well, if reworded other responses is what you want then here you go.
The doc reference has already been posted.
Force logging does as the name implies. It basically disables the NOLOGGING option on all commands. You can specify it, but it won't be honored. This is done when a database has a standby because you want all of the operations duplicated in the standby.
The doc reference has already been posted.
Force logging does as the name implies. It basically disables the NOLOGGING option on all commands. You can specify it, but it won't be honored. This is done when a database has a standby because you want all of the operations duplicated in the standby.
>> This is done when a database has a standby because you want all of the operations duplicated in the standby.
Since we are re-wording:
This is done when a database has a standby AND you want all of the operations duplicated in the standby.
The reason this is important: Just because you have a standby database, does not mean you want ALL operations duplicated.
For production systems, any object created nologging is obviously not considered important for disaster recovery per say.
You have to know your database.
For my database I have a bunch of intermediate working tables for longer processes where global temp tables would not work. I created them nologging to reduce the overhead since the data in them is transactional.
There is NO reason I would ever want any data in them duplicated over in a standby database.
Since we are re-wording:
This is done when a database has a standby AND you want all of the operations duplicated in the standby.
The reason this is important: Just because you have a standby database, does not mean you want ALL operations duplicated.
For production systems, any object created nologging is obviously not considered important for disaster recovery per say.
You have to know your database.
For my database I have a bunch of intermediate working tables for longer processes where global temp tables would not work. I created them nologging to reduce the overhead since the data in them is transactional.
There is NO reason I would ever want any data in them duplicated over in a standby database.
Personally, I have always set force logging on when there is a standby. It prevented other people from messing things up that didn't know better. Someone would create a script with nologging because they read it in something they googled and data would have been lost if force logging wasn't turned on. Or, an admin who normally worked with databases that don't have a standby ran something nologging without realizing the consequences. I would rather have extra data logged and moved across than lose data.
ASKER
Thanks..
ASKER
Thanks