How to patch the Oracle Instant Client?

That’s an interesting question a customer raised the other day: How to patch the Oracle Instant Client? I silently assumed that there’s a new release of the Oracle Instant Client every quarter or at least when we deliver fixes which apply to the client as well. Hm … What is the Oracle Instant Client? First of all, the Oracle Instant Client is a pretty cool thing. It gets distributed via OTN as a simple download. You deploy it to your client machine, you set LD_LIBRARY_PATH (or PATH on Windows) and add a tnsnames file if necessary, you may add SQL*Plus…

DBMS_OPTIM_BUNDLE – only available in Oracle 12.1.0.2 – or not?

The DBMS_OPTIM_BUNDLE package got introduced with the April 2014 Exadata 11.2.0.4 Bundle Patch. And it got introduced for all Oracle 12.1.0.2 databases with the April 2017 Bundle Patch (BP). DBMS_OPTIM_BUNDLE is only available in Oracle 12.1.0.2. Addition March 6, 2018: See the updated blog post about DBMS_OPTIM_BUNDLE available in Oracle 12.2 and 18c onwards. https://mikedietrichde.com/2018/03/08/dbms_optim_bundle-package-oracle-12-2-18c/ For more information on this package on Exadata in Oracle 11.2.0.4 you may look at: MOS Note:1942966.1: Exadata: DBMS_OPTIM Package Philippe Fierens’ blog post from October 2014 Purpose of DBMS_OPTIM_BUNDLE package in Oracle 12.1.0.2 The package got introduced to enable module bug fixes which cause…

Applying the first RU for Oracle Database 12.2.0.1

The first RU (Release Update) for Oracle 12.2 is available on most platforms since July 18, 2017. And of course I started applying the first RU for Oracle Database 12.2.0.1 as soon as it got released. See: https://mikedietrichde.com/2017/07/19/first-ru-oracle-12-2-0-1-available/ Download the RU 12.2.0.1.170718 for Linux First of all I downloaded the Database RU 12.2.0.1.170718 Patch 26123830 for Linux from MyOracle Support. To my absolute surprise it was very small compared to previous Proactive Bundle Patches such as the April 2017 one. It has just 40 MB in size (no typo!). Applying the first RU for Oracle Database 12.2.0.1 Then I unzipped…

More Information about RU and RUR patches for Oracle 12.2

The first RU (Release Update) for Oracle Database 12.2.0.1 has been released. And Oracle Support provides some very helpful documents to explain the implication of the new RU (Release Update) and RUR (Release Update Revision) patches. More Information about RU and RUR patches for Oracle 12.2 First of all, these are the most important MOS notes to have a look at: MOS Note:742060.1 – Release Schedule for Current Database Releases (updated Aug 3, 2017 ) MOS Note: 2285040.1 – Release Update and Release Update Revisions for Database Proactive Patch Program MOS Note: 2275525.1 – FAQ for RU and RUR (not…

The first RU for Oracle Database 12.2.0.1 is available

The first RU (Release Update) for Oracle 12.2.0.1 is available Just in case the port you are looking for is not available right now please see the ETA dates in the link below. Details of the July 2017 Critical Patch Advisory Find the General Information about the July 2017 Critical Patch Advisory here: http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html Find the Risk Matrix for the July 2017 Critical Patch Advisory here: http://www.oracle.com/technetwork/security-advisory/cpujul2017verbose-3236625.html#DB The details about the Database are included in this document: MOS Note: 2261562.1 – Patch Set Update and Critical Patch Update July 2017 Availability Document Please find the “Missing patches” in section 2.2…

Adpative Features Patches with Oracle Peoplesoft

I’ve met David Kurtz, an Oracle ACE Director working for Accenture’s Enkitec division in the UK earlier this year on the OUGN Conference‘s boat trip from Oslo to Kiel and return. We set across the table at dinner. And of course we started discussing “Oracle”. David went to my talk about “How to ensure Performance Stability” before. He did ask me questions about the adaptive features patches I was recommending in my talk: Enabling ADAPTIVE Features of Oracle 12.2 in 12.1 The Adaptive Feature Patches I explained to him that he will have to request these specific two fixes unfortunately…

Oracle 12.2.0.1 – June 2017 Bundle Patch is available for Linux

After the removal of the first Oracle Database 12.2.0.1 Bundle Patch in May, the June 2017 Proactive Bundle Patch on Linux got released now: Oracle Database 12.2.0.1 Proactive Bundle Patch – June 2017 – BP170620 What’s inside? The Proactive Bundle Patch 12.2.0.1.170620 contains the June Database Bundle Patch and the June Grid Infrastructure Patch Set Update. More information about previous and future BPs? First of all, the well known schedule for BPs (and of course PSUs) will be kept – so please expect the next Proactive Bundle Patch at the regular date in July. My reading of the June (and…

Can you apply Bundle Patches to SE2 databases?

Can you apply Bundle Patches (BP) to Standard Edition (SE2) databases? This question got raised by Adam (thanks!) via the comments section of the blog. But a few days later I read it on the internal mailing lists as well. Adam was referring to this sentence in the BP READMEs since October 2015: “In this document Oracle Database Home refers to Enterprise Edition. Standard Edition Database software installs should install Database PSU.” Why was this sentence added? There were issues with enabling functionality on SE2 databases by accident with a Proactive Bundle Patch – something which got fixed and corrected…

Issue with 2k and 4k db_block_size – ORA-1450 when upgrading to Oracle 12.2.0.1

Recently we got alerted by a customer and a colleague from Italy about an issue with the upgrade from Oracle 12.1.0.x to Oracle 12.2.0.1 if – and only if – your database got created with 2k or 4k db block size. Problem If your database got created with 2k or 4k db block size, and you attempt an upgrade from any upgrade-supported Oracle version to Oracle Database 12.2.0.1 the upgrade – regardless of DBUA or catctl.pl – will fail with an ORA-1450: maximum key length (1478) exceeded. Analysis In the catupgrd0.log – regardless of using the DBUA or the command…

Oracle 12.2.0.1 Bundle Patch 12.2.0.1.170516 DBBP on Linux x86-64 is available [not anymore]

All credits go to Ricardo Maeda as I knew that we’ll release a Bundle Patch for Oracle 12.2.0.1 sometime this week – but I couldn’t find it linked from the usual MOS notes. And please don’t ask my why that is. Anyhow, with patch 2579308 you’ll get access to the first BP for Oracle Database 12.2.0.1. There will be a first bigger Proactive Bundle Patch in July at the usual schedule – but this one is at least a start. Plus in addition get the OPatch version 12.2.0.1.7 via patch 6880880. The BP contains: Obrigado, Ricardo! Update June 9, 2017…

PSU or BP? Patch Set Update or Bundle Patch? RUR or RU?

Well, in my new role as unofficial Junior Product Manager for Patching (just kidding) I get asked once a day (at least!) via email or in customer meetings or workshops: Should we take the PSUs or the BPs? Or RUs or RURs? Addition: I updated the blog post due to the arrival of the RUs and RURs in Oracle Database 12.2.0.1.Changes are marked in orange. See. https://mikedietrichde.com/2017/07/19/first-ru-oracle-12-2-0-1-available/ Should we take the PSUs or the BPs? RURs or RUs? PSUs are Patch Set Updates, BPs are (sometimes called: Proactive) Bundle Patches. RUs are Release Upgrades which replace the BPs in Oracle…

Keep your patch versions between Grid Infrastructure and Databases Homes in synch

I’ve had some interesting discussions with Anil Nair, our RAC Product Manager and a customer in the past days. The customer was looking for a definite statement that they can have a higher version of Patch Set Updates (PSUs) or Proactive Bundle Patches (BPs) in the Database homes than in the Grid Infrastructure home managing the resources. Can you have different PSU/BP versions between Database and GI homes? Yes, you can have a higher version PSU or BP in the Database home than in the Grid Infrastructure home managing the resources. This is implicitly documented in MOS Note 337737.1 – Oracle…

The OJVM Patching Saga – and how to solve it – Part V

Related Posts on “The OJVM Patching Saga – and how to solve it“: Part I – The OJVM Basics Part II – Important Notes and Information Part III – The Mitigation Patch Part IV – What you may have missed Part V – MOS Note explaining “Conditional Rolling Install”  MOS Note released explaining patching without STARTUP UPGRADE mode An important note regarding OJVM rolling patching has been published on MyOracle Support: MOS Note: 2217053.1 RAC Rolling Install Process for the “Oracle JavaVM Component Database PSU” (OJVM PSU) Patches “Beginning with the Jan2017 OJVM PSU patchset for 11.2.0.4 and for 12.1.0.2,…

The OJVM Patching Saga – and how to solve it – Part IV

Related Posts on “The OJVM Patching Saga – and how to solve it“: Part I – The OJVM Basics Part II – Important Notes and Information Part III – The Mitigation Patch Part IV – What you may have missed Part V – MOS Note explaining “Conditional Rolling Install”  What is missing with the “Mitigation Patch? Michael, the team lead from a large Oracle customer mailed me the other day. He wanted to disable Java on all their +600 databases by using the Mitigation Patch for OJVM. But he received a strange error when trying to enable the mitigation patch…

DBMS_QOPATCH does not work in PDBs (right now)

Thanks to Murthy who commented on this blog post and Jeannette Holland (SimCorp) who opened an SR resulting in an ER. DBMS_QOPATCH in Multitenant DBMS_QOPATCH will deliver useful information about installed patches only when executed within the CDB$ROOT. It has been designed this way for security reasons in Oracle Database 12.1 but I can easily see a need to check for installed patches within a PDB as well. Testcase I “borrowed” this test case from Jeannette’s SR: SQL> COLUMN NAME FORMAT A8 SQL> SELECT NAME, CON_ID, DBID, CON_UID, GUID FROM V$CONTAINERS ORDER BY CON_ID; NAME     CON_ID DBID       CON_UID   …

Where is the Jan 2017 PSU for Oracle Database 11.2.0.4?

Where is it? This question reached me a week ago: “Where is the January 2017 PSU for Oracle Database 11.2.0.4?” “What’s the deal?” was my first thought – just go and download it from MOS. Well, not really … Where to download Proactive Bundle Patches, Patch Set Updates and Patch Sets? My favorite note is: MOS Note:1454618.1 Quick Reference to Patch Numbers for PSU, SPU(CPU), BPs and Patchsets It gives me access to all the download links for the patch bundles I’m looking for. But for 11.2.0.4. there’s only “NA” (not available) stated: And a very small asterisk “m”: Why…

DBA_REGISTRY_HISTORY vs DBA_REGISTRY_SQLPATCH

At the DOAG Conference in November in Nürnberg in November 2016 a customer asked me right after my talk about “Upgrade to Oracle Database 12.2. – Live and Uncensored” why the DBA_REGISTRY_HISTORY does not get updated when he applies a Bundle Patch and follows all instructions including the “./datapatch -verbose” call. I was wondering as well and asked him to open an SR. Which he did. And he received the message from Support that it is not supposed to appear in Oracle 12c anymore this way but only in DBA_REGISTRY_SQLPATCH. Now I dug a bit deeper internally to get a…

October 2016 Proactive BP got replaced

Just received a message from Oracle Support this early morning as I did install the Proactive Bundle Patch from October 2016 into my Oracle Database 12.1.0.2 environment saying: Dear Oracle Customer, You are receiving this email because our recordsindicate you downloaded the following patch: Patch number: 24448103 Release: DB Proactive Bundle 12.1.0.2.161018 Platform: Linux x86-64 This patch has been replaced and is now available for download. Please review section 1.1 of the following My Oracle Support note for further technical details and instructions: Note: 2171506.1 – Oracle Database Proactive Patch 12.1.0.2.161018 Known Issues Issue found: SCAN Listener or local listener…

October 2016 PSU and BP – Database Patching?

What will you get when you download the most recent Oracle Database PSU or BP from October 2016? MOS Note: 1683799.1 – 12.1.0.2 Patch Set – Availability and Known Issues is not entirely clear. Therefore lets shed some light … The Matrix This matrix in MOS Note: 1683799.1 tells you about the availability of PSUs and BPs for a regular database installation (non-RAC, non-Exadata). But it doesn’t clearly tell you what’s included – and the names being used aren’t very revealing either. Non Exadata Non RAC   Document Description Rolling RAC Patch Download Note:24448103.8 12.1.0.2.161018 Database Proactive Bundle Patch (Oct…

October 2016 PSU and Proactive BP are available

When the leafs are falling down … … then it’s time for the October 2016 Patch Set Update (PSU) and Proactive Bundle Patches (BP). Things you need to know: General information: Critical Patch Update – October 2016 Risk Matrix for: Oracle Database Server, version(s) 11.2.0.4, 12.1.0.2 Patch Availability: MOS Note: 2171485.1 Download the Database PSU or BP: MOS Note: 1683799.1 – 12.1.0.2 Patch Set – Availability and Known Issues Interesting information: Newly scheduled final patches: Oracle Database 12.1.0.2 – July 2021 (See MOS Note 742060.1) Oracle Database 11.2.0.4 – October 2020 (See MOS Note 742060.1) I’ll update you as soon…

_rowsets_enabled – Apply patch and use the default

I while back I blogged about issues with “rowsets“, a new Oracle 12c feature which unfortunately had two known wrong result (WQR) bugs: Switch off “_rowsets_enabled” in Oracle Database 12c UPDATE: _rowsets_enabled in Oracle Database 12c What does “rowsets” actually mean? I’d like to thank Sankar, our Development manager for providing this explanation which sheds some light on how important this feature actually is: “Rowsets is a SQL execution performance enhancement introduced in Oracle RDBMS release 12.1 and further extended in a future release of the Oracle Database. Prior to 12.1, data processing in the SQL layer were done on…

RMAN Recovery Catalog with July PSU: How to resolve RASCHEMAVER and BASCHEMAVER schema mismatch

Related blog posts: RMAN Catalog Upgrade fails – ORA-02296 – error creating modify_ts_pdbinc_key_not_null (April 19, 2016) RMAN Catalog requires Enterprise Edition (EE) since Oracle Database 12.1.0.2 (April 22, 2016) RMAN Catalog Upgrade to Oracle 12.1.0.2 (August 1, 2014) Thanks to Ah Huat Tan from Amway IT Services for keeping me updated! Actually as I see that more people who got hit by this issue so I’d consider it to be worth to write about it. Problem and Analysis You’d apply the July 2016 PSU or BP. According to the readme you are required to upgrade your RMAN catalog afterwards. The…

Can I apply a BP on top of a PSU? Or vice versa? PART 2

I thought I won’t blog about this again: Can I apply a BP on top of a PSU? Or vice versa? But then a colleague of mine raised this simple question: “I have a customer that would like to change from patching using PSU to patching using Bundle Patch. I am wondering what happens if my home has had several PSUs installed. Before applying a BP, would I need to rollback one by one all the PSUs that have been installed in reverse order (tedious) OR only the latest PSU (good)?” Unfortunately the “simple” solution is hidden deep down in…

The OJVM Patching Saga – and how to solve it – Part III

Related Posts on “The OJVM Patching Saga – and how to solve it“: Part I – The OJVM Basics Part II – Important Notes and Information Part III – The Mitigation Patch Part IV – What you may have missed Part V – MOS Note explaining “Conditional Rolling Install”  What is the “Mitigation Patch? In MOS Note:1929745.1 – Oracle JavaVM Component Database Patches there’s a section called What is the Mitigation Patch. It says: “For situations where the latest OJVM PSU cannot be installed immediately there is a “Mitigation Patch” that can be used. The “Mitigation Patch” is an interim…

The OJVM Patching Saga – and how to solve it – Part II

Related Posts on “The OJVM Patching Saga – and how to solve it“: Part I – The OJVM Basics Part II – Important Notes and Information Part III – The Mitigation Patch Part IV – What you may have missed Part V – MOS Note explaining “Conditional Rolling Install”  Important Notes MOS Note: 1929745.1 – Oracle JavaVM Component Database Patches MOS Note: 1940702.1 – Database JVM Vulnerabilities FAQ MOS Note: 2165212.1 – What to do if the Database JAVAVM Component becomes INVALID After installing an OJVM Patch? This Note contains a pretty detailed removal procedure for JAVAVM as well –…