![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Predictive Self-Healing Sure Solution 2356377.1 : Pre-requisites for updating the SuperCluster Virtual Assistant to version 2.5.0.1378 via the JAN 2018 (or later) QFSDPs
This document guides customers applying the January 2018 QFSDP through the pre-requisite actions required for the osc-domcreate package (which delivers the SuperCluster Virtual Assistant). In this Document
Applies to:Oracle SuperCluster M6-32 Hardware - Version All Versions and laterSPARC SuperCluster T4-4 Oracle SuperCluster M7 Hardware - Version All Versions and later Oracle SuperCluster T5-8 Hardware - Version All Versions and later Information in this document applies to any platform. PurposeThis document guides customers applying the January 2018 QFSDP through the prerequisite actions required for the osc-domcreate package (which delivers the SuperCluster Virtual Assistant). This note can be ignored if applying the JAN 2018 QFSDP to systems that DO NOT use the SuperCluster Virtual Assistant (previously called the IO Domain Creation Tool). This note can also be ignored if the current patch level of the target SuperCluster system is at the JUL 2017 QFSDP level (or later).
ScopeThis note is applicable to SuperCluster systems with the osc-domcreate package installed on the first control domain of the first Physical Node, where the version of that package is at an earlier version than "Branch" 2.4.0.1219. In short, this will affect SuperCluster systems with patch levels equivalent to the APR 2016 QFSDP up to the APR 2017 QFSDP levels (inclusive).
DetailsThe "Master Control Domain" (MCD) referred to below is the first control domain of the first physical node on the SuperCluster. It will be the control domain that has the osc-domcreate IPS package installed. The JAN 2018 QFSDP will deliver SuperCluster Virtual Assistant (SVA) version 2.5.0.1378. This version of SVA uses a MySQL backend database, while 2.4.0.x and earlier versions of SVA use an sqlite3 database. To ensure that the sqlite3 database is at the right level for SVA v2.5.0.1378 to perform the migration from sqlite3 to MySQL, the MCD must have osc-domcreate version 2.4.0.1219 (or later) installed on the live Boot Environment (BE) prior to running install_smu from the JAN 2018 QFSDP on that domain. In order to check the version of osc-domcreate installed on the MCD's live BE, please run the following command: # pkg info osc-domcreate | grep Branch
As long as the Branch/version for osc-domcreate is at 2.4.0.1219 (or later), then the MCD is ready to proceed with running install_smu and the rest of this note can be ignored!
If the Branch for osc-domcreate is between version 2.2.0.890 (delivered via the OCT 2016 QFSDP) and version 2.3.0.1091 (delivered via the APR 2017 QFSDP), then you will need to update the version of osc-domcreate to v2.4.0.x prior to running install_smu. For this reason, osc-domcreate Branch 2.4.0.1253 is included with the "Exa-Family 2.5.0.1378 Update" shipped in the JAN 2018 QFSDP. An example of how to upgrade the osc-domcreate package to 2.4.0.1253 is provided below. Please be aware that the osc-domcreate package can be updated in the live BE (i.e. this is not like applying package updates to Solaris, which will create an alternate Boot Environment and patch that). # cp -rp /production/databases/iodine/iodine.db /production/databases/iodine/iodine.db.<BACKUP_DATE> # mkdir /mnt/a # mount -f hsfs <path_to_SCMU_2018.01>/solaris/components/s11/exafamily/sol-exafamily-2.5.0.1378-repo-incr.iso /mnt/a # pkg list -avf -g /mnt/a/repo/ osc-domcreate FMRI IFO pkg://exa-family/system/platform/supercluster/osc-domcreate@0.5.11,5.11-2.5.0.1378:20180117T191204Z --- pkg://exa-family/system/platform/supercluster/osc-domcreate@0.5.11,5.11-2.4.0.1253:20171215T221738Z --- # pkg publisher exa-family | grep Origin # pkgrecv -s /mnt/a/repo/ -d /net/192.168.28.1/export/IPS-repos/exafamily/repo/ osc-domcreate@0.5.11,5.11-2.4.0.1253 Processing packages for publisher exa-family ... Retrieving and evaluating 1 package(s)... PROCESS ITEMS GET (MB) SEND (MB) Completed 1/1 1.5/1.5 0.0/0.0 # pkgrepo rebuild -s /net/192.168.28.1/export/IPS-repos/exafamily/repo/ Initiating repository rebuild. # pkg refresh # pkg list -avf osc-domcreate@0.5.11,5.11-2.4.0.1253 FMRI IFO pkg://exa-family/system/platform/supercluster/osc-domcreate@0.5.11,5.11-2.4.0.1253:20171215T221738Z --- # pkg update osc-domcreate@0.5.11,5.11-2.4.0.1253 Packages to update: 1 DOWNLOAD PKGS FILES XFER (MB) SPEED PHASE ITEMS
After completing the upgrade to osc-domcreate@0.5.11,5.11-2.4.0.1253, it is worth ensuring that the iodct-upgrade-monitor service is in an online state and it is also recommended to take a look through the associated logfile for any errors: # svcs -xv iodct-upgrade-monitor
svc:/site/iodct-upgrade-monitor:default (IODCT Upgrade Monitor) State: online since Fri Feb 02 02:31:02 2018 See: /var/svc/log/site-iodct-upgrade-monitor:default.log Impact: None. #
If the target system has met the requirement to have osc-domcreate 2.4.0.1253 applied and the procedure above has been followed to do just that, then the rest of this note can be ignored!
In an effort to minimize disruption to customers looking to apply the JAN 2018 QFSDP to systems starting from a QFSDP level of either the APR 2016 QFSDP or JUL 2016 QFSDP, there is one additional osc-domcreate update that needs to be applied, prior to applying osc-domcreate 2.4.0.1253 using the process detailed above. The APR 2016 QFSDP & JUL 2016 QFSDP deliver osc-domcreate versions 2.1.0.811 & 2.1.0.819 respectively. These 2.1.0.x versions need to be brought up to version 2.2.0.916, prior to updating to version 2.4.0.1253. # cp -rp /production/databases/iodine/iodine.db /production/databases/iodine/iodine.db.<BACKUP_DATE>
# mkdir /export/2.2.0.916 # cd /export/2.2.0.916 /export/2.2.0.916# ls p25491589_2x_SOLARIS64.zip /export/2.2.0.916# unzip -q p25491589_2x_SOLARIS64.zip /export/2.2.0.916# ls p25491589_2x_SOLARIS64.zip ssc-2.2.0.916_readme.html sol-exafamily-2.2.0.916-repo-incr.iso /export/2.2.0.916# mkdir /mnt/b /export/2.2.0.916# mount -f hsfs /export/2.2.0.916/sol-exafamily-2.2.0.916-repo-incr.iso /mnt/b /export/2.2.0.916# pkg list -avf -g /mnt/b/repo osc-domcreate@0.5.11,5.11-2.2.0.916 FMRI IFO pkg://exa-family/system/platform/supercluster/osc-domcreate@0.5.11,5.11-2.2.0.916:20170114T002301Z --- /export/2.2.0.916# From this point forward, the process to go from osc-domcreate version 2.1.0.x up to osc-domcreate 2.2.0.916 on the live BE, is the same as that outlined previously to update to version 2.4.0.1253. Once osc-domcreate has successfully been updated to version 2.2.0.916, then proceed to subsequently update osc-domcreate to version 2.4.0.1253 by following the process outlined previously.
Attachments This solution has no attachment |
||||||||||||||||
|