Behavioral Changes in Oracle 12c & 18c – The Devil is in the Details
Posted: Mon Jan 27, 2025 6:40 am
In times of agile software development and DevOps and the associated continuous integration and continuous delivery processes, companies find it difficult to avoid introducing automation tools - such as Ansible or Puppet - to map recurring processes. Automation can be used in many places, such as when installing Oracle software, providing a new database or even installing current patches. In all of these examples, the database administrators assume that the Oracle software behaves as they know it and have implemented it. Changes to the processes are usually made when a version jump, such as from 12c to 18c, is imminent.
But what happens if a new belarus telegram screening patch level causes the Oracle software to no longer behave as expected and, above all, as the established process requires? In many cases, such behavioral changes are only noticed during active use and by then it is already too late. The time it takes to analyze the problems can lead to delays at other levels or, in the worst case, even cost money or reputation.
This article shows a series of behavioral changes in Oracle 12c and 18c. The two software products Grid Infrastructure and Oracle Database are considered. Many of these small behavioral changes are also sparsely or not at all documented.
But what happens if a new belarus telegram screening patch level causes the Oracle software to no longer behave as expected and, above all, as the established process requires? In many cases, such behavioral changes are only noticed during active use and by then it is already too late. The time it takes to analyze the problems can lead to delays at other levels or, in the worst case, even cost money or reputation.
This article shows a series of behavioral changes in Oracle 12c and 18c. The two software products Grid Infrastructure and Oracle Database are considered. Many of these small behavioral changes are also sparsely or not at all documented.