OneAgent 1.347 Compatibility Issue Affecting Orabase Command-line Interface (CLI) Tool

We are aware of an issue affecting customers who have upgraded to OneAgent version 1.347. The issue is due to an emergent incompatibility with Oracle, customers may experience issues running the Orabase command-line interface (CLI) tool.

Out of an abundance of caution, we recommend that customers running Orbase CLI tool do not upgrade to OneAgent 1.347 until the incompatibility has been resolved. If you have already upgraded and are experiencing impact, we recommend downgrading to a OneAgent version earlier than 1.347 until resolved.

We understand the potential disruption this may cause and appreciate your patience as we work to resolve this issue. We will provide another update within the next four hours, or sooner if additional information becomes available.

We are actively addressing an issue affecting customers who upgraded to OneAgent version 1.347. The issue stems from an emergent incompatibility with Oracle and may impact customers using the Orabase command-line interface (CLI) tool.

As a precaution, we continue to recommend that customers using the Orabase CLI tool do not upgrade to OneAgent 1.347 until the incompatibility is resolved. Customers already experiencing impact should downgrade to a OneAgent version earlier than 1.347.

A mitigating OneAgent version is currently being rolled out. We will provide the next update within two hours, or sooner if new information becomes available.

We identified an issue affecting some customers who upgraded to OneAgent version 1.347. Our investigation determined that the issue is related to an incompatibility with Oracle and may impact customers using the Orabase command-line interface (CLI) tool.

To address this, a new version of OneAgent has been rolled out and is expected to mitigate the issue for affected customers. We encourage any customer who believes they may be impacted to update to the latest version of OneAgent. Since this version has been released, our teams will continue monitoring the fix to confirm it is working as expected.

If the issue persists, please contact your support team. Our support teams are available to assist and will work with you to resolve any remaining impact. We will provide the next update within four hours, or sooner if new information becomes available.

We are currently rolling out a new version of OneAgent to address an incompatibility with Oracle that may impact customers using the Orabase command-line interface (CLI) tool.

The new version has been successfully deployed to all AWS environments, and we are working to complete the roll out for a small number of Azure and GCP environments.

Once available, we encourage any customer who believes they may be impacted to update to the latest version of OneAgent.

We will provide the next update at 05:00 AM UTC, or sooner if new information becomes available.

We are continuing to work on completing the roll out of the new OneAgent version for the remaining Azure and GCP environments.

The new version is available on all AWS environments.

We will provide the next update by 09:00 AM UTC, or sooner if new information becomes available.

We have completed the rollout of the updated OneAgent version to all AWS environments. We expect the updated version for the remaining Azure and GCP environments to become available early next week.

Customers on Azure and GCP environments who are using the Orabase command-line interface (CLI) tool should pause upgrading to OneAgent version 1.347 until the updated version becomes available. Customers already experiencing impact may use a OneAgent version earlier than 1.347 as a workaround.

As the rollout timeline for the remaining Azure and GCP environments is longer than initially anticipated, we will provide the next update by Monday, 8:00 AM UTC, or sooner if new information becomes available.