News

  1. Home
  2. All posts
All posts, Exa DATA by Team Ajara

Pre checks for QFSDP on Exadata Environment

Pre checks for QFSDP on Exadata Environment.

 

What is QFSDP in Exadata?

QFSDP is short form for QUARTERLY FULL STACK DOWNLOAD PATCH in Exadata environment.

Quarterly full stack download patches for Exadata are available on Oracle’s website. These patches are released four times a year and are used to update the software components of Exadata systems. They include the latest operating system updates, new firmware and drivers, and other software updates. The latest full stack download patch will need to be installed on all Exadata systems in order to ensure they are running on the most up-to-date version of the software. This helps to ensure the systems are secure and reliable. Additionally, the full stack download patch can be used to update any customization or features that may have been added to the system.

 

Below are the list of Action Items, that we can start work and make system ready from DBA end for Exadata QFSDP activity. For example Patch 24918318: QUARTERLY FULL STACK DOWNLOAD PATCH FOR EXADATA (Jan 2017 – 12.1.0.2)

 

  1.  Make sure that we have enough space in  mount  point ( /u00 or /u01) after extracting the patch to avoid outage’s due to file system space .
  2. Download latest  QFSDP for current DB Version and upload it Non-Prod Server.
  3. Copy the patch to both DR and Prod server’s and unzip the patch on all three Environments.
  4. Perform Pre-checks on Storage Servers on all three Env’s.
  5. Perform Pre-checks on Compute Nodes on all three Env’s.
  6. DO NOT PERFORM ANY PRE-CHECKS on IB SWITCHES ON ANY Exadata ENVIRONMENT (PROD, DR & NON-PROD) .(Pre-checks should never be performed on IB Switches on any Exadata environment, regardless of whether it be production,disaster recovery, or non-production. Pre-checks can interfere with the integrity of the network and the switches, as well as
    potentially cause outages. Furthermore, pre-checks can introduce additional risks to the environment, such as security vulnerabilities or potential data loss.)
  7. Perform Bundle Patch conflict’s Checks on both Grid and DB Oracle Homes on all three Env’s.
  8. Run exachk on all three environment’s and review the report.
  9. Make sure that all Pre-checks are successful on both Storage and compute nodes.
  10. If any pre-checks are failed, fix the Errors that are in our Scope and if required will raise an SR with OSS.
  11. opatch conflict checks should be successful, if there are any conflicts, then need to get one off / Merge patch as per our Requirement.
  12. Do not perform any OS level changes on these clusters during this period.
  13. If we encounter any hardware Failure’s during patching, let’s have details like point of contact for Data Centre visit to share with Oracle Field Engineer.
  14. Oracle Support team also may run pre-checks before they perform the activity, but we need to make sure that system is Ready for Patching from our End.

 

Further reading on support.oracle.com