DBMS_QOPATCH

Virtual Classroom Seminar 16: Release and Patching Strategy for Oracle 19c and 23c

Posted on May 8, 2023 by Patch Recommendation Release Schedule Workshop 9

There are just two days left to sign up for our Virtual Classroom Seminar 16: Release and Patching Strategy for Oracle 19c and 23c. We’ll talk to you on Wednesday, May 10 at 16:00h CET.

What’s the topic?

We’ll try to cover everything for your best release and patching strategy with Oracle Database 19c of course, but also moving forward to Oracle Database 23c. Our big focus will be several aspects of patching. You’ll hear us talking not only about standard database patching but especially about patching in RAC environments.

We’ll put together a …

Continue reading...

OPatch … oh OPatch … why is datapatch so stubborn?

Posted on December 15, 2018 by Patch Recommendation 14

Well, it is Friday night – and I’d rather should sleep or do something cool people tend to do on Friday night’s. But I try to verify a strange issue with DBMS_OPTIM_BUNDLE and the October 2018 Update for Oracle 12.2.0.1. I’m patching. Can you think of anything better on a Friday night than patching?

OPatch ... oh OPatch ... why is datapatch so stubborn?

Of course I know that I’m not alone. I know at least two customers I work with right now who do some maintenance jobs tonight as well. And I’m struggling with OPatch … oh OPatch … why is datapatch so stubborn?

My test setup

I have …

Continue reading...

DBMS_QOPATCH does not work in PDBs (right now)

Posted on February 8, 2017 by Oracle Database 12.2.0.1 Oracle Database 12c Patch Recommendation Single-/Multitenant 4

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    GUID
 --------
… Continue reading...

How to find out if a PSU has been applied? DBMS_QOPATCH

Posted on February 2, 2016 by Patch Recommendation 10

pflaster.jpgSince we change the PSU and BP patch numbering from Oracle Database 12.1.0.2.PSU6 to 12,1,0,2,160119 it is almost impossible to distinguish from the patch name only if you have applied a PSU or a BP.

But:
In Oracle Database 12c there’s a package available which is very useful to query plenty of information about patches from within the database: DBMS_QOPATCH.

Here are a few helpful examples which I created by checking in our DBaaS Cloud database.

Which patches have been applied (or rolled back)?

SQL> set serverout on

SQL> exec dbms_qopatch.get_sqlpatch_status;

Patch Id : 20415564
        Action : APPLY
        Action
… Continue reading...
Mike Dietrich
Oracle Senior Director of Product Manager for Database Upgrade, Migrations and Patching writing just another blog.

Opinions certainly are my own as is this page.

Archives

Categories

Upgrade @YouTube

Subscribe via Email

Join 7,331 other subscribers

Follow me on Twitter