6 Updating Oracle Database Appliance X6-2 Software

To keep Oracle Database Appliance running with the latest software, check for and apply Oracle Database Appliance patch bundles when they are released.

Topics:

About Updating Oracle Database Appliance X6-2 Software

Review this topic to understand the patching process for 12.1.2.8.0, and to understand the patching options available to you in this patch set release.

About Oracle Database Appliance Software Updates

Note:

Oracle Database Appliance release 12.1.2.8.1 release introduces support for Oracle Database Appliance X6-2L and does not contain patches or updates.

To keep Oracle Database Appliance running with the latest software, check for and apply Oracle Database Appliance patch bundles when they are released. As well as offering new features, patches may improve the functionality of existing features.

Oracle Database Appliance patch bundles are released on a quarterly schedule. My Oracle Support note 2144642.1 and 888888.1 provide information about the latest Oracle Database Appliance patch bundle. See My Oracle Support note 2144642.1 to obtain the most current updates and known issues for the 12.1.2.8.0 Oracle Database Appliance patch bundle installation.

Caution:

Do not patch Oracle Database Appliance using individual patches for Oracle Grid Infrastructure, Oracle Database, or Oracle Linux. Also do not use individual infrastructure patches, such as firmware patches. You must only use Oracle Database Appliance patches.

If you use patches that are not intended for Oracle Database Appliance, or if you use Opatch, or a similar patching tool, then Oracle Database Appliance inventory is not updated, and you cannot complete future patch updates.

Overview of the 12.1.2.8.0 Patch Upgrade

Oracle Database Appliance patch set release 12.1.2.8.0 includes new enhancements, including a comprehensive patching solution for Oracle Database Appliance X6–2S and X6–2M.

If you are using Oracle Database Appliance 12.1.2.7, then you must upgrade the dcs-agent before installing the latest patch set. The dcs-agent upgrade includes changes that enable you to install the patch set bundle. Use the describe-job command to monitor the progress of each patching job.

Note:

Before updating the repository, agent, server, or database, ensure that you do not have any jobs running or pending during the update window.

Step 1: Update the DCS Agent to the Latest Version

Run the update-image command to update the dcs-agent image to the latest version.

Note:

You must update the dcs-agent to the latest version before using the patching command–line interface. The 12.1.2.8.0 dcs-agent includes information needed to use the command–line interface to install the update bundle and update the agent, server, and databases.
  1. From an external client machine, open My Oracle Support note 2144642.1 and review for notes on updating the dcs-agent.
  2. Download the 12.1.2.8 patch from My Oracle Support. For example, patch 24391174.
  3. Log in to Oracle Database Appliance as a root user.
  4. Update the dcs-agent using the update-image command.
    # /opt/oracle/oak/bin/update-image --image-files /tmp/oda-sm-12.1.2.8.0-160xxx-DCS.zip
    The agent automatically restarts. It may take 1-2 minutes for the dcs-agent to complete restarting. Wait until the agent completes restarting before updating the patch repository or performing any tasks.

Caution:

Do not patch Oracle Database Appliance using individual patches for Oracle Grid Infrastructure, Oracle Database, or Oracle Linux. Also do not use individual infrastructure patches, such as firmware patches. You must only use Oracle Database Appliance patches.

If you use patches that are not intended for Oracle Database Appliance, or if you use Opatch, or a similar patching tool, then Oracle Database Appliance inventory is not updated, and you cannot complete future patch updates.

Step 2: Update the Patch Repository

Use this procedure to download the Oracle Database Appliance patch set bundle from My Oracle Support and update the repository with the new patches.

Before running the update-repository command, ensure that your appliance has the latest version of the agent.
  1. From an external client machine, open My Oracle Support note 2144642.1:
  2. Under Patch Search, select Oracle Database Appliance from the Product list.
  3. Select the patch release number from the Select a Release list.
  4. Click Search.
  5. Select the patch or patches that you want to download, and click Download. For example, the 12.1.2.8.0 patch is 24391219.

    Caution:

    Do not patch Oracle Database Appliance using individual patches for Oracle Grid Infrastructure, Oracle Database, or Oracle Linux. Also do not use individual infrastructure patches, such as firmware patches. You must only use Oracle Database Appliance patches.

    If you use patches that are not intended for Oracle Database Appliance, or if you use Opatch, or a similar patching tool, then Oracle Database Appliance inventory is not updated, and you cannot complete future patch updates.

  6. Run the update-repository command to unpack the patch bundle to the correct locations in the file system. If you have more than one patch, you can use a comma-separated list for the filename.
    # /opt/oracle/dcs/bin/odacli update-repository -f comma seperated list of enduser bundles

Step 3: Update the Agent

Run the update-dcsagent command to update the agent to the 12.1.2.8 version.

Before updating the agent, ensure that you do not have any jobs running or pending during the update window. The update automatically restarts the DCS Agent.
  1. Log in as the root user.
  2. Run the update dcsagent command to define the patch set bundle version and update the agent.
    # /opt/oracle/dcs/bin/odacli update-dcsagent -v version
    
    As the patch runs, output displays advising you of the installation progress. After the update is applied, the agent automatically restarts. It takes a few minutes to reconnect to the dcs-agent. Wait until the agent shuts down and completes restarting before proceeding to the next step.
  3. Run the describe-job command for the patch job to verify that the update completed successfully. The jobID displays in the update-dcsagemt output. You can also get the job ID by running the list-jobs command.
    # /opt/oracle/dcs/bin/odacli describe-job -i jobid
    

Example 6-1 Updating the DCS Agent to Version 12.1.2.8

Run the following command to update the DCS Agent to version 12.1.2.8:

# odacli update-dcsagent -v 12.1.2.8 

{
   "jobId" : "11a9dcb7-01bc-44b5-b178-334978ee5faf",
   "status" : "Created",
   "message" : null,
   "reports" : [ ],
   "createTimestamp" : "August 03, 2016 06:15:00 AM EDT",
   "description" : "DcsAgent patching",
   "updatedTime" : "August 03, 2016 06:15:00 AM EDT"
 }

Example 6-2 Verifying that the DCS Agent is on Version 12.1.2.8

The following example uses job ID 11a9dcb7-01bc-44b5-b178-334978ee5faf from the previous example to get the job details.

  # odacli describe-job -i "11a9dcb7-01bc-44b5-b178-334978ee5faf"  

Job details
----------------------------------------------------------------
                      ID: 11a9dcb7-01bc-44b5-b178-334978ee5faf
             Description: DcsAgent patching
                  Status: Success
                 Created: August 3, 2016 6:15:00 AM EDT
                 Message:
Task Name                                       Start Time                                          End Time                                                                    Status
-------------------  -------------------------------- ------------------------------ ------
location validation     August 3, 2016 6:15:00 AM EDT   August 3, 2016 6:15:00 AM EDT Success
Apply patch                                     August 3, 2016 6:15:00 AM EDT   August 3, 2016 6:15:01 AM EDT Success

Step 4: Update the Server

Run the update-server command to update the operating system, firmware, Oracle Appliance Kit , Oracle Clusterware, and all other infrastructure components.

Before updating the server, patch the DCS Agent to the 12.1.2.7 update version, update the repository with the latest patch bundle, and update the DCS Agent. Before updating the server, ensure that the agent is running.
  1. Log in as the root user.
  2. Run the command update-server -v version, where version is the patch set bundle version.
    # /opt/oracle/dcs/bin/odacli update-server -v version
    
    Observe the patch status reports. As the patch runs, it displays output that advises you of the installation progress.
  3. Run the describe-job command for the patch job to verify that the update completed successfully. The jobID displays in the update-server output. You can also get the job ID by running the list-jobs command.
    # /opt/oracle/dcs/bin/odacli describe-job -i jobid
    
When the server is patched, proceed to the next step.

Example 6-3 Updating the Server to Version 12.1.2.8

Run the following command to update the server to version 12.1.2.8:

# /opt/oracle/dcs/bin/odacli update-server -v 12.1.2.8

{
   "jobId" : "94685c73-55c2-40b1-a02e-265a23c45642",
   "status" : "Created",
   "message" : null,
   "reports" : [ ],
   "createTimestamp" : "August 03, 2016 06:16:19 AM EDT",
   "description" : "GiHome Patching",
   "updatedTime" : "August 03, 2016 06:16:19 AM EDT" }

Example 6-4 Verifying that the Server is on Version 12.1.2.8

The following example uses job ID 94685c73-55c2-40b1-a02e-265a23c45642 from the previous example to get the job details and status.

# /opt/oracle/dcs/bin/odacli describe-job -i "94685c73-55c2-40b1-a02e-265a23c45642"  

Job details 
----------------------------------------------------------------

              ID: 94685c73-55c2-40b1-a02e-265a23c45642
             Description: GiHome Patching
              Status: Running
              Created: August 3, 2016 6:16:19 AM EDT
             Message:

Task Name                       Start Time                      End Time                        Status
------------------------------- ------------------------------  ------------------------------  ------
location validation             August 3, 2016 6:16:19 AM EDT   August 3, 2016 6:16:19 AM EDT  Success
Apply patch                     August 3, 2016 6:16:20 AM EDT   August 3, 2016 6:16:40 AM EDT  Success
Patch application verification  August 3, 2016 6:16:40 AM EDT   August 3, 2016 6:16:42 AM EDT  Success
location validation             August 3, 2016 6:16:42 AM EDT   August 3, 2016 6:16:42 AM EDT  Running

Step 5: Update Oracle Database

Run the update-dbhome command to update a specific RDBMS Home to the latest patch bundle version.

After patching, download the latest database end user bundles. If you do not download the latest database bundle, you cannot use the Web Console to create an older version of the database. You can use the odacli create-database command to create different versions of the database without downloading the latest database end user bundle.

  1. Log in as the root user.
  2. Run the odacli list-dbhomes command to get a list of database homes in the system and the dbhomeid for each database.
    # /opt/oracle/dcs/bin/odacli list-dbhomes                                            
    
  3. Run the command update-dbhome dh dbhomeid -v version, where dbhomeid is the Oracle Database Home to update and version is the Oracle Database Appliance patch set bundle version.

    Note:

    You cannot perform individual database updates for databases running in the same home. All databases running in the homes that you update are patched to the Oracle Database 12c release 1 patch for Oracle Database Appliance (12.1.0.2.160719). For Oracle Database 11.2, the database is patched to 11.2.0.4.160719.

    # /opt/oracle/dcs/bin/odacli update-dbhome -dh dbhomeid -v version
    
    Observe the patch status reports. As the patch runs, it displays output that advises you of the job identifier (ID) and the installation progress.
  4. Run the describe-job command for the patch job to verify that the update completed successfully. The jobID displays in the update-dbhome output. You can also get the job ID by running the list-jobs command.
    # /opt/oracle/dcs/bin/odacli describe-job -i jobid
    

Example 6-5 Getting a List of Database Home IDs

The following example shows how to get a database home ID.

# /opt/oracle/dcs/bin/odacli list-dbhomes

ID                                   Name               DB Version  
------------------------------------ -----------------  ----------  
89427c39-7f87-43c7-a8bf-0a5f59c3a33a ODB12102_home1     12.1.0.2     

(continued)
Home Location
-----------------------------------------
/u01/app/orauser/product/12.1.0.2/dbhome_1

Example 6-6 Updating the Database Home to Version 12.1.2.8

The following example updates database home ID 89427c39-7f87-43c7-a8bf-0a5f59c3a33a to Oracle Database Appliance version 12.1.2.8.

# /opt/oracle/dcs/bin/odacli update-dbhome -dh 89427c39-7f87-43c7-a8bf-0a5f59c3a33a -v 12.1.2.8 

{   
  "jobId" : "801c3919-d235-4db1-9b00-6c2f382d8a07",
   "status" : "Created",
   "message" : null,
   "reports" : [ ],
   "createTimestamp" : "August 03, 2016 11:57:27 AM EDT",
   "description" : "DbHome Patching: Home Id is 89427c39-7f87-43c7-a8bf-0a5f59c3a33a",
   "updatedTime" : "August 03, 2016 11:57:27 AM EDT" 
}

Example 6-7 Verifying that Database Home is on Version 12.1.2.8

The following example uses job ID 801c3919-d235-4db1-9b00-6c2f382d8a07 from the previous example to get the job details.

# /opt/oracle/dcs/bin/odacli describe-job -i "801c3919-d235-4db1-9b00-6c2f382d8a07"  
Job details
 ----------------------------------------------------------------
                      ID: 801c3919-d235-4db1-9b00-6c2f382d8a07
             Description: DbHome Patching: Home Id is 89427c39-7f87-43c7-a8bf-0a5f59c3a33a
                  Status: Running
                 Created: August 3, 2016 11:57:27 AM EDT
                 Message: 

Task Name                          Start Time                    
--------------------------------- -------------------------------
Patch application verification     August 3, 2016 11:57:27 AM EDT
location validation                August 3, 2016 11:57:29 AM EDT
updateOpatch                       August 3, 2016 11:58:31 AM EDT
analyzing patch                    August 3, 2016 11:58:33 AM EDT
 
(continued)
End Time                           Status
---------------------------------  --------
August 3, 2016 11:57:29 AM EDT     Success
August 3, 2016 11:57:34 AM EDT     Success
August 3, 2016 11:58:33 AM EDT     Success
August 3, 2016 11:58:33 AM EDT     Running