OCI Infrastructure Patching

Posted on By Admin

Simplifying Quarterly Infrastructure Patching with Oracle Cloud Infrastructure (OCI) Exadata Cloud@Customer (EXACC)

Introduction

Maintaining a secure, high-performance Oracle Exadata Cloud@Customer (EXACC) environment requires regular patching to address security vulnerabilities, performance improvements, and bug fixes. Oracle’s Quarterly Infrastructure Patching ensures that your EXACC infrastructure remains up-to-date with the latest patches from Oracle.

In this guide, we’ll walk through the OCI EXACC patching process, including prerequisites, patching steps, and best practices to ensure a smooth and efficient patching cycle.

Why Quarterly Patching Matters for EXACC

Oracle releases Quarterly Infrastructure Patches to provide:
✅ Security updates – Protecting against known vulnerabilities.
✅ Bug fixes – Resolving performance and stability issues.
✅ New features & optimizations – Enhancing infrastructure capabilities.
✅ Compliance & best practices – Ensuring alignment with Oracle’s recommended configurations.

Since EXACC is a dedicated, on-premises Oracle-managed infrastructure, patching is handled by Oracle Support, but your involvement is crucial for scheduling, validation, and post-patch testing.

Prerequisites for EXACC Patching

Before initiating the patching process, ensure the following:

1. Oracle Support Access

  • You must have an active Oracle Support contract with EXACC privileges.
  • Verify that your My Oracle Support (MOS) credentials have access to the latest patches.

2. Patch Availability

  • Check MOS Note 2793630.1 for the latest EXACC Quarterly Infrastructure Patches.
  • Ensure the patch is compatible with your EXACC version.

3. Maintenance Window Coordination

  • Schedule a maintenance window with Oracle Support (typically 4-6 hours).
  • Coordinate with business stakeholders to minimize downtime impact.

4. Pre-Patch Backup & Validation

  • Backup critical data (if applicable) before patching.
  • Test in a non-production environment (if possible) to validate patch behavior.

Step-by-Step EXACC Patching Process

Step 1: Request Patching via Oracle Support

  1. Log in to My Oracle Support (MOS).
  2. Navigate to the EXACC Dashboard (under Cloud Services > Exadata Cloud@Customer).
  3. Select your EXACC instance and check for available patches.
  4. Submit a Service Request (SR) to Oracle Support, specifying:
    – Patch number (e.g., EXACC_QIP_<version>).
    – Preferred maintenance window.
    – Any known issues in your environment.

(Example SR details:)
Subject: Request for EXACC Quarterly Infrastructure Patching (Patch 24.3.0.0.0)
Description:
Please schedule and apply the latest EXACC Quarterly Infrastructure Patch (Patch 24.3.0.0.0) for EXACC ID: [Your_EXACC_ID].
Preferred maintenance window: [Date & Time].
Environment details:
- EXACC Version: [X.Y.Z]
- Number of DB Nodes: [N]
- Current patch level: [Previous Patch]

Step 2: Oracle Performs Pre-Patch Validation

Oracle Support will:
✔ Verify patch compatibility with your EXACC configuration.
✔ Check for known issues in your specific setup.
✔ Confirm the maintenance window with you.

Step 3: Patching Execution (Oracle-Managed)

Oracle will automate the patching process while you monitor progress:
1. Backup critical components (if required).
2. Apply patches to Exadata Storage Servers (EXSS), Compute Nodes, and InfiniBand switches.
3. Restart services (if necessary).
4. Validate patch success before proceeding.

(You will receive email/SMS alerts during and after patching.)

Step 4: Post-Patch Validation & Testing

After patching, perform the following checks:

A. Verify Patch Application

  • Check MOS Note 2793630.1 for the patch verification steps.
  • Run Oracle-provided validation scripts (if available).

B. Monitor Performance & Logs

  • Review exadm logs (/var/log/exadm).
  • Check dcli commands for node health:
    bash
    dcli -g /opt/oracle.SupportTools/onecommand/group_vars/all.yml -l root "exadm -workload=OLTP -verbose=all"
  • Monitor database performance (AWR, ADDM reports).

C. Test Critical Workloads

  • Run benchmark tests (if applicable).
  • Verify backup & recovery processes.
  • Check network connectivity (InfiniBand, storage).

Step 5: Close the Service Request (SR)

Once validation is complete:
1. Confirm patch success with Oracle Support.
2. Update internal documentation with the new patch level.
3. Close the SR in MOS with a success status.

Best Practices for EXACC Patching

To ensure a smooth patching experience, follow these best practices:

1. Schedule Patches During Low-Traffic Periods

  • Avoid patching during peak business hours.
  • Consider rolling patches (if applicable) to minimize downtime.

2. Automate Pre- and Post-Patch Checks

  • Use Oracle’s provided scripts for validation.
  • Implement custom monitoring (e.g., Nagios, Zabbix) to track patch status.

3. Maintain a Patch History Log

  • Document patch versions, dates, and outcomes for auditing.
  • Example log entry:
    Date: 2024-05-15
    Patch: EXACC_QIP_24.3.0.0.0
    Applied by: Oracle Support
    Status: Success
    Notes: Minor performance improvement in storage latency.

4. Stay Updated with Oracle Announcements

  • Subscribe to Oracle’s EXACC Newsletter (Oracle Cloud News).
  • Follow MOS Notes for known issues & workarounds.

5. Consider a Staging EXACC for Testing

  • If possible, test patches in a non-production EXACC before applying to production.

Common Challenges & Troubleshooting

Issue Possible Cause Solution
Patching fails Incompatible patch version Check MOS for correct patch compatibility.
Performance degradation New patch introduces latency Roll back (if needed) and open an SR.
Network connectivity issues InfiniBand switch misconfiguration Verify ibstat and dcli connectivity checks.
Database service disruption Patch affects Oracle Grid Infrastructure Monitor crsctl and srvctl status.
Storage issues EXSS patch failure Check /var/log/exadm for errors.

Conclusion

Quarterly Infrastructure Patching for Oracle Exadata Cloud@Customer (EXACC) is a critical maintenance task that ensures security, performance, and compliance. While Oracle manages the patching process, your role in scheduling, validation, and post-patch testing is essential for a successful outcome.

By following this guide, you can:
✅ Schedule patches efficiently with Oracle Support.
✅ Validate patch success using Oracle-provided tools.
✅ Monitor performance post-patch to ensure stability.
✅ Adopt best practices for a seamless patching experience.

For the latest updates, always refer to My Oracle Support (MOS) and Oracle’s official EXACC documentation.

Need Help?

Happy Patching! 🚀

Would you like any modifications, such as adding specific SQL queries, deeper technical details, or a troubleshooting section for common EXACC patching errors?

Uncategorized

Related Posts