Oracle Database Recommendations 19c

Email from Oracle Support - no doubt one every year from now on, ad infinitum (should not complain really keeps us DBAs in a job).

Dear Oracle Database Customer,

Oracle Database 19c is now available on all major platforms. Oracle will be supporting Oracle Database 19c (Long Term Support Release) with Oracle Premier Support through March 2023 and with Extended Support through March 2026.

In order to stay current, minimize future upgrades and take advantage of new features, we encourage you to upgrade to Oracle Database 19c without delay.

We recommend the following upgrade options:

If you are running Oracle Database 11.2.0.4 or 12.1.0.2, you need to maintain an Unlimited License Agreement that includes Extended Support, or pay for Extended Support fees and upgrade to Oracle Database 19c before patching ends on these releases.

--Oracle Database 11.2.0.4 (Terminal patch set release for 11.2, currently in Extended Support through December 2020)

--Oracle Database 12.1.0.2 (Terminal patch set release for 12.1, currently in Extended Support through July 2021 with a fee waiver available through July 2019)

If you are running Oracle Database 12.2.0.1 or 18c, you will need to upgrade to Oracle Database 19c before the error correction end dates are reached.

--Oracle Database 12.2.0.1 (Annual release with error correction ending July 2020)

--Oracle Database 18c (Annual release with error correction ending June 2021)

The purpose of these recommendations is to help you stay within the guidelines of Lifetime Support and Error Correction Policies (allowing you to avoid costly support exceptions), and to encourage you to take advantage of the new features that are available in the latest product releases.

For questions related to certification combinations and Lifetime Support agreements with other Oracle products like Oracle E-Business Suite, Oracle JD Edwards, Oracle PeopleSoft, and Oracle Siebel, please contact your Oracle Account Representative.

For questions about the Oracle Database 19c upgrade process, refer to the following MOS Community topic:

--Planning on or Currently Upgrading to 19c?

For additional information, refer to:

--Release Schedule of Current Database Releases (Doc ID 742060.1).

Regards,

Oracle Support

Swamped by audit files

Seeing massive numbers of .aud files on many of the server I am working on.

Uwe has beaten me to it :

https://uhesse.com/2015/07/24/audit_sys_operations-defaults-to-true-in-oracle-12c/

Many of the audit files relate to the dbms_stats job. Wondering if there is a way to somehow filter what oracle decides to audit; seems to be all or nothing.

Going to investigate purging using the link below, rather than manually deleting the files at the o/s level.

https://aprakash.wordpress.com/2012/01/20/use-dbms_audit_mgmt-for-purging-audit-files-at-os-level/

See also :

https://www.durham.computer/search?q=clearing

Cloning a pluggable database

Not going to reinvent the wheel, all the information you need here :

https://oracle-base.com/articles/12c/multitenant-hot-clone-remote-pdb-or-non-cdb-12cr2

Some quick notes:

SQL> select con_id, name, open_mode, RESTRICTED from v$pdbs where NAME like 'MDS5FA%';

CON_ID NAME OPEN_MODE RES

---------- ------------------------------ ---------- ---
34 MDS5FA1 READ WRITE NO
39 MDS5FA1_20190626 MOUNTED
47 MDS5FA1_2JUN019 MOUNTED

SQL> alter session set container = MDS5FA1;

Session altered.

SQL> show pdbs;

CON_ID CON_NAME OPEN MODE RESTRICTED

---------- ------------------------------ ---------- ----------
34 MDS5FA1 READ WRITE NO

SQL> shutdown immediate;

Pluggable Database closed.

SQL> alter session set container = CDB$ROOT;

Session altered.

SQL> select con_id, name, open_mode, RESTRICTED from v$pdbs where NAME like 'MDS5FA%';

CON_ID NAME OPEN_MODE RES

---------- ------------------------------ ---------- ---
34 MDS5FA1 MOUNTED
39 MDS5FA1_20190626 MOUNTED
47 MDS5FA1_2JUN2019 MOUNTED

-- Use read only so no worries about date changes.

SQL> alter pluggable database MDS5FA1 open read only force;

Pluggable database altered.

SQL> create pluggable database MDS5FA1_10JUN2019 from MDS5FA1;