[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 256
  • Last Modified:

logging

why we are using force logging while dataguard setup..
0
dev_dba
Asked:
dev_dba
  • 5
  • 3
  • 3
  • +1
1 Solution
 
chaauCommented:
Do you realise that the person who interviews you may have an account at EE?
0
 
dev_dbaAuthor Commented:
There is no interview ,
I ask when I cannot find satisfied answers from google.
I hope you can understand,
0
 
slightwv (䄆 Netminder) Commented:
What part from the docs is confusing?

http://docs.oracle.com/cd/E11882_01/server.112/e10803/config_dg.htm#HABPT4887

In a nutshell:  If you perform some operations that specify nologging, for example: inserts into a nologging table, the changes are forced into the logs anyway so they can be picked up and sync'ed in the standby database.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
dev_dbaAuthor Commented:
Could any other experts answer my question..
0
 
johnsoneSenior Oracle DBACommented:
What answer are you looking for?  I can reword slightwv's answer, but it would be the same answer.
0
 
dev_dbaAuthor Commented:
Keeping going if any other experts...
0
 
slightwv (䄆 Netminder) Commented:
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?
0
 
johnsoneSenior Oracle DBACommented:
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.
0
 
slightwv (䄆 Netminder) Commented:
>> 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.
0
 
johnsoneSenior Oracle DBACommented:
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.
0
 
dev_dbaAuthor Commented:
Thanks..
0
 
dev_dbaAuthor Commented:
Thanks
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 5
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now