Re: init.ora parameters for 19C CDB

This may not be quite what you are asking with regards to default parameters, but two that I would recommend you change are *to* inmemory_force=BASE_LEVEL and max_pdbs=3. These permit you to utilize the free tiers of In-memory and Multitenant options without risk of jumping up to the licensed tiers. The BASE_LEVEL In-memory enables a sort of minimized 16GB inmemory_size that you can use to test the In-memory feature without an additional license. With a smaller database like the one you're working with, it might actually be useful at that level.

The max_pdbs=3 caps you at three PDBs, obviously, which is the maximum allowed without additional license, starting with 19.7 I believe.

As for the decision to stick with non-CDB format, I would also note that non-CDB is deprecated in database 20c. There's no reason to avoid the switch to CDB in your 19.x upgrade now, in my opinion anyway.

Andy

On Thu, Mar 4, 2021 at 12:59 PM <oracle_at_1001111.com> wrote:

> Hello All,
> Finally got the business to upgrade. Standard Edition, 11.2.0.4,
> nothing complex, 500GB.
> The instance is running on top-quality hardware but with extremely low
> quality code hitting it.
> Over 80% of the reports are single row fetches for example.
>
> I have already done the non-CDB upgrade, now looking at moving to the
> future. Are the
> oracle defaults for the CDB adequate? It would be a first ever if they
> are, lol
>
> Looking ahead to the production upgrade, is it worth while going to 19
> as a non-CDB and later
> move it in to a CDB or just go to PDB in a CDB initially? I will be
> testing both of course
>
> TIA
> Dave
>
> Dave Morgan
>
> Senior Consultant, 1001111 Alberta Limited
> dave.morgan_at_1001111.com
> 403 399 2442
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l