Oracle Database 23c Beta

Oracle Database 23c is the next long-term release, set to be released in early 2023, featuring over 300 new capabilities.

Viscosity participates as a beta partner through multiple channels, as an Oracle partner and as a collective of ACE Directors. This dual perspective allows evaluation from both development and DBA angles, positioning them to provide valuable insights and feedback to Oracle.

Upgrade Methodology

• Creating tailored project plans based on specific applications and infrastructure
• Collaborative planning with development and database administration teams
• Clear definition of roles and responsibilities
• Minimizing disruptions and downtime for customers

Any downtime can be costly and disruptive to a business. Post-upgrade activities include thorough testing and ongoing customer support to ensure optimal performance.

Pre-Upgrade Research Resources

Check the Oracle Support website for updates and consider partnerships with experienced Oracle consultants.

Upgrade Planning: OS and Database Compatibility

• Oracle 11.2.0.4 to 19c: Requires both OS and database upgrade in a single outage
• Oracle 12.1.0.2 to 19c: May allow separated OS and database upgrades across multiple outages
• Legacy versions (pre-11.2.0.4): Typically requires simultaneous OS and database upgrades

Note: Windows Server 64-bit 2012 and HP-UX Itanium platforms have longer lifespans but still require regular OS patching.

Key Planning Factors

• Database size (impacts migration duration)
• Available data transfer technology
• Source and target hardware specifications
• Database and OS version compatibility

Upgrade Methods

1. In-Place Upgrade

Installing new software on the same server and storage. Simplest option but potentially disruptive, requiring careful downtime planning.

2. Cross-Platform Upgrade

Creating a new system and migrating data using Oracle tools. Allows continued operation on legacy systems but demands more resources and planning.

3. Real Time/Rolling Upgrade

Creating a replicated environment, upgrading in place, then switching over once synchronized. Minimizes user disruption but represents the most complex approach.

Additional Considerations

• Downtime tolerance: High-availability requirements may necessitate cross-platform or rolling upgrade methods
• Hardware and software environment: Outdated systems may require component upgrades
• Team expertise: Proper training on chosen methods and application-specific requirements
• Organizational alignment: Connecting upgrade efforts to long-term business goals and strategy

Careful planning, proper funding, and consideration of these factors ensure smooth transitions to new Oracle database versions.