Re: Todays Oracle 11.2.0.2 quiz...
- From: Kellyn Pot'vin <kellyn.potvin@xxxxxxxxx>
- To: "troach@xxxxxxxxx" <troach@xxxxxxxxx>, "robertgfreeman@xxxxxxxxx" <robertgfreeman@xxxxxxxxx>
- Date: Tue, 2 Aug 2011 09:38:14 -0700 (PDT)
For a quiz I pick "C", for my large database environments that are reality, I
would have to say for the majority of objects, "C" is fine and for 20%, I need
"A" and other options... Now ask me why I think my developers choices in code,
hints that are in use and design demand the change and it's not Oracle fault...
:)
________________________________
From: Thomas Roach <troach@xxxxxxxxx>
To: robertgfreeman@xxxxxxxxx
Cc: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
Sent: Tuesday, August 2, 2011 9:44 AM
Subject: Re: Todays Oracle 11.2.0.2 quiz...
I vote for C. Default sample size : )
On Tue, Aug 2, 2011 at 10:16 AM, Robert Freeman <robertgfreeman@xxxxxxxxx>
wrote:
Without looking in the docs, answer this question:
>
>When collecting Oracle statistics in 11.2.0.2 (generally, there are always
>fringe cases) you should:
>
>A. Manually set the sample size and not take the default.
>B. Use the analyze command.
>C. Use the default value for the sample size.
>D. Use a sample size between 10 and 20.
>E. Set the _optimizer_stats_modify parameter first to a value of 60.
>
>What is your answer and why?
>
>RF
>
>
> Robert G. Freeman
>Master Principal Consultant, Oracle Corporation, Oracle ACE
>Author of various books on RMAN, New Features and this shorter signature line.
>Blog: http://robertgfreeman.blogspot.com
>
>
>Note: THIS EMAIL IS NOT AN OFFICIAL ORACLE SUPPORT COMMUNICATION. It is just
>the opinion of one Oracle employee. I can be wrong, have been wrong in the
>past and will be wrong in the future. If your problem is a critical production
>problem, you should always contact Oracle support for assistance. Statements
>in this email in no way represent Oracle Corporation or any subsidiaries and
>reflect only the opinion of the author of this email.
>
>
>
>
>
>
--
Thomas Roach
813-404-6066
troach@xxxxxxxxx
Other related posts:
