Re: Interesting performance challege (persistent child cursor mis-match)
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Sun, 3 May 2020 13:32:25 -0400
Message-ID: <f0fd78ae-40f3-d739-2a5f-ab2d04679b8c_at_gmail.com>
> I *theorize *that UTF-8 plans are unsharable with clients who connect
> as WE8MSWIN1252 .... but SQLs that are *first *parsed by WE8MSWIN1252
> connected sessions *can be *re-used by clients that come in using UTF-8 .
Date: Sun, 3 May 2020 13:32:25 -0400
Message-ID: <f0fd78ae-40f3-d739-2a5f-ab2d04679b8c_at_gmail.com>
Hi Chris!
You can set your Widows code page to UTF8:
https://docs.microsoft.com/en-us/windows/uwp/design/globalizing/use-utf8-code-page
I believe that this would resolve your problem. As for the baseline issue, I am not sure why would baseline or tuning profile care about the language settings. This sounds like a bug.
On 5/2/20 1:12 PM, Chris Taylor wrote:
>
> I *theorize *that UTF-8 plans are unsharable with clients who connect
> as WE8MSWIN1252 .... but SQLs that are *first *parsed by WE8MSWIN1252
> connected sessions *can be *re-used by clients that come in using UTF-8 .
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 -- http://www.freelists.org/webpage/oracle-lReceived on Sun May 03 2020 - 19:32:25 CEST