2.12 Re-Imaging the Oracle Exadata Database Server

The re-image procedure is necessary when a database server needs to be brought to an initial state for various reasons.

Some examples scenarios for re-imaging the database server are:

• You want to install a new server and need to use an earlier release than is in the image already installed on the server.
• You need to replace a damaged database server with a new database server.
• Your database server had multiple disk failures causing local disk storage failure and you do not have a database server backup.
• You want to repurpose the server to a new rack.

During the re-imaging procedure, the other database servers on Oracle Exadata are available. When the new server is added to the cluster, the software is copied from an existing database server to the new server. It is your responsibility to restore scripting, CRON jobs, maintenance actions, and non-Oracle software.

Note:

The procedures in this section assume the database is Oracle Database 11g Release 2 (11.2) or later.

Starting with Oracle Exadata System Software release 19.1.0, Secure Eraser is automatically started during re-imaging if the hardware supports Secure Eraser. This significantly simplifies the re-imaging procedure while maintaining performance. Now, when re-purposing a rack, you only have to image the rack and the secure data erasure is taken care of transparently as part of the process.

The following tasks describes how to re-image an Oracle Exadata Database Server running Oracle Linux:

• Contact Oracle Support Services
  If a failed server is being replaced, open a support request with Oracle Support Services.
• Download Latest Release of Cluster Verification Utility
  The latest release of the cluster verification utility (cluvfy) is available from My Oracle Support.
• Remove the Database Server from the Cluster
  If you are reimaging a failed server or repurposing a server, follow the steps in this task to remove the server from the cluster before you reimage it. If you are reimaging the server for a different reason, skip this task and proceed with the reimaging task next.
• Image the Database Server
  After the database server has been installed or replaced, you can image the new database server.
• Configure the Re-imaged Database Server
  The re-imaged database server does not have any host names, IP addresses, DNS or NTP settings. The steps in this task describe how to configure the re-imaged database server.
• Prepare the Re-imaged Database Server for the Cluster
  This task describes how to ensure the changes made during initial installation are done to the re-imaged, bare metal database server.
• Apply Oracle Exadata System Software Patch Bundles to the Replacement Database Server
  Oracle periodically releases Oracle Exadata System Software patch bundles for Oracle Exadata.
• Clone Oracle Grid Infrastructure to the Replacement Database Server
  This procedure describes how to clone Oracle Grid Infrastructure to the replacement database server.
• Clone Oracle Database Homes to the Replacement Database Server
  The following procedure describes how to clone the Oracle Database homes to the replacement server.