Category: Update

This post outlines the process for upgrading Oracle Application Express (APEX) from version 19.2 to 24.1. APEX is a low-code platform for developing web applications with Oracle Database. The upgrade process is independent of the database version but requires Oracle Database version 19c or later. The steps include downloading the new version, creating dedicated tablespaces, executing installation scripts, modifying request-handling procedures, and dropping the old APEX user and tablespace. Finally, the latest cumulative patch, released on December 9, 2024, is applied to ensure a secure, reliable, and efficient APEX environment.

The necessity of a time zone upgrade depends on whether a database stores timestamp data with time zones. For organizations with clients in various time zones, upgrading may be essential. The data types TIMESTAMP WITH TIME ZONE (TSTZ) and TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) are key considerations, with TSTZ retaining original time zone data while TSLTZ normalizes it according to DBTIMEZONE value. Oracle’s Data Pump requires matching time zone versions during data transfers. The steps for upgrading the time zone in a sample database are explained in detail.

This post discusses the introduction of a new patching feature (one-button patching) in the AutoUpgrade tool, now at version 24.7, which simplifies the database release update process. Although currently, it only supports single-instance homes and Oracle Database 19c on Linux, the Oracle Database Upgrade Team will be addressing additional requirements in future versions. Since automating patching is essential for large environments to ensure updates and compliance, I have provided a comprehensive set of Ansible playbooks for database patching(19.24) on my GitHub repo, which can help promote efficiency and reduce errors in the patching process.

This post discusses using Ansible Playbooks to patch Oracle database software, from installing Ansible to completing the patching process. It provides detailed playbooks for creating new database software directories, applying release updates and one-off patches, running datapatch, and removing old database homes. The author also revised the playbooks for better readability and compatibility.

This blog post discusses the usage of Redhat Ansible to patch grid infrastructure, emphasizing its simplicity and efficiency. It explains the process of installing Ansible, preparing the environment, and executing playbooks for grid software patching with detailed steps. The author also provides valuable insights into the revision of playbooks for best practices.

Patching your database is crucial for security and performance. Develop a strategy based on your organization’s needs. Regularly schedule routine patches, test thoroughly, and inform stakeholders. Prioritize critical security fixes. Read release notes and consider expert blogs. Apply patches selectively, and consider in-place and out-of-place patching methods. Fleet Patching and Provisioning can scale patch deployment effectively.