Discussion:
disable histogram usage at session / statement level
Jonathan Lewis
2021-03-18 11:05:20 UTC
Permalink
Here's an odd little detail from my library:

The fix_control isn't available in 10.2.0.5 but the hidden parameter is;
then neither the parameter nor the fix_control are in 11.1.0.7 then the
fix_control appears 1in 11.2.0.4.



Regards
Jonathan Lewis
Hi,
/*+ opt_param('_optimizer_use_histograms' 'false') */
Best Regards
Adding the hint
/*+ opt_param('_fix_control','9550277:1') */
seems to work.
Regards
Jonathan Lewis
Laurentiu Oprea
2021-03-18 11:10:14 UTC
Permalink
Thanks a lot, yes both methods work fine .

As a background for my question: I noticed that for a lot of tables the
stats job computed hybrid histograms on ID or PARENT_ID columns and the
cardinality estimate for joins using these columns are orders of
magnitude trillion of rows. Dropping/disabling the histogram resolves the
estimate to 20-30 millions (the expected cardinality)

Because there are so many tables I need to take now query by query and do a
quick evaluation with/without histograms and drop where I see a negative
impact.

I`m starting to think that actually the best method is to have them
disabled since the beginning and where is the case create one. (instead of
taking Maria`s advise to use auto and evaluate where they create issues) -
not to mention that because of histograms for some tables the incremental
stats don't work as expected
Hi,
/*+ opt_param('_optimizer_use_histograms' 'false') */
Best Regards
Adding the hint
/*+ opt_param('_fix_control','9550277:1') */
seems to work.
Regards
Jonathan Lewis
On Thu, 18 Mar 2021 at 09:49, Laurentiu Oprea <
Hello,
Is there a method to influence the optimizer at session / statement
level to avoid histogram (especially hybrid) usage?
Thank you.
--
*Chinar Aliyev*
Visit My :Blog <http://chinaraliyev.wordpress.com/>
Let's Connect - <http://fr.linkedin.com/pub/mohamed-houri/11/329/857/>*Linkedin
Profile <https://www.linkedin.com/in/chinaraliyev/>*
My Twitter <https://twitter.com/MohamedHouri> - ChinarAliyev
<https://twitter.com/ChinarAliyev>
Noveljic Nenad
2021-03-18 11:20:11 UTC
Permalink
«I`m starting to think that actually the best method is to have them disabled since the beginning and where is the case create one. (instead of taking Maria`s advise to use auto and evaluate where they create issues) - not to mention that because of histograms for some tables the incremental stats don't work as expected “

Disabling histograms at the outset and then enabling them explicitly as needed might actually work well.

METHOD_OPT AUTO defeats the purpose of incremental stats, as synopses have to be recreated whenever the statistic gather procedure decides to create new histograms: https://nenadnoveljic.com/blog/incremental-statistics-histogram-pitfall/

Best regards,

Nenad


From: oracle-l-***@freelists.org <oracle-l-***@freelists.org> On Behalf Of Laurentiu Oprea
Sent: Donnerstag, 18. MÀrz 2021 12:10
To: Chinar Aliyev <***@gmail.com>
Cc: Jonathan Lewis <***@gmail.com>; ORACLE-L (oracle-***@freelists.org) <oracle-***@freelists.org>
Subject: Re: disable histogram usage at session / statement level

Thanks a lot, yes both methods work fine .

As a background for my question: I noticed that for a lot of tables the stats job computed hybrid histograms on ID or PARENT_ID columns and the cardinality estimate for joins using these columns are orders of magnitude trillion of rows. Dropping/disabling the histogram resolves the estimate to 20-30 millions (the expected cardinality)

Because there are so many tables I need to take now query by query and do a quick evaluation with/without histograms and drop where I see a negative impact.

I`m starting to think that actually the best method is to have them disabled since the beginning and where is the case create one. (instead of taking Maria`s advise to use auto and evaluate where they create issues) - not to mention that because of histograms for some tables the incremental stats don't work as expected

____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.

Important Notice

This message is intended only for the individual named. It may contain confidential or privileged information. If you are not the named addressee you should in particular not disseminate, distribute, modify or copy this e-mail. Please notify the sender immediately by e-mail, if you have received this message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall prevail in any case, we take it as your authorization to correspond with you by e-mail if you send us messages by e-mail. However, we reserve the right not to execute orders and instructions transmitted by e-mail at any time and without further explanation.
E-mail transmission may not be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also processing of incoming e-mails cannot be guaranteed. All liability of Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively referred to as "Vontobel Group") for any damages resulting from e-mail use is excluded. You are advised that urgent and time sensitive messages should not be sent by e-mail and if verification is required please request a printed version.
Please note that all e-mail communications to and from the Vontobel Group are subject to electronic storage and review by Vontobel Group. Unless stated to the contrary and without prejudice to any contractual agreements between you and Vontobel Group which shall prevail in any case, e-mail-communication is for informational purposes only and is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction.
The legal basis for the processing of your personal data is the legitimate interest to develop a commercial relationship with you, as well as your consent to forward you commercial communications. You can exercise, at any time and under the terms established under current regulation, your rights. If you prefer not to receive any further communications, please contact your client relationship manager if you are a client of Vontobel Group or notify the sender. Please note for an exact reference to the affected group entity the corporate e-mail signature. For further information about data privacy at Vontobel Group please consult www.vontobel.com <https://www.vontobel.com>.
Laurentiu Oprea
2021-03-18 12:45:40 UTC
Permalink
Thank you.

Actually my issue is that in an env where nothing is happening if I gather
stats on some particular tables where incremental is enabled and regather
them immediately reconstruct 90% of the histograms. I basically hit a bug
with the query responsable with the quality of histograms (disabling fix
16726844 eliminates this issue)
Post by Noveljic Nenad
«I`m starting to think that actually the best method is to have them
disabled since the beginning and where is the case create one. (instead of
taking Maria`s advise to use auto and evaluate where they create issues) -
not to mention that because of histograms for some tables the incremental
stats don't work as expected “
Disabling histograms at the outset and then enabling them explicitly as
needed might actually work well.
METHOD_OPT AUTO defeats the purpose of incremental stats, as synopses have
to be recreated whenever the statistic gather procedure decides to create
https://nenadnoveljic.com/blog/incremental-statistics-histogram-pitfall/
Best regards,
Nenad
Behalf Of *Laurentiu Oprea
*Sent:* Donnerstag, 18. MÀrz 2021 12:10
*Subject:* Re: disable histogram usage at session / statement level
Thanks a lot, yes both methods work fine .
As a background for my question: I noticed that for a lot of tables the
stats job computed hybrid histograms on ID or PARENT_ID columns and the
cardinality estimate for joins using these columns are orders of
magnitude trillion of rows. Dropping/disabling the histogram resolves the
estimate to 20-30 millions (the expected cardinality)
Because there are so many tables I need to take now query by query and do
a quick evaluation with/without histograms and drop where I see a negative
impact.
I`m starting to think that actually the best method is to have them
disabled since the beginning and where is the case create one. (instead of
taking Maria`s advise to use auto and evaluate where they create issues) -
not to mention that because of histograms for some tables the incremental
stats don't work as expected
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee
you should in particular not disseminate, distribute, modify or copy this
e-mail. Please notify the sender immediately by e-mail, if you have
received this message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which
shall prevail in any case, we take it as your authorization to correspond
with you by e-mail if you send us messages by e-mail. However, we reserve
the right not to execute orders and instructions transmitted by e-mail at
any time and without further explanation.
E-mail transmission may not be secure or error-free as information could
be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of
Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively
referred to as "Vontobel Group") for any damages resulting from e-mail use
is excluded. You are advised that urgent and time sensitive messages should
not be sent by e-mail and if verification is required please request a
printed version.
Please note that all e-mail communications to and from the Vontobel Group
are subject to electronic storage and review by Vontobel Group. Unless
stated to the contrary and without prejudice to any contractual agreements
between you and Vontobel Group which shall prevail in any case,
e-mail-communication is for informational purposes only and is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction.
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your
consent to forward you commercial communications. You can exercise, at any
time and under the terms established under current regulation, your rights.
If you prefer not to receive any further communications, please contact
your client relationship manager if you are a client of Vontobel Group or
notify the sender. Please note for an exact reference to the affected group
entity the corporate e-mail signature. For further information about data
privacy at Vontobel Group please consult www.vontobel.com.
Noveljic Nenad
2021-03-18 11:13:57 UTC
Permalink
I wonder if that might indicate that both Oracle 10 and 11 have been developed simultaneously using Oracle 9 as a code base.

Best regards,

Nenad

From: oracle-l-***@freelists.org <oracle-l-***@freelists.org> On Behalf Of Jonathan Lewis
Sent: Donnerstag, 18. MÀrz 2021 12:05
To: ORACLE-L (oracle-***@freelists.org) <oracle-***@freelists.org>
Subject: Re: disable histogram usage at session / statement level




Here's an odd little detail from my library:

The fix_control isn't available in 10.2.0.5 but the hidden parameter is; then neither the parameter nor the fix_control are in 11.1.0.7 then the fix_control appears 1in 11.2.0.4.



Regards
Jonathan Lewis


____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.

Important Notice

This message is intended only for the individual named. It may contain confidential or privileged information. If you are not the named addressee you should in particular not disseminate, distribute, modify or copy this e-mail. Please notify the sender immediately by e-mail, if you have received this message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall prevail in any case, we take it as your authorization to correspond with you by e-mail if you send us messages by e-mail. However, we reserve the right not to execute orders and instructions transmitted by e-mail at any time and without further explanation.
E-mail transmission may not be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also processing of incoming e-mails cannot be guaranteed. All liability of Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively referred to as "Vontobel Group") for any damages resulting from e-mail use is excluded. You are advised that urgent and time sensitive messages should not be sent by e-mail and if verification is required please request a printed version.
Please note that all e-mail communications to and from the Vontobel Group are subject to electronic storage and review by Vontobel Group. Unless stated to the contrary and without prejudice to any contractual agreements between you and Vontobel Group which shall prevail in any case, e-mail-communication is for informational purposes only and is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction.
The legal basis for the processing of your personal data is the legitimate interest to develop a commercial relationship with you, as well as your consent to forward you commercial communications. You can exercise, at any time and under the terms established under current regulation, your rights. If you prefer not to receive any further communications, please contact your client relationship manager if you are a client of Vontobel Group or notify the sender. Please note for an exact reference to the affected group entity the corporate e-mail signature. For further information about data privacy at Vontobel Group please consult www.vontobel.com <https://www.vontobel.com>.
Loading...