Proper maintenance and patching of Oracle Exadata Database Service is crucial for security, performance, and reliability. This guide covers the complete lifecycle of maintenance updates, from planning to execution, ensuring your database infrastructure remains current and secure.
Maintenance Update Models
Oracle Exadata Database Service offers two distinct maintenance approaches to accommodate different organizational needs and operational preferences.
User-Managed Maintenance Updates
User-managed maintenance updates provide organizations with complete control over when and how updates are applied. This model offers:
- Full scheduling control over maintenance windows
- Custom timing based on business requirements
- Selective patching capabilities for specific components
- Testing flexibility in non-production environments first
- Coordination with application maintenance schedules
This approach is ideal for organizations with:
- Complex application dependencies
- Strict change management processes
- Specific compliance requirements
- Need for extensive pre-production testing
Oracle-Managed Infrastructure Updates
Oracle-managed infrastructure updates automate the maintenance process while ensuring systems remain current and secure. Key benefits include:
- Automated scheduling with minimal user intervention
- Consistent update cycles following Oracle's recommended timeline
- Reduced administrative overhead for database teams
- Proactive security with timely patch application
- Best practice implementation by Oracle experts
Oracle expects to be able to perform infrastructure maintenance at least once per quarter, ensuring systems receive critical security and stability updates regularly.
Best Practices for Applying Updates and Patches
Following established best practices minimizes risk and ensures successful patch deployment across your Exadata infrastructure.
Pre-Update Preparation
Database Backup Requirements
Back up your database before applying any update to the database home. This critical step provides:
- Complete recovery capability if issues arise during patching
- Point-in-time restore options for rapid rollback
- Data protection during the update process
- Compliance assurance for regulatory requirements
Database Migration Strategy
Move the database to a new database home when applying major updates. This approach:
- Maintains current environment as a fallback option
- Reduces downtime through parallel deployment
- Enables testing in the new environment before cutover
- Provides clean separation between old and new configurations
Infrastructure Sequencing
Upgrade Grid Infrastructure before updating or creating database home. Oracle recommends your Oracle Grid Infrastructure RU version be no more than 6 months behind your latest database RU version. This ensures:
- Compatibility between infrastructure and database layers
- Proper dependency resolution during updates
- Stable foundation for database operations
- Optimal performance post-update
System Readiness Validation
Ensure all servers and database instances are up and running before beginning maintenance:
- Health checks on all cluster nodes
- Service verification for critical components
- Resource availability confirmation
- Network connectivity validation
Storage Space Requirements
Grid Infrastructure Home Directory
Ensure /u01 (Grid Infrastructure home directory) has 15GB free space before Grid Infrastructure update. This space is required for:
- Patch extraction and staging
- Backup files during the update process
- Temporary files created during installation
- Rollback capabilities if needed
Database Home Directory
Ensure /u02 (database home directory) has 15GB free space. Adequate space prevents:
- Installation failures due to insufficient disk space
- Incomplete patch application causing system instability
- Performance degradation during the update process
- Rollback complications if recovery is needed
Updating Exadata VM OS Image
Operating system updates ensure your Exadata virtual machines have the latest security patches and performance improvements.
Update Process
Update OS image using OCI Console or REST APIs through these steps:
- Choose the desired OS version from available options
- Run precheck update prior to maintenance window to validate system readiness
- Schedule the maintenance window during low-usage periods
- Execute the update with automated rollback capabilities
- Verify system functionality post-update
Pre-Update Validation
Running precheck operations before the maintenance window:
- Identifies potential issues before they impact production
- Validates system configuration requirements
- Checks resource availability for the update process
- Ensures compatibility with existing workloads
Grid Infrastructure Patching
Grid Infrastructure patching maintains the foundation layer that supports all database operations on your Exadata system.
Patching Methodology
Update Grid Infrastructure using OCI Console or REST APIs:
- Select the desired Grid Infrastructure version from certified releases
- Run precheck for update to validate system readiness
- Schedule maintenance during approved windows
- Execute rolling updates to minimize downtime
- Perform post-patch validation of cluster services
Version Management
To upgrade your GI to Oracle Database 19c, you must be using the Oracle Linux 7 operating system for your VM cluster. This ensures:
- Operating system compatibility with Grid Infrastructure
- Support for advanced features in newer releases
- Security compliance with current standards
- Performance optimization capabilities
Database Home Patching
Database home patching provides two flexible approaches for maintaining your Oracle Database software at current patch levels.
Approach 1: In-Place Updates
Update an existing database home to the desired patch level, which:
- Updates all databases using that database home simultaneously
- Maintains current file system structure and configurations
- Requires coordinated downtime for all databases in the home
- Provides consistent patch levels across related databases
Approach 2: New Home Migration
Create a new database home with the desired patch level and move database to the new database home:
- Enables independent patching of individual databases
- Reduces downtime through parallel preparation
- Allows testing before production cutover
- Provides rollback capability by maintaining the old home
Both approaches support OCI Console or REST APIs for management flexibility.
Upgrading Grid Infrastructure
Grid Infrastructure upgrades allow you to provision Oracle database homes and databases with the most current Oracle Database software, ensuring access to latest features and security enhancements.
Pre-Upgrade Preparation
Database Backup
Back up your database before beginning any upgrade process:
- Complete database backup including all data files
- Control file backup for recovery scenarios
- Archive log backup for point-in-time recovery
- Configuration backup of database parameters
Upgrade Precheck
Run an upgrade precheck operation to validate:
- System resource requirements for the upgrade
- Compatibility checks between versions
- Dependency validation for installed components
- Potential blocking issues that need resolution
Database Home Creation
Create an Oracle Database home with the target version:
- Separate installation from current production home
- Complete software stack for the new version
- Proper configuration matching production requirements
- Testing environment preparation for validation
Pluggable Database Validation
Ensure all Pluggable Databases in Container Databases can be opened:
- PDB compatibility with the new version
- Resource allocation verification
- Service dependencies validation
- Application connectivity testing
Maintenance Scheduling and Planning
Quarterly Maintenance Cycles
The patching is done every quarter following a structured approach:
- Exadata Infrastructure (EI): IB Switches, Storage cells, Dom0 operating system
- Autonomous VM clusters (AVM): Grid Infrastructure and Guest VM operating system patching
- Autonomous Container Database (ACD): Oracle Database patching
Recommended Patching Sequence
Although there is no order dependency between EI/AVM/ACD, it is preferred to patch in the sequence EI, AVM, and then ACD for optimal results.
Advanced Maintenance Considerations
Manual Patching Options
Oracle recommends that you use the facilities provided by Exadata Cloud at Customer to perform routine patching. However, for special circumstances:
- Work with Oracle Support Services to identify appropriate patches
- Follow documented procedures for manual patch application
- Maintain support compliance through proper channels
- Document all changes for audit and troubleshooting purposes
Operating System Package Management
You are permitted to install and update operating system packages on Oracle Exadata Database Service on Dedicated Infrastructure as long as you do not modify the kernel or InfiniBand-specific packages.
Monitoring and Validation
Post-Update Verification
After completing any maintenance update:
- Verify all services are running correctly
- Test database connectivity and performance
- Validate backup operations are functioning
- Check monitoring systems for alerts or issues
- Document the update in change management systems
Performance Monitoring
- Baseline performance metrics before and after updates
- Monitor system resources during peak usage periods
- Track database performance indicators
- Validate application functionality end-to-end
Conclusion
Effective maintenance and patching of Oracle Exadata Database Service requires careful planning, proper preparation, and adherence to best practices. Whether you choose user-managed or Oracle-managed maintenance updates, following the structured approaches outlined in this guide ensures your database infrastructure remains secure, performant, and up-to-date.
The combination of automated tools, comprehensive prechecks, and flexible scheduling options makes Exadata Database Service maintenance manageable while maintaining the high availability requirements of enterprise applications.
Remember that proper backup procedures, adequate storage space, and systematic validation are the cornerstones of successful database maintenance operations. Regular maintenance not only ensures security and stability but also provides access to the latest features and performance improvements that Oracle continues to deliver.
Ready to implement a comprehensive maintenance strategy for your Exadata Database Service? Start by evaluating your current update model and establishing the proper backup and validation procedures outlined in this guide.
Top comments (0)