Oda X7 2SM

EIS Installation Checklist for the
ORACLE® Database Appliance X7-2S & X7-2M
Customer:
TASK Number:
Technician:
Date:
• This checklist describes the “Limited Software Install” for the Oracle Database Appliance.
• It is recommend that the EIS web pages are checked for the latest version of this checklist prior
to commencing the installation.
• The idea behind this checklist is to help the installer achieve a "good" installation.
• It is assumed that the installer has attended the appropriate training classes.
• The installation should be prepared using EISdoc V4.
• For systems to be rack mounted the racks must be as defined in the Oracle System Handbook
(via MOS).
• It is not intended that this checklist be handed over to the customer.
• Feedback is welcome – refer to the last page of this checklist.
This EIS installation checklist covers only Bare Metal installations.
The ODA X7-2S & X7-2M is a single node system without external storage. The ODA X7-2S has
a single CPU; the ODA X7-2M has two CPUs and more memory.
The ODA X7-2S & X7-2M are delivered with the OS pre-installed.
Server Type Serial Number

Oracle Database Appliance X7-2 S/M
Oracle Internal and Approved Partners Only Page 1 of 32 Vn 1.2 Created: 15. Feb. 2018
ENGINEERED SYSTEMS ENTERPRISE SUPPORT TEAM EEST
If a Field Support Engineer (FSE) requires assistance while installing an Engineered System, a
streamlined method of engaging an Engineered Systems Enterprise Support Team (EEST)
engineer when the SR owner is not available is described below.
The SR referred to is the installation SR.
An FSE would use this option if they are onsite and require immediate assistance from EEST.
This process is specifically for FSE Callbacks for hardware, installation and Field Change Order
(FCOs) support and should NOT be used by ACS or partners.
The complete process is described in MOS Document ID 1803744.1 EEST: Silent Menu Option:
GCSEXA (internal-only). Ensure that you understand the contents before going onsite.
If you encounter an issue during the installation, this may be documented in the ODA Current
Product Issues page: MOS Document ID 1538187.1 (internal-only). Refer to this document for a
possible workaround to any bug you may encounter during the installation.
Task Check
INSTALLATION OVERVIEW– EIS DELIVERABLES

For an overview of the activities carried out during the installation of this product via the
EIS Methodology, refer to the EIS-Deliverables page within the EIS website for the Oracle
Database Appliance ODA.
MEMORY DIMM FAULT BEST PRACTICES

TSC are seeing many DIMMs being replaced in the field due to initial boot up and Memory
DIMM fault either due to Memory DIMM movement during shipping or improper seating during
memory upgrades.
If Memory DIMM faults are encountered during the installation or upgrade of any engineered
systems, please follow the "BEST PRACTICE" as supplied by the hardware team.
Best Practice for resolving DIMM Faults during Installation or upgrade:
1. We (TSC) are recommending the re-seating of Memory DIMMs when seeing faults during
installation or memory upgrades, as a first step.
2. If we see these failures outside of upgrades or rack installs, we don't want to take the chance
and risk of a second visit if they're truly failed Memory DIMMs. So we recommend, in these
instances, to simply replace the Memory DIMM. If the replaced Memory DIMM experiences
Training errors, then it might be prudent to re-seat the Memory DIMM.
INFORMATION: EIS Checklist Steps & Estimated Timing
Item First Page Est. Duration
Preparation 4 4 hours
Unpacking 7 30 mins
Assembly / Cabling 8 45 mins
ILOM Service Processor Configuration 8 10 mins
Server Power On & POST 10 15 mins
Bare Metal Configuration 11 70 mins
Changing the ODA CPU Core Count 22 15 mins
Deploying the Oracle Database Appliance 23 10 mins
Monitor Deployment Progress 27 20 mins
Post Validation 28 15 mins
Redeployment if Necessary 29 40 mins
Securing the ILOM Service Processors (SP) 30 10 mins
Handover 30 10 mins
Appendix A: Using the odacli Command to
31 10 mins
Monitor Deployment
Task Comment Check
PREPARATION
AUTOMATIC SERVICE REQUEST (ASR) ACTIVITIES
If the ODA will not be configured to use ASR go to the section entitled “ODA
PREPARATION” below.
If the ASR Manager has not been previously installed AND the Customer requests that
Oracle install it, go to the documentation page for Oracle ASR and select the URL for the
ASR Manager installation and operations guide, quick install guide, security white paper.
There you will find the current Installation and Operations Guide. Follow the instructions
to install the ASRM based on the system you have been given to install it in.
Register the ASR manager with Oracle – follow the installation process through the point
where the ASR is registered to the backend.
This activity must be completed prior to installation of the ODA(s).
CHECKING A CUSTOMER'S EXISTING ASR MANAGER SERVER
If the Customer has a configured and operational ASR Manager system available, the
components within the ODA will be configured to use ASR. Ensure that the IP address &
root password of the ASR Manager host are available.
We understand that when ODA is configured to use a customer’s existing ASR
environment, this ASR Manager must be at version 5.7.6 or higher.
ODA PREPARATION
EIS Site-Audit Report complete? EISdoc V4:
File EIS-SiteAudit-Racked-Item.odt
The ODA X7-2S & X7-2M require 1RU space.
EIS Installation Configuration Plan & Test EISdoc V4:
Procedures Plan complete? Use appropriate BUILD & TPP templates, inserted
into “Master” files (Chapter Servers):
EIS-BUILD-Server-ODA-X7SM.odt
EIS-TPP-Server-ODA-X7SM.odt
Review the network configuration information IP addresses are required for both the host & the
supplied by the customer to ensure the correct Service Processor (ILOM).
data is recorded. Do this BEFORE going
onsite.
Review the documentation set for the Oracle Database Appliance (ODA) X7.
Also available is an Oracle Internal-only FAQ for the Oracle Database Appliance
Externally-available information on all ODA products is on OTN. Should a customer have
further questions they should contact their sales representative.
Task Comment Check
Terminology
Oracle Database Appliance patches and software consists the following components:
• ODA X7-2S/ODA X7-2M Bundle Patch – Contains patches to the following
components: OS, Component Firmware and Oracle Appliance Manager Modules,
Grid Infrastructure and RDBMS.
• OS ISO Image – Used to restore the OS to the "shipped from factory" state. Use
only when necessary.
• Bare Metal – Refers to the non-virtualized ODA configuration.
• Image files – GI/RDBMS Clone files – Contains the latest Grid Infrastructure and
RDBMS components, for deployment on an Oracle Database Appliance in the
"shipped from factory" state, or an Oracle Database Appliance that has been re-
imaged using the OS ISO Image.
• Some documentation refer the above to the Oracle Database Appliance Single
Instance software Bundle (SIB) file(s).
The latest releases are listed and can be accessed from MOS Document ID 888888.1
“Oracle Database Appliance – 12.2.1.1 and 2.X Supported ODA Versions & Known
Issues” – this is the easiest method to access the required files.
PREPARING THE DOWNLOADS
It is highly recommended that you always obtain the latest ODA software releases directly
from MOS. The Bare Metal software image is installed by the factory and is most likely
not the latest version available on MOS. Also, in the past, the ODA Patch Bundle number
has been known to change with each release
The Oracle Database Appliance X7-2 S/M can only be deployed Bare Metal Configuration.
The latest patches and ISO images can be found in MOS in the Patches and Updates tab.
In the Patch Search section, click on the Product or Family (Advanced) side tab, and next
to the Product field enter “Oracle Database Appliance X7-2 S/M Hardware”. Next to the
Release field, in the drop-down box, select “Oracle Appliance Kit 12.2.1.2.0”
Click on Search button.
DOWNLOADING PATCHES
It is recommended to download all the patches that might be needed ahead of time in order
to avoid excessive download times while at the customer site.
Task Comment Check
Download the most recent versions of the following files from MOS. At the time of this
writing the latest release version of these files is 12.2.1.2.0.
• 23530609 – ODA ISO Bare Metal Restore file – only be necessary if a complete re-
image is required. (1.4GB)
• 27119393 – GI Clone files. This file is required for deployment. (3.8GB)
• 27141226 – Server patch bundle, has three (3) parts. (total 9.0GB)
◦ p27141226_122120_Linux-x86-64_1of3.zip (1.9GB)
◦ p27141226_122120_Linux-x86-64_2of3.zip (3.3GB)
◦ p27141226_122120_Linux-x86-64_3of3.zip (3.8GB)
Database Clone patches:
• 27119402 – Oracle 12.2.0.1 RDBMS Software Clone file for creating any new 12.2.0.1
database homes. This DB clone file is only required if you are deploying a 12.2.0.1
database. (3.6GB)
• 23494992 – Oracle 12.1.0.2 RDBMS Software Clone file for creating any new 12.1
database. (3.9GB)
• 23494997 – Oracle 11.2.0.4 RDBMS Software Clone file for creating any new 11.2
database. (2.2GB)
The downloaded files can be copied onto a USB flash drive (up to 32GB) for access by the
system.
NOTE: When using a USB flash drive, FAT32 is a requirement. As such, FAT32 has
limitations such as a single filesize limit of 4GB and drive/partition sizes are capped at
32GB. Confirm that the file system type on the USB flash drive is FAT32 in order to
prevent Linux filesystem mounting problems during the installation.
Task Comment Check
UNPACKING
Delivery complete?
Collect the white Customer Information File away carefully!
Sheets (CIS).
Allow the system to acclimatise (power off) at Refer to EIS standard “Acclimatisation of Oracle
the customer site. Hardware products”.
Collect packing material together for disposal.
Unpack outside data center to ensure no
contamination/dust is released inside
customer's controlled environment.
Verify all packing material has been removed, Fans & air vents must be free to operate.
i.e. nothing is blocked.
Gather excess parts, cables etc. in a box.
Collect documentation together. Give to customer during handover.
Refer to the Oracle Database Appliance Owner's Guide for details on inserting the system
into a rack. A 1RU space is required for either an ODA X7-2S or ODA X7-2M
configuration.
Supported in any racks meeting the below criteria:
• Four-post rack (mounting at both front and rear), not supported in two-post racks.
• Rack should have a horizontal opening and unit vertical pitch conforming to ANSI/EIA 310-D-
1992 or IEC 60927 standards.
• Distance between front and rear mounting planes between approximately 24 and 36 inches
(610 mm and 915 mm).
• Minimum clearance depth (to front cabinet door) in front of front rack mounting plane: 1 inch
(25.4 mm).
• Minimum clearance depth (to rear cabinet door) behind front rack mounting plane: 35.43
inches (900 mm) with the cable management arm, or 800 mm (31.5 in) without the cable
management arm.
• Minimum clearance width (between structural supports and cable troughs) between front and
rear mounting planes: 18 inches (456 mm).
• Minimum clearance for front service access is 48.5 inches (123.2 cm).
• Minimum clearance for rear service access is 36 inches (91 cm).
Always load equipment into a rack from the bottom upwards so that it will not become top-
heavy and tip over. Deploy the rack's anti-tilt bar to prevent the rack from tipping during
equipment installation.
Task Comment Check
ASSEMBLY/CABLING
Note the serial number. The sticker which contains the serial number is on
the top of a server node, on the left-hand side
towards the front.
Distribute systems across power-sequencers considering failure-safety.
Connect Ethernet cable for the SP to the To the NET MGT port.
administration network.
Connect serial cable between the SP and a To the SER MGT port.
terminal device or PC – used for the initial
configuration.
Task Comment Check
ILOM SERVICE PROCESSOR CONFIGURATION

This checklist assumes IPv4 networking.
If you are using a KVM or directly attached monitor and keyboard, the ILOM may be configured
using the web configurator. This will save the task of connecting to the serial port to configure the
ILOM net management port manually. In this case skip this entire section and go to page 10
(Server Power on & Post).
When the SP initially boots it will attempt to If DHCP server is available you can connect to the
obtain an IP address from a DHCP server. SP via network (ssh or https), otherwise you have to
connect to the SP via a serial line (see below) and
You must have a cable connected to the SP specify a static Ethernet configuration.
Network Management port (NET MGT).
Obtain the Service Processor IP address from This will be the address assigned by the DHCP
one of the following locations. Record the IP server.
address for future reference: Advanced → BMC Network Configuration → Current
Ipv4 address in BMC
• The system BIOS setup screen.
User = root
• Command-line interface – connect to serial Password = changeme
port via terminal device (such as a laptop). show /SP/network
Log into the SP via CLI and display the IP
address.
CONFIGURING ILOM VIA CLI AND A SERIAL CONNECTION
To set a static IP address for the SP using the CLI and a serial line connection perform the
steps below.
Establish a serial connection to the SP Serial E.g. When using a laptop start a terminal interface
Management Port (SER MGT). to the serial port that is connected to the ILOM SP.
The default serial port speed is 115200 baud with no Previously 9600 baud.
flow control.
Log in to the ILOM SP. User = root
Password = changeme
Set the working directory. -> cd /SP/network
Task Comment Check
Enter the following commands to specify a The following are example values:
static Ethernet configuration. Note that there -> set pendingipaddress=<ip addr>
-> set pendingipnetmask=<ip netmask>
are no spaces in command line structure. -> set pendingipgateway=<ip gateway>
-> set pendingipdiscovery=static
It is also possible to configure ILOM network -> set commitpending=true
settings via the system BIOS in the Advanced -> set state=enabled
Menu tab under BMC Network. Note that the commitpending command requires
several seconds to complete.
Verify the changes. -> show /SP/network
Verify that the gateway can be reached:

-> set /SP/network/test ping=<IP of gateway>
ping of <IP of gateway> succeeded
After setting up the SP, exit. -> exit
CONFIGURING ILOM VIA GUI & ETHERNET CONNECTION

To set a static IP address for the SP using the GUI perform the steps below.
Determine the current IP address of the SP using one of the methods described at the top of
this page. For this to work IP assignment by DHCP must have succeeded!
Connect to the SP via a web browser running
on a remote system (Firefox or Internet
Explorer).
Log into the web GUI using the default user https://<ip-addr-of-sp>
User = root
name & password.
Password = changeme
Select ILOM Administration and then Connectivity to display information about the
current network configuration of your ILOM. The network configuration can be modified
then press the Save button.
CONFIGURING THE SP'S CLOCK PROPERTIES VIA CLI
For more details, refer to the Oracle ILOM Administrator's Guide for Configuration and
Maintenance Firmware Release 4.0.x.
To examine the current settings:
-> show /SP/clock
/SP/clock
Targets:
Properties:
datetime = Fri Aug 23 10:10:09 2013
timezone = GMT (GMT)
uptime = 1 day, 19:17:16
usentpserver = disabled
If required, the timezone can be changed from GMT (default) to EST or PST8PDT:
-> set /SP/clock timezone=EST5EDT
Task Comment Check
To manually set the ILOM clock property values:
-> set /SP/clock datetime=MMDDhhmmYYYY
Example:
-> set /SP/clock datetime=082310132013
Set 'datetime' to '082310132013'
-> show /SP/clock

/SP/clock
Targets:
Properties:
datetime = Fri Aug 23 10:13:04 2013
timezone = GMT (GMT)
uptime = 1 day, 19:17:16
usentpserver = disabled
To synchronise the SP's clock property values with an NTP server:

-> set /SP/clients/ntp/server/1 address=<ip_address>
-> set /SP/clock usentpserver=enabled
CONFIGURING THE SP'S CLOCK PROPERTIES VIA GUI

For more details, refer to the Oracle ILOM Administrator's Guide for Configuration and
Maintenance Firmware Release 4.0.x.
Log into the web GUI using the default user https://<ip-addr-of-sp>
User = root
name & password.
Password = changeme
Select ILOM Administration and then Date You can make desired change and then press the
and Time. Select the Timezone tab to display Save button.
the current timezone information.
Then select the Clock tab to display the You can make desired changes (date, time &
current Clock Settings page. optional NTP configuration) and then press the
Save button.
Task Comment Check
SERVER POWER ON & POST

Refer to the Oracle Database Appliance Getting Started Guide.
Power on the server. There are several ways to do this:
• Press the power-on button on the front panel (with clock symbol).
• From the CLI on the SP issue: start /SYS
• On the ILOM GUI expand the Host Management link in the left column then select
Power Control. In the Main panel you will see “Host is currently off”. Select Power
On and then Save.
The fans will speed up and after a few seconds The console will show the results of POST. Expect
back down. Observe the POST results. to see “BMC Responding”.
Task Comment Check
If using CLI: gain host console access. From server's SP:
-> start /HOST/console
To stop the host console press ESC followed
You could use keyboard, mouse and monitor
by ( i.e. opening round bracket. To leave the directly attached to the server's ports.
secure shell: exit
At the OS login prompt: User root with welcome1 as password.
Task Comment Check
BARE METAL CONFIGURATION

A high-level version of the instructions for “Bare Metal” (based on the README) are given here.
PREREQUISITES
To verify the current ODA system version, run the following command:
# cat /opt/oracle/oak/pkgrepos/System/VERSION
version=12.2.1.2.0
If the version is the latest available on MOS, then you can proceed with the Bare Metal
deployment – go to Patches Needed to Deploy ODA (page 14) of this checklist. If the
version is older than what is available on MOS, you can re-image using the ISO file
contained in patch 23530609 (which was downloaded during the Preparation activities).
To re-image with a newer version, you will require the Bare Metal ISO image.
The file can be unzipped on a Linux or Windows environment using appropriate
commands to unzip the file. For example on Linux use:
# unzip p23530609_xxxxxx_Linux-x86-64.zip
Connect to ILOM from the Browser and login as root:
On Successful login, the Browser will redirect to the Oracle Integrated Lights out Manager
home page. Click on the Launch button to continue:
Task Comment Check
Depending on the state of the system, there may be some message on the console. Click on
KVMS and then Storage as highlighted below:
Click on Add, then browser to choose the iso image as shown below:
Click on the file you've just selected and press Connect at the bottom of the screen.
After you have pressed Connect, if the Java window suddenly crashes, try it again, but this
time uncheck the SSL Enabled box on this screen.
Task Comment Check
Now that the ISO image has successfully been mounted, return to the ILOM web GUI to
set the boot device to CDROM and press Save.
Now click on the Power Control tab as shown below and choose Power Cycle and press
Save:
The Database Appliance Bare Metal install will start after reboot. This process will
continue for about an hour and then the following screen will be displayed:
Now you can login using user name root and password welcome1.
Task Comment Check
PATCHES NEEDED TO DEPLOY ODA
Now you will require the patches previously download on page 5 for deployment:
• p27119393_xxxxxx_Linux-x86-64.zip – GI Clone files. This file is required for
deployment.
• p27141226_122120_Linux-x86-64_1/2/3of3.zip – ODA Server Patch Bundle
• p23494992_xxxxxx_Linux-x86-64.zip – Oracle 12.1.0.2 RDBMS Software Clone
file for creating any new 12.1 database homes. This DB clone file is only required if
you are deploying a 12.1.0.2 database.
file for creating any new 11.2 database homes. This DB clone file is only required if
you are deploying a 11.2.0.4 database.
file for creating any new 12.2.0.1 database homes. This DB clone file is only required
if you are deploying a 12.2.0.1 database.
CONFIGURING THE NETWORK INTERFACE
On the X7-2 servers, there are 4 onboard network ports: NET1/NET2 (1-10GbE) copper or
NET1/NET2 (10/25GbE) fiber. The configure-firstnet script will only configure one
pair or the other. You cannot use both pairs. Make sure there is a live network cable
plugged in before running the configure-firstnet script, so that it can configure the
appropriate bonding.
Run the command configure-firstnet. Respond to the prompts to configure the public
network interface. Also provide the netmask and gateway IP address.
Example output below:
[root@oak ~]# configure-firstnet
Select the Interface to configure the network on (btbond1) [btbond1]:
Configure DHCP on btbond1 (yes/no) [no]:
INFO: You have chosen Static configuration
Enter the IP address to configure : 10.145.228.239
Enter the Netmask address to configure : 255.255.252.0
Enter the Gateway address to configure[10.145.228.1] :
INFO: Plumbing the IPs now
INFO: Restarting the network
Shutting down interface btbond1: [ OK ]
Shutting down interface em1: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface btbond1: Determining if ip address 10.145.228.239 is already in use
for device btbond1...
[ OK ]
Bringing up interface em1: [ OK ]
*** BE aware of bug 27187539 if the customer wants to use the two 10/25GbE SFP+
ports. The normal transceivers will not work. The customer will have two options:
• Use the 2x RJ45 10GBase-T ports with a twisted pair cable
• Use a twinax copper connection to the SFP+ ports (P/N X2130A-5M-N)
UPLOADING PATCH TO THE SERVER NODE
Task Comment Check
Now that you have an active network interface, you can use scp/ftp/filezilla to transfer the
files to the server node, for example:
# scp p27119393_122120_Linux-x86-64.zip root@<ip of oda>:/tmp
# scp p27141226_122120_Linux-x86-64_1of3.zip root@<ip of oda>:/tmp
UPLOADING PATCHES TO NODES FROM USB MEDIA

Assuming that the appropriate patches are Example: /tmp
available on a mounted USB stick:
Mount the USB flash drive and transfer the # cd /
# mkdir /usb
files to a convenient temporary location. # mount /dev/sdc /usb
To locate the device name (/dev/sdc from above)
use: lsscsi
# lsscsi
[1:0:0:0] disk ATA INTEL SSDSCKJB48 0112 /dev/sda
[2:0:0:0] disk ATA INTEL SSDSCKJB48 0112 /dev/sdb
[8:0:0:0] cd/dvd SUN Remote ISO CDROM 1.01 /dev/sr0
[9:0:0:0] disk PNY USB 2.0 FD 8192 /dev/sdc <<<<<<<<<<<<<<<<<< here is usb
Be sure to unmount the USB filesystem when # umount /dev/sday1 /usb
finished – either via a reboot of the system or
via the Linux command:
UNPACK AND INSTALL THE GI PATCH
Unzip the patch:
# unzip p27119393_122120_Linux-x86-64.zip
Archive: p27119393_122120_Linux-x86-64.zip
extracting: oda-sm-12.2.1.2.0-171124-GI-12.2.0.1.zip
inflating: README.txt
Apply the update:

# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/oda-sm-12.2.1.2.0-171124-GI-
12.2.0.1.zip
{
"jobId" : "2e84c187-94a5-452d-8775-2d0af69a28e1",
"status" : "Created",
"message" : "/tmp/oda-sm-12.2.1.2.0-171124-GI-12.2.0.1.zip",
"reports" : [ ],
"createTimestamp" : "February 05, 2018 08:13:45 AM PST",
"resourceList" : [ ],
"description" : "Repository Update",
"updatedTime" : "February 05, 2018 08:13:45 AM PST"
}
This process should take about 3 minutes to complete.

Confirm that the update has been successful:
# /opt/oracle/dcs/bin/odacli describe-job -i "2e84c187-94a5-452d-8775-2d0af69a28e1"
Job details
----------------------------------------------------------------
ID: 2e84c187-94a5-452d-8775-2d0af69a28e1
Description: Repository Update
Status: Success
Created: February 5, 2018 8:13:45 AM PST
Message: /tmp/oda-sm-12.2.1.2.0-171124-GI-12.2.0.1.zip
Task Name Start Time End Time Status

-------------------------------------- ------------------------- ------------------------- ------------
Task Comment Check
Delete the unneeded files to free up space for unpacking other patches:
# rm oda-sm-12.2.1.2.0-171124-GI-12.2.0.1.zip
rm: remove regular file òda-sm-12.2.1.2.0-171124-GI-12.2.0.1.zip'? yes
Keep the original patch file, just in case you need to redeploy
UNPACK AND INSTALL THE SERVER PATCH
Unzip the patch:
# unzip p27141226_122120_Linux-x86-64_1of3.zip
Archive: p27141226_122120_Linux-x86-64_1of3.zip
extracting: oda-sm-12.2.1.2.0-180103.2-server1of3.zip
inflating: README.html
Do NOT unzip the other two zip files: p27141226_122120_Linux-x86-64_2of3.zip and

p27141226_122120_Linux-x86-64_3of3.zip. The patch installation scripts require these two
files to remain in their original zipped state.
Applying Patches in a Single Command Set
The server patch can be applied individually or all in one command set.
This is the command to do them all at once:
# /opt/oracle/dcs/bin/odacli update-repository -f /opt/oda-sm-12.2.1.2.0-180103.2-
server1of3.zip,/opt/p27141226_122120_Linux-x86-64_2of3.zip,/opt/p27141226_122120_Linux-x86-
64_3of3.zip
This process should take about 5 minutes to complete. If the command completes
successfully, you may skip the below section on Applying Patches Individually and proceed
to the section on Updating dcsagent on page 18.
If this command set fails for any reason, you will need to apply each zip file individually.
Proceed to the steps below.
Applying Patches Individually
Apply the update:
# /opt/oracle/dcs/bin/odacli update-repository -f /u01/patches/oda-sm-12.2.1.2.0-180103.2-
server1of3.zip
{
"jobId" : "7a3c15b8-55db-4984-bd07-98ff40f00151",
"message" : "/u01/patches/oda-sm-12.2.1.2.0-180103.2-server1of3.zip",
"reports" : [ ],
}

# /opt/oracle/dcs/bin/odacli describe-job -i "7a3c15b8-55db-4984-bd07-98ff40f00151"
Job details
----------------------------------------------------------------
ID: 7a3c15b8-55db-4984-bd07-98ff40f00151
Status: Success
Message: /u01/patches/oda-sm-12.2.1.2.0-180103.2-server1of3.zip

-------------------------------------- ------------------------- ------------------------- ------------
Task Comment Check
Apply the update on 2nd patch:
# /opt/oracle/dcs/bin/odacli update-repository -f /u01/patches/p27141226_122120_Linux-x86-
64_2of3.zip
{
"jobId" : "ab5f3843-8dcc-4a1b-ba16-39d8a63622fc",
"message" : "/u01/patches/p27141226_122120_Linux-x86-64_2of3.zip",
"reports" : [ ],
}

# /opt/oracle/dcs/bin/odacli describe-job -i "ab5f3843-8dcc-4a1b-ba16-39d8a63622fc"
Job details
----------------------------------------------------------------
ID: ab5f3843-8dcc-4a1b-ba16-39d8a63622fc
Status: Success
Message: /u01/patches/p27141226_122120_Linux-x86-64_2of3.zip

-------------------------------------- ------------------------- ------------------------- ------------
Apply the update on 3rd patch:

# /opt/oracle/dcs/bin/odacli update-repository -f /u01/patches/p27141226_122120_Linux-x86-
64_3of3.zip
{
"jobId" : "d7653699-5b1a-4842-ac45-78b0bef7d520",
"message" : "/u01/patches/p27141226_122120_Linux-x86-64_3of3.zip",
"reports" : [ ],
}

# /opt/oracle/dcs/bin/odacli describe-job -i "d7653699-5b1a-4842-ac45-78b0bef7d520"
Job details
----------------------------------------------------------------
ID: d7653699-5b1a-4842-ac45-78b0bef7d520
Status: Success
Message: /u01/patches/p27141226_122120_Linux-x86-64_3of3.zip

-------------------------------------- ------------------------- ------------------------- ------------
Task Comment Check
Updating dcsagent
Update dcsagent:
# /opt/oracle/dcs/bin/odacli update-dcsagent -v 12.2.1.2.0;sleep 120
{
"jobId" : "dd7acb8b-6e7d-4d8d-95fd-4a8bc5da1c2c",
"message" : "Dcs agent will be restarted after the update. Please wait for 2-3 mins
before executing the other commands",
"reports" : [ ],
"description" : "DcsAgent patching",
}

# /opt/oracle/dcs/bin/odacli describe-job -i "dd7acb8b-6e7d-4d8d-95fd-4a8bc5da1c2c"
Job details
----------------------------------------------------------------
ID: dd7acb8b-6e7d-4d8d-95fd-4a8bc5da1c2c
Description: DcsAgent patching
Status: Success
Message:

----------------------------- ------------------------------- ------------------------------- ------------
Patch location validation February 5, 2018 8:28:41 AM PST February 5, 2018 8:28:41 AM PST Success
dcs-agent upgrade February 5, 2018 8:28:41 AM PST February 5, 2018 8:28:42 AM PST Success
Update Storage:
# /opt/oracle/dcs/bin/odacli update-storage -v 12.2.1.2.0
{
"jobId" : "f8e06921-9527-42b4-a46f-56e3a9b470ac",
"message" : "Success of Storage Update may trigger reboot of node after 4-5 minutes. Please wait till
node restart",
"reports" : [ ],
"description" : "Storage Firmware Patching",
}

# /opt/oracle/dcs/bin/odacli describe-job -i "f8e06921-9527-42b4-a46f-56e3a9b470ac"
Job details
----------------------------------------------------------------
ID: f8e06921-9527-42b4-a46f-56e3a9b470ac
Description: Storage Firmware Patching
Status: Success
Message:
------------------------------------ -------------------------------- -------------------------------- ------------
Applying Firmware Controller Patches February 5, 2018 11:18:47 AM PST February 5, 2018 11:18:49 AM PST Success
Reboot Ilom February 5, 2018 11:18:49 AM PST February 5, 2018 11:18:49 AM PST Success
Update server:
# /opt/oracle/dcs/bin/odacli update-server -v 12.2.1.2.0
{
"jobId" : "21dd683b-efde-439f-b464-f5d336c34fdb",
"message" : "Success of Server Update may trigger reboot of node after 4-5 minutes.
Please wait till node restart",
"reports" : [ ],
"description" : "Server Patching",
}
Task Comment Check
# /opt/oracle/dcs/bin/odacli describe-job -i "21dd683b-efde-439f-b464-f5d336c34fdb"
Job details
----------------------------------------------------------------
ID: 21dd683b-efde-439f-b464-f5d336c34fdb
Description: Server Patching
Status: Success
Message:

------------------------------------ ------------------------------- ------------------------------- ------------
dcs-controller upgrade February 5, 2018 8:31:56 AM PST February 5, 2018 8:31:56 AM PST Success
dcs-cli upgrade February 5, 2018 8:31:56 AM PST February 5, 2018 8:31:56 AM PST Success
Creating repositories using yum February 5, 2018 8:31:56 AM PST February 5, 2018 8:31:57 AM PST Success
Applying HMP Patches February 5, 2018 8:31:57 AM PST February 5, 2018 8:32:30 AM PST Success
oda-hw-mgmt upgrade February 5, 2018 8:32:30 AM PST February 5, 2018 8:32:30 AM PST Success
Creating repositories using yum February 5, 2018 8:32:30 AM PST February 5, 2018 8:32:37 AM PST Success
Applying OS Patches February 5, 2018 8:32:37 AM PST February 5, 2018 8:33:11 AM PST Success
Applying Firmware Controller Patches February 5, 2018 8:33:11 AM PST February 5, 2018 8:33:12 AM PST Success
Reboot Ilom February 5, 2018 8:33:12 AM PST February 5, 2018 8:33:12 AM PST Success
Describe-component to make sure all components are up-to-date:

# /opt/oracle/dcs/bin/odacli describe-component
System Version
---------------
12.2.1.2.0
Component Installed Version Available Version

---------------------------------------- -------------------- --------------------
OAK 12.2.1.2.0 up-to-date
DCSAGENT 12.2.1.2.0 up-to-date
ILOM 4.0.0.28.r121827 4.0.0.22.r120818
BIOS 41017600 41017100
OS 6.8 up-to-date
In the above example, the Installed ILOM/BIOS version is higher than the Available
version. If you are seeing this on your system, this is OK. The update-server will not
downgrade the ILOM/BIOS version, or any other firmware version.
OVERVIEW OF OPTIONAL DATABASE VERSIONS & REQUIRED PATCHES
The web provisioning tool will only allow you to deploy just one database version on initial
deployment. The database version that the customer wants to deploy will determine which
patch to install:
• p27119402_xxxxxx_Linux-x86-64.zip – Oracle 12.2.0.1.171017 RDBMS Software
Clone file for creating any new 12.2.0.1 database homes.
Clone file for creating any new 12.1 database homes.
Clone file for creating any new 11.2 database homes.
You can install all three if the customer is planning on deploying other database versions.
OPTIONAL: DB CLONE FILE TO DEPLOY A 12.2.0.1 DATABASE
Unpack the DB clone file for deploying a 12.2.0.1 database.
extracting: oda-sm-12.2.1.2.0-171124-DB-12.2.0.1.zip
replace README.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
Task Comment Check
Apply the update:
# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/oda-sm-12.2.1.2.0-171124-DB-
12.2.0.1.zip
{
"jobId" : "51a8f22f-2773-4015-8e74-72ac2a3b11ee",
"message" : "/tmp/oda-sm-12.2.1.2.0-171124-DB-12.2.0.1.zip",
"reports" : [ ],
}

Confirm that the respository update has been successful:
# /opt/oracle/dcs/bin/odacli describe-job -i "51a8f22f-2773-4015-8e74-72ac2a3b11ee"
Job details
----------------------------------------------------------------
ID: 51a8f22f-2773-4015-8e74-72ac2a3b11ee
Status: Success
Message: /tmp/oda-sm-12.2.1.2.0-171124-DB-12.2.0.1.zip

------------------------------------ ------------------------------- ------------------------------- ------------
# rm oda-sm-12.2.1.2.0-171124-DB-12.2.0.1.zip
rm: remove regular file òda-sm-12.2.1.2.0-171124-DB-12.2.0.1.zip'? yes

Unpack the DB clone file for deploying a 12.1.0.2 database on both nodes:
Apply the update:

12.1.0.2.zip
{
"jobId" : "311120ec-9210-470e-9ead-cbeae4a30f74",
"reports" : [ ],
}

Confirm the job was successful, using the JobId from previous command’s output:
# /opt/oracle/dcs/bin/odacli describe-job -i "311120ec-9210-470e-9ead-cbeae4a30f74"
Job details
----------------------------------------------------------------
ID: 311120ec-9210-470e-9ead-cbeae4a30f74
Status: Success

------------------------------------ ------------------------------- ------------------------------- ------------
Task Comment Check
# rm oda-sm-12.2.1.2.0-171124-DB-12.1.0.2.zip
rm: remove regular file òda-sm-12.2.1.2.0-171124-DB-12.1.0.2.zip'? Yes

Unpack the DB clone file for deploying a 11.2.0.4 database on both nodes:
Apply the update:

11.2.0.4.zip
{
"jobId" : "98929ae8-7e61-4467-875d-8bf5cb971301",
"reports" : [ ],
}

Confirm the job was successful, using the JobId from previous command’s output:
# /opt/oracle/dcs/bin/odacli describe-job -i "98929ae8-7e61-4467-875d-8bf5cb971301"
Job details
----------------------------------------------------------------
ID: 98929ae8-7e61-4467-875d-8bf5cb971301
Status: Success

------------------------------------ ------------------------------- ------------------------------- ------------
# rm oda-sm-12.2.1.2.0-171124-DB-11.2.0.4.zip
rm: remove regular file òda-sm-12.2.1.2.0-171124-DB-11.2.0.4.zip'? Yes
Task Comment Check
CHANGING THE ODA CPU CORE COUNT

The ODA is delivered with all cores on the This section is only applicable of the customer
server enabled. For the ODA X7-2S, 20 cores requires less than the default number of cores
enabled.
are enabled by default. For the ODA X7-2M,
36 cores are enabled by default.
Set the cores in multiples of 2 (e.g. 12, from an X7-2M):
# /opt/oracle/dcs/bin/odacli update-cpucore --cores 12
{
"jobId" : "23bba1f7-0fbf-4084-8243-f09adbbf8552",
"message" : null,
"reports" : [ ],
"description" : "CPU cores service update",
}

# /opt/oracle/dcs/bin/odacli describe-job -i "23bba1f7-0fbf-4084-8243-f09adbbf8552"
Job details
----------------------------------------------------------------
ID: 23bba1f7-0fbf-4084-8243-f09adbbf8552
Description: CPU cores service update
Status: Success
Message:

------------------------------------ ------------------------------- ------------------------------- ------------
Confirm that the core count is now 12:

# /opt/oracle/dcs/bin/odacli describe-cpucore
Node Cores Modified Job Status

----- ------ ------------------------------ ---------------
0 12 February 5, 2018 11:47:52 AM PST Configured
Task Comment Check
DEPLOYING THE ORACLE DATABASE APPLIANCE

You are now ready to deploy the Oracle Database Appliance. Monitor the progress by:
# tail -f /opt/oracle/dcs/log/dcs-agent.log
Using the Chrome or IE browser, enter the following URL and log into the ODA:
• https://<ipaddress-node0>:7093/mgmt/index.html
• Username: oda-admin
• Password (default): welcome1
If the login fails due to an authentication issue, make sure that network between the ODA
and the installer’s laptop etc. has ports 7070 and 7093 open. If this is not the case
authentication will not work, even after changing the oda-admin password.
On the first screen of a new system, you will see this, click on Create Appliance.
The web provisioning tool will appear. Mandatory fields are denoted by an asterisk (*).
Task Comment Check
Even if the ILOM network has been configured, it is good practice to also input the values
here.
In the “User and Group Selection” area (Example below) asks if you want to “Customize
Users & Groups”.
If you select Yes, the section will expand and you will need to fill in the following fields:
Task Comment Check
Creating an initial database is not mandatory for deployment, as this can be done later by
the customer using the odacli create-database command. Additional databases can also be
created with odacli create-database.
If you select Yes above, you will need to fill in the following fields. The database name
must begin with an alpha character and contain only alphanumeric characters. The
database name must not exceed 8 characters.
In order to use the External ASR Manager, the customer will need an existing ASR
Manager IP. While using an External ASR Manager is highly recommended, it is
supported to use the internal ASR manager.
If Yes, the ASR User Name and Password is required.

If Yes to HTTP Proxy, the Proxy Server Name and Proxy Port is required.
If Yes to HTTP Proxy Requires Authentication, Proxy User Name and Proxy Password
is required.
Then press Submit.
Task Comment Check
Select Yes in the pop-up confirmation window:
You should see a pop-up with the job ID:
The provisioning process takes approximately 30-45 minutes.

You can click the link in the above pop-up window for a job status.
Task Comment Check
MONITOR DEPLOYMENT PROGRESS

To monitor deployment progress, you can Example below.
monitor the dcs-agent.log file. If there is an error during deployment, we will see it
# tail -f /opt/oracle/dcs/log/dcs-agent.log in the dcs-agent.log file.
You can also run the odacli command to

monitor/check status. For an example, refer to
Appendix A on page 31 of this checklist.
Using the web configurator, you can check on Example below.
the status.
Click on Activity on the top left hand corner to
reveal details of the provisioning job.
As you can see here the Job ID is shown and the Status is Running. When completed, the
status will change to Success.
Another way to check the status of Example below.

provisioning is to use odacli describe-job In the output shown, you can see the job is still in
command. “Running” status. This will change to “Success”
when the job is complete.
# /opt/oracle/dcs/bin/odacli describe-job -i 90045308-6cf3-4a6d-9382-747f70cfe52c
Job details
----------------------------------------------------------------
ID: 90045308-6cf3-4a6d-9382-747f70cfe52c
Description: Provisioning service creation
Status: Running <<<<<<<<<<<<< still Running.
Created: February 5, 2018 9:50:59 AM MST
Message:

------------------------------------ ------------------------------- ------------------------------- ------------
Checking the ipAddress February 5, 2018 9:51:00 AM MST February 5, 2018 9:51:00 AM MST Success
Setting up Network February 5, 2018 9:51:00 AM MST February 5, 2018 9:51:00 AM MST Success
OS usergroup 'asmdba'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:05 AM MST Success
OS usergroup 'asmoper'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:05 AM MST Success
OS usergroup 'asmadmin'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:05 AM MST Success
OS usergroup 'dba'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:05 AM MST Success
OS usergroup 'dbaoper'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:06 AM MST Success
OS usergroup 'oinstall'creation February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
OS user 'grid'creation February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
OS user 'oracle'creation February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
SSH equivalance setup February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
Grid home creation February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Running
Creating GI home directories February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
Cloning Gi home February 5, 2018 9:51:06 AM MST February 5, 2018 9:53:27 AM MST Success
Task Comment Check
POST VALIDATION
Verify the system has been successfully Example Below.
deployed by checking the new system version You no longer need to use the full patch for
with the command: odacli. The results should look similar to the
output below:
odacli describe-appliance.
# /opt/oracle/dcs/bin/odacli describe-appliance
Appliance Information
----------------------------------------------------------------
ID: fd9a3575-b1f5-4e14-9091-db4b1a0eeab7
Platform: OdaliteM
Data Disk Count: 2
CPU Core Count: 36
System Information
----------------------------------------------------------------
Name: odax7-2m-brm06-a
Domain Name: us.oracle.com
Time Zone: America/Denver
DB Edition: EE
DNS Servers: 192.135.82.132 192.135.82.172
NTP Servers: 144.20.15.203 144.20.15.204
Disk Group Information

----------------------------------------------------------------
DG Name Redundancy Percentage
------------------------- ------------------------- ------------
Data Normal 80
Reco Normal 20
If ASR was configured as part of the Example below.

deployment this can be tested with the
command: odacli test-asr
# /opt/oracle/dcs/bin/odacli test-asr
Job details
----------------------------------------------------------------
ID: 73fc6be7-fc89-4f07-9260-16b397b41b1a
Description: Test ASR
Status: Created
Message:

------------------------------------ ------------------------------- ------------------------------- ------------
# /opt/oracle/dcs/bin/odacli describe-job -i 73fc6be7-fc89-4f07-9260-16b397b41b1a
Job details
----------------------------------------------------------------
ID: 73fc6be7-fc89-4f07-9260-16b397b41b1a
Description: Test ASR
Status: Success
Message:

----------------------- ------------------------------- ------------------------------- ------------
Test ASR February 5, 2018 10:34:40 AM MST February 5, 2018 10:34:41 AM MST Success
If you need to redeploy for any reason, proceed to the section Redeployment if Necessary
on page 29.
Task Comment Check
REDEPLOYMENT IF NECESSARY
In case of a mistake, where a redeployment is Example below.
needed, the previous configuration can be
wiped out using the following perl script:
/opt/oracle/oak/onecmd/cleanup.pl
# perl /opt/oracle/oak/onecmd/cleanup.pl
About to clean up deployment.

Cleanup erase 4MB of ASM metadata from ASM disks, it may cause data loss, take backup of
user data on ASM disks
Running cleanup will delete Grid User - 'grid' and DB user - 'oracle' and also the groups
'oinstall,dba,asmadmin,asmoper,asmdba'
nodes will be rebooted.
Do you want to continue (yes/no) : yes
Log file name is : /tmp/cleanup_temp_21:04:39_Dec_18.log
Executing </u01/app/12.2.0.1/grid/bin/crsctl disable crs>
CRS-4621: Oracle High Availability Services autostart is disabled.
Executing </u01/app/12.2.0.1/grid/bin/crsctl stop cluster -all>
CRS-2673: Attempting to stop 'ora.crsd' on 'odax7-2m-brm06-a'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on server 'odax7-
2m-brm06-a'
CRS-2673: Attempting to stop 'ora.data.commonstore.acfs' on 'odax7-2m-brm06-a'
CRS-2673: Attempting to stop 'ora.broomdb.db' on 'odax7-2m-brm06-a'
…....................
…................................
This will reboot the server.

After the reboot, you can confirm that the Example below.
previous configuration has been erased.
[root@test ~]# odacli describe-appliance
DCS-10032:Resource sysInstance is not found.
Appliance is not configured. <<<<<<<<<<<<<<<<<< Your confirmation.

Now, you can use the web browser to re- Make sure you exit from the web browser
provision the ODA. completely, then open it back up and restart the
deployment.
If you are now satisfied with the deployment go to SECURING THE ILOM SERVICE
PROCESSOR (SP) on page 30 of this checklist.
Task Comment Check
SECURING THE ILOM SERVICE PROCESSOR (SP)

The ILOM SP must be secured as part of the system's initial installation. Securing requires
the changing of the root password from ‘changeme’. By default connections are secure to
the ILOM either through ssh or https connection through the browser.
Do NOT change the default password until after you have completed software deployment
on the Oracle Appliance.
Change the root password. The password length must between 8-16 characters.
You can use the GUI or the CLI.
Examples below.
Example using the GUI:
1. Pull down the ILOM Administration menu on the left.
2. Select User Management, select the User Accounts sub-tab.
3. Select root user & click on edit.
4. Change the root password.
Example using the CLI:
ssh -l root <SP-ipaddr>
set /SP/users/root password=<new password>
Changing password for user /SP/users/root/password...
Enter new password again: *********
New password was successfully set for user /SP/users/root
For further information refer to the Oracle ILOM Administrator's Guide for Configuration
and Maintenance Firmware Release 4.0.x.
Task Comment Check

COMPLETION
Perform Installation Assessment tests as EISdoc V4 – completed during preparation of
described in the EIS Test Procedures Plan. installation.
Complete documentation and hand over to EISdoc V4:

customer. File EIS-DOCS-Operational Handover-
Document.odt
Short customer briefing: the configuration.
Installation of the ODA X7-2S/M is
COMPLETE.
Copies of the checklists are available on the EIS web pages or on the EIS-DVD. We recommend that you always check
the web pages for the latest version.
Comments & RFEs are welcome. Oracle staff should mail to EIS-SUPPORT_WW@oracle.com .
Partners should mail to: SUPPORT-PARTNER-QUESTIONS_WW_GRP@oracle.com .
Appendix A: Using the odacli Command to Monitor Deployment
# /opt/oracle/dcs/bin/odacli list-jobs
ID Description Created Status

---------------------------------------- --------------------------------- ----------------------------------- ----------
2e84c187-94a5-452d-8775-2d0af69a28e1 Repository Update February 5, 2018 9:13:45 AM MST Success
7a3c15b8-55db-4984-bd07-98ff40f00151 Repository Update February 5, 2018 9:24:50 AM MST Success
ab5f3843-8dcc-4a1b-ba16-39d8a63622fc Repository Update February 5, 2018 9:25:44 AM MST Success
d7653699-5b1a-4842-ac45-78b0bef7d520 Repository Update February 5, 2018 9:26:29 AM MST Success
dd7acb8b-6e7d-4d8d-95fd-4a8bc5da1c2c DcsAgent patching February 5, 2018 9:28:41 AM MST Success
21dd683b-efde-439f-b464-f5d336c34fdb Server Patching February 5, 2018 9:31:56 AM MST Success
51a8f22f-2773-4015-8e74-72ac2a3b11ee Repository Update February 5, 2018 9:43:10 AM MST Success
311120ec-9210-470e-9ead-cbeae4a30f74 Repository Update February 5, 2018 9:45:43 AM MST Success
98929ae8-7e61-4467-875d-8bf5cb971301 Repository Update February 5, 2018 9:48:05 AM MST Success
90045308-6cf3-4a6d-9382-747f70cfe52c Provisioning service creation February 5, 2018 9:50:59 AM MST Success
# /opt/oracle/dcs/bin/odacli describe-job -i 90045308-6cf3-4a6d-9382-747f70cfe52c
Job details
----------------------------------------------------------------
ID: 90045308-6cf3-4a6d-9382-747f70cfe52c
Description: Provisioning service creation
Status: Success
Message:

-------------------------------------------------- ----------------------------------- ----------------------------------- ----------
Checking the ipAddress February 5, 2018 9:51:00 AM MST February 5, 2018 9:51:00 AM MST Success
Setting up Network February 5, 2018 9:51:00 AM MST February 5, 2018 9:51:00 AM MST Success
OS usergroup 'asmdba'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:05 AM MST Success
OS usergroup 'asmoper'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:05 AM MST Success
OS usergroup 'asmadmin'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:05 AM MST Success
OS usergroup 'dba'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:05 AM MST Success
OS usergroup 'dbaoper'creation February 5, 2018 9:51:05 AM MST February 5, 2018 9:51:06 AM MST Success
OS usergroup 'oinstall'creation February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
OS user 'grid'creation February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
OS user 'oracle'creation February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
SSH equivalance setup February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
Grid home creation February 5, 2018 9:51:06 AM MST February 5, 2018 9:53:30 AM MST Success
Creating GI home directories February 5, 2018 9:51:06 AM MST February 5, 2018 9:51:06 AM MST Success
Cloning Gi home February 5, 2018 9:51:06 AM MST February 5, 2018 9:53:27 AM MST Success
Updating GiHome version February 5, 2018 9:53:29 AM MST February 5, 2018 9:53:30 AM MST Success
Storage discovery February 5, 2018 9:53:30 AM MST February 5, 2018 9:58:07 AM MST Success
Grid stack creation February 5, 2018 9:58:07 AM MST February 5, 2018 10:09:58 AM MST Success
Configuring GI February 5, 2018 9:58:07 AM MST February 5, 2018 9:58:11 AM MST Success
Running GI root scripts February 5, 2018 9:58:11 AM MST February 5, 2018 10:05:44 AM MST Success
Running GI config assistants February 5, 2018 10:05:45 AM MST February 5, 2018 10:06:53 AM MST Success
Post cluster OAKD configuration February 5, 2018 10:09:58 AM MST February 5, 2018 10:12:41 AM MST Success
Disk group 'RECO'creation February 5, 2018 10:12:46 AM MST February 5, 2018 10:12:56 AM MST Success
Volume 'datBrmdb'creation February 5, 2018 10:12:56 AM MST February 5, 2018 10:13:21 AM MST Success
Volume 'reco'creation February 5, 2018 10:13:21 AM MST February 5, 2018 10:13:33 AM MST Success
Volume 'commonstore'creation February 5, 2018 10:13:33 AM MST February 5, 2018 10:13:44 AM MST Success
ACFS File system 'DATA'creation February 5, 2018 10:13:44 AM MST February 5, 2018 10:13:52 AM MST Success
ACFS File system 'RECO'creation February 5, 2018 10:13:52 AM MST February 5, 2018 10:14:00 AM MST Success
ACFS File system 'DATA'creation February 5, 2018 10:14:00 AM MST February 5, 2018 10:14:07 AM MST Success
Database home creation February 5, 2018 10:14:07 AM MST February 5, 2018 10:16:24 AM MST Success
Validating dbHome available space February 5, 2018 10:14:07 AM MST February 5, 2018 10:14:07 AM MST Success
Creating DbHome Directory February 5, 2018 10:14:08 AM MST February 5, 2018 10:14:08 AM MST Success
Extract DB clones February 5, 2018 10:14:08 AM MST February 5, 2018 10:15:15 AM MST Success
Clone Db home February 5, 2018 10:15:15 AM MST February 5, 2018 10:16:09 AM MST Success
Enable DB options February 5, 2018 10:16:09 AM MST February 5, 2018 10:16:16 AM MST Success
Run Root DB scripts February 5, 2018 10:16:16 AM MST February 5, 2018 10:16:16 AM MST Success
Provisioning service creation February 5, 2018 10:16:24 AM MST February 5, 2018 10:22:35 AM MST Success
Database Creation February 5, 2018 10:16:24 AM MST February 5, 2018 10:21:25 AM MST Success
Change permission for xdb wallet files February 5, 2018 10:21:25 AM MST February 5, 2018 10:21:25 AM MST Success
Place SnapshotCtrlFile in sharedLoc February 5, 2018 10:21:25 AM MST February 5, 2018 10:21:27 AM MST Success
Running DataPatch February 5, 2018 10:22:23 AM MST February 5, 2018 10:22:35 AM MST Success
updating the Database version February 5, 2018 10:22:35 AM MST February 5, 2018 10:22:35 AM MST Success
users tablespace creation February 5, 2018 10:22:35 AM MST February 5, 2018 10:22:37 AM MST Success
Copies of the checklists are available on the EIS web pages or on the EIS-DVD. We recommend that you always check the web pages for the latest version.
Comments & RFEs are welcome. Oracle staff should mail to EIS-SUPPORT_WW@oracle.com .
Partners should mail to: SUPPORT-PARTNER-QUESTIONS_WW_GRP@oracle.com .

Oda X7 2SM

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oda X7 2SM

Uploaded by

Copyright:

Available Formats

EIS Installation Checklist for the

ORACLE® Database Appliance X7-2S & X7-2M

This EIS installation checklist covers only Bare Metal installations.

Server Type Serial Number

INSTALLATION OVERVIEW– EIS DELIVERABLES

MEMORY DIMM FAULT BEST PRACTICES

Task Comment Check

ILOM SERVICE PROCESSOR CONFIGURATION

Verify that the gateway can be reached:

After setting up the SP, exit. -> exit

CONFIGURING ILOM VIA GUI & ETHERNET CONNECTION

-> show /SP/clock

To synchronise the SP's clock property values with an NTP server:

CONFIGURING THE SP'S CLOCK PROPERTIES VIA GUI

Task Comment Check

SERVER POWER ON & POST

Task Comment Check

BARE METAL CONFIGURATION

Connect to ILOM from the Browser and login as root:

UPLOADING PATCH TO THE SERVER NODE

UPLOADING PATCHES TO NODES FROM USB MEDIA

Apply the update:

This process should take about 3 minutes to complete.

Task Name Start Time End Time Status

Do NOT unzip the other two zip files: p27141226_122120_Linux-x86-64_2of3.zip and

This process should take about 2 minutes to complete.

Task Name Start Time End Time Status

This process should take about 2 minutes to complete.

Task Name Start Time End Time Status

Apply the update on 3rd patch:

This process should take about 2 minutes to complete.

Task Name Start Time End Time Status

Confirm that the update has been successful:

Task Name Start Time End Time Status

Confirm that the update has been successful:

Task Name Start Time End Time Status

Describe-component to make sure all components are up-to-date:

Component Installed Version Available Version

This process should take about 2 minutes to complete.

Task Name Start Time End Time Status

OPTIONAL: DB CLONE FILE TO DEPLOY A 12.1.0.2 DATABASE

Apply the update:

This process should take about 2 minutes to complete.

Task Name Start Time End Time Status

OPTIONAL: DB CLONE FILE TO DEPLOY A 11.2.0.4 DATABASE

Apply the update:

This process should take about 2 minutes to complete.

Task Name Start Time End Time Status

CHANGING THE ODA CPU CORE COUNT

Confirm that the update has been successful:

Task Name Start Time End Time Status

Confirm that the core count is now 12:

Node Cores Modified Job Status

DEPLOYING THE ORACLE DATABASE APPLIANCE

If Yes, the ASR User Name and Password is required.

Then press Submit.

You should see a pop-up with the job ID:

The provisioning process takes approximately 30-45 minutes.

MONITOR DEPLOYMENT PROGRESS

You can also run the odacli command to

Another way to check the status of Example below.

Task Name Start Time End Time Status

Disk Group Information