Skip navigation
Share This:

As per the Oracle Quarterly Patch schedule, Oracle Quarterly Patches are available from 14th January 2020. These patches will be available on the Oracles website.

 

BDA engineering team has downloaded these patches and have created the respective patch wrappers which are later consumed by BDA customers for patching purposes. This blog provides information about the availability of these patch wrappers for customers using BDA.

 

After Oracle releases quarterly patches on 14th January 2020, as usual:

     1. Uncertified patch wrappers have made available.

     2. Certified patch wrappers would be made available within 15 working days (after Oracle delivers them)

 

Kindly watch this space for more details on the delivery date of individual patch wrapper and all kinds of updates with respect to January 2020 Patch wrappers.

 

NOTE: If you have a grid environment in your infrastructure, where you use BDA provided patch wrappers to patch these grid homes and grid databases, then make sure you read the following blog and take necessary steps before patching begins.

          BDA Oracle Patch Wrappers: Confirmation From Oracle on Ownership Change for "sqlplus" file under GRID_HOME

Share This:

I’m pleased to announce that BMC Database Automation 2019 Release 3 is now available for download.

 

While you can find the complete list of enhancements in the release notes, I’ll share some of the highlights with you here:

 

  • Improved REST API – We’ve extended the API to allow you to automate even more of your process and made it easier for you to put to use.
    • New DB2 and SAP provisioning functions
    • New API calls for approval functions and patch conflicts.
    • A new Swagger UI that makes it easy to learn and test calls for the API

 

  • Compliance: DISA compliance rules have been updated to the latest standards for Oracle and SQL Server.  This helps you automate the process of auditing your databases and applying the settings needed to keep them secure. 

              

  • IBM DB2 11.5 (Enterprise Server Edition) support

 

  • Patch level via the UI: You can now add Microsoft patch level via the BDA user interface.  No need to edit the file manually when updating to address a newly released Microsoft Patch

 

  • Oracle 19c Media Path: The Oracle 19c media path has been updated so that you no longer need to unzip the media for version 18c and forward

 

  • Security enhancements – Our security team is constantly scanning the code and testing the product to ensure it’s updated for any new threats.  This version continues that process with several new updates.

 

  • Bug Decimation – We’ve crushed a number of bugs to make the product even more reliable. You can find the list here.

 

If you have any questions or feedback, you can post them in the comments here, you can post a new message in the Bladelogic Database Automation community, or you can contact the support team by logging a ticket here.

 

On behalf of the Database Automation team here at BMC, I sincerely hope you enjoy this new update to the product.

Share This:

I am happy to announce that final Batch 3 of Certified BDA Quarterly Patch Wrappers is available with support team. This batch contains all the patch wrappers for platforms AIX, HPUX-IA64, Linux-x86-64, Solaris64 for all the supported Oracle versions. Kindly get in touch with support team to consume these available certified patch wrappers.

 

Patch Name

DB Version

Platforms

ETA

RU19.0.0.0Linux-x86-64, WindowsAvailable
OJVM19.0.0.0Linux-x86-64Available
RU-OJVM19.0.0.0Linux-x86-64Available
GIRU19.0.0.0Linux-x86-64Available
RU18.0.0.0Linux-x86-64, WindowsAvailable
OJVM18.0.0.0Linux-x86-64Available
RU-OJVM18.0.0.0Linux-x86-64

Available

GIRU18.0.0.0Linux-x86-64Available
RU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64, WindowsAvailable
OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64, WindowsAvailable
RU-OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIRU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64, WindowsAvailable
OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64, WindowsAvailable
PSU-OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIPSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
CPU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
PSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64, WindowsAvailable
OJVM11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64, WindowsAvailable
PSU-OJVM11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
GIPSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available

 

Kindly watch this space for availability on remaining patch wrappers.

 

Also share your feedback on these wrappers.

 

Happy Patching!!!

 

NOTE: BDA latest version 2019R2 supports Oracle 19c on Linux (both standalone and grid) and Windows (Standalone) platforms. To apply patch wrapper against Oracle version 19c Grid Setup, you need to apply a HOTFIX to BDA version 2019R2. Kindly get in touch with support team to get this HOTFIX.

 

To know more about this HOTFIX, kindly visit this page:     Oracle 19c Grid October 2019 Patch Related Hotfix Available for BDA 2019R2

 

Bladelogic Database Automation

Share This:

While testing October 2019 quarterly patch wrapper for Oracle 19c Grid setup on Linux environment, it was observed that one of the cluster related command "crsctl" output is slightly different than that for earlier versions of Oracle databases. Due to this change, one of the BDA's activity during grid patching "AutoStart Services" was failing. To address this command output change, we had to modify the BDA code. This modified BDA code is available through the HOTFIX.

 

So, if you are trying to patch your Oracle 19c Grid Setup with October 2019 GIPSU patch, make sure you apply the HOTFIX in advance i.e. before you start patching.

 

Kindly get in touch with our support team to get this HOTFIX.

 

Bladelogic Database Automation

Share This:

I am happy to announce that Batch 2 of Certified BDA Quarterly Patch Wrappers are available with support team. This batch contains all the pending Grid patch wrappers for platforms AIX, HPUX-IA64, Linux-x86-64, Solaris64 for all the supported Oracle versions except for 19c along with already delivered Single Instance patch wrappers for all the platforms and for all the Oracle versions. Grid patch wrapper for other Oracle versions 19c will be made available soon. Windows Patch Wrappers are still under certification and will be made available soon. Kindly get in touch with support team to consume these available certified patch wrappers.

 

Patch Name

DB Version

Platforms

ETA

RU19.0.0.0Linux-x86-64Available
OJVM19.0.0.0Linux-x86-64Available
RU-OJVM19.0.0.0Linux-x86-64Available
GIRU19.0.0.0Linux-x86-64TBD
RU18.0.0.0Linux-x86-64Available
OJVM18.0.0.0Linux-x86-64Available
RU-OJVM18.0.0.0Linux-x86-64

Available

GIRU18.0.0.0Linux-x86-64Available
RU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
RU-OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIRU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU-OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIPSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
CPU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
PSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
OJVM11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
PSU-OJVM11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
GIPSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available

 

Kindly watch this space for availability on remaining patch wrappers.

 

Also share your feedback on these wrappers.

 

Happy Patching!!!

 

Bladelogic Database Automation

Share This:

I am happy to announce that Batch 1 of Certified BDA Quarterly Patch Wrappers are available with support team. This batch contains all the Single Instance patch wrappers for platforms AIX, HPUX-IA64, Linux-x86-64, Solaris64 for all the supported Oracle versions. Grid patch wrappers are available for Oracle version 11.2.0.4. Grid patch wrappers for other Oracle versions (12.2.0.1, 18c and 19c) will be made available soon. Certified Windows Patch Wrappers are still under certification. Kindly get in touch with support team to consume these available certified patch wrappers.

 

Patch Name

DB Version

Platforms

ETA

RU19.0.0.0Linux-x86-64Available
OJVM19.0.0.0Linux-x86-64Available
RU-OJVM19.0.0.0Linux-x86-64Available
GIRU19.0.0.0Linux-x86-64TBD
RU18.0.0.0Linux-x86-64Available
OJVM18.0.0.0Linux-x86-64Available
RU-OJVM18.0.0.0Linux-x86-64

Available

GIRU18.0.0.0Linux-x86-64TBD
RU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
RU-OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIRU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64TBD
PSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU-OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIPSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64TBD
CPU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
PSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
OJVM11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
PSU-OJVM11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
GIPSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available

 

Kindly watch this space for availability on remaining patch wrappers.

 

Also share your feedback on these wrappers.

 

Happy Patching!!!

 

Bladelogic Database Automation

Share This:

As per Oracle Quarterly Patch schedule, Oracle Quarterly Patches will be available from 15th October. These patches will be available on Oracles' website.

 

BDA engineering team will download these patches on this date and start creating the respective patch wrappers which are later consumed by BDA customers for patching purposes. This blog provides information about the availability of these patch wrappers for customers using BDA.

 

After Oracle releases quarterly patches on 15th October, as usual:

     1. Uncertified patch wrappers will be made available within 3 to 5 working days (after Oracle delivers them) and

     2. Certified patch wrappers would be made available within 15 working days (after Oracle delivers them)

 

Kindly watch this space for more details on delivery date of individual patch wrapper and all kind of updates with respect to October 2019 Patch wrappers.

 

NOTE: If you have grid environment in your infrastructure, where you use BDA provided patch wrappers to patch these grid homes and grid databases, then make sure you read below blog and take necessary steps before patching begins.

          BDA Oracle Patch Wrappers: Confirmation From Oracle on Ownership Change for "sqlplus" file under GRID_HOME

 

 

To know more about BDA Patch Wrappers visit this page: BDA Patch Wrappers for Oracle

Share This:

We had earlier reported an issue while patching Oracle GRID environment using BDA product with the help of patch wrappers. The issue is described here. We were continuously following up with Oracle for almost 3 months, to confirm this ownership change. Today we got the confirmation from Oracle on the same. Oracle says, the ownership of the file "$GRID_HOME/bin/sqlplus" is changed from "<grid_user>/oinstall" to "root:oinstall" after applying the GIRU/GIPSU patches from April 2019 onward. This is an expected behavior. However Oracle does not have any documentation as of today which talks about this change. Oracle support person has confirmed this on the request I raised with them. Reference of this request is:

          SR 3-20452464551 : After applying GIRU April2019, the permission of "$GRID_HOME/bin/sqlplus" changed to root:oinstall.

 

How it affects BDA's logic of applying patches using its patch wrappers:

     BDA uses "GRID_HOME/bin/sqlplus" file to determine the ownership of Oracle Software. As the ownership is changed from Oracle side, we have to change the logic within BDA to determine the ownership of Oracle Software. So going forward BDA will use "$GRID_HOME/bin/oracle" file instead of "$GRID_HOME/bin/sqlplus" file to determine the ownership of Oracle Software. This file exists in all oracle home types (db, crs, grid) and will always be owned by the id that owns the database.

 

When this change will be available in product:

     This change will be available in the upcoming release i.e. 2019 R3

 

What about Oracle patches that are released by Oracle till the availability of above BDA version:

     The patch wrappers which BMC will release for further quarters till the release of BDA 2019 R3 version will be modified so that post patching of such patches the ownership of "$GRID_HOME/bin/sqlplus" will be changed to "<grid_user>:oinstall". So going forward, customers will not face any issue during patching due to ownership issues. We have already confirmed with Oracle that, this change of ownership post applying the respective patch is acceptable and it does no harm to the installed Oracle Software.

  

     However we think of below two situations in your environments. You have to take step(s) according to the situation applicable to your environment:

          Situation 1: If prior to patching, the file "$GRID_HOME/bin/sqlplus" is owned by "root:oinstall" then change the ownership of "$GRID_HOME/bin/sqlplus" from "root:oinstall" to "<grid_user>:oinstall". Then carry out a “node rescan” through BDA. Then go for patching. Ownership of the file can be changed manually or using custom action in case there is no access to the server.

          Situation 2: If prior to patching, the file "$GRID_HOME/bin/sqlplus" is owned correctly by "<grid_user>:oinstall", then no need to do anything.

 

Hope this information helps. Kindly leave your comments below if you are looking for any further information around patching or have any doubt on the above provided information.

 

NOTE: This information is applicable to only grid patches that is GIPSU and GIRU. For other patches like PSU, OJVM, RU, PSU-OJVM, RU-OJVM, everything remains the same. There is no change in the patching logic for these patches.

Eric Liszt

BDA "How To" Videos

Posted by Eric Liszt Employee Aug 30, 2019
Share This:

Today I just wanted to remind everyone of a  great resources for BDA... our "How To" Videos on YouTube.

.

If you want to learn how to do things in BDA such as patch, provision, enforce compliance or even create custom commands, we have some great videos to show you how to do these things.  The videos are typically between 2 and 4 minutes long and give you everything you need to know to understand the concept and put the feature to use.

 

Here are a few examples:

 

And these are just a few of what is available.  The see them all, check out our BDA YouTube Channel.  The entire list is there.

 

If there are other videos you would like to see us produce, please just drop a comment here or create a thread in the message section of the Bladelogic Database Automation community.

 

Thanks!

Share This:

The Database Automation team is pleased to announce the availability of BDA 2019 Release 2

 

This release includes product enhancements, security improvements, and expanded platform support and updated compliance content. This blog post will give you all the information you need to understand what’s new in this release. 

 

Before jumping into the details, allow me to first highlight two of the improvements included in in 2019 Release 02.  These are:

 

  1. Automated Agent Upgrade – You can now automatically update all or some of the BDA agents on your network from directly within BDA and by simply highlighting a domain and selecting “Upgrade Agents”.  BDA handles the process automatically.  This is a huge time saver and eliminates the risk of errors due to version incompatibility between the BDA agent and manager.

 

  1. Support for Oracle 19c, Enterprise edition - Support for Oracle 19c is included for enterprise edition that covers Single Instance (Windows and Linux), RAC and Restart-enabled

 

In addition to these two important updates, we’ve also included numerous other improvements in terms of functionality, platform support, compliance, and security:

 

REST API Updates

    • APIs for Node activities
    • APIs for Database provisioning

 

Patching job improvements

    • When you rerun a patch job following a failure, the job does not run on the nodes where patching was successful. It only runs on the nodes where patching had failed.
    • All nodes that had shut down during the patching job, restart automatically after patching is complete.
    • Patching job improvements are supported for Oracle, Sybase, and MSSQL databases.

 

View Patch List for Oracle databases

    • The Patch List for an Agent is available on the Database Configuration panel.
    • In earlier releases, this was available for MSSQL server only.

 

Updates to software prerequisites

    • Support for PostgreSQL version 11.2
    • PHP is upgraded to version 7.2.20

 

Updated and newly added CIS compliances for MSSQL

    • MSSQL 2017 V1.0 - 813645
    • MSSQL 2016 V1.1 - 814210
    • MSSQL 2014 V1.4 - 814379  
    • MSSQL 2012 V1.5 - 814382
    • MSSQL 2008 V1.6 - 814441

 

Security enhancements

  • A number of application security improvements are also included in this release

 

 

Our entire team is very excited to provide you with these updates to BDA and we are confident they will help you more effectively secure, provision, patch and manage your database environments.  

 

We’re also looking forward to your feedback on this release.  So please share any thoughts or questions you may have here in the Bladelogic Database Automation community.  

Thank you for providing us with the opportunity to continually earn your business!   I look forward to hearing from you.

Share This:

I am happy to announce that Batch 1 of Certified BDA Quarterly Patch Wrappers are available with support team. This batch contains all the patch wrappers for platforms AIX, HPUX-IA64, Linux-x86-64, Solaris64. Certified Windows Patch Wrappers are yet to be made available. Kindly get in touch with support team to consume these available certified patch wrappers.

 

Patch Name

DB Version

Platforms

ETA

RU19.0.0.0Linux-x86-64Available
OJVM19.0.0.0Linux-x86-64Available
RU-OJVM19.0.0.0Linux-x86-64Available
RU18.0.0.0Linux-x86-64Available
OJVM18.0.0.0Linux-x86-64Available
RU-OJVM18.0.0.0Linux-x86-64

Available

GIRU18.0.0.0Linux-x86-64Available
RU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
RU-OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIRU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU-OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIPSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available
OJVM11.2.0.4AIX, HPUX-IA64,  Linux-x86-64,  Solaris64Available
PSU-OJVM11.2.0.4AIX, HPUX-IA64,  Linux-x86-64,  Solaris64Available
GIPSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Available

 

Kindly watch this space for availability on remaining patch wrappers.

 

Also share your feedback on these wrappers.

 

Happy Patching!!!

 

Important Note: There is an open issue with Oracle regarding GIRU/GIPSU patches. It is described in detail here. So kindly think about applying the workaround mentioned there before applying these patches.

 

Bladelogic Database Automation

Share This:

Situation:

Based on our experience with April 2019 Oracle patches we have learnt that, ownership of some of the files have been changed after applying April 2019 patch. Especially GIPSU/GIRU patch. Due to which some of the patches failed while applying through BDA. The root cause of this failure in BDA is changed ownership of file "$GRID_HOME/bin/sqlplus". Before applying the patch the file was owned by "grid/oracle" user and post applying it is owned by "root" user. This will result in the July 2019 patches failing when applied in a RAC environment.

 

Possible Scenarios:

1. April 2019 Patch Did Not Fail: There is a possibility that, April 2019 GIPSU/GIRU patch went well when applied through BDA. This happened because the ownership of above mentioned file was correct before applying the patch. But after the patch got applied, the above mentioned file is now owned by root user instead of "grid/oracle" user. As a result there is a possibility that July 2019 GIPSU/GIRU patch will fail on the same RAC environment.

 

2. April 2019 Patch Did Fail: If the mentioned file is owned by root user before applying the patch, April patch must have failed. This will also result in July patch to be failed.

 

What we are doing about it:

  • We have already opened a ticket with Oracle (SR 3-20452464551 )
  • Oracle has confirmed this issue on 12.1.0.2 as “Bug 29415452 : 12102 APR19 GIPSU: FILE PERMISSION GETS CHANGED FOR MANY FILES UNDER GRID HOME”
  • Oracle is still in the process of confirming this in later releases of the product.

 

Looking Forward:

  • We hope to have Oracle address this in their upcoming July releases
  • If Oracle does not do this, we do have a workaround available from Support.   The workaround would be to change the ownership of "$GRID_HOME/bin/sqlplus" from "root:oinstall" to "<grid_user>/oinstall" followed by a “node rescan” through BDA. Ownership of the file can be changed manually or using custom action in case there is no access to the server.

 

Next Steps:

  • Please make sure you are subscribed to the BDA blog on the BDA community so you will be emailed automatically as we get more information from Oracle.

  Reach out to Support or contact us on the BDA community if you have any questions.

 

Update on October 4th 2019:

     Oracle has confirmed this change and it is as per their expectation. For more information kindly visit below page:

               BDA Oracle Patch Wrappers: Confirmation From Oracle on Ownership Change for "sqlplus" file under GRID_HOME

 

 

Share This:

As per Oracle Quarterly Patch schedule, Oracle Quarterly Patches will be available from 16th July. These patches will be available on Oracles' website.

 

BDA engineering team will download these patches on this date and start creating the respective patch wrappers which are later consumed by BDA customers for patching purposes. This blog provides information about the availability of these patch wrappers for customers using BDA.

 

After Oracle releases quarterly patches on 16th July, as usual certified patch wrappers would be made available within 15 working days (after Oracle delivers them).

 

Kindly watch this space for more details on delivery date of individual patch wrapper and all kind of updates with respect to July 2019 Patch wrappers.

 

To know more about BDA Patch Wrappers visit this page: BDA Patch Wrappers for Oracle

 

Bladelogic Database Automation

Share This:

The Database Automation team is pleased to announce the availability of BDA 2019 Release 1

This release includes product enhancements, security improvements, and expanded platform support. It also includes a change in the version numbering we use for our products.  This blog post will give you all the information you need to understand what’s new in this release.  

Further down in this blog post, you’ll find a full list of all the updates included in 2019 Release 1. But, before I share that with you, I’d like to spend a moment focusing on one of the most exciting updates in this release…. Parallel Patching for Oracle.

 

Parallel Patching for Oracle dramatically improves the experience of patching your databases.  It makes the process faster, easier, and more reliable. 

To explain how Parallel Patching does this, I’ll provide a description of how a patching job is executed moving forward.   Here’s the process that’s followed once a patching job is executed.

  • All databases on a node within the job will be stopped
  • All databases on that node will be patched simultaneously
  • If patching fails on any node (for example due to a missing pre-requisite), patching will continue on all other nodes until the full job is complete.  This ensures that any node capable of being patched, will be patched, as part of the first run of the job.    (Note: In earlier versions of BDA, the patching job would end immediately upon any error or failure leaving the remaining nodes unpatched. Parallel Processing eliminates this issue)
  • Regardless of whether patching fails or succeeds on a node, all services that were shut down as part of the job will be restarted immediately after patching has completed (or failed) for that node.   This ensures the databases are returned to a functional state regardless of whether the patching succeeded for failed, and without having to wait for the entire job to complete.
  • For any job where patching of a node has failed, the job status will be set to “Failed”. This informs the administrator that one or more of the nodes in a job was not successfully patched.  The administrator will then determine the cause of the failure(s), address the issue, and re-run the job to ensure all systems are fully patched.

 

So the takeaway here is that you’ll spend less time managing Oracle patch jobs and your users will experience smaller maintenance windows thanks to this new feature.

 

In our next release, we plan to extend this functionality to work with Microsoft SQL Server.  We’ll also updated the process to dramatically reduce the size of the maintenance window needed for re-running jobs where one or more nodes couldn’t be patched. In the current release, when you re-run a job, BDA will go through the full process of stopping services, attempting to patch, and restarting the services for every node.   In the upcoming release, we are planning to add a pre-check so that BDA will take actions only on those nodes that have failed.  This will dramatically reduce the size of the maintenance window needed for the re-run. 

 

So that’s Parallel Patching for Oracle … but that’s not all we’ve delivered in 2019 Release 1.   Here are the other updates delivered in this version: 

  • Support for Microsoft Windows Server 2019
  • Support for DB2 11.1 (Enterprise Server Edition, Advanced Enterprise Server Edition and Advanced Workgroup Server Edition)
  • Support Windows Server Failover Clusters using PowerShell rather than cluster.exe
  • Multiple security enhancements including updates to gridapp.conf file
  • Support for Java OpenJDK 11

 

Lastly, you’ve probably noticed that we’ve changed method we use for version numbering.   The “old school” method of version numbering that we used previously was devised to communicate the scope of change in a particular release.  A “9.0” release had more change than a “9.1” release.  And that had more change than a “9.1.3” release.   With BDA now releasing updates on a much more frequent and consistent cadence, the “old school” method no longer provides meaningful value since each release contains approximately the same amount of change.    With this in mind, we will now provide our release number in terms of the year of the release, and the release order.  For example, BDA 2019 Release 1 is our first release of the product for 2019.    Our second release will be 2019 Release 2, and so on until 2020 when our first release will be BDA 2020 Release 1.

 

Our entire team is very excited to provide you with these updates to BDA and we are confident they will help you more effectively secure, provision, patch and manage your database environments.   We’re also looking forward to your feedback on this release.  So please share any thoughts or questions you may have here in the Bladelogic Database Automation community.   

 

Thank you for providing us with the opportunity to continually earn your business!   I look forward to hearing from you.

 

 

Share This:

You all know that we have already released certified patch wrappers for 12.1.0.2 PSU, 12.1.0.2 OJVM and 12.2.0.1 RU on April 30th 2019. Today I am back with few more certified patch wrappers. I am pleased to share that all the standalone patch wrappers (i.e. non-cluster/grid) for Oracle versions 12.1.0.2, 12.2.0.1 and 18.0.0.0 are done with their certification. Kindly get in touch with our support team to consume them in your environments.

 

Below is the detailed tabular representation of current status of all the patch wrappers.

 

 

Patch NameDB VersionPlatformsETA
RU18.0.0.0Linux-x86-64Available
OJVM18.0.0.0Linux-x86-64Available
RU-OJVM18.0.0.0Linux-x86-64Available
RU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
RU-OJVM12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
PSU-OJVM12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64Available
GIRU18.0.0.0Linux-x86-64 Coming Soon
GIRU12.2.0.1AIX, HPUX-IA64, Linux-x86-64, Solaris64 Coming Soon
GIPSU12.1.0.2AIX, HPUX-IA64, Linux-x86-64, Solaris64 Coming Soon
CPU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Coming Soon
PSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Coming Soon
OJVM11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Coming Soon
PSU-OJVM11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Coming Soon
GIPSU11.2.0.4AIX, HP64, HPUX-IA64,  Linux-x86-64,  Solaris64Coming Soon
RU18.0.0.0Win64Coming Soon
OJVM18.0.0.0Win64Coming Soon
RU12.2.0.1Win64Coming Soon
OJVM12.2.0.1Win64Coming Soon
PSU12.1.0.2Win64Coming Soon
OJVM12.1.0.2Win64Coming Soon
PSU11.2.0.4Win64Coming Soon
OJVM11.2.0.4Win64Coming Soon

 

If you cannot wait for currently unavailable patch wrappers, then do check our newly introduced Faster Access To Patch Wrappers

 

Do not forget to share your feedback here. Also leave comments below. We are always in learning mode!!!

 

Happy Patching!!!

Filter Blog

By date:
By tag: