Oracle Database 18.3.0 on premises is available for download on Linux since July 23, 2018. The other ports will follow soon. And via twitter I received a question why Oracle 18.3.0 on premises includes 1.4GB patches?
Oracle 18.3.0 on premises includes 1.4GB patches?
When you unzip the downloaded database image:
then you may discover the following folder .patch_storage of 1.4GB size:
[oracle@localhost .patch_storage]$ ls -lrt total 40 drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:39 28090523_Jul_14_2018_00_03_50 drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:40 28090553_Jul_11_2018_19_20_31 drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:41 27923415_Jul_15_2018_10_33_22 drwxr-xr-x. 8 oracle dba 4096 Jul 18 19:43 NApply -rw-r--r--. 1 oracle dba 5802 Jul 18 19:43 record_inventory.txt -rw-r--r--. 1 oracle dba 92 Jul 18 19:43 LatestOPatchSession.properties -rw-r--r--. 1 oracle dba 5917 Jul 18 19:43 interim_inventory.txt drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:44 27908644_May_4_2018_01_21_02 [oracle@localhost .patch_storage]$ du -sh 1.4G
It contains 4 major subdirectories of different sizes:
- 28090523 ==>
DATABASE RELEASE UPDATE 18.3.0.0.180717
(Patch 28090523)
Size: 785MB
- 28090553 ==>
OCW RELEASE UPDATE 18.3.0.0.0 (Patch 28090553)
Size: 185MB
- 27923415 ==>
OJVM RELEASE UPDATE 18.3.0.0.180717(Patch 27923415)
Size: 374MB
- 27908644 ==>
UPDATE 18.3 DATABASE CLIENT JDK IN ORACLE HOME TO JDK8u171 (Patch 27908644)
Size 163MB
Why weren’t these patches included directly into the shipped home?
Actually they are. When you look at the time stamps of certain files you’ll recognize that it says July 18. But the .patch_storage is needed for rollback reasons. And it contains the correct scripts to adjust a freshly created databases.
Final check with the check_patches_18.sql script (CDB/DBA_REGISTRY_SQLPATCH have been changed significantly in Oracle 18c):
CON_ID ACTION_TIME PATCH_ID PATCH_TYPE ACTION DESCRIPTION SOURCE_VERSION TARGET_VERSION
---------- ------------ ---------- ---------- ---------- -------------------------------- --------------- ---------------
1 2018-07-25 27923415 INTERIM APPLY OJVM RELEASE UPDATE: 18.3.0.0.18 18.1.0.0.0 18.1.0.0.0
0717 (27923415)
1 2018-07-25 28090523 RU APPLY Database Release Update : 18.3.0 18.1.0.0.0 18.3.0.0.0
.0.180717 (28090523)
2 2018-07-25 27923415 INTERIM APPLY OJVM RELEASE UPDATE: 18.3.0.0.18 18.1.0.0.0 18.1.0.0.0
0717 (27923415)
2 2018-07-25 28090523 RU APPLY Database Release Update : 18.3.0 18.1.0.0.0 18.3.0.0.0
.0.180717 (28090523)
This means: Binary files are patched already. But databases you create need to see the SQL changes.
List of Fixes
If you’d like to see which fixes are included in 18.3.0, please see this note:
- MOS Note 2369376.1
Database 18 Proactive Patch Information - MOS Note 2369471.1
Database 18 Release Updates and Revisions Bugs Fixed Lists - MOS Note: 2384954.1
Grid Infrastructure 18 Release Updates and Revisions Bugs Fixed Lists - MOS Note: 2418149.1
OJVM 18 Release Updates Bugs Fixed Lists
–Mike
Why not remove .patch_storage from download clone image before putting out this release?
Konstantin,
I thought I was more clear in my explanation.
The download is a 18.1.0 – and the .patch_storage is needed to have the patches shipped with the release. See it as a “complete packaging”.
Cheers,
Mike
“with an automatic process which applies the patches to it.”
thanks, the main thing I missed..
Thanks 🙂
Mike
Hi Mike,
Where can we find the 18c rpm for the rpm install that is mentioned in the documentation?
https://docs.oracle.com/en/database/oracle/oracle-database/18/ladbi/running-rpm-packages-to-install-oracle-database.html#GUID-BB7C11E3-D385-4A2F-9EAF-75F4F0AACF02
It hasn’t been released yet as far as I see.
And I don’t know the reason “why”. Saw some emails but don’t know any dates yet.
Sorry for the inconvenience – Mike
Mike,
just one minor issue – check_patches_18.sql link points to 12c version: https://mikedietrichde.com/wp-content/scripts/12c/check_patches.sql instead of https://mikedietrichde.com/wp-content/scripts/18c/check_patches_18.sql
br,
Kamil
Thanks – will update it!
Cheers,
Mike
Updated the link:
https://mikedietrichde.com/wp-content/scripts/18c/check_patches_18.sql
Cheers,
Mike
Mike,
Great article as always. We are starting to plan the migration of our on-prem databases to 18c. We have been migrating from RAC to dataguard and now have mostly single instance 12.1.0.2 homes without Grid Infrastructure installs. Like many enterprises we juggle between minimizing downtime but ensuring that any required patches get applied. With 18c om-prem coming with some patches installed we have some questions going forward:
1. Since we normally only install the database RU and OJVM patches, would we be leaving ourselves in an unsupported position by rolling back the OCW patch 28090553 that is installed with 18c?
2. If the patch should remain installed, do we also need to plan on applying the OCW release updates to our single instance homes going forward or can these be ignored?
Or to put it another way is there an advantage to applying the OCW release updates to a single instance home and is this something we should have been doing all along?
Regards,
Jeff.
Hi Jeff,
thanks – and you will need the OCW patch bundles if you have Grid Infrastructure installed. That would apply to the case having ASM and/or ACFS and/or Oracle Restart environments as well. But if you have pure Single Instance installations, there’s no need for the OCW patches.
Thanks,
Mike
Note that the installation does not apply the patches in .patch_storage. What .patch_storage contains is the files needed to rollback the applied patches; the patches are already applied when you download the (18.3) zip.
Some files show a time stamp of July 18, 2018.
You may be right – and I will correct the entry 😉
Thanks!
Mike