Introduction

You can manage entire Oracle Database Appliance stack using oakcli command-line interface. There are several options available using oakcli, you can use the “oakcli -h” to list the options that you can use to manage ODA. Validating an ODA is an important task for ODA administrator.

[root@odanode1 ~]# oakcli -h
Usage: oakcli show       – Shows disk, diskgroup, expander, controller, server, processor, memory, power, cooling, network, enclosure, storage, version, fs, raidsyncstatus, dbhomes, dbstorage, databases, db_config_params, core_config_key, env_hw, ASR
        oakcli configure – Configures the Network or ASR or additional Net
        oakcli apply      – Applies the core_config_key
        oakcli locate     – Locates a disk
        oakcli deploy     – Deploys the Database Appliance
        oakcli update     – Updates the Database Appliance
        oakcli validate   – Validates the Database Appliance
        oakcli manage     – Manages the OAK repository, diagcollect etc.,
        oakcli unpack     – Unpack the given package to OAK repository
        oakcli copy       – Copies the deployment config file
        oakcli upgrade    – Upgrades database
        oakcli stordiag   – Run storage diagnostic tool on both Nodes
        oakcli test       – Test ASR
        oakcli orachk     – Performs configuration settings check on ODA
        oakcli create     – Creates Database, DB storage, snapshotdb, dbhome, db_config_params file
        oakcli delete     – Deletes Database, DB storage, dbhome, db_config_params file
        oakcli modify     – Performs modify opeartions on Database
        oakcli resize     – Resizes DB storage

In this article we will focus on validating ODA using “oakcli validate” command.

To check if the ODA is Bare Metal or Virtual Platform setup, execute the following command:

[root@odanode1 ~]# oakcli show env_hw
BM ODA X4-2
Public interface : COPPER

To check the ODA software and its components versions, execute the following command:

[root@odanode1 ~]# /opt/oracle/oak/bin/oakcli show version -detail
Reading the metadata. It takes a while…
System Version Component Name            Installed Version         Supported Version
————– —————           ——————        —————–
12.1.2.10.0
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  0018                      Up-to-date
                SSD_SHARED                944A                      Up-to-date
                HDD_LOCAL                 A72A                      Up-to-date
                HDD_SHARED                A72A                      Up-to-date
                ILOM                      3.2.8.25 r114493          Up-to-date
                BIOS                      25040100                  Up-to-date
                IPMI                      1.8.12.4                  Up-to-date
                HMP                       2.3.5.2.8                 Up-to-date
                OAK                       12.1.2.10.0               Up-to-date
                OL                        6.8                       Up-to-date
                GI_HOME                   12.1.0.2.170117(2473      Up-to-date
                                          2082,24828633)
                DB_HOME                   12.1.0.2.170117(2473      Up-to-date
                                          2082,24828633)

To check the Oracle Homes and their versions, execute the following command:

[root@odanode1 ~]# oakcli show dbhomes -detail
Oracle HomeName       Oracle Home Version                  Oracle HomeLocation                                 Database Name    Database Type
—————-      ———————                —————————————             ————— ———–
OraDb12102_home1      12.1.0.2.170117(24732082,24828633)   /u01/app/oracle/product/12.1.0.2/dbhome_1           xyz12c           RAC

Validate Oracle Databsae Appliance

To list options available with “oakcli valiadate”, execute the following command:

[root@odanode1 ~]# oakcli validate -h
Usage:
oakcli validate [-V | -l | -h]
oakcli validate [-v] [-f absolute output_file_name] [-a | -d | -c check1[,check2] [-ver <patch version>] <-prechecks|-postchecks>]
        ARGUMENTS:
                -v      verbose output
                -f      output_file_name.The output is sent to the file instead of standard output
                -a      run all checks
                -d      run only default checks.
                -c      check1[,check2] run specific checks
                -l      list the checks and description
                -V      Print the Version
                -h      print help
        EXAMPLES:
        oakcli validate -l
        oakcli validate -a
        oakcli validate -c OSDiskStorage
        oakcli validate -c SharedStorage
        oakcli validate -c StorageTopology
        oakcli validate -c DiskCalibration
        oakcli validate -c SystemComponents,NetworkComponents,asr
        oakcli validate -c ospatch -ver 12.1.2.0.0
        oakcli validate -c ol6upgrade <-prechecks|postchecks>

To perform default ODA checks, execute the following command:

[root@odanode1 ~]# oakcli validate -d
INFO: oak system information and Validations
RESULT: System Software inventory details
Reading the metadata. It takes a while…
System Version Component Name            Installed Version         Supported Version
————– —————           ——————        —————–
12.1.2.10.0
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  0018                      Up-to-date
                SSD_SHARED                944A                      Up-to-date
                HDD_LOCAL                 A72A                      Up-to-date
                HDD_SHARED                A72A                      Up-to-date
                ILOM                      3.2.8.25 r114493          Up-to-date
                BIOS                      25040100                  Up-to-date
                IPMI                      1.8.12.4                  Up-to-date
                HMP                       2.3.5.2.8                 Up-to-date
                OAK                       12.1.2.10.0               Up-to-date
                OL                        6.8                       Up-to-date
                GI_HOME                   12.1.0.2.170117(2473      Up-to-date
                                          2082,24828633)
                DB_HOME                   12.1.0.2.170117(2473      Up-to-date
                                          2082,24828633)
RESULT: System Information:-
        Manufacturer:Oracle Corporation
        Product Name:SUN FIRE X4170 M3
        Serial Number:xxxxxx
RESULT: BIOS Information:-
        Vendor:American Megatrends Inc.
        Version:17110500
        Release Date:12/22/2014
        BIOS Revision:11.5
        Firmware Revision:3.2
SUCCESS: Controller p1 has the IR Bypass mode set correctly
SUCCESS: Controller p2 has the IR Bypass mode set correctly
INFO: Reading ilom data, may take short while..
INFO: Read the ilom data. Doing Validations
RESULT: System ILOM Version: 3.2.7.32.a r112581
RESULT: System BMC firmware version 3.02
RESULT: Powersupply PS0 V_IN=212 Volts IN_POWER=120 Watts OUT_POWER=120 Watts
RESULT: Powersupply PS1 V_IN=214 Volts IN_POWER=120 Watts OUT_POWER=110 Watts
SUCCESS: Both the powersupply are ok and functioning
RESULT: Cooling Unit FM0 fan speed F0=4400 RPM F1=4100 RPM
RESULT: Cooling Unit FM1 fan speed F0=4400 RPM F1=4100 RPM
SUCCESS: Both the cooling unit are present
RESULT: Processor P0 present Details:-
        Version:Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
        Current Speed:2900 MHz Core Enabled:8 Thread Count:16
SUCCESS: All 4 memory modules of CPU P0 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Processor P1 present Details:-
        Version:Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
        Current Speed:2900 MHz Core Enabled:8 Thread Count:16
SUCCESS: All 4 memory modules of CPU P1 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Total Physical System Memory is 264361708 kB
SUCCESS: All OS Disks are present and in ok state
RESULT: Power Supply=19 degrees C
INFO: Checking Operating System Storage
SUCCESS: The OS disks have the boot stamp
RESULT: Raid device /dev/md0 found clean
RESULT: Raid device /dev/md1 found clean
RESULT: Physical Volume   /dev/md1 in VolGroupSys has 154920.81M out of total 599449.93M
RESULT: Volumegroup   VolGroupSys consist of 1 physical volumes,contains 4 logical volumes, has 0 volume snaps with total size of 599449.93M and free space of 154920.81M
RESULT: Logical Volume   LogVolOpt in VolGroupSys Volume group is of size 60.00g
RESULT: Logical Volume   LogVolRoot in VolGroupSys Volume group is of size 30.00g
RESULT: Logical Volume   LogVolSwap in VolGroupSys Volume group is of size 24.00g
RESULT: Logical Volume   LogVolU01 in VolGroupSys Volume group is of size 300.00g
RESULT: Device /dev/mapper/VolGroupSys-LogVolRoot is mounted on / of type ext3 in (rw)
RESULT: Device /dev/md0 is mounted on /boot of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolOpt is mounted on /opt of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolU01 is mounted on /u01 of type ext3 in (rw)
RESULT: / has 19978 MB free out of total 30238 MB
RESULT: /boot has 419 MB free out of total 485 MB
RESULT: /opt has 40179 MB free out of total 60476 MB
RESULT: /u01 has 252770 MB free out of total 302380 MB
INFO: Checking Shared Storage
RESULT: Disk HDD_E0_S00_373739864 path1 status active device sdy with status active path2 status active device sda with status active
SUCCESS: HDD_E0_S00_373739864 has both the paths up and active
RESULT: Disk HDD_E0_S01_373740616 path1 status active device sdb with status active path2 status active device sdz with status active
SUCCESS: HDD_E0_S01_373740616 has both the paths up and active
RESULT: Disk HDD_E0_S02_373260876 path1 status active device sdc with status active path2 status active device sdaa with status active
SUCCESS: HDD_E0_S02_373260876 has both the paths up and active
RESULT: Disk HDD_E0_S03_373338164 path1 status active device sdd with status active path2 status active device sdab with status active
SUCCESS: HDD_E0_S03_373338164 has both the paths up and active
RESULT: Disk HDD_E0_S04_373746132 path1 status active device sde with status active path2 status active device sdac with status active
SUCCESS: HDD_E0_S04_373746132 has both the paths up and active
RESULT: Disk HDD_E0_S05_373581568 path1 status active device sdf with status active path2 status active device sdad with status active
SUCCESS: HDD_E0_S05_373581568 has both the paths up and active
RESULT: Disk HDD_E0_S06_373745880 path1 status active device sdg with status active path2 status active device sdae with status active
SUCCESS: HDD_E0_S06_373745880 has both the paths up and active
RESULT: Disk HDD_E0_S07_373740700 path1 status active device sdh with status active path2 status active device sdaf with status active
SUCCESS: HDD_E0_S07_373740700 has both the paths up and active
RESULT: Disk HDD_E0_S08_371918788 path1 status active device sdi with status active path2 status active device sdag with status active
SUCCESS: HDD_E0_S08_371918788 has both the paths up and active
RESULT: Disk HDD_E0_S09_371919956 path1 status active device sdj with status active path2 status active device sdah with status active
SUCCESS: HDD_E0_S09_371919956 has both the paths up and active
RESULT: Disk HDD_E0_S10_371907528 path1 status active device sdk with status active path2 status active device sdai with status active
SUCCESS: HDD_E0_S10_371907528 has both the paths up and active
RESULT: Disk HDD_E0_S11_371833792 path1 status active device sdl with status active path2 status active device sdaj with status active
SUCCESS: HDD_E0_S11_371833792 has both the paths up and active
RESULT: Disk HDD_E0_S12_371908584 path1 status active device sdm with status active path2 status active device sdak with status active
SUCCESS: HDD_E0_S12_371908584 has both the paths up and active
RESULT: Disk HDD_E0_S13_371909804 path1 status active device sdn with status active path2 status active device sdal with status active
SUCCESS: HDD_E0_S13_371909804 has both the paths up and active
RESULT: Disk HDD_E0_S14_373517740 path1 status active device sdo with status active path2 status active device sdam with status active
SUCCESS: HDD_E0_S14_373517740 has both the paths up and active
RESULT: Disk HDD_E0_S15_371921536 path1 status active device sdp with status active path2 status active device sdan with status active
SUCCESS: HDD_E0_S15_371921536 has both the paths up and active
RESULT: Disk HDD_E0_S16_373740588 path1 status active device sdq with status active path2 status active device sdao with status active
SUCCESS: HDD_E0_S16_373740588 has both the paths up and active
RESULT: Disk HDD_E0_S17_371922120 path1 status active device sdr with status active path2 status active device sdap with status active
SUCCESS: HDD_E0_S17_371922120 has both the paths up and active
RESULT: Disk HDD_E0_S18_371834964 path1 status active device sds with status active path2 status active device sdaq with status active
SUCCESS: HDD_E0_S18_371834964 has both the paths up and active
RESULT: Disk HDD_E0_S19_371835288 path1 status active device sdt with status active path2 status active device sdar with status active
SUCCESS: HDD_E0_S19_371835288 has both the paths up and active
RESULT: Disk SSD_E0_S20_805833242 path1 status active device sdu with status active path2 status active device sdas with status active
SUCCESS: SSD_E0_S20_805833242 has both the paths up and active
RESULT: Disk SSD_E0_S21_805834016 path1 status active device sdv with status active path2 status active device sdat with status active
SUCCESS: SSD_E0_S21_805834016 has both the paths up and active
RESULT: Disk SSD_E0_S22_805833106 path1 status active device sdw with status active path2 status active device sdau with status active
SUCCESS: SSD_E0_S22_805833106 has both the paths up and active
RESULT: Disk SSD_E0_S23_805829508 path1 status active device sdx with status active path2 status active device sdav with status active
SUCCESS: SSD_E0_S23_805829508 has both the paths up and active
INFO: Doing oak network checks
RESULT: Detected active link for interface eth0 with link speed 10000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth1 with link speed 10000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth2 with link speed 1000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth3 with link speed 1000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth4 with link speed 1000Mb/s and cable type as Twisted Pair
WARNING: No Link detected for interface eth5 with cable type as Twisted Pair
INFO: Checking bonding interface status
RESULT: Bond interface bond0 is up configured in mode:fault-tolerance (active-backup) with current active interface as eth2
                Slave1 interface is eth2 with status:up Link fail count=0 Maccaddr:00:10:e0:23:d9:86
                Slave2 interface is eth3 with status:up Link fail count=0 Maccaddr:00:10:e0:23:d9:87
ERROR: Bond interface bond1 has 0 slave interfaces, expected 2 interface
SUCCESS: eth0 is running 192.168.16.24
SUCCESS: eth1 is running 192.168.17.24
It may take a while. Please wait…
INFO    : ODA Topology Verification
INFO    : Running on Node0
INFO    : Check hardware type
SUCCESS : Type of hardware found : X4-2
INFO    : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO    : Check number of Controllers
SUCCESS : Number of Internal LSI SAS controller found : 1
SUCCESS : Number of External LSI SAS controller found : 2
INFO    : Check for Controllers correct PCIe slot address
SUCCESS : Internal LSI SAS controller   : 50:00.0
SUCCESS : External LSI SAS controller 0 : 30:00.0
SUCCESS : External LSI SAS controller 1 : 40:00.0
INFO    : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO    : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO    : Check for External Controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for controller 0
INFO    : Check for External Controller 1
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for Controller 1
INFO    : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
INFO    : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE0
INFO    : Check JBOD Nickname
SUCCESS : JBOD Nickname set correctly : Oracle Database Appliance – E0
INFO    : The details for Storage Topology Validation can also be found in the log file=/opt/oracle/oak/log/dstmo605001por/storagetopology/StorageTopology-2017-07-26-09:43:08_8061_20345.log

To list the different validation checks and their description, execute the following command.

[root@odanode1 ~]# oakcli validate -l
        Checkname — Description
        =========    ===========
        *SystemComponents — Validate system components based on ilom sensor data readings
        *OSDiskStorage — Validate OS disks and filesystem information
        *SharedStorage — Validate Shared storage and multipathing information
        DiskCalibration — Check disk performance with orion
        *NetworkComponents — Validate public and private network components
        *StorageTopology — Validate external JBOD connectivity
        asr — Validate asr components based on asr config file and ilom sensor data readings
        ospatch — Verifies whether OS patching could be successful or not
        ol6upgrade — Validates the ol6 upgrade
* — These checks are also performed as part of default checks

To validate JBOD (just a bunch of disks) connectivity, execute the following command:

[root@odanode1 ~]# /opt/oracle/oak/bin/oakcli validate -c storagetopology
It may take a while. Please wait…
INFO    : ODA Topology Verification
INFO    : Running on Node0
INFO    : Check hardware type
SUCCESS : Type of hardware found : X4-2
INFO    : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO    : Check number of Controllers
SUCCESS : Number of Internal LSI SAS controller found : 1
SUCCESS : Number of External LSI SAS controller found : 2
INFO    : Check for Controllers correct PCIe slot address
SUCCESS : Internal LSI SAS controller   : 50:00.0
SUCCESS : External LSI SAS controller 0 : 30:00.0
SUCCESS : External LSI SAS controller 1 : 40:00.0
INFO    : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO    : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO    : Check for External Controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for controller 0
INFO    : Check for External Controller 1
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for Controller 1
INFO    : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
INFO    : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE0
INFO    : Check JBOD Nickname
SUCCESS : JBOD Nickname set correctly : Oracle Database Appliance – E0
INFO    : The details for Storage Topology Validation can also be found in the log file=/opt/oracle/oak/log/odanode1/storagetopology/StorageTopology-2017-06-28-14:17:35_10800_11311.log

To Validate OS disks and filesystem information, execute the following command:

[root@odanode1 ~]# oakcli validate -c OSDiskStorage
INFO: Checking Operating System Storage
SUCCESS: The OS disks have the boot stamp
RESULT: Raid device /dev/md0 found clean
RESULT: Raid device /dev/md1 found clean
RESULT: Physical Volume   /dev/md1 in VolGroupSys has 369669.18M out of total 599449.93M
RESULT: Volumegroup   VolGroupSys consist of 1 physical volumes,contains 4 logical volumes, has 0 volume snaps with total size of 599449.93M and free space of 369669.18M
RESULT: Logical Volume   LogVolOpt in VolGroupSys Volume group is of size 60.00g
RESULT: Logical Volume   LogVolRoot in VolGroupSys Volume group is of size 30.00g
RESULT: Logical Volume   LogVolSwap in VolGroupSys Volume group is of size 24.00g
RESULT: Logical Volume   LogVolU01 in VolGroupSys Volume group is of size 100.00g
RESULT: Device /dev/mapper/VolGroupSys-LogVolRoot is mounted on / of type ext3 in (rw)
RESULT: Device /dev/md0 is mounted on /boot of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolOpt is mounted on /opt of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolU01 is mounted on /u01 of type ext3 in (rw)
RESULT: / has 13665 MB free out of total 30238 MB
RESULT: /boot has 419 MB free out of total 485 MB
RESULT: /opt has 46447 MB free out of total 60476 MB
RESULT: /u01 has 76169 MB free out of total 100794 MB

To Validate Shared storage and multipathing information, execute the following command:

[root@odanode1 ~]# oakcli validate -c SharedStorage
INFO: Checking Shared Storage
RESULT: Disk HDD_E0_S00_1464747464 path1 status active device sdy with status active path2 status active device sda with status active
SUCCESS: HDD_E0_S00_1464747464 has both the paths up and active
RESULT: Disk HDD_E0_S01_1464755868 path1 status active device sdz with status active path2 status active device sdb with status active
SUCCESS: HDD_E0_S01_1464755868 has both the paths up and active
RESULT: Disk HDD_E0_S02_1464707864 path1 status active device sdc with status active path2 status active device sdaa with status active
SUCCESS: HDD_E0_S02_1464707864 has both the paths up and active
RESULT: Disk HDD_E0_S03_1464750264 path1 status active device sdab with status active path2 status active device sdd with status active
SUCCESS: HDD_E0_S03_1464750264 has both the paths up and active
RESULT: Disk HDD_E0_S04_1464735404 path1 status active device sdac with status active path2 status active device sde with status active
SUCCESS: HDD_E0_S04_1464735404 has both the paths up and active
RESULT: Disk HDD_E0_S05_1464754648 path1 status active device sdad with status active path2 status active device sdf with status active
SUCCESS: HDD_E0_S05_1464754648 has both the paths up and active
RESULT: Disk HDD_E0_S06_1464734536 path1 status active device sdae with status active path2 status active device sdg with status active
SUCCESS: HDD_E0_S06_1464734536 has both the paths up and active
RESULT: Disk HDD_E0_S07_1464777748 path1 status active device sdaf with status active path2 status active device sdh with status active
SUCCESS: HDD_E0_S07_1464777748 has both the paths up and active
RESULT: Disk HDD_E0_S08_1464777992 path1 status active device sdag with status active path2 status active device sdi with status active
SUCCESS: HDD_E0_S08_1464777992 has both the paths up and active
RESULT: Disk HDD_E0_S09_1464744228 path1 status active device sdj with status active path2 status active device sdah with status active
SUCCESS: HDD_E0_S09_1464744228 has both the paths up and active
RESULT: Disk HDD_E0_S10_1464734532 path1 status active device sdk with status active path2 status active device sdai with status active
SUCCESS: HDD_E0_S10_1464734532 has both the paths up and active
RESULT: Disk HDD_E0_S11_1464757412 path1 status active device sdl with status active path2 status active device sdaj with status active
SUCCESS: HDD_E0_S11_1464757412 has both the paths up and active
RESULT: Disk HDD_E0_S12_1464430876 path1 status active device sdak with status active path2 status active device sdm with status active
SUCCESS: HDD_E0_S12_1464430876 has both the paths up and active
RESULT: Disk HDD_E0_S13_1464736940 path1 status active device sdn with status active path2 status active device sdal with status active
SUCCESS: HDD_E0_S13_1464736940 has both the paths up and active
RESULT: Disk HDD_E0_S14_1464781048 path1 status active device sdam with status active path2 status active device sdo with status active
SUCCESS: HDD_E0_S14_1464781048 has both the paths up and active
RESULT: Disk HDD_E0_S15_1464786920 path1 status active device sdan with status active path2 status active device sdp with status active
SUCCESS: HDD_E0_S15_1464786920 has both the paths up and active
RESULT: Disk HDD_E0_S16_1464781112 path1 status active device sdq with status active path2 status active device sdao with status active
SUCCESS: HDD_E0_S16_1464781112 has both the paths up and active
RESULT: Disk HDD_E0_S17_1464780984 path1 status active device sdr with status active path2 status active device sdap with status active
SUCCESS: HDD_E0_S17_1464780984 has both the paths up and active
RESULT: Disk HDD_E0_S18_1464786496 path1 status active device sdaq with status active path2 status active device sds with status active
SUCCESS: HDD_E0_S18_1464786496 has both the paths up and active
RESULT: Disk HDD_E0_S19_1464781148 path1 status active device sdt with status active path2 status active device sdar with status active
SUCCESS: HDD_E0_S19_1464781148 has both the paths up and active
RESULT: Disk SSD_E0_S20_805976279 path1 status active device sdas with status active path2 status active device sdu with status active
SUCCESS: SSD_E0_S20_805976279 has both the paths up and active
RESULT: Disk SSD_E0_S21_805976092 path1 status active device sdat with status active path2 status active device sdv with status active
SUCCESS: SSD_E0_S21_805976092 has both the paths up and active
RESULT: Disk SSD_E0_S22_805976245 path1 status active device sdau with status active path2 status active device sdw with status active
SUCCESS: SSD_E0_S22_805976245 has both the paths up and active
RESULT: Disk SSD_E0_S23_805976275 path1 status active device sdx with status active path2 status active device sdav with status active
SUCCESS: SSD_E0_S23_805976275 has both the paths up and active

To Validate system components based on ilom sensor data readings, execute the following command:

[root@odanode1 ~]# oakcli validate -c SystemComponents
INFO: oak system information and Validations
RESULT: System Software inventory details
Reading the metadata. It takes a while…
System Version Component Name            Installed Version         Supported Version
————– —————           ——————        —————–
12.1.2.10.0
                 Controller_INT            11.05.03.00               Up-to-date
                 Controller_EXT            11.05.03.00               Up-to-date
                 Expander                  0018                      Up-to-date
                 SSD_SHARED                944A                      Up-to-date
                 HDD_LOCAL                 A72A                      Up-to-date
                 HDD_SHARED                A72A                      Up-to-date
                 ILOM                      3.2.8.25 r114493          Up-to-date
                 BIOS                      25040100                  Up-to-date
                 IPMI                      1.8.12.4                  Up-to-date
                 HMP                       2.3.5.2.8                 Up-to-date
                 OAK                       12.1.2.10.0               Up-to-date
                 OL                        6.8                       Up-to-date
                 GI_HOME                   12.1.0.2.170117(2473      Up-to-date
                                           2082,24828633)
                 DB_HOME                   12.1.0.2.170117(2473      Up-to-date
                                           2082,24828633)
RESULT: System Information:-
        Manufacturer:Oracle Corporation
        Product Name:SUN SERVER X4-2
        Serial Number:1438NML03N
RESULT: BIOS Information:-
        Vendor:American Megatrends Inc.
        Version:25040100
        Release Date:11/09/2016
        BIOS Revision:4.1
        Firmware Revision:3.2
SUCCESS: Controller p1 has the IR Bypass mode set correctly
SUCCESS: Controller p2 has the IR Bypass mode set correctly
INFO: Reading ilom data, may take short while..
INFO: Read the ilom data. Doing Validations
RESULT: System ILOM Version: 3.2.8.25 r114493
RESULT: System BMC firmware version 3.02
RESULT: Powersupply PS0 V_IN=118 Volts IN_POWER=130 Watts OUT_POWER=120 Watts
RESULT: Powersupply PS1 V_IN=116 Volts IN_POWER=130 Watts OUT_POWER=110 Watts
SUCCESS: Both the powersupply are ok and functioning
RESULT: Cooling Unit FM0 fan speed F0=5900 RPM F1=3100 RPM
RESULT: Cooling Unit FM1 fan speed F0=6300 RPM F1=3400 RPM
SUCCESS: Both the cooling unit are present
RESULT: Processor P0 present Details:-
        Version:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
        Current Speed:2700 MHz Core Enabled:12 Thread Count:24
SUCCESS: All 4 memory modules of CPU P0 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Processor P1 present Details:-
        Version:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
        Current Speed:2700 MHz Core Enabled:12 Thread Count:24
SUCCESS: All 4 memory modules of CPU P1 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Total Physical System Memory is 264360108 kB
SUCCESS: All OS Disks are present and in ok state
RESULT: Power Supply=23 degrees C

To Check disk performance, execute the following command:

(Do not execute it on a business system. It may degrade the performance)

[root@odanode1 ~]# oakcli validate -c DiskCalibration
INFO: Doing oak disk calibration checks
INFO: About to run random read IOPS throughput tests for SASDisk
RESULT: Random read throughput across all 20 SASDisk = 3195 IOPS
INFO: About to run random read IOPS throughput tests for SSDDisk
RESULT: Random read throughput across all 4 SSDDisk = 99947 IOPS
INFO: About to run random read MBPS throughput tests for SASDisk
RESULT: Random read throughput across all 20 SASDisk = 1689 MBPS
INFO: About to run random read MBPS throughput tests for SSDDisk
RESULT: Random read throughput across all 4 SSDDisk = 1506 MBPS
INFO: Completed IOPS tests for individual disks of type SASDisk
INFO: Completed MBPS tests for individual disks of type SASDisk
INFO: Completed IOPS tests for individual disks of type SSDDisk
INFO: Completed MBPS tests for individual disks of type SSDDisk
INFO: Completed all single disk tests
INFO: Calibration results for SASDisk
RESULT: Random read throughput of HDD_E0_S13_1464736940 is 236 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S05_1464754648 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S03_1464750264 is 239 IOPS 156 MBPS
RESULT: Random read throughput of HDD_E0_S00_1464747464 is 238 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S11_1464757412 is 238 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S15_1464786920 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S07_1464777748 is 238 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S16_1464781112 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S14_1464781048 is 238 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S09_1464744228 is 237 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S01_1464755868 is 237 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S02_1464707864 is 240 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S08_1464777992 is 238 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S06_1464734536 is 236 IOPS 147 MBPS
RESULT: Random read throughput of HDD_E0_S04_1464735404 is 236 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S17_1464780984 is 235 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S18_1464786496 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S10_1464734532 is 233 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S19_1464781148 is 202 IOPS 130 MBPS
RESULT: Random read throughput of HDD_E0_S12_1464430876 is 236 IOPS 148 MBPS
INFO: Calibration results for SSDDisk
RESULT: Random read throughput of SSD_E0_S23_805976275 is 39761 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S22_805976245 is 39463 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S21_805976092 is 39683 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S20_805976279 is 43784 IOPS 434 MBPS

To Validate asr components based on asr config file, execute the following command:

[root@dstmo606001por ~]# oakcli validate -c asr
INFO: oak Asr information and Validations
RESULT: /opt/oracle/oak/conf/asr.conf exist
RESULT: ASR Manager ip:192.168.1.11
RESULT: ASR Manager port:162
SUCCESS: ASR configuration file validation successfully completed
RESULT: ilom alertmgmt level is set to minor
RESULT: ilom alertmgmt type is set to snmptrap
RESULT: alertmgmt snmp_version is set to 2c
RESULT: alertmgmt community_or_username is set to public
RESULT: alertmgmt destination is set to 192.168.1.11
RESULT: alertmgmt destination_port is set to 162
SUCCESS: Ilom snmp confguration for asr set correctly
RESULT: /etc/hosts has entry 141.146.1.169 transport.oracle.com
RESULT: notification trap configured to ip:192.168.1.11
RESULT: notification trap configured to port:162
SUCCESS: Asr notification trap set correctly
…..
…..
…..

Conclusion
In this article we have learned several Oracle Database Applinace validation commands along with their outputs. Validating ODA is an important task for an administrator to ensure there are hardware or software issues. oakcli command line interface made it easy to manage the entire ODA stack. Thanks to oakcli.

Different Oracle Health Check Tools

By Netsoftmate on

September 10, 2017

- Uncategorized

Introduction

There are quite a few health check tools provided by Oracle for both Engineered and Non-Engineered Systems. This article explains which tool is a best choice for a given system.

Table showing different Health Check Tools available for Engineered and Non-Engineered Systems

ORAchk (1268927.2)	Exachk
Oracle Database Appliance (ODA)	Exadata Database Machine (1070954.1)
Non-Engineered Systems	Exalogic (1449226.1)
	Exalytics (1566134.1)
	BIG Data Appliance (BDA) (1643715.1)
	Zero Data Loss Recovery Appliance (ZDLRA) (1643715.1)

Examples executing Health Check utilities

ORAchk

Download ORAchk using MOS – ORAchk – Health Checks for the Oracle Stack (Doc ID 1268927.2)

Non-Engineered Systems

Run ORAchk Interactively.

Log in to the system as root user
Stage the appropriate orachk.zip kit in its own directory the node on which the tool will be executed. Eg: /u01/app/oracle/stage
Unzip orachk.zip kit, leaving the script and driver files together in the same directory

# unzip orachk.zip –d /tmp/orachk
Validate the permissions for orachk are 755 (-rwxr-xr-x). If the permissions are not currently set to 755, set the permissions on orachk as follows:

#cd /tmp/orachk

# chmod 755 orachk
Invoke the tool as follows:

#cd /tmp/orachk

#./orachk

Follow the prompts while reading and understanding all messages.
Upon completion of ORAchk command the following (or similar) will be displayed:

Detailed report (html) – /home/oracle/orachk_oradbnode1_orcl_100715_105241/orachk_oradbnode1_orcl_100715_105241.html

Engineered System – Oracle Database Appliance (ODA)

# /opt/oracle/oak/orachk -a

Exachk

Exadata Database Machine

Download Exachk using MOS Oracle Exadata Database Machine exachk or HealthCheck (Doc ID 1070954.1)

# ./exachk -a

Conclusion

In this article we have seen different Oracle Health Check tool available and how to use them.

Oracle Database Appliance: Create Database

By Netsoftmate on

August 28, 2017

- Uncategorized

Introduction

In my previous articles, we have learned how to Deploy an Oracle Database Appliance.
One can use OAKCLI or DBCA utility to create the database on ODA. But it is recommended to use OAKCLI on ODA to create the database.
With OAKCLI, creating database is very easy and it is just one command.
Let’s see how to quickly create a database on ODA.

Steps to create Database on ODA

List the existing RDBMS Oracle Homes. With OAKCLI it is very easy to get the Oracle Homes Printed.

[root@odanode1 ~]# oakcli show dbhomes
Oracle Home Name Oracle Home version Home Location
—————- ——————- ————
OraDb12102_home1 /u01/app/oracle/product/12.1.0.2/dbhome_1

You can also use the following option to get the Oracle HOME Name.

[root@odanode1 ~]# cd /u01/app/oraInventory/ContentsXML
[root@odanode1 ContentsXML]# grep -i “HOME NAME” inventory.xml
<HOME NAME=”OraGrid12102″ LOC=”/u01/app/12.1.0.2/grid” TYPE=”O” IDX=”1″ CRS=”true”>
<HOME NAME=”OraDb12102_home1″ LOC=”/u01/app/oracle/product/12.1.0.2/dbhome_1″ TYPE=”O” IDX=”2″>

Here we have only Oracle HOME name OraDb12102_home1. We will be using this name to create the database.

Using OAKCLI to create database. Let’s see the options available.

Display options that can be used with OAKCLI

[root@odanode1 ~]# oakcli -h
Usage: oakcli show – Shows disk, diskgroup, expander, controller, server, processor, memory, power, cooling, network, enclosure, storage, version, fs, raidsyncstatus, dbhomes,

dbstorage, databases, db_config_params, core_config_key, env_hw, ASR
oakcli configure – Configures the Network or ASR or additional Net
oakcli apply – Applies the core_config_key
oakcli locate – Locates a disk
oakcli deploy – Deploys the Database Appliance
oakcli update – Updates the Database Appliance
oakcli validate – Validates the Database Appliance
oakcli manage – Manages the OAK repository, diagcollect etc.,
oakcli unpack – Unpack the given package to OAK repository
oakcli copy – Copies the deployment config file
oakcli upgrade – Upgrades database
oakcli stordiag – Run storage diagnostic tool on both Nodes
oakcli test – Test ASR
oakcli orachk – Performs configuration settings check on ODA
oakcli create – Creates Database, DB storage, snapshotdb, dbhome, db_config_params file
oakcli delete – Deletes Database, DB storage, dbhome, db_config_params file
oakcli modify – Performs modify opeartions on Database
oakcli resize – Resizes DB storage

Display options that can be used with OAKCLI CREATE

[root@odanode1 ~]# oakcli create -h
Usage:
oakcli create {database | dbstorage | snapshotdb| dbhome | db_config_params } [<options>]
Where:
database – Creates the Database
snapshotdb – Creates the Snapshot Database
dbhome – Creates the Database Home
dbstorage – Creates Storage for a given Database
db_config_params – Creates the Database configuration parameter file

Display options that can be used with OAKCLI CREATE DATABASE

[root@odanode1 ~]# oakcli create database -h
Usage:
oakcli create database -db <db_name> [[[-oh <home>] | [-version <version>]] [-params <params_file>] [-cdb]]

where:
db_name – Name of the database to be created.
home – Existing oracle home for creating the database. By default we create a new database home.
version – Database Version information for creating the database home. [ex. 11.2.0.2.7] If not provided create the database home from latest available bits.
params_file – Name of the db_config_parameter file [This file can be created using using ‘oakcli create db_config_params’].
If not provided, create the database using default configuration file
cdb – Creates this database as a container database

Create Database as follows

When you execute the create database command, it will prompt you the following details:

root password
SYSASM password
Databsae Type (OLTP, DSS or In-Memory)
Database Deployment (EE, RACONE or RAC)
Database Class

[root@odanode1 ~]# oakcli create database -db odatest -oh OraDb12102_home1
INFO: 2017-07-04 12:02:24: Please check the logfile ‘/opt/oracle/oak/log/odanode1/tools/12.1.2.10.0/createdb_odatest_71669.log’ for more details
INFO: 2017-07-04 12:02:26: Database parameter file is not provided. Will be using default parameters for DB creation

Please enter the ‘root’ password :
Please re-enter the ‘root’ password:

Please enter the ‘SYSASM’ password : (During deployment we set the SYSASM password to ‘welcome1’):
Please re-enter the ‘SYSASM’ password:
Please select one of the following for Database type [1 .. 3] :
1 => OLTP
2 => DSS
3 => In-Memory
1
The selected value is : OLTP
Please select one of the following for Database Deployment [1 .. 3] :
1 => EE : Enterprise Edition
2 => RACONE
3 => RAC
3
The selected value is : RAC

Specify the Database Class (1. odb-01 ‘1 core, 8 GB memory’ 2. Others) [1] : 2

Please select one of the following for Database Class [1 .. 9] :
1 => odb-01s ( 1 cores , 4 GB memory)
2 => odb-01 ( 1 cores , 8 GB memory)
3 => odb-02 ( 2 cores , 16 GB memory)
4 => odb-04 ( 4 cores , 32 GB memory)
5 => odb-06 ( 6 cores , 48 GB memory)
6 => odb-12 ( 12 cores , 96 GB memory)
7 => odb-16 ( 16 cores , 128 GB memory)
8 => odb-20 ( 20 cores , 160 GB memory)
9 => odb-24 ( 24 cores , 192 GB memory)
3
The selected value is : odb-02 ( 2 cores , 16 GB memory)
INFO : Logging all actions in the file /opt/oracle/oak/onecmd/tmp/odanode1-20170704120410.log and traces in the file /opt/oracle/oak/onecmd/tmp/odanode1-20170704120410.trc
INFO : Loading the configuration file /opt/oracle/oak/onecmd/create_database.params…
INFO : Creating the node list files…
INFO : Setting up ssh for root…
INFO : Setting up SSH across the Private Network…
…………Completed
INFO : Running as root: /usr/bin/ssh -l root 192.168.16.24 /root/DoAllcmds.sh
INFO : Running as root: /usr/bin/ssh -l root 192.168.16.25 /root/DoAllcmds.sh
INFO : Background process 77365 (node: 192.168.16.24) gets done with the exit code 0
INFO : Background process 77412 (node: 192.168.16.25) gets done with the exit code 0
INFO : Setting up SSH completed successfully
INFO : Running the command /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd –exclude=*zip –exclude=*gz –exclude=*log –exclude=*trc —

exclude=*rpm to sync directory</opt/oracle/oak/onecmd> on node <192.168.16.25>
SUCCESS: Ran /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd –exclude=*zip –exclude=*gz –exclude=*log –exclude=*trc –exclude=*rpm and it

returned: RC=0

……….Completed
INFO : Did not do scp for node : odanode1
INFO : Running as root: /usr/bin/ssh -l root odanode1 /root/DoAllcmds.sh
INFO : Running as root: /usr/bin/ssh -l root odanode2 /root/DoAllcmds.sh
INFO : Background process 78082 (node: odanode1) gets done with the exit code 0
INFO : Background process 78130 (node: odanode2) gets done with the exit code 0
INFO : Did not do scp for node : odanode1
INFO : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120453.sh
INFO : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120453.sh
INFO : Background process 78210 (node: odanode1) gets done with the exit code 0
INFO : Background process 78256 (node: odanode2) gets done with the exit code 0
INFO : Setting up SSH for user oracle…
…INFO : checking nodes in /opt/oracle/oak/onecmd/tmp/db_nodes…
…
SUCCESS: All nodes in /opt/oracle/oak/onecmd/tmp/db_nodes are pingable and alive.
INFO : Checking SSH setup for user (oracle) on nodes in /opt/oracle/oak/onecmd/tmp/db_nodes…
INFO : Did not do scp for node : odanode1
INFO : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120518.sh
INFO : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120518.sh
INFO : Background process 79851 (node: odanode1) gets done with the exit code 0
INFO : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120518.sh
INFO : Background process 79897 (node: odanode2) gets done with the exit code 0
INFO : Setting up ACFS storage
INFO : Did not do scp for node : odanode1
INFO : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/acfsm_71669.sh
INFO : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/acfsm_71669.sh
INFO : Background process 80312 (node: odanode1) gets done with the exit code 0
INFO : Background process 80360 (node: odanode2) gets done with the exit code 0
INFO: 2017-07-04 12:05:36: Successfully setup the storage structure for the database ‘odatest’
SUCCESS: Successfully setup ACFS storage for the database odatest
INFO : Creating Database using DBCA…
INFO : Did not do scp for node : odanode1
INFO : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120536.sh
INFO : Background process 83721 (node: odanode1) gets done with the exit code 0
INFO : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120536.sh
INFO : Background process 83768 (node: odanode2) gets done with the exit code 0
INFO : Running DBCA using /opt/oracle/oak/onecmd/tmp/dbca-odatest.sh on odanode1 as oracle…
INFO : Check output in /opt/oracle/oak/onecmd/tmp/dbca-odatest-20170704120410.log on odanode1
INFO : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/dbca-odatest.sh
INFO : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbca-odatest.sh
Instance odatest1 is running on node odanode1
Instance odatest2 is running on node odanode2
INFO : One or more Instances running on the cluster nodes.
INFO : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl setenv database odatest -t ‘TZ=America/New_York’ to set

DB timezone
INFO : Running the command /u01/app/12.1.0.2/grid/bin/crsctl stat resource ora.odatest.db -p
.INFO : Did not do scp for node : odanode1
..
INFO : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/dbupdates-odatesth
INFO : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbupdates-odatest.sh
INFO : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl stop database -ddatest
INFO : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl start database -odatest
INFO: 2017-07-04 12:24:56: Successfully set the RMAN SNAPSHOT control file
.INFO : Did not do scp for node : odanode1
..
INFO : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/runDatapatch.sh
INFO : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/runDatapatch.sh
SUCCESS: 2017-07-04 12:25:27: Successfully created the Database : odatest
INFO : Resecuring the environment… odanode1 odanode2
INFO : Removing the SSH setup for root…

INFO : Running as root: /usr/bin/ssh -l root odanode1 chmod 751 /opt/oracle/oak/onecmd/tmp

INFO : Running as root: /usr/bin/ssh -l root odanode2 chmod 751 /opt/oracle/oak/onecmd/tmp
INFO : Running as root: /usr/bin/ssh -l root odanode2 /bin/rm -rf /root/.ssh
INFO : Running as root: /usr/bin/ssh -l root odanode1 /bin/rm -rf /root/.ssh

********THIS COMPLETES THE DATABASE CREATION PROCESS***********

Validate Database

SQL> select * from v$version;

BANNER CON_ID
——————————————————————————– ———-
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production 0
PL/SQL Release 12.1.0.2.0 – Production 0
CORE 12.1.0.2.0 Production 0
TNS for Linux: Version 12.1.0.2.0 – Production 0
NLSRTL Version 12.1.0.2.0 – Production 0

SQL> select name,open_mode,database_role,log_mode,flashback_on from v$database;

NAME OPEN_MODE DATABASE_ROLE LOG_MODE FLASHBACK_ON
——— ——————– —————- ———— ——————
ODATEST READ WRITE PRIMARY ARCHIVELOG NO

[oracle@odanode1 ~]$ srvctl status database -d odatest
Instance odatest1 is running on node odanode1
Instance odatest2 is running on node odanode2

[oracle@odanode1 ~]$ srvctl config database -d odatest
Database unique name: odatest
Database name: odatest
Oracle home: /u01/app/oracle/product/12.1.0.2/dbhome_1
Oracle user: oracle
Spfile: /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/odatest/spfileodatest.ora
Password file: /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/odatest/orapwodatest
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups:
Mount point paths: /u01/app/oracle/oradata/datastore,/u02/app/oracle/oradata/datastore,/u01/app/oracle/fast_recovery_area/datastore
Services:
Type: RAC
Start concurrency:
Stop concurrency:
OSDBA group: dba
OSOPER group: racoper
Database instances: odatest1,odatest2
Configured nodes: odanode1,odanode2
Database is administrator managed

SQL> set lines 150
SQL> select name from v$datafile;

NAME
—————————————————————————————————————-
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_system_doqhbjop_.dbf
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_sysaux_doqhbnkx_.dbf
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_undotbs1_doqhbq7b_.dbf
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_undotbs2_doqhbzyd_.dbf
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_users_doqhc0tz_.dbf

SQL> select name from v$controlfile;

NAME
—————————————————————————————————————-
/u01/app/oracle/oradata/datastore/odatest/ODATEST/controlfile/o1_mf_doqhbb49_.ctl

SQL> select member from v$logfile;

MEMBER
—————————————————————————————————————-
/u01/app/oracle/oradata/datastore/odatest/ODATEST/onlinelog/o1_mf_1_doqhbb7f_.log
/u01/app/oracle/oradata/datastore/odatest/ODATEST/onlinelog/o1_mf_2_doqhbf18_.log
/u01/app/oracle/oradata/datastore/odatest/ODATEST/onlinelog/o1_mf_3_doqhxbg9_.log
/u01/app/oracle/oradata/datastore/odatest/ODATEST/onlinelog/o1_mf_4_doqhxg9m_.log

Conclusion
In this article we have learned how to create a database on Oracle Database Appliance. Creating an Oracle Database on ODA is just one step process. OAKCLI utility takes care of everything for you to create the database. You can also use the DBCA utility to create the database but it is recommended to use OAKCLI utility to create database.

Oracle Database Appliance Bare Metal Setup In A Nutshell

By Netsoftmate on

August 28, 2017

- Uncategorized

Introduction

Deploying an Oracle Database Appliance consists of several basic steps. It is very important to plan the ODA deployment properly before performing the actual steps, this helps you to avoid issues during deployment and save time.

In this article I will layout the high level steps required to perform a successful ODA deployment.

Pre-Deployment Steps

Gather Network details.

Fill the ODA Pre-Install Checklist form with details like, Cluster name, Hostname, IP Address etc.

Allocate IPs and Submit DNS and firewall requests

Other network details required are, Domain name, DNS, NTP.

Work with your Network administartor to gather all these details.

Oracle Appliance Manager Configurator

Build the deployment configuration files using the Oracle Appliance Manager Configurator utility in offline mode. This is an optional step which will save time to complete the deployment and perform network validation before deployment.

ODA : Update Firmware On ODA Post Reimage

By Netsoftmate on

August 11, 2017

- Uncategorized

Introduction

In my previous article we have learned how to Reimage an Oracle Database Appliance to 12.1.2.10. It is important to note that the Reimage process doesn’t update the firmware (BIOS, ILOM, Local and Shared HDD) on ODA nodes. The below screen shot show the output post Re-imaging an ODA X4-2. There is nothing wrong with reimage process and it is completely expected as the reimage process doesn’t update the firmware.

We can see that the ILOM, BIOS, HDD _Local and HDD_Shared are not up-to-date.

In this article I will demonstrate how to update the firmware post ODA re-imaging.

Prerequisites

Root user access to ODA ILOM
Download the ODA Bundle Patch using patch 25499210

The following steps should be followed to update the firmware on ODA post reimaging.

Configure initial network
Copy ODA software
Update firmware

Configure initial network

The “oakcli configure firstnet” command is used to configure an initial network on Oracle Database Appliance (ODA) that enables you to copy ODA End User Bundle software to ODA server. oakcli configure firstnet allows you to establish the network interfaces for the Oracle Database Appliance upon first usage. Once you have completed the reimaging of ODA servers, you should log onto the one of the node ILOM console and do the initial configuration of the Oracle Database Appliance network using the command firstnet. The bond0 interface is configured when execute the firstnet utility. Before running firstnet, ensure that you allocated IP addresses and verify that their entries in the DNS have been completed.

Steps to Execute firstnet utility

Connect to the ILOM console using browser or putty to configure the initial IP address for the node you are connected to.

Once you execute the firstnet utility it will ask you for the IP address, Netmask and Gateway IPs.

Once the network interfaces have been configured, you need to test them by using the ping command on the node. Additionally, you can test the network by pinging the configured node from your remote client.

[root@oak1 ~]# ping 10.10.17.11

PING 172.16.202.71 (10.10.17.11) 56(84) bytes of data.

64 bytes from 10.10.17.11: icmp_seq=1 ttl=64 time=0.027 ms

64 bytes from 10.10.17.11: icmp_seq=2 ttl=64 time=0.008 ms

64 bytes from 10.10.17.11: icmp_seq=3 ttl=64 time=0.008 ms

64 bytes from 10.10.17.11: icmp_seq=4 ttl=64 time=0.006 ms

64 bytes from 10.10.17.11: icmp_seq=5 ttl=64 time=0.005 ms

— 172.16.202.71 ping statistics —

5 packets transmitted, 5 received, 0% packet loss, time 4544ms

rtt min/avg/max/mdev = 0.005/0.010/0.027/0.009 ms

[root@oak1 ~]# ifconfig

bond0 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2

inet addr:10.10.17.11 Bcast:10.10.17.255 Mask:255.255.255.0

UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1

RX packets:12 errors:0 dropped:0 overruns:0 frame:0

TX packets:13 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)

bond1 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4

UP BROADCAST MASTER MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B4

inet addr:192.168.16.24 Bcast:192.168.16.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1

RX packets:138257 errors:0 dropped:0 overruns:0 frame:0

TX packets:138436 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:11200490 (10.6 MiB) TX bytes:11134648 (10.6 MiB)

eth1 Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B5

inet addr:192.168.17.24 Bcast:192.168.17.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1

RX packets:138217 errors:0 dropped:0 overruns:0 frame:0

TX packets:138434 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:11197894 (10.6 MiB) TX bytes:11134800 (10.6 MiB)

eth2 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2

UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1

RX packets:12 errors:0 dropped:0 overruns:0 frame:0

TX packets:13 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)

eth3 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2

UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth4 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4

UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth5 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4

UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:512371 errors:0 dropped:0 overruns:0 frame:0

TX packets:512371 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:38908072 (37.1 MiB) TX bytes:38908072 (37.1 MiB)

Repeat the steps on ODA node 2.

Copy Patches to ODA

Once the initial network is configured you can now copy the ODA patch to ODA node 1 under /tmp.

Update firmware

The Reimage process doesn’t update the firmware (BIOS, ILOM, Local and Shared HDD). The below screen shows that the firware is not updated on both the nodes.

Let’s update the firmware on ODA nodes.

Copy the patches from node 1 to node 2.

Unpack the patches using oakcli command as shown on both the nodes

Update the firmware on node 1. At the end of the firmware update the node is rebooted.

Once the node 1 comes back, verify the firmware is updated.

Update the firmware on node 2. At the end of the firmware update the node is rebooted.

Once the node 2 comes back, verify the firmware is updated.

Update the firmware on Shared Storage. Both the ODA nodes rebooted at the end of storage update.

Now verify the firmware on both the nodes.

We can now see that the firware is update on both the nodes.

Conclusion

Reimaging an Oracle Database Appliance doesn’t update the firmware (BIOS, ILOM, Local and Shared HDD). So we have to download the ODA patches and update the firmware post reimage manually. You must run the update command on both the ODA nodes and once for storage from node 1. It is fairly straight forward to update the firmware.

Reimage Oracle Database Appliance (ODA)

By Netsoftmate on

July 5, 2017

- Uncategorized

Re-image Oracle Database Appliance (ODA)

Oracle Database Appliance comes preinstalled with the most current version of the Base Metal Operating System. It is not be necessary to re-image the ODA operating system. However, if there is a OS corruption or if you want to update the ODA software quickly or a large period of time has passed between ODA shipment and deployment, a latest version of Bare Metal image may have been released.

You can also reimaging ODA if you want to convert a ODA Virtualized platform back to ODA Bare Metal deployment.

The command “oakcli show version” is used to display the version that is currently installed, compare the results with the MOS note 888888.1 to know the latest version available. If a latest version is available, download the latest image and re-image the ODA operating system.

The Bare Metal restore OS reimaging is specific to the node on which the procedure is executed and overwrites the local storage on that node. ODA reimaging does not Patch the firware (BIOS, ILOM, Local HDD and Shared HDD). It only re-image the local disk from an OS perspective. Use the Patch number 12999313 for Bare Metal re-imaging.

Note: Patch number 12999313 contains different releases of the Oracle Appliance Kit make sure to select the latest release.

In this article I have demonstrate how to reimage an Oracle Database Appliance X4-2 to Oracle Appliance Kit version 12.1.2.10.0.

Prerequisites:

A valid IP address is configured for ILOM
Root user access to ILOM (Default password changeme)
Latest Java software installed on the client (Laptop/Desktop)
Download latest ODA kit using patch number 12999313

Procedure to Reimage Oracle Database Appliance

– Open a web browser and enter hostname or IP address of the ILOM

https://10.10.1.20

– On the home page Expand Remote Control, Select Redirection, click Launch Remote Console

– Click Ok

– Java Application is starting

– Click Continue

– Click Run

– We can now see the ILOM console

– Under Devices menu, select CD-ROM Image

– Select the ISO image on your laptop/desktop

– We can see that the ISO image is attached to ILOM

– On left, under Expand Host Management, Select Host Control, Select Next Boot Device as CDROM and click Save

– On left, under Expand Host Management, Select Power Control, Select Power Cycle and Save

– Click OK to confirm

– Now the ODA server is restarted

– Reimage process start after the system restart. The Reimage process takes roughly between 1 to 2 hours

– When prompted select the Fiber or Copper cards for Public Interface and enter YES to reboot the server.

– Reimage process completed and prompted for login

– Verify the Oracle Database Appliace Kit Version

We have just completed Reimaging Oracle Database Appliance.

You should repeat the above steps on the second ODA server.

The reimaging process can take somewhere between one to two hours. To save time you can run the procedure in parallel on both server.

Conclusion:

In this article we have learned how to reimage an Oracle Database Appliance X4-2 to latest version. ILOM allows reimaging of the appliance server nodes via ISO images. In most cases, it is not be necessary to re-image the ODA operating system. There are situations where you reimage system such as corruption, or if you want to update the software to the latest version quickly.

Configure VNC On Oracle Database Appliance

By Netsoftmate on

July 3, 2017

- Uncategorized

Introduction:

To Deploy ODA you need GUI interface, to do this you make use of VNC server to connect with ODA and open GUI interface.

In this article I will demonstrate how to configure VNC on Oracle Database Appliance.

Configure VNC:

You can access database servers remotely by using tools such as PuTTY and Virtual Network Computing (VNC) which are freely available for download.

In most cases, accessing a database server in a command-line mode via PuTTY is enough. Sometimes we may need to access a database server to run GUI-based software. For example, to run runInstaller to install Oracle software or DBCA to create databases. In these cases, VNC a cool tool for running GUI-based sofware.

VNC allows you to run GUI interface on database server. It allows you to execute programs locally on the server, while only the screen output is sent to the VNC client on your desktop.

On ODA you can configure VNC in two ways:

startx command
vncserver command

Using startx command:

– Login to ILOM as super user (root) and execute startx command

– VNC screen is displayed

– Execute “oakcli deploy” to test GUI access

– Left click and exit to return back to ILOM session

Using vncserver command:

– Login to database server as Suport user (root), Check if vnc servers is running, Execute vncserver command to start vnc. Enter the root password first time and enter again to verify. Check if vnc server is started and note down the port number.

– Download VNC-Viewer and Click on VNC-Viewer on desktop

– ON VNC-Viewer page enter the ODA Node IP or hostname along with VNC server port

– Click Continue

– Enter the root password

– VNC screen is displayed

– Execute “oakcli deploy” to test GUI access

– Left click and exit to return back to ILOM session

Conclusion:

In this article we have learned about VNC and how to configure VNC on Oracle Database Appliance. Configure VNC is simple and straight forward. VNC comes handy when you want to run GUI-Based applications. To Deploy ODA you need GUI interface, to do this you make use of VNC server to connect with ODA and open GUI interface.

Oracle Database Appliance (ODA) and Its Components

By Netsoftmate on

July 3, 2017

- Uncategorized

Oracle Database Appliance:

Oracle Database Appliance (ODA) is a pre-configured, highly available Oracle Database Engineered system. ODA system consists of hardware, software, storage and networking. The hardware configuration is designed to provide redundancy and protection against single points of failures in the system.

The Oracle Database Appliance saves time and money by simplifying deployment, maintenance, and support of high availability Database solutions.

ODA consists of two physical servers (Node 0 and Node 1), a storage shelf and optionally an additional storage shelf. The two independent physical servers are interconnected and direct attached to SAS and SSD storage.

ODA is basically a 2-node RAC cluster database system running Oracle Linux operating (OEL), Oracle Database, Oracle Grid Infrastructure (Clusterware and ASM). All these together provides the Oracle Database high availability running on ODA.

Picture of ODA X6-2:

ODA X5-2 HA with optional Storage Expansion

ODA X6-2 HA

Advantages of Oracle Database Appliance:

Oracle marketed ODA using the tagline “Simple, Reliable and Affordable”.
– Simple: The ODA deployment made simple and easy to use by using the wizard based deployment.
– Reliable: The ODA platform provide complete high availability for Database and Application
– Affordable: With ODA you have the benefit of using Capacity-on-Demand Licensing. Pay for what you use.

Few other benefits includes:

– Saves Time and Money
– Single Vendor Support
– High Performance and High Availability
– End to End Monitoring for all components
– Reduced Cost
– Easy management and Supporting

Why ODA?

Traditional hardware deployments are complex, they can take from several weeks to months to implement. It depends on the several factors such as hardware procurement, deployment model choose by the organization and hardware & software certification.

The ODA deployment time is far less than a tranditional hardware deployment as ODA comes pre-configured with hardware and software in just on box. ODA includes Oracle Appliance Manager software to manage and maintain the
database server, patching/Upgrade ODA stack and troubleshooting.

H/W components of ODA

ODA consists of:

– 2 physical servers
– 1 Storage Shelf
– Optional additional storage shelf
– Networking
– Interconnect

S/W components of ODA

The Oracle Database Appliance runs Oracle Database Enterprise Edition, and customers have the choice of running Oracle Real Application Clusters (Oracle RAC) or Oracle RAC One Node.

• Oracle Enterprise Linux
• oracle Database Appliance Manager
• Oracle VM (Optional)
• Hardware Drivers
• Oracle Database 11g Enterprise Edition Release 2 and Oracle Database 12c Enterprise Edition
• Oracle Real Application Clusters One Node
• Oracle Real Application Clusters

Note: There are changes in ODA X6. Oracle introduced X6-2S, X6-2M and X6-2L which I will cover in a different article.

Oracle Database Appliance Deployment options:

You can deploy ODA in one of the following model:

1. Bare Metal Deployment
2. Virtualized Platform Deployment

Conclusion:

In this article we have learned what is Oracle Database Appliance and different hardware and software components of it. The Oracle Database Appliance saves time and money by simplifying deployment, maintenance, and support of high availability Database solutions.

Oracle Database Appliance (ODA) Firstnet Utility In Action

By Netsoftmate on

June 8, 2017

- Uncategorized

About Firstnet Utility

The “oakcli configure firstnet” command is used to configure an initial network on Oracle Database Appliance (ODA) that enables you to copy ODA End User Bundle software to ODA server.

oakcli configure firstnet allows you to establish the network interfaces for the Oracle Database Appliance upon first usage.

Once you have completed the reimaging of ODA servers, you should log onto the one of the node ILOM console and do the initial configuration of the Oracle Database Appliance network using the command firstnet.

The bond0 interface is configured when execute the firstnet utility.

Before running firstnet, ensure that you allocated IP addresses and verify that their entries in the DNS have been completed.

Execute firstnet utility

Connect to the ILOM console using browser or putty to configure the initial IP address for the node you are connected to.

Default password for root user on ILOM is “changeme”

login as: root
Using keyboard-interactive authentication.
Password:
Oracle(R) Integrated Lights Out Manager

Version 3.2.4.46.a r101689

Copyright (c) 2015, Oracle and/or its affiliates. All rights reserved.

Warning: password is set to factory default.

Hostname: ORACLESP-1113NML13N

->

(->) This means you are connect to ILOM now.

Start the Serial console by executing the following command. When prompted, enter y and then root and it’s password. Default root password for ODA servers is “welcome1”

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started. To stop, type ESC (

Oracle Linux Server release 6.8
Kernel 2.6.39-400.290.1.el6uek.x86_64 on an x86_64

oak1 login: root
Password:
Last login: Wed Jun 7 11:32:57 on tty1

oakcli used to execute the firstnet utility

[root@oak1 ~]# locate oakcli
/opt/oracle/oak/bin/oakcli

Now execute the firstnet utility as follows:

[root@oak1 ~]# /opt/oracle/oak/bin/oakcli configure firstnet
Select the Interface to configure the network on (bond0 bond1) [bond0]:
Configure DHCP on bond0 (yes/no) [no]:
INFO: You have chosen Static configuration
Enter the IP address to configure : 10.10.17.11
Enter the Netmask address to configure : 255.255.255.0
Enter the Gateway address to configure[10.10.17.1] : 10.10.15.1
INFO: Plumbing the IPs now
INFO: Restarting the network
Shutting down interface bond0: bonding: bond0: Removing slave eth2.
bonding: bond0: Warning: the permanent HWaddr of eth2 – 00:10:e0:62:3f:f2 – is still in use by bond0. Set the

HWaddr of eth2 to a different address to avoid conflicts.
bonding: bond0: releasing active interface eth2
bonding: bond0: Removing slave eth3.
bonding: bond0: releasing backup interface eth3
[ OK ]
Shutting down interface bond1: bonding: bond1: Removing slave eth4.
bonding: bond1: Warning: the permanent HWaddr of eth4 – 00:10:e0:62:3f:f4 – is still in use by bond1. Set the

HWaddr of eth4 to a different address to avoid conflicts.
bonding: bond1: releasing backup interface eth4
bonding: bond1: Removing slave eth5.
bonding: bond1: releasing backup interface eth5
[ OK ]
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: bonding: bond0: setting mode to active-backup (1).
bonding: bond0: Setting MII monitoring interval to 100.
bonding: bond0: Adding slave eth2.
bonding: bond0: enslaving eth2 as a backup interface with a down link.
bonding: bond0: Adding slave eth3.
bonding: bond0: enslaving eth3 as a backup interface with a down link.
bonding: bond0: Setting eth2 as primary slave.
Determining if ip address 172.16.202.71 is already in use for device bond0…
ixgbe 0000:20:00.0: eth2: NIC Link is Up 1 Gbps, Flow Control: RX
bonding: bond0: link status definitely up for interface eth2, 1000 Mbps full duplex.
bonding: bond0: making interface eth2 the new active one.
bonding: bond0: first active interface up!
[ OK ]
Bringing up interface bond1: bonding: bond1: setting mode to active-backup (1).
bonding: bond1: Setting MII monitoring interval to 100.
bonding: bond1: Adding slave eth4.
bonding: bond1: enslaving eth4 as a backup interface with a down link.
bonding: bond1: Adding slave eth5.
bonding: bond1: enslaving eth5 as a backup interface with a down link.
bonding: bond1: Setting eth4 as primary slave.
[ OK ]
Bringing up interface eth0: Determining if ip address 192.168.16.24 is already in use for device eth0…
ixgbe 0000:a0:00.0: eth0: detected SFP+: 3
ixgbe 0000:a0:00.0: eth0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ OK ]
Bringing up interface eth1: Determining if ip address 192.168.17.24 is already in use for device eth1…
ixgbe 0000:a0:00.1: eth1: detected SFP+: 4
ixgbe 0000:a0:00.1: eth1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ OK ]
[root@oak1 ~]#

Once the network interfaces have been configured, you need to test them by using the ping command on the node.

[root@oak1 ~]# ping 10.10.17.11
PING 172.16.202.71 (10.10.17.11) 56(84) bytes of data.
64 bytes from 10.10.17.11: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 10.10.17.11: icmp_seq=2 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=3 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=4 ttl=64 time=0.006 ms
64 bytes from 10.10.17.11: icmp_seq=5 ttl=64 time=0.005 ms

— 172.16.202.71 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4544ms
rtt min/avg/max/mdev = 0.005/0.010/0.027/0.009 ms

[root@oak1 ~]# ifconfig
bond0     Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
          inet addr:10.10.17.11 Bcast:10.10.17.255 Mask:255.255.255.0          UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)

bond1     Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
          UP BROADCAST MASTER MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0      Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B4
          inet addr:192.168.16.24 Bcast:192.168.16.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
          RX packets:138257 errors:0 dropped:0 overruns:0 frame:0
          TX packets:138436 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11200490 (10.6 MiB) TX bytes:11134648 (10.6 MiB)

eth1      Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B5
          inet addr:192.168.17.24 Bcast:192.168.17.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
          RX packets:138217 errors:0 dropped:0 overruns:0 frame:0
          TX packets:138434 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11197894 (10.6 MiB) TX bytes:11134800 (10.6 MiB)

eth2      Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)

eth3      Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
          UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth4      Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
          UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth5      Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
          UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:512371 errors:0 dropped:0 overruns:0 frame:0
          TX packets:512371 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:38908072 (37.1 MiB) TX bytes:38908072 (37.1 MiB)

Conclusion:
In this short article we have learned about Firstnet utility and have seen to use it to configure initial network to copy software to ODA servers.

Oracle Database Appliance (ODA) Standalone Configurator

By Netsoftmate on

June 3, 2017

- Uncategorized

Oracle Database Appliance (ODA) Configurator: The standalone Oracle Appliance Manager (ODA) configurator is a Java-based tool that enables you to generate your ODA deployment plan and validate your network settings before the actual ODA deployment.

ODA Configurator option:

ODA Congigurator can be run in offline or online mode.

Offline: Use the standalone ODA configurator to create an offline deployment plan and validate your network settings before the actual deployment.

Online: You can configure your system at the time of deployment. In that case, you can use the online ODA Configurator which is part of the base Oracle Database Appliance software.

You can run ODA Configurator before deployment by downloading the ODA Configurator on your local system which can be a Linux/UNIX, Windows or MAC system.

If you choose to run the ODA Configurator in offline mode, you can save your deployment plan in a configuration file at the end of an offline configurator session. When the time comes for the actual deploy, copy the configuration file to ODA and run the online Oracle Appliance Configurator and import it to deploy your saved plan.

Download ODA Configurator:

Enter the following URL in a web browser

http://www.oracle.com/technetwork/database/database-appliance/overview/oda-configurator-1928685.html

Accept the license and click on desired ODA Configurator version. Here I am downloading ODA Manager Configurator 12.1.2.10

Enter the login credentials to begin the download

If you are using Chrome the download status is shown at the bottom of the browser.

Running ODA Configurator:

If you wish to use ODA Configurator before deployment, then you can download and run the ODA Configurator on your system runing Linux/UNIX, Window or MAC operating system.

Extract the ODA Configurator software

On Window: Right Click and select Extract here
On Linux/Unix: use unzip command to extract the files

To start the ODA Configurator

On Windows: Double click the batch file config.bat
On Linux/Unix: Use the command ./config.sh

The ODA Configurator welcome/home page looks like this

Steps to Run ODA Configurator in Offline mode:

Start the ODA Configurator by double click config.bat on a Windows system (./config.sh on Linux).

On the welcome screen click next

On Configuration Type Screen you have various options:

In Select Configuration Type, you can choose from “Typica (Recommended)”, “Custom” or “SAP Application”.
Custom which will give you more flexibility to provide more information.

In Select Environment, You choose “Bare Metal” (Physical) if you want to deploy a Physical setup or “Virtualized Platform” for Virtualization setup.

In Select Hardware, you can choose the hardware you purchased. For Example: ODA-X5-2

Use “Browse” button if you have existing configuration file the was created earlier using ODA Configurator.

Click Next

On System Information screen, you can enter:

“System Name” – this will be your prefix for Hostname, Interface, SCAN name and ILOM

Select appropriate “Region” and “Timezone”

“Database Backup Location” – You have “Internal” and “External” option. If you choose “Internal” the space will be used from DATA and RECO disk groups. Oracle will internally size DATA and RECO ASM disk group to 40% and 60% repectively.

“Root password” – enter root password and confirm root password.

Disk Group Redundancy – Select HIGH or Normal

Accelerator Disk Group – select REDO or FLASH

Click Next

On Generic Network screen, enter:

Enter “Domain name” to be used
Check the box if no DNS Server available.
If you are using DNS and NTP server enter thier IPs.

Click Next

On Public Network Screen:

Enter the Node0 and Node1 IP, VIPs, SCAN IPs, Netmask and Gateway IP.
Select bond0 for interface. This is the only choice.
Enter ILOM IPs for ILOM0 and ILOM1, Netmask and Gateway IP

Click Next

On Other Network Screen, enter:

Enter the IPs for for Node0 and Node1 for net1, else click next to continue.

Click Next

On Database Information screen, enter:

If you don’t want to create an intial database uncheck the box and click next
if you wish to create an initial database, check the box and fill the required information.
“Database name” – Name for the database to be created
“Is Container Database” – Choose true if you want to create a container database else false to create a regular (non-container database)
“Database Type” – Choose from OLTP, DSS or In-Memory.
“Database Class” – Choose from the 10 different database template that comes with ODA
“Database Deployment” – Choose from RAC, RAC One Node or Enter Edition (Standalone)
“Database Files on Flash Storage” – If you wish to store database in Flash disk select true

Click Next

On Database Information Screen, Select:

Database Language, Block Size, Characterset, Territory and National Character set.

Click Next

On ASR Configuration Screen, Select:

“Configure Internal Oracle ASR” – If you wish to configure ASR on ODA Server and enert the Proxy server name, port number and MOS credentails

“Configure External Oracle AS” – If you wish to configure ASR on a separate server. Enter the ASR Manager Hostname or IP and port number.

Select SNMP 2 for configuring ASR

Note: If you don’t select to configure ASR now you can configure ASR post ODA deployment using oakcli commands

Click Next

On CloudFS Information Screen:

You can choose to configure ACFS file system called /cloudfs.

Click Next

On Network Validation Screen:

Click on “Run Validation” button to perform the network validation. It will ping every IP that has entered and attempts to resolve the names using DNS or /etc/hosts file.
If you are running ODA Configuration on a server which is not ODA or not part of same subnet select “Skip Nework Configuration”

Click Next

On the summary page:

Click Save button to save to store the configuration in a text file.

Click Finish to exit the ODA Configuration application.

Conclusion:
In this article we have learned to run the Standalone Oracle Database Appliance configuration in offline mode. ODA configuration is a Java-based tool that enables you to generate your ODA deployment plan and validate your network settings before the actual ODA deployment.

NO OLD POSTSPage 3 of 3NEXT POSTS

Good Contents Are Everywhere, But Here, We Deliver The Best of The Best.Please Hold on!

Home

About

Services

Blog

Contact

Validate Oracle Database Appliance (ODA)

Different Oracle Health Check Tools

Oracle Database Appliance: Create Database

Oracle Database Appliance Bare Metal Setup In A Nutshell

ODA : Update Firmware On ODA Post Reimage

Reimage Oracle Database Appliance (ODA)

Configure VNC On Oracle Database Appliance

Oracle Database Appliance (ODA) and Its Components

Oracle Database Appliance (ODA) Firstnet Utility In Action

Oracle Database Appliance (ODA) Standalone Configurator

ABOUT US

Services

CONTACT US

Follow Us!