Message-ID: <0beb08db-3a0d-1a8f-fa07-37cc7716f7f4@gmail.com>
Date: Wed, 17 Nov 2021 15:53:39 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.3.0
Subject: Re: Things to consider during upgrade/migration
Content-Language: en-US
To: oracle-l@freelists.org
References: <CAKna9VZd8SmTOytxCexPBzjGtU_rPU8WJGM6tCBL9Foag9hWLQ@mail.gmail.com>
 <CO1PR19MB49841DF2D90CC41F9D917DEE9B969@CO1PR19MB4984.namprd19.prod.outlook.com>
 <53b301d7da27$fb3a4a40$f1aedec0$@rsiz.com>
 <CAKna9VbFx0AYStv+cznZXOOmqNvFi-H4ynR5o=9CwMMkgjtCAQ@mail.gmail.com>
 <543f01d7da6a$129656b0$37c30410$@rsiz.com>
 <CACj1VR610e9ESXSnvFKjCw9wFC1BMu6T7DQ+fEKc_9rbWczsHg@mail.gmail.com>
 <55f501d7dbd4$75a9f020$60fdd060$@rsiz.com>
 <CAKna9Vaa-Kmc6jY8q7EVCgHF_QKgKGWA0XOP6YOmFA6RYdL4kA@mail.gmail.com>
From: Mladen Gogala <gogala.mladen@gmail.com>
In-Reply-To: <CAKna9Vaa-Kmc6jY8q7EVCgHF_QKgKGWA0XOP6YOmFA6RYdL4kA@mail.gmail.com>
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: gogala.mladen@gmail.com

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 11/17/21 12:28, Lok P wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKna9Vaa-Kmc6jY8q7EVCgHF_QKgKGWA0XOP6YOmFA6RYdL4kA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Yes Mark, so my point was, we already have ~9 sqls
        which are using baseline in current 11.2. version and of course
        have optimizer_use_sql_plan_baselines set as TRUE(which is
        default). But Now that we will be
        setting optimizer_capture_sql_plan_baselines to TRUE a few days
        before 19C upgrade on production to get hold of all the
        possible sql and their plans(say we captured ~1000 sqls
        baseline), but we don't want all of those to be enabled at that
        same moment. rather we want only to enable the baseline for
        those ~9 old sqls + additional few sql (say e.g. 3 sqls )
        which misbehaved/changed plan post upgrade to 19c. And we want
        to drop/get rid of those other ~997 sql baselines from our 19C
        version database (which we captured initially just for our
        safety). So considering its inplace upgrade and we don't have an
        exact test environment like RAT, is there a way to achieve this
        in the existing production database? I am still unable to get it
        clearly.</div>
      <br>
    </blockquote>
    <p>Well Lok, the way I see it, you're in the so called "Bridge of
      Death" situation. <br>
    </p>
    <p><span class="Rxerq">Must answer these questions three, the other
        side to see. And these questions are about your SQL. The only
        way you will answer the questions is by testing. Test, test and
        then test again. And then retry the answers to the questions
        three. </span><span class="Rxerq"><span class="Rxerq">Nobody
          can give you the exact recipe how to migrate your database.  </span>Well,
        you have to know these things when you're a DBA. Think of the
        brave Sir Robin and start testing.<br>
      </span></p>
    <pre class="moz-signature" cols="72">-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
<a class="moz-txt-link-freetext" href="https://dbwhisperer.wordpress.com">https://dbwhisperer.wordpress.com</a>
</pre>
  </body>
</html>
--
http://www.freelists.org/webpage/oracle-l