EIS Installation Checklist For The ORACLE® Database Appliance (ODA) X8-2S & X8-2M

EIS Installation Checklist for the
ORACLE® Database Appliance (ODA) X8-2S & X8-2M
Customer:
TASK Number:
Technician:
Date:
This EIS installation checklist covers only “Limited Software Install”/Bare Metal installations of the
ODA X8-2S/M.
• Be sure to check the EIS web page for the latest versions prior to commencing the
installation.
• The purpose of this checklist is to help the installer achieve a consistent, "good" installation.
• Installers must have attended the appropriate training classes.
◦ EIS checklists are NOT a replacement for proper training.
• 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.
• Do NOT hand this checklist over to the customer.
• Feedback on issues with EIS content or product quality is welcome.
◦ Oracle staff should send email to EIS-SUPPORT_WW_GRP@oracle.com
◦ Partners should contact the Partner Help Portal for assistance and feedback.
Please note the following:

• The ODA X8-2S & X8-2M are single node systems without external storage.
• The ODA X8-2S has a single CPU; the ODA X8-2M has two CPUs and more memory.
• The ODA X8-2S & X8-2M are delivered with the OS pre-installed.
Server Type Serial Number
Oracle Database Appliance X8-2 S/M
Oracle Internal and Approved Partners Only Page 1 of 47 Version 1.4 – Created: 27 Aug 2020
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.
For additional help with ODA deployment, you can send an email to the following mailing list:
global-field-oda-sme-assist_grp@oracle.com
This mailing list is intended for use by Installers/FEs to reach out to other Field resources, who have
been identified as ODA Subject Matter Experts, for help with ODA installs.
Task Comment 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.
Table of Contents: 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 11 15 mins
Bare Metal Configuration 70 mins
Changing the ODA CPU Core Count Error:
Reference
15 mins
source not
found
Deploying the Oracle Database Appliance 30 10 mins
Monitor Deployment Progress 36 20 mins
Post Validation Error:
Reference
15 mins
source not
found
Redeployment if Necessary 43 40 mins
Securing the ILOM Service Processors (SP) 45 10 mins
Handover 45 10 mins
Appendix A: Using the odacli Command to Monitor
46 10 mins
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.
ODA PREPARATION
EIS Site-Audit Report complete? EISdoc V4:
File EIS-SiteAudit-Racked-Item.odt
The ODA X8-8S & X8-8M 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-X8SM.odt
EIS-TPP-Server-ODA-X8SM.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) X8.
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 X8-2S/ODA X8-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).
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 X8-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 Software”. Next to the Release field, in
the drop-down box, select “Oracle Database Appliance Software (ODA) 19.8.0.0.0”.
Click on Search button.
Task Comment Check
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.
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 19.8.0.0.0
• 30403643 – ODA ISO Bare Metal Restore file (4.1 G)

NOTE: Due to bug 30651492 (Internal), it will be necessary to completely re-image the server.
You can NOT just perform an upgrade.
• 30403673 – GI Clone files. This file is required for deployment. (4.9GB)

• 31481816 – Server patch bundle, has two (2) parts. (15.2 GB)
p31481816_198000_Linux-x86-64_1of2.zip 8.7
• p31481816_198000_Linux-x86-64_2of2.zip 6.5
•
Database Clone patches:
• 30403662 – Oracle 19.8.0.0 RDBMS Software Clone file for creating any new
19.8.0.0 database homes. This DB clone file is only required if you are deploying a
19.8.0.0 database. (4.2 GB)
18.11.0.0 database. (5.7 GB)
12.2.0.1 database. (4.5 GB)
• 23494992 – 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. (6.1 GB)
• 23494997 – Oracle 11.2.0.4 RDBMS Software Clone 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. (2.8 GB)
NOTE: We recommend transferring the files directly to the server over a network connection.
Alternatively, if you prefer, you can also use a USB drive to transfer the files. The larger files
(over 4GB) will not transfer to a FAT32 formatted USB drive due to filesystem limitations.
The drive must be formatted with “EXT4” (Linux) or Windows NTFS filesystem.
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”.
Unpack outside data center to ensure no

contamination/dust is released inside
customer's controlled environment.
Collect packing material together for disposal.
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 2RU space is required for either an ODA X8-2S or ODA X8-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 11 (Server
Power on & Post).
When the SP initially boots it will attempt to If DHCP server is available you can connect to the SP
obtain an IP address from a DHCP server. 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 server.
one of the following locations. Record the IP Advanced → BMC Network Configuration → Current
Ipv4 address in BMC
address for future reference:
User = root
• The system BIOS setup screen.
Password = changeme
• Command-line interface – connect to -> show /SP/network
serial port via terminal device (such as
a laptop). 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 When using a laptop start a terminal interface to the
Management Port (SER MGT). serial port that is connected to the ILOM SP.
The default serial port speed is 115200 Previously 9600 baud.

baud with no flow control.
Task Comment Check
Log in to the ILOM SP. User = root

Password = changeme
Set the working directory. -> cd /SP/network
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>
It is also possible to configure ILOM network -> set pendingipdiscovery=static
settings via the system BIOS in the Advanced -> set commitpending=true
-> 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>
name & password. User = root
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
Task Comment Check
If required, the timezone can be changed from GMT (default) to EST or PST8PDT:
-> set /SP/clock timezone=EST5EDT
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>
name & password. User = root
Password = changeme
Select ILOM Administration and then Date You can make desired change and then press the Save
and Time. Select the Timezone tab to button.
display the current timezone information.
Then select the Clock tab to display the You can make desired changes (date, time & optional
current Clock Settings page. 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 to
back down. Observe the POST results. see “BMC Responding”.
If using CLI: gain host console access. From server's SP:

To stop the host console press ESC followed -> start /HOST/console
by ( i.e. opening round bracket. To leave the You could use keyboard, mouse and monitor directly
attached to the server's ports.
secure shell: exit
At the OS login prompt: User root with welcome1 as password.
Task Comment Check
VERIFY PRE-INSTALLED VERSION

To verify the current ODA system version, run the following command:
# cat /opt/oracle/oak/pkgrepos/System/VERSION
version=19.8.0.0.0
Most likely, the version that is installed is not the latest available on MOS. In this case, you
can proceed with the Bare Metal deployment – go to Patches Needed to Deploy ODA (page
17) 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 30403643 (for 19.8.0.0.0).
RE-IMAGING FOR THE BARE METAL CONFIGURATION
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 p30403643_198000_Linux-x86-64.zip
Connect to ILOM from the Browser and login

as root:
Task Comment Check
On Successful login, the Browser will redirect

to the Oracle Integrated Lights out Manager
home page.
Click on the Launch button to continue.
Depending on the state of the system, there may be some message on the console. Click on
KVMS and then Storage as highlighted below:
Task Comment Check
Click on Add, then browser to choose the ISO image as shown below:
Task Comment Check
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 or you are having
issues booting from the ISO image, perform the following steps:
• On the next reset, repeat the above steps.
• But this time, uncheck the SSL Enabled box on this screen and mount the ISO image
again.
• Proceed only after the ISO image successfully mounts.
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:
Task Comment Check
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.
QUICK HARDWARE VERIFICATION
Use the nvmeadm command to verify the presence of all NVMe drives:
# nvmeadm list -v
SUNW-NVME-1
PCI Vendor ID: 0x8086
Serial Number: PHLN902400SC6P4CGN
Model Number: 7361456_ICRPC2DD2ORA6.4T
Firmware Revision: VDV1RL02
Number of Namespaces: 1
SUNW-NVME-2
PCI Vendor ID: 0x8086
Serial Number: BTLN909304NM6P4CGN
Model Number: 7361456_ICRPC2DD2ORA6.4T
Firmware Revision: VDV1RL02
Number of Namespaces: 1
You should see a minimum of two NVMe drives listed. If not, re-seat the drives. If still not
seen, it may need to be replaced. This is an important step, as the deployment will fail if both
drives are not recognized by the system.
By default, the Small and Medium will come with 2 NVMe drives.
Task Comment Check
PATCHES NEEDED TO DEPLOY ODA 19.8.0.0.0

Now you will require the patches previously download on page 6 for deployment:
• p30403673_198000_Linux-x86-64.zip – GI Clone files. * required
• ODA Patch Bundle * required

p31481816_198000_Linux-x86-64_1of2.zip
p31481816_198000_Linux-x86-64_2of2.zip
• p30403662_198000_Linux-x86-64.zip * optional
Oracle 19.8.0.0 RDBMS Software Clone file for creating any new 19.8 database
homes. This DB clone file is only required if you are deploying a 19.8.0.0 database.
homes. This DB clone file is only required if you are deploying an 18.11.0.0 database.
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.
homes. This file is only required if you are deploying a 12.1.0.2 database.
• p23494997_198000_Linux-x86-64.zip *optional
homes. This DB clone file is only required if you are deploying an 11.2.0.4 database.
CONFIGURING THE NETWORK INTERFACE
Task Comment Check
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 includes sample IP addresses for network, netmask and gateway. You
may get different options, other than btbond1/btbond3, depending on what type of network
cards and how many network cards are installed. For the X8-2 systems, breaking the bond is
not an option.
Example output below:
[root@oak ~]# configure-firstnet
Select the Interface to configure the network on (btbond1 btbond2 btbond3 btbond4)
[btbond1]:
WARNING: Interface [btbond1] is not connected correctly, please check the connection
Configure DHCP on btbond1 (yes/no) [no]:

INFO: You have chosen Static configuration
Use VLAN on btbond1 (yes/no) [no]:
Enter the IP address to configure : 10.144.204.116
Enter the Netmask address to configure : 255.255.248.0
Enter the Gateway address to configure[10.144.200.1] :
INFO: Restarting the network
Resetting dcs-agent config file...
generating credentials for dcs-cli and dcs-agent
done generating credentials for dcs-cli and dcs-agent
Zookeeper process exist with id - 8693
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper/bin/../conf/zoo.cfg
Starting zookeeper ... already running as process 8693.
Sleeping for 30 Seconds
ZooKeeper JMX enabled by defaultUsing config:
/opt/zookeeper/bin/../conf/zoo.cfgMode: standalone
ZooKeeper Started properly
Task Comment Check
UPLOADING PATCH TO THE SERVER NODE

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 p31481816_198000_Linux-x86-64_1of2.zip root@<ip of oda>:/u01
# scp p31481816_198000_Linux-x86-64_2of2.zip root@<ip of oda>:/u01
# scp p30403662_198000_Linux-x86-64.zip root@<ip of oda>:/u01
If you have the patches on your laptop, then a good way to transfer the files over is to
configure em1 to attach your laptop directly to the NET0 port.
To configure em1:
# ifconfig em1 10.10.10.1 netmask 255.255.255.0
# ifconfig em1
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.1 netmask 255.255.255.0 broadcast 10.10.10.255
ether 00:10:e0:eb:ec:4c txqueuelen 1000 (Ethernet)
RX packets 17352 bytes 1537513 (1.4 MiB)
RX errors 0 dropped 229 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x9ca00000-9cafffff
On your laptop, you will also need to configure the network port to 10.10.10.2
NOTE: em1 gets unconfigured during deployment, so your direct network connection will get
disconnected shortly after you hit submit.
Now, you can transfer the patches over using winscp, filezilla, etc..
UNPACK AND INSTALL THE GI PATCH
Unzip the patch:
[root@oak u01]# unzip p30403673_198000_Linux-x86-64.zip
Archive: p30403673_198000_Linux-x86-64.zip
extracting: odacli-dcs-19.8.0.0.0-200713-GI-19.8.0.0.zip
inflating: README.txt
Task Comment Check
Apply the update. Example output below:

# odacli update-repository -f /u01/odacli-dcs-19.8.0.0.0-200713-GI-19.8.0.0.zip
{
"jobId" : "56476c5a-2ec4-4b9b-872f-f5b1b9ba2ec7",
"status" : "Created",
"message" : "/u01/odacli-dcs-19.8.0.0.0-200713-GI-19.8.0.0.zip",
"reports" : [ ],
"createTimestamp" : "July 30, 2020 12:33:22 PM PDT",
"resourceList" : [ ],
"description" : "Repository Update",
"updatedTime" : "July 30, 2020 12:33:22 PM PDT"
}
Confirm that the update has been successful:

[root@oak u01]# odacli describe-job -i "56476c5a-2ec4-4b9b-872f-f5b1b9ba2ec7"
Job details
----------------------------------------------------------------
ID: 56476c5a-2ec4-4b9b-872f-f5b1b9ba2ec7
Description: Repository Update
Status: Success
Created: July 30, 2020 12:33:22 PM PDT
Message: /u01/odacli-dcs-19.8.0.0.0-200713-GI-19.8.0.0.zip
Task Name Start Time End Time Status

---------------------------------------- -----------------
Delete the unneeded files to free up space for unpacking other patches:
[root@oak u01]# rm p30403673_198000_Linux-x86-64.zip
rm: remove regular file ‘p30403673_198000_Linux-x86-64.zip’? y
[root@oak u01]# rm README.txt
rm: remove regular file ‘README.txt’? y
UNPACK AND INSTALL THE SERVER PATCH

Unzip all 4 parts to the patch:
[root@oak u01]# unzip p31481816_198000_Linux-x86-64_1of2.zip
Archive: p31481816_198000_Linux-x86-64_1of2.zip
extracting: oda-sm-19.8.0.0.0-200718-server1of2.zip
[root@oak u01]# unzip p31481816_198000_Linux-x86-64_2of2.zip

Archive: p31481816_198000_Linux-x86-64_2of2.zip
extracting: oda-sm-19.8.0.0.0-200718-server2of2.zip
Apply the update.

The server patch can be applied individually or all in one command set.
Below is the command sequence to do them all at once (command wraps):
[root@oak u01]# odacli update-repository -f /u01/oda-sm-19.8.0.0.0-200718-
Task Comment Check
server1of2.zip,/u01/oda-sm-19.8.0.0.0-200718-server2of2.zip
{
"jobId" : "076e19a4-cd1a-49a5-a4b7-d26627eb04fd",
"message" : "/u01/oda-sm-19.8.0.0.0-200718-server1of2.zip,/u01/oda-sm-19.8.0.0.0-
200718-server2of2.zip",
"reports" : [ ],
}
NOTE: If this command set fails for any reason, you will need to apply each zip file
individually. Proceed to the steps below.
[root@oak u01]# odacli describe-job -i "076e19a4-cd1a-49a5-a4b7-d26627eb04fd"
Job details
----------------------------------------------------------------
ID: 076e19a4-cd1a-49a5-a4b7-d26627eb04fd
Status: Success
Message: /u01/oda-sm-19.8.0.0.0-200718-server1of2.zip,/u01/oda-sm-
19.8.0.0.0-200718-server2of2.zip

---------------------------------------- -----------------------------------
[root@oak u01]# rm p31481816_198000_Linux-x86-64_1of2.zip
rm: remove regular file ‘p31481816_198000_Linux-x86-64_1of2.zip’? y
[root@oak u01]# rm p31481816_198000_Linux-x86-64_2of2.zip
rm: remove regular file ‘p31481816_198000_Linux-x86-64_2of2.zip’? y
UPDATING STORAGE AND SERVER COMPONENTS
Task Comment Check
Update server components:

[root@oak u01]# odacli update-server -v 19.8.0.0.0
{
"jobId" : "9f8f0c94-cd75-4d6a-990b-7fc6d39987d9",
"message" : "Success of server update will trigger reboot of the node after 4-5
minutes. Please wait until the node reboots.",
"reports" : [ ],
"description" : "Server Patching",
}
Confirm that the update has been successful.

During the ilom update, the server will reset, including the ilom. After the reboot, you can
check to make sure the update-server job has completed successfully.
[root@oak ~]# odacli describe-job -i 9f8f0c94-cd75-4d6a-990b-7fc6d39987d9
Job details
----------------------------------------------------------------
ID: 9f8f0c94-cd75-4d6a-990b-7fc6d39987d9
Description: Server Patching
Status: Success
Message:

---------------------------------------- -----------------------------------
Patch location validation July 30, 2020 12:51:40 PM PDT July
30, 2020 12:51:40 PM PDT Success
dcs-controller upgrade July 30, 2020 12:51:40 PM PDT July
30, 2020 12:51:40 PM PDT Success
30, 2020 12:51:40 PM PDT Success
dcs-cli upgrade July 30, 2020 12:51:40 PM PDT July
30, 2020 12:51:40 PM PDT Success
Creating repositories using yum July 30, 2020 12:51:40 PM PDT July
30, 2020 12:51:42 PM PDT Success
Updating YumPluginVersionLock rpm July 30, 2020 12:51:42 PM PDT July
30, 2020 12:51:42 PM PDT Success
Applying OS Patches July 30, 2020 12:51:42 PM PDT July
30, 2020 12:51:43 PM PDT Success
Applying Firmware Disk Patches July 30, 2020 12:51:43 PM PDT July
30, 2020 12:51:46 PM PDT Success
Applying Firmware Expander Patches July 30, 2020 12:51:46 PM PDT July
30, 2020 12:51:55 PM PDT Success
Applying Firmware Controller Patches July 30, 2020 12:51:55 PM PDT July
30, 2020 12:52:14 PM PDT Success
Checking Ilom patch Version July 30, 2020 12:52:15 PM PDT July
30, 2020 12:52:17 PM PDT Success
30, 2020 12:52:18 PM PDT Success
Save password in Wallet July 30, 2020 12:52:19 PM PDT July
30, 2020 12:52:19 PM PDT Success
Apply Ilom patch July 30, 2020 12:52:19 PM PDT July
30, 2020 1:00:27 PM PDT Success
Task Comment Check
Copying Flash Bios to Temp location July 30, 2020 1:00:27 PM PDT July
30, 2020 1:00:27 PM PDT Success
Update System version July 30, 2020 1:00:27 PM PDT July
30, 2020 1:00:27 PM PDT Success
preRebootNode Actions July 30, 2020 1:00:27 PM PDT July
30, 2020 1:00:27 PM PDT Success
Reboot Ilom July 30, 2020 1:00:27 PM PDT July
30, 2020 1:00:27 PM PDT Success
Update storage components:

[root@oak ~]# odacli update-storage -v 19.8.0.0.0
{
"jobId" : "b5f45379-bab2-4353-a931-b419bf9b887e",
"message" : "Success of Storage Update may trigger reboot of node after 4-5
minutes. Please wait till node restart",
"reports" : [ ],
"description" : "Storage Firmware Patching",
}
Confirm that the update has been successful.

The server may reboot, depending on which components get updated. Wait until after the
reboot to confirm the update has been successful.
[root@oak ~]# odacli describe-job -i b5f45379-bab2-4353-a931-b419bf9b887e
Job details
----------------------------------------------------------------
ID: b5f45379-bab2-4353-a931-b419bf9b887e
Description: Storage Firmware Patching
Status: Success
Message:
Task Name Start Time End

Time Status
---------------------------------------- -----------------------------------
----------------------------------- ----------
Applying Firmware Disk Patches July 30, 2020 1:12:10 PM PDT July
30, 2020 1:12:19 PM PDT Success
Applying Firmware Controller Patches July 30, 2020 1:12:19 PM PDT July
30, 2020 1:15:42 PM PDT Success
preRebootNode Actions July 30, 2020 1:15:42 PM PDT July
30, 2020 1:15:42 PM PDT Success
Reboot Ilom July 30, 2020 1:15:42 PM PDT July
30, 2020 1:15:42 PM PDT Success
Task Comment Check
Describe-component to make sure all components are up-to-date:

[root@oak ~]# odacli describe-component
System Version
---------------
19.8.0.0.0
Component Installed Version Available Version

---------------------------------------- -------------------- --------------------
OAK 19.8.0.0.0 up-to-date
DCSAGENT 19.8.0.0.0 up-to-date
ILOM 4.0.4.51.r134837 up-to-date
BIOS 52021300 up-to-date
OS 7.8 up-to-date
FIRMWARECONTROLLER VDV1RL04 up-to-date
FIRMWAREDISK 1102 up-to-date
HMP 2.4.5.0.1 up-to-date
Task Comment Check
OVERVIEW OF OPTIONAL DATABASE VERSIONS & REQUIRED
PATCHES
NOTE: This section will go through installing the patch for all 5 database versions, but not all
are required. Most customers will only use one database version.
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:
• p30403662_198000_Linux-x86-64.zip – Oracle 19.8.0.0 RDBMS Software Clone file
for creating any new 19.8.0.0 database homes.
for creating any new 18.11.0.0 database homes. This DB clone file is only required if
you are deploying a 18.11.0.0 database.
for creating any new 12.2.0.1 database homes.
for creating any new 12.1 database homes.
for creating any new 11.2 database homes.
OPTIONAL: DB CLONE FILE TO DEPLOY A 19.8.0.0 DATABASE
Unpack the DB clone file for deploying an 19.8.0.0 database.
extracting: odacli-dcs-19.8.0.0.0-200713-DB-19.8.0.0.zip
Apply the update.
[root@oak u01]# odacli update-repository -f /u01/odacli-dcs-19.8.0.0.0-200713-DB-
19.8.0.0.zip
{
"jobId" : "9dd012cd-f401-45ba-9770-d9c0aaf25f78",
"message" : "/u01/odacli-dcs-19.8.0.0.0-200713-DB-19.8.0.0.zip",
"reports" : [ ],
}
Confirm that the repository update has been successful:
[root@oak u01]# odacli describe-job -i "9dd012cd-f401-45ba-9770-d9c0aaf25f78"
Job details
----------------------------------------------------------------
ID: 9dd012cd-f401-45ba-9770-d9c0aaf25f78
Status: Success
Message: /u01/odacli-dcs-19.8.0.0.0-200713-DB-19.8.0.0.zip

---------------------------------------- -----------------------------------
Task Comment Check
Unpack the DB clone file for deploying an 18.11.0.0 database.
Apply the update.
18.11.0.0.zip
{
"jobId" : "a079b631-e9cd-4800-9f66-21ea7e72071f",
"reports" : [ ],
}
Confirm that the repository update has been successful:
[root@oak u01]# odacli describe-job -i "a079b631-e9cd-4800-9f66-21ea7e72071f"
Job details
----------------------------------------------------------------
ID: a079b631-e9cd-4800-9f66-21ea7e72071f
Status: Success

---------------------------------------- -----------------------------------
Task Comment Check

Unpack the DB clone file for deploying a 12.2.0.1 database.
Apply the update:

12.2.0.1.zip
{
"jobId" : "e01706b9-2e3f-463a-9aac-953978a9d207",
"reports" : [ ],
}
Confirm that the respository update has been successful:

[root@oak u01]# odacli describe-job -i "e01706b9-2e3f-463a-9aac-953978a9d207"
Job details
----------------------------------------------------------------
ID: e01706b9-2e3f-463a-9aac-953978a9d207
Status: Success

---------------------------------------- ----------------------------------- -------
Task Comment Check

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" : "0bd22124-4b81-4e38-9fa9-1ce12f1a65b3",
"reports" : [ ],
}
Confirm the job was successful, using the JobId from previous command’s output:
[root@oak u01]# odacli describe-job -i "0bd22124-4b81-4e38-9fa9-1ce12f1a65b3"
Job details
----------------------------------------------------------------
ID: 0bd22124-4b81-4e38-9fa9-1ce12f1a65b3
Status: Success

---------------------------------------- ----------------------------------- ------
Task Comment Check

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

11.2.0.4.zip
{
"jobId" : "0b777c00-db00-4068-b64d-efeda50be9cb",
"reports" : [ ],
}
Confirm the job was successful, using the JobId from previous command’s output:
[root@oak u01]# odacli describe-job -i "0b777c00-db00-4068-b64d-efeda50be9cb"
Job details
----------------------------------------------------------------
ID: 0b777c00-db00-4068-b64d-efeda50be9cb
Status: Success

------------------------ -------------------------- -------------------------
Delete the unneeded files to free up space for unpacking other patches and deployment:
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-node>:7093/mgmt/index.html
• The first screen will ask you to change the password for the oda-admin user.
After you have changed the password and click on Submit, the login screen will appear. User
name is oda-admin.
NOTE: If the login fails due to an authentication issue, make sure that network between the
ODA and the installer’s laptop has ports 7070 and 7093 open. Unless these ports are opened
up, you will continue to get authentication errors and will not be able to login until the
customer opens up these ports.
If opening up these ports is not an option, you can connect directly to the ODA by configuring
em1 up and using your laptop to connect directly.
Task Comment Check
If you're not able to have access to the client's network, then a good workaround is to
configure em1 to attach your laptop directly to the NET0 port.
To configure em1:
# ifconfig em1 10.10.10.1 netmask 255.255.255.0
# ifconfig em1
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.1 netmask 255.255.255.0 broadcast 10.10.10.255
ether 00:10:e0:eb:ec:4c txqueuelen 1000 (Ethernet)
RX packets 17352 bytes 1537513 (1.4 MiB)
RX errors 0 dropped 229 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x9ca00000-9cafffff
On your laptop, you will also need to configure the network port to 10.10.10.2
• NOTE: em1 gets unconfigured during deployment, so your direct network connection
will get disconnected shortly after you hit submit.
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. You will see that the network information is auto-populated. This is information input
during “configure-firstnet”.
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.
Selecting Yes for Create Initial Database will require you to complete 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.
Task Comment Check
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. Make sure this is the customer’s
username/password.
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.
It is a good idea to first Save Configuration, so that you have it in case you need to redeploy.
Then press Submit.

Select Yes in the pop-up confirmation
window:
Task Comment Check
After clicking “Yes”, you will see this screenshot on the bottom left hand corner, and then
eventually give you the job ID screen in the next screenshot.
Also, you can get the job ID number with this command: (NOTE: Output edited for size)
[root@oak u01]# odacli list-jobs
ID Description
Created Status
----------------------------------------
---------------------------------------------------------------------------
----------------------------------- ----------
56476c5a-2ec4-4b9b-872f-f5b1b9ba2ec7 Repository Update
July 30, 2020 1:33:22 PM MDT Success
076e19a4-cd1a-49a5-a4b7-d26627eb04fd Repository Update
9f8f0c94-cd75-4d6a-990b-7fc6d39987d9 Server Patching
b5f45379-bab2-4353-a931-b419bf9b887e Storage Firmware Patching
9dd012cd-f401-45ba-9770-d9c0aaf25f78 Repository Update
a079b631-e9cd-4800-9f66-21ea7e72071f Repository Update
e01706b9-2e3f-463a-9aac-953978a9d207 Repository Update
0bd22124-4b81-4e38-9fa9-1ce12f1a65b3 Repository Update
ac6cc8a0-677a-4cd0-a9c3-ee39660a5897 Repository Update
0b777c00-db00-4068-b64d-efeda50be9cb Repository Update
7e31dad1-9325-458c-9e87-a57a72c0f5da Provisioning service creation
July 30, 2020 2:37:15 PM MDT Running
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 in
# tail -f /opt/oracle/dcs/log/dcs- the dcs-agent.log file.
agent.log
You can also run the odacli command to

monitor/check status. For an example, refer to
Appendix A on page 46 of this checklist.
Using the web configurator, you can check on the status. Example below.
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 snippet shown, you can see the job is still
command. in “Running” status. This will change to “Success”
when the job is complete.
[root@oak u01]# odacli describe-job -i 7e31dad1-9325-458c-9e87-a57a72c0f5da
Job details
----------------------------------------------------------------
ID: 7e31dad1-9325-458c-9e87-a57a72c0f5da
Description: Provisioning service creation
Status: Running
Created: July 30, 2020 2:37:15 PM MDT
Message:

Time Status
---------------------------------------- -----------------------------------
----------------------------------- ----------
network update July 30, 2020 2:37:16 PM MDT July
30, 2020 2:37:23 PM MDT Success
updating network July 30, 2020 2:37:16 PM MDT July
30, 2020 2:37:23 PM MDT Success
Setting up Network July 30, 2020 2:37:16 PM MDT July
30, 2020 2:37:16 PM MDT Success
OS usergroup 'asmdba'creation July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
OS usergroup 'asmoper'creation July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
OS usergroup 'asmadmin'creation July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
OS usergroup 'dba'creation July 30, 2020 2:37:23 PM MDT July
Task Comment Check
30, 2020 2:37:23 PM MDT Success
OS usergroup 'dbaoper'creation July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
OS usergroup 'oinstall'creation July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
OS user 'grid'creation July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
OS user 'oracle'creation July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
Default backup policy creation July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
Backup config metadata persist July 30, 2020 2:37:23 PM MDT July
30, 2020 2:37:23 PM MDT Success
SSH equivalance setup July 30, 2020 2:37:24 PM MDT July
30, 2020 2:37:24 PM MDT Success
Grid home creation July 30, 2020 2:37:24 PM MDT July
30, 2020 2:39:48 PM MDT Success
Creating GI home directories July 30, 2020 2:37:24 PM MDT July
30, 2020 2:37:24 PM MDT Success
Cloning Gi home July 30, 2020 2:37:24 PM MDT July
30, 2020 2:39:45 PM MDT Success
Updating GiHome version July 30, 2020 2:39:45 PM MDT July
30, 2020 2:39:48 PM MDT Success
Storage discovery July 30, 2020 2:39:48 PM MDT July
30, 2020 2:39:48 PM MDT Running
When successfully completed, you will see the Status change to “Success”
# odacli describe-job -i 7e31dad1-9325-458c-9e87-a57a72c0f5da
Job details
----------------------------------------------------------------
ID: 7e31dad1-9325-458c-9e87-a57a72c0f5da
Description: Provisioning service creation
Status: Success
Message:

Time Status
---------------------------------------- -----------------------------------
----------------------------------- ----------
network update July 30, 2020 1:37:16 PM MDT July
30, 2020 1:37:23 PM MDT Success
updating network July 30, 2020 1:37:16 PM MDT July
30, 2020 1:37:23 PM MDT Success
Setting up Network July 30, 2020 1:37:16 PM MDT July
30, 2020 1:37:16 PM MDT Success
OS usergroup 'asmdba'creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
OS usergroup 'asmoper'creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
OS usergroup 'asmadmin'creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
OS usergroup 'dba'creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
OS usergroup 'dbaoper'creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
OS usergroup 'oinstall'creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
Task Comment Check
OS user 'grid'creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
OS user 'oracle'creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
Default backup policy creation July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
Backup config metadata persist July 30, 2020 1:37:23 PM MDT July
30, 2020 1:37:23 PM MDT Success
SSH equivalance setup July 30, 2020 1:37:24 PM MDT July
30, 2020 1:37:24 PM MDT Success
Grid home creation July 30, 2020 1:37:24 PM MDT July
30, 2020 1:39:48 PM MDT Success
Creating GI home directories July 30, 2020 1:37:24 PM MDT July
30, 2020 1:37:24 PM MDT Success
Cloning Gi home July 30, 2020 1:37:24 PM MDT July
30, 2020 1:39:45 PM MDT Success
Updating GiHome version July 30, 2020 1:39:45 PM MDT July
30, 2020 1:39:48 PM MDT Success
Storage discovery July 30, 2020 1:39:48 PM MDT July
30, 2020 1:44:19 PM MDT Success
Grid stack creation July 30, 2020 1:44:19 PM MDT July
30, 2020 1:54:49 PM MDT Success
Configuring GI July 30, 2020 1:44:19 PM MDT July
30, 2020 1:44:52 PM MDT Success
Running GI root scripts July 30, 2020 1:44:52 PM MDT July
30, 2020 1:50:53 PM MDT Success
Running GI config assistants July 30, 2020 1:50:54 PM MDT July
30, 2020 1:51:31 PM MDT Success
Post cluster OAKD configuration July 30, 2020 1:54:49 PM MDT July
30, 2020 1:58:02 PM MDT Success
Disk group 'RECO'creation July 30, 2020 1:58:11 PM MDT July
30, 2020 1:58:23 PM MDT Success
Register Scan and Vips to Public Network July 30, 2020 1:58:23 PM MDT July
30, 2020 1:58:25 PM MDT Success
Volume 'commonstore'creation July 30, 2020 1:58:25 PM MDT July
30, 2020 1:58:58 PM MDT Success
ACFS File system 'DATA'creation July 30, 2020 1:58:58 PM MDT July
30, 2020 1:59:14 PM MDT Success
Database home creation July 30, 2020 1:59:14 PM MDT July
30, 2020 2:01:35 PM MDT Success
Validating dbHome available space July 30, 2020 1:59:14 PM MDT July
30, 2020 1:59:14 PM MDT Success
Creating DbHome Directory July 30, 2020 1:59:14 PM MDT July
30, 2020 1:59:14 PM MDT Success
Extract DB clones July 30, 2020 1:59:14 PM MDT July
30, 2020 2:00:31 PM MDT Success
Clone Db home July 30, 2020 2:00:31 PM MDT July
30, 2020 2:01:17 PM MDT Success
Enable DB options July 30, 2020 2:01:17 PM MDT July
30, 2020 2:01:32 PM MDT Success
Run Root DB scripts July 30, 2020 2:01:32 PM MDT July
30, 2020 2:01:32 PM MDT Success
Provisioning service creation July 30, 2020 2:01:35 PM MDT July
30, 2020 2:10:50 PM MDT Success
Database Creation July 30, 2020 2:01:35 PM MDT July
30, 2020 2:09:07 PM MDT Success
Change permission for xdb wallet files July 30, 2020 2:09:07 PM MDT July
30, 2020 2:09:07 PM MDT Success
Place SnapshotCtrlFile in sharedLoc July 30, 2020 2:09:07 PM MDT July
30, 2020 2:09:09 PM MDT Success
SqlPatch upgrade July 30, 2020 2:10:36 PM MDT July
Task Comment Check
30, 2020 2:10:44 PM MDT Success
Running dbms_stats init_package July 30, 2020 2:10:44 PM MDT July
30, 2020 2:10:47 PM MDT Success
updating the Database version July 30, 2020 2:10:47 PM MDT July
30, 2020 2:10:50 PM MDT Success
users tablespace creation July 30, 2020 2:10:50 PM MDT July
30, 2020 2:10:55 PM MDT Success
Clear all listeners from Databse {435ed502-abcc-4f7a-a0b6-239e19213277} July 30,
2020 2:10:55 PM MDT July 30, 2020 2:10:56 PM MDT Success
Clear local and remote listeners from Databse July 30, 2020 2:11:00 PM MDT
Install oracle-ahf July 30, 2020 2:11:02 PM MDT July
30, 2020 2:12:03 PM MDT Success
Provisioning service creation July 30, 2020 2:12:03 PM MDT July
30, 2020 2:12:03 PM MDT Success
persist new agent state entry July 30, 2020 2:12:03 PM MDT July
30, 2020 2:12:03 PM MDT Success
persist new agent state entry July 30, 2020 2:12:03 PM MDT July
30, 2020 2:12:03 PM MDT Success
Restart Zookeeper and DCS Agent July 30, 2020 2:12:03 PM MDT July
30, 2020 2:12:03 PM MDT Success
Task Comment Check
CHANGING THE ODA CPU CORE COUNT

The ODA is delivered with all cores on the server enabled. For the ODA X8-2S, 16 cores are enabled
by default. For the ODA X8-2M, 32 cores are enabled by default.
This section is only required if the customer needs to limit the cpucores due to licensing.
Set the cores in multiples of 2 (e.g. 12, from an X8-2M):
# odacli update-cpucore --cores 12
{
"jobId" : "9bbadc05-db00-49e9-802f-677936657ac2",
"message" : null,
"reports" : [ ],
"createTimestamp" : "July 31, 2020 11:35:53 AM MDT",
"description" : "CPU cores service update",
"updatedTime" : "July 31, 2020 11:35:53 AM MDT"
}

# odacli describe-job -i "9bbadc05-db00-49e9-802f-677936657ac2"
Job details
----------------------------------------------------------------
ID: 9bbadc05-db00-49e9-802f-677936657ac2
Description: CPU cores service update
Status: Success
Created: July 31, 2020 11:35:53 AM MDT
Message:

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

# odacli describe-cpucore
Node Cores Modified Job Status

----- ------ ------------------------------ ---------------
0 12 July 31, 2020 11:35:54 AM MDT Configured
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 odacli.
with the command: odacli describe-system The results should look similar to the output below:
# odacli describe-system
Appliance Information
----------------------------------------------------------------
ID: 45a12be9-126f-4c3c-806c-0e9b020659fb
Platform: X8-2M
Data Disk Count: 2
CPU Core Count: 12
Task Comment Check
System Information
----------------------------------------------------------------
Name: odax8-2m-a
Domain Name: us.oracle.com
Time Zone: America/Denver
DB Edition: EE
DNS Servers: 206.223.27.1 206.223.27.2
NTP Servers: 10.236.0.1 10.236.0.2
Disk Group Information

----------------------------------------------------------------
DG Name Redundancy Percentage
------------------------- ------------------------- ------------
Data Normal 80
Reco Normal 20
If ASR was configured as part of the deployment this can be tested with the command,
odacli test-asr
Examples in the below steps.
If ASR has been configured, start the “Test ASR” routine and obtain the job ID.
[root@oak opt]# /opt/oracle/dcs/bin/odacli test-asr
Job details
----------------------------------------------------------------
ID: 832f32e4-27a9-47e7-a7ae-111cfdf4414e
Description: Test ASR
Status: Created
Message:

--------------- ---------------------------- ---------------------------- -------
Task Comment Check
Check the status of the job ID.

[root@oak opt]# /opt/oracle/dcs/bin/odacli describe-job -i 832f32e4-27a9-47e7-a7ae-
111cfdf4414e
Job details
----------------------------------------------------------------
ID: 832f32e4-27a9-47e7-a7ae-111cfdf4414e
Description: Test ASR
Status: Success
Message:

--------------- ---------------------------- ---------------------------- -------
Test ASR July 23, 2018 5:55:53 PM MDT July 23, 2018 5:55:54 PM MDT Success
If you need to redeploy for any reason, proceed to the section Redeployment if Necessary on
page 43.
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
[root@oak onecmd]# /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_17:56:59_Jul_23.log
/u01/app/12.2.0.1/grid/bin/crsctl.bin
/u01/app/12.2.0.1/grid/.patch_storage/27464465_Mar_31_2018_05_33_42/files/bin/
crsctl.bin
Executing </u01/app/12.2.0.1/grid/tfa/odaX8-2m-brm06-a/tfa_home/bin/uninstalltfa.sh
-silent>
TFA will be uninstalled on node odaX8-2m-brm06-a :
Removing TFA from odaX8-2m-brm06-a...
Stopping TFA Support Tools...
Stopping TFA in odaX8-2m-brm06-a...
Shutting down TFA

oracle-tfa stop/waiting
This will reboot the server. You do not have to reapply the patches after running the cleanup
script, simply login to the web console again (the password has been reset back to welcome1),
and redeploy after filling in all the fields.
After the reboot, you can confirm that the Example below.
previous configuration has been erased.
[root@oak ~]# odacli describe-system
DCS-10032:Resource sysInstance is not found.
Appliance is not configured. <<<< Confirmation that the previous config is erased.
You will also need to reconfigure the public network with configure-firstnet:
[root@oak ~]# configure-firstnet
Now, you can use the web browser to re- Make sure you exit from the web browser completely,
provision the ODA. then open it back up and restart the deployment.
If you are now satisfied with the deployment proceed to SECURING THE ILOM SERVICE
PROCESSOR (SP) on page 45 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 X8-2S/M is
COMPLETE.
Appendix A: Using the odacli Command to Monitor Deployment
# odacli list-jobs
ID Description Created Status

---------------------------------------- --------------------------------
56476c5a-2ec4-4b9b-872f-f5b1b9ba2ec7 Repository Update
076e19a4-cd1a-49a5-a4b7-d26627eb04fd Repository Update
9f8f0c94-cd75-4d6a-990b-7fc6d39987d9 Server Patching
b5f45379-bab2-4353-a931-b419bf9b887e Storage Firmware Patching
9dd012cd-f401-45ba-9770-d9c0aaf25f78 Repository Update
a079b631-e9cd-4800-9f66-21ea7e72071f Repository Update
e01706b9-2e3f-463a-9aac-953978a9d207 Repository Update
0bd22124-4b81-4e38-9fa9-1ce12f1a65b3 Repository Update
ac6cc8a0-677a-4cd0-a9c3-ee39660a5897 Repository Update
0b777c00-db00-4068-b64d-efeda50be9cb Repository Update
7e31dad1-9325-458c-9e87-a57a72c0f5da Provisioning service creation
ebd2a5b5-9c44-4f79-8165-e65204a670b8 Agent State Update Job
65213926-e117-4f75-84ac-78ac44372016 log file cleanup
July 31, 2020 3:00:03 AM MDT Success
9bbadc05-db00-49e9-802f-677936657ac2 CPU cores service update
July 31, 2020 11:35:53 AM MDT Success
# odacli describe-component
System Version
---------------
19.8.0.0.0
Component Installed Version Available Version

---------------------------------------- -------------------- --------------------
OAK 19.8.0.0.0 up-to-date
GI 19.8.0.0.200714 up-to-date
DB 19.8.0.0.200714 up-to-date
DCSAGENT 19.8.0.0.0 up-to-date
ILOM 4.0.4.51.r134837 up-to-date
BIOS 52021300 up-to-date
OS 7.8 up-to-date
FIRMWARECONTROLLER VDV1RL04 up-to-date
FIRMWAREDISK 1102 up-to-date
ASR 20.1.0 up-to-date
HMP 2.4.5.0.1 up-to-date
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 welcome. Oracle staff should mail to EIS-SUPPORT_WW_GRP@oracle.com

Partners should contact the PartnerHelp Portal for assistance and feedback.

EIS Installation Checklist For The ORACLE® Database Appliance (ODA) X8-2S & X8-2M

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

EIS Installation Checklist For The ORACLE® Database Appliance (ODA) X8-2S & X8-2M

Uploaded by

Copyright:

Available Formats

EIS Installation Checklist for the

ORACLE® Database Appliance (ODA) X8-2S & X8-2M

Please note the following:

Server Type Serial Number

Oracle Database Appliance X8-2 S/M

Task Comment Check

INSTALLATION OVERVIEW– EIS DELIVERABLES

MEMORY DIMM FAULT BEST PRACTICES

Click on Search button.

• 30403643 – ODA ISO Bare Metal Restore file (4.1 G)

• 30403673 – GI Clone files. This file is required for deployment. (4.9GB)

Unpack outside data center to ensure no

Task Comment Check

ILOM SERVICE PROCESSOR CONFIGURATION

The default serial port speed is 115200 Previously 9600 baud.

Log in to the ILOM SP. User = root

Verify that the gateway can be reached:

After setting up the SP, exit. -> exit

CONFIGURING ILOM VIA GUI & ETHERNET CONNECTION

To manually set the ILOM clock property values:

-> show /SP/clock

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

CONFIGURING THE SP'S CLOCK PROPERTIES VIA GUI

SERVER POWER ON & POST

If using CLI: gain host console access. From server's SP:

Task Comment Check

VERIFY PRE-INSTALLED VERSION

Connect to ILOM from the Browser and login

On Successful login, the Browser will redirect

PATCHES NEEDED TO DEPLOY ODA 19.8.0.0.0

• p30403673_198000_Linux-x86-64.zip – GI Clone files. * required

• ODA Patch Bundle * required

CONFIGURING THE NETWORK INTERFACE

Configure DHCP on btbond1 (yes/no) [no]:

UPLOADING PATCH TO THE SERVER NODE

Apply the update. Example output below:

Confirm that the update has been successful:

Task Name Start Time End Time Status

UNPACK AND INSTALL THE SERVER PATCH

[root@oak u01]# unzip p31481816_198000_Linux-x86-64_2of2.zip

Apply the update.

Task Name Start Time End Time Status

UPDATING STORAGE AND SERVER COMPONENTS

Update server components:

Confirm that the update has been successful.

[root@oak ~]# odacli describe-job -i 9f8f0c94-cd75-4d6a-990b-7fc6d39987d9

Task Name Start Time End Time Status

Update storage components:

Confirm that the update has been successful.

[root@oak ~]# odacli describe-job -i b5f45379-bab2-4353-a931-b419bf9b887e

Task Name Start Time End

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

Component Installed Version Available Version

Task Name Start Time End Time Status

Task Name Start Time End Time Status

OPTIONAL: DB CLONE FILE TO DEPLOY A 12.2.0.1 DATABASE

Apply the update:

Confirm that the respository update has been successful:

Task Name Start Time End Time Status

OPTIONAL: DB CLONE FILE TO DEPLOY A 12.1.0.2 DATABASE

Apply the update:

Task Name Start Time End Time Status

OPTIONAL: DB CLONE FILE TO DEPLOY A 11.2.0.4 DATABASE