Easier Patching of Oracle Database on Windows

Patching 1 Minute

We just released a new version, 24.8, of AutoUpgrade that supports the new patching features on Windows.

Further, we also made it easier to download the latest version of AutoUpgrade:

wget https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar

How Does It Work?

Here’s a simple demo of the new functionality.

Also, you can get much more information about the new patching features in general in our webinar One-Button Patching – makes life easier for every Oracle DBA.

A Few Notes

Credential File

Currently, if you use a credential file to store the username/password of the Windows service, then AutoUpgrade delete it afterwards. We consider that the most secure approach.

But that’s not suitable for automation, so in the next version of AutoUpgrade, a config file parameter will allow you to re-use the credential file repeatedly.

Missing Registry Entries

If you use the credential file – depending on your configuration – you might see that entries are missing in Windows Registry for the database instance.

You can add those manually after patching by executing:

%NEW_ORACLE_HOME%\bin\oradim.exe -edit -sid %ORACLE_SID% -startmode auto

Oradim will see that registry keys are missing and add those.

This will also be automated in a future version of AutoUpgrade. We’re also working on adding support for virtual users.

Happy Patching

AutoUpgrade patching makes it easier to patch your Oracle Database.

Give it a try on Windows, and let us know if something is missing.

Patching Oracle Database should be as easy as patching a smartphone.

Published

8 thoughts on “Easier Patching of Oracle Database on Windows”

  2. Hi Daniel,

    we are on Windows and just AU-patched 2 CDBs from 19.22 to 19.26 using “out of place”-methode and AU-Version 25.1

    After the AU-Job finished both WinServices are started from the new OraHome “19.26”. Listener still from 19.22.
    As you metioned in your Blog some Windows Registry for the database instances are missing (still in 25.1 they are missing).
    So far so good.

    We just tried to ORADIM to get those RegKeys set:

    set oracle_home=C:Oracle1919_26
    %oracle_home%binoradim.exe -edit -sid CPADBAA -startmode auto
    %oracle_home%binoradim.exe -edit -sid CPADBAB -startmode auto

    both oradim commands returned:

    DIM-00077: Failed to change service configuration.
    O/S-Error: (OS 1060) The specified service does not exist as an installed service.

    but the RegKeys were added – i recognized it 10 mins later :-/
    so the error mesage is a bit confusing or am i missing something?

    Cheers, Marco

    Like

    Reply

    1. Hi Marco,

      I’m glad to hear that you were able to patch without problems on Windows. It’s always nice to hear “battlefield-experiences” of our tool.

      You’re doing it the right way, and the error message from oradim.exe is “expected”. But as you noted, oradim.exe still creates the missing pieces, like adding registry entries.

      I agree it’s misleading, but that’s the state of oradim.exe.

      I hope that a coming version of AutoUpgrade will take care of all this for you.

      Regards,
      Daniel

      Liked by 1 person

      Reply

  3. Hi Daniel,

    thnx for the response. I have 2 more questions about AU-Patchings:

    1) you said, that there will be a config file parameter to omitt the deletion of the cred file. I had a look inside the ora docu (on 28 february) but havn’t found that new parameter. Can you please give me that new parameter?

    2) whiole setting a starttime inside the config file “patch.start_time=05/03/2025 06:30:00” is there a way to bypass it wth a parameter to do the analyze job without temporarely editing the config file ?

    thnx and best regards
    Marco

    Like

    Reply

    1. Hi Marco,

      1. It’s called delete_wincredential_file (https://docs.oracle.com/en/database/oracle/oracle-database/23/upgrd/local-parameters-autoupgrade-config-file.html#GUID-80D21BD0-DEF9-4FAC-9A0F-55B7EE9C374C).
      2. When using refreshable clone PDBs (during the REFRESHPDB stage), you can adjust the start_time of a running job using the “proceed” command (https://docs.oracle.com/en/database/oracle/oracle-database/23/upgrd/autoupgrade-command-line-parameters.html#UPGRD-GUID-46EF1C88-FDC8-41FE-99D6-C2DED7F35139).

      You can find a little information about both parameters/commands in the following slide deck:

      Click to access 2025_02_25_warsaw_workshop-1.pdf

      I plan on blogging about both in the near future.

      Regards,
      Daniel

      Like

      Reply

      1. Hi Daniel,

        thank you for your reply and awesome work you and Mike do – i must have been blind about “delete_wincredential_file” :-/

        I’m really looking forward to the upcoming blog and i will have a look into the PDF you pinned.

        thnx and regards,
        Marco

        Like

        Reply

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.