Author Topic: Oracle DBA Question 60  (Read 59 times)

0 Members and 1 Guest are viewing this topic.

Offline ralph0595

  • Full Member
  • *
  • Posts: 107
  • Karma: +0/-0
    • View Profile
Oracle DBA Question 60
« on: April 21, 2009, 11:40:50 AM »
Question:

As a DBA, one of your tasks is to periodically monitor the alert log file and the background trace files. In doing so, you notice repeated messages indicating that Log Writer (LGWR) frequently has to wait for a redo log group because a checkpoint has not completed or a redo lg group has not been archived.
What should you do to eliminate the wait LGWR frequently encounters?

A. Increase the number of redo log groups to guarantee that the groups are always available to LGWR.
B. Increase the size of the log buffer to guarantee that LGWR always has information to write.
C. Decrease the size if the redo buffer cache to guarantee that LGWR always has information to write.
D. Decrease the number of redo log groups to guarantee that checkpoints are cl= completed prior to LGWR writing.

Answer: A

Techronnati | where technology never sleeps

Oracle DBA Question 60
« on: April 21, 2009, 11:40:50 AM »

Mountain View

 

Related Topics

  Subject / Started by Replies Last post
0 Replies
63 Views
Last post April 19, 2009, 06:01:21 AM
by ralph0595
0 Replies
64 Views
Last post April 19, 2009, 06:39:28 AM
by ralph0595
0 Replies
55 Views
Last post April 19, 2009, 06:41:37 AM
by ralph0595
0 Replies
59 Views
Last post April 19, 2009, 06:46:32 AM
by ralph0595
0 Replies
55 Views
Last post April 19, 2009, 06:51:28 AM
by ralph0595

Posting Disclaimer: Any individual may post a message in this forum and may do so anonymously. Therefore, the sole author is exclusively and entirely responsible for all opinions in that message. They do not represent the official opinions of Techronnati, its administrators or moderators or the Techronnati Management. Techronnati is merely acting as an impartial conduit for constitutionally protected free speech and is not responsible and will not be held liable for the content of such messages. All images and service logos are trademarks of their respective owners.