Friday 27 October 2017

Exadata Storage Software 18c released

Oracle Released Exadata Storage Software version 18.1.0.0.0 on October 2nd 2017.
Patch (25342756) for Storage server software and Infiniband Switch software For more details review the MOS note 2288392.1 ESS version 18.1.0.0.0 supports the following Oracle Database software releases:
  • 12.2.0.1.0
  • 12.1.0.2.0
  • 12.1.0.1.0
  • 11.2.0.4.0
  • 11.2.0.3.0
Exadata 18.1.0.0.0 Software and Image files for upgrade are:
  • Patch 25342756 - Storage server software (18.1.0.0.0.170915.1) and InfiniBand switch software (2.2.7-1)
  • Patch 26829586 - Database server bare metal / domU ULN ISO image (18.1.0.0.0.170915.1)
  • Patch 26829591 - Database server dom0 ULN OVM channel ISO image (18.1.0.0.0.170915.1)

Exadata Storage Software 18c update released

Another Exadata Storage Software 18c update released!! Oracle Released Exadata Storage Software version 18.1.1.0.0 on October 26th 2017. Earlier release was ESS version 18.1.0.0.0 on October 2nd 2017. - Patch (26875767) for Storage server software and Infiniband Switch software For more details review the MOS "Exadata 18.1.1.0.0 release and patch (26875767) (Doc ID 2311786.1)" ESS version 18.1.1.0.0 supports the following Oracle Database software releases: - 12.2.0.1.0 - 12.1.0.2.0 - 12.1.0.1.0 - 11.2.0.4.0 - 11.2.0.3.0 Exadata 18.1.1.0.0 Software and Image files for upgrade are: - Patch 26875767 - Storage server software (18.1.1.0.0.171018) and InfiniBand switch software (2.2.7-1) - Patch 26923500 - Database server bare metal / domU ULN exadata_dbserver_18.1.1.0.0_x86_64_base OL6 channel ISO image (18.1.1.0.0.171018) - Patch 26923501 - Database server dom0 ULN exadata_dbserver_dom0_18.1.1.0.0_x86_64_base OVM channel ISO image (18.1.1.0.0.171018)

Thursday 26 October 2017

Exadata: Clear Hardware Fault Post Hardware Replacement

Introduction

I was working on a hardware (Processor) failure on Exadata X5-2 Compute node. There was an Automatic SR generated for the hardware failure, Oracle Field Engineer contacted us for hardware  replacement and replaced the faulty hardware. Everything went smooth until this point. But we noticed that even after the hardware replacement the fault was not cleared automatically. So we ended up clearing the hardware fault manually.

In this article I will demonstrate how to clear a hardware (Processor) fault manually. The same steps can be used for clearing all type of faulty hardware by replacing the hardware name/path.


  • To identify faulty hardware, execute the ILOM following command:

[root@dm01db01 ~]# ipmitool sunoem cli "show -d properties -level all /SYS/MB fault_state==Faulted"
Connected. Use ^D to exit.
-> show -d properties -level all /SYS/MB fault_state==Faulted
  /SYS/MB/P1
    Properties:
        type = Host Processor
        ipmi_name = MB/P1
        fru_name = Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
        fru_version = 02
        fru_part_number = 060F
        fault_state = Faulted
        clear_fault_action = (none)


-> Session closed
Disconnected

From the output above we can see that Processor P1 (/SYS/MS/P1) is faulty and replacement.

You can also check for hardware failures using Web ILOM

Steps to Clear a hardware fault post hardware replacement:


  • Identify the hardware fault

[root@dm01db01 ~]# ipmitool sunoem cli "show -d properties -level all /SYS/MB fault_state==Faulted"
Connected. Use ^D to exit.
-> show -d properties -level all /SYS/MB fault_state==Faulted
  /SYS/MB/P1
    Properties:
        type = Host Processor
        ipmi_name = MB/P1
        fru_name = Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
        fru_version = 02
        fru_part_number = 060F
        fault_state = Faulted
        clear_fault_action = (none)


-> Session closed
Disconnected


  • Connect to problematic Compute node ILOM

[root@dm01db01 ~]# ssh dm01db01-ilom
The authenticity of host 'dm01db01-ilom (10.10.10.11)' can't be established.
RSA key fingerprint is 52:45:af:c4:08:29:c4:6a:15:d9:5f:6d:14:cb:23:b1.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'dm01db01-ilom,10.10.10.11' (RSA) to the list of known hosts.
Password:

Oracle(R) Integrated Lights Out Manager

Version 3.2.8.24 r114580

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

Warning: HTTPS certificate is set to factory default.

Hostname: dm01db01-ilom

-> show -d properties -level all /SYS/MB fault_state==Faulted
  /SYS/MB/P1
    Properties:
        type = Host Processor
        ipmi_name = MB/P1
        fru_name = Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
        fru_version = 02
        fru_part_number = 060F
        fault_state = Faulted
        clear_fault_action = (none)


  • Execute the following command to clear the fault

-> set /SYS/MB/P1 clear_fault_action=true
Are you sure you want to clear /SYS/MB/P1 (y/n)? y
Set 'clear_fault_action' to 'true'


  • Verify the fault is cleared

-> show -d properties -level all /SYS/MB fault_state==Faulted
show: Query found no matches.

No Faulty hardware found.

Verify from Web ILOM


  • Exit from ILOM

-> exit
Connection to dm01db01-ilom closed.
[root@dm01db01 ~]#

Conclusion

In this article we have learned how to identify the hardware fault and clear it post hardware replacement.

Tuesday 10 October 2017

Exadata: How To Mount diag.iso On An Exadata X5 Server From A NFS Server

Introduction

I was testing Exadata Compute node snapshot restore procedure on an Exadata X5-2. As per of testing I had to start the machine in special mode using diag.iso, the easiest option is to use WEB ILOM to mount he diag.iso, but for some technical reason or BUG I was unable to mount diag.iso using WEB ILOM. Oracle provided a procedure to mount the diag.iso image using an NFS server.

In this article I will demonstrate step by step procedure on how mount diag.iso image using NFS Server along with the output.


Steps to mount diag.iso on an Exadata Compute node from NFS server:


  • First login to the Compute node ILOM CLI or SSH from another Compute node 

[root@dm01db01 ~]# ssh dm01db01-ilom
Password:

Oracle(R) Integrated Lights Out Manager

Version 3.2.8.24 r114580

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

Warning: HTTPS certificate is set to factory default.

Hostname: dm01db01-ilom

->


  • Execute the following command to mount diag.iso from a NFS server

Syntax:
set /SP/services/kvms/host_storage_device/remote/ server_URI=NFS_or_Samba_URI_file_location


-> set /SP/services/kvms/host_storage_device/remote server_URI=nfs://10.10.10.1:/export/dm01/backup1/diag.iso
Set 'server_URI' to 'nfs://10.10.10.1:/export/dm01/backup1/diag.iso'


  • Verify the server_URI to make it is poing to correct NFS location

-> show /SP/services/kvms/host_storage_device/remote server_URI

  /SP/services/kvms/host_storage_device/remote
    Properties:
        server_URI = nfs://10.10.10.1:/export/dm01/backup1/diag.iso


  • Execute the following command to Enable storage redirection:

-> set /SP/services/kvms/host_storage_device/ mode=remote
Set 'mode' to 'remote'


  • Check the status of redirection:

-> show /SP/services/kvms/host_storage_device/ status

  /SP/services/kvms/host_storage_device
    Properties:
        status = operational

Note -  Redirection is active if the status is set to either Operational or Connecting.


  • Now set the next boot device to cdrom

-> set /HOST boot_device=cdrom
Set 'boot_device' to 'cdrom'


  • Verify the next boot device is pointing to cdrom:

-> show /HOST

 /HOST
    Targets:
        console
        diag
        provisioning

    Properties:
        boot_device = cdrom
        generate_host_nmi = (Cannot show property)

    Commands:
        cd
        set
        show


  • Execute the following command to Reboot the Server:

-> reset /SYS
Are you sure you want to reset /SYS (y/n)? y
Performing hard reset on /SYS

At this time the server boot from diag.iso, enter into interactive mode, restore/recovery the machine or correct the OS configuration that you have and when you are done, disable redirection.




Steps to Disable steps Server_URI and Storage redirection


  • Execute the following command to disable Storage redirection:

-> set /SP/services/kvms/host_storage_device/ mode=disabled
Set 'mode' to 'disabled'

-> show /SP/services/kvms/host_storage_device/ mode

  /SP/services/kvms/host_storage_device
    Properties:
        mode = disabled


  • Execute the following command to disable Server_URI:

-> set /SP/services/kvms/host_storage_device/remote server_URI=''
Set 'server_URI' to ''

-> show /SP/services/kvms/host_storage_device/remote server_URI

  /SP/services/kvms/host_storage_device/remote
    Properties:
        server_URI = (none)


  • Verify the Next boot device:

-> show /HOST

/HOST
    Targets:
        console
        diag
        provisioning

    Properties:
        boot_device = default
        generate_host_nmi = (Cannot show property)

    Commands:
        cd
        set
        show


  • Reboot the server to boot with the normal Exadata kernel

-> reset /SYS
Are you sure you want to reset /SYS (y/n)? y
Performing hard reset on /SYS


Conclusion

In this article we have learned how to mount diag.iso on Exadata compute node from NFS Server. If the WEB ILOM is not working for some reason then mounting the diag.iso using NFS server comes handy. The process to mount is diag.iso from NFS Server is very simply and much faster.

Friday 6 October 2017

Oracle Database Appliance Virtualized Platform Deployment In A Nutshell

Introduction

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.

You can deploy ODA in one of the following model:

  • Bare Metal Deployment
  • Virtualized Platform Deployment

By default, ODA ships with the latest version of Bare Metal Operating System. To deploy Oracle Database Appliance Virtualized platform, you must re-image ODA using Virtualized OS ISO image.

To identify ODA deployment type, execute the following command:

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

The output shows that it is a Bare Metal deployment. If you see the string VM-Dom0, it means that is a Virtualized platform.

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 Oracle Database Appliance Virtualized Platform deployment.




Pre-Deployment Steps

  • Decide the type of Deployment
    • Bare Metal (BM) or Virtualized Platform (VM)

  • 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 administrator 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.

Read more on ODA configuration at: http://netsoftmate.blogspot.in/2017/06/oracle-database-appliance-oda.html

  • Download ODA Virtualized Platform patches

Download the below patches from MOS note 888888.1
Read the MOS note 888888.1 carefully before downloading the patches.

As of writing the latest Virtualized OS ISO image and latest ODA_BASE is 12.1.2.12.0

    • ODA Virtualized Platform Patches - Choose the correct release from the drop down  menu.

Patch 16186163 - Oracle Database Appliance VM ISO Image. (DOM0)  
Patch 16186172 - Oracle Database Appliance VM Template (ODA_BASE)

Note: Oracle Grid Infrastructure and Oracle Database software are installed by deploying ODA_BASE

Deployment Steps

  • Receive Oracle Database Appliance delivery at Data Center
  • Unpack Oracle Database Appliance box
  • Read the Manually carefully that comes with ODA box
  • Mount ODA components as per guidelines
  • Connect the Power and Network Cables. Read the ODA Setup poster for your model, for example: Setup Poster X6-2 HA
  • Power On the PSU
  • Power On the Systems. Turn on the power to  Storage shelf first and the power on the ODA Node 0 and Node 1.
  • Configure and Setup Oracle ILOM Configuration.

ILOM configuration via Serial port (Doc ID 1395445.1)
How to Setup ILOM (Doc ID 1393191.1)

  • Using Virtualized OS ISO image perform the complete reimage of both the nodes - MUST

  • Validate the cable connections to the Storage shelf

# oakcli validate -c storageTopology

Note: If you see any errors or warning, connect the cables correctly. DO NOT ignore the error or the warning.

  • Network Configuration -  Configure firstnet
    • Connect to ODA node 0 using ILOM and run firstnet

# /opt/oracle/oak/bin/oakcli configure firstnet

    • Verify you can ping node 0 and node 1
    • Respond to the prompts (Domain Name, DNS Server, Hostname, Network, IP address and Gateway

  • Copy the downloaded ODA_BASE zip files to DOM0 under /OVS
    • Copy to /OVS or file system where there is more stapce

  • Unzip the zip files copied under /OVS
# cd /OVS
# unzip unzip p16186172_1212120_Linux-x86-64_1of3.zip
# unzip unzip p16186172_1212120_Linux-x86-64_2of3.zip
# unzip unzip p16186172_1212120_Linux-x86-64_3of3.zip


unzipping the zip files will create two files, oda_base_12.1.2.12.gz01, oda_base_12.1.2.12.gz02 and oda_base_12.1.2.12.gz03

  • Merge or concatenate the above 2 files as below:
# cat oda_base_12.1.2.12.gz01 oda_base_12.1.2.12.gz02 oda_base_12.1.2.12.gz03 > oda_base_12.1.2.12.tar.gz

This file name will be used in next step.

  • Deploy ODA_BASE
    • From Node0 (oak1-dom0), deploy oda_base by executing the following command as root user

# /opt/oracle/oak/bin/oakcli deploy oda_base

Enter the file name with full path /OVS/oda_base_12.1.2.12.tar.gz when prompted

    • Select the number of cores for ODA_BASE and network for ODA_BASE

  • Verify the ODA_BASE domain

# xm list
# /opt/oracle/oak/bin/oakcli show oda_base

  • VNC Configuration and Connection

To Deploy ODA you need GUI interface, to do this you make use of VNC server to connect with ODA and open GUI interface.
You can also connect to Web ILOM and execute xstart to start VNC

Connect to oda_base using vncviewer with <oak1-dom0>:5900

  • Complete the ODA Virtualized Platform deployment
    • Connect to ILOM as root user and start the X window.
    • Execute the following command to complete ODA Deployment

# /opt/oracle/oak/bin/oakcli deploy



  • Verify the ODA Deployment

# oakcli show env_hw
# oakcli show version -detail

Post Deployment and Cleanup

  • Validate ODA Deployment

# /opt/oracle/oak/bin/oakcli show version -detail
# crsctl status res -t
# /opt/oracle/oak/bin/oakcli validate -c storagetopology
# oakcli show dbhomes -detail
# oakcli validate -d
# oakcli validate -c OSDiskStorage
# oakcli validate -c SharedStorage
# oakcli validate -c SystemComponents
# oakcli validate -c NetworkComponents
# oakcli validate -c DiskCalibration

  • ODA Redeploy or Cleanup - Optional

To perform a redeploy for the Oracle Database Appliance is a very simple task and is executed with the cleanupDeploy.pl script

# /opt/oracle/oak/onecmd/cleanupDeploy.pl

Once this cleanupDeploy.pl script completes, you can rerun the deployment process using the Oracle Appliance Manager utility discussed earlier.


Conclusion

In this article we have learned the steps required to perform an Oracle Database Appliance Virtualized Platform Deployment. It is very important to consider the deployment steps carefully to avoid issues. By default, ODA ships with the latest version of Bare Metal Operating System. To deploy Oracle Database Appliance Virtualized platform, you must re-image ODA using Virtualized OS ISO image.

Thursday 5 October 2017

Oracle Database Appliance X7-2 Family - First Look

Oracle Database Appliance X7-2 HA - First look

October 2017 Oracle announced Oracle Database Appliance X7-2 (Small, Medium and HA). ODA X7-2 comes with more computing resources compared with X6-2 Models.
Let's take a quick look at few benefits of ODA followed by the technical specification on ODA X7-2 Small/Medium and HA.

Benfits of ODA:

  • Software, server, storage, and networking engineered and optimized to run Oracle Database and applications.
  • Supports Oracle Database Standard Edition, Standard Edition One, Standard Edition 2, and Enterprise Edition.
  • Optimized for Cloud
  • Capacity on Demand Licensing - Reduced Cost
  • Easy Deployment and management


Oracle Database Appliance X7-2 HA specification
  • 32 cores per server (72 cores in total for 2 servers)
  • 384 GB physical memory per server expandable upto 1.5TB (768 GB memory in total for 2 servers)
  • Storage Shelf
    • High Capacity: 150 TB HDD raw capacity per shelf
    • High Performance: 64 TB SDD raw capacity per shelf
  • 3.2 TB raw capacity for redo log storage per shelf
  • Choice of 10GBase-T or 10/25 GbE SFP28 public networking


For more information on the technical specification loot at the ODA X7-2 HA Data Sheet at:
http://www.oracle.com/technetwork/database/database-appliance/learnmore/odax7-2-ha-ds-3933489.pdf
https://www.oracle.com/engineered-systems/database-appliance/x7-2-ha/index.html#ct07tabcontent2

Oracle Database Appliance X7-2 Small specification

  • One server 
  • 1 Intel Xeon processor, 10 Cores
  • 192GB Physical memory expandable upto 384GB 
  • Choice of 10GBase-T or 10/25 GbE SFP28 public networking
  • 12.8TB NVMe raw storage


Oracle Database Appliance X7-2 Medium specification

  • One server 
  • 2 Intel Xeon processor, 36 Cores
  • 384 GB Physical memory expandable upto 768GB 
  • Choice of 10GBase-T or 10/25 GbE SFP28 public networking
  • 12.8 TB NVMe raw storage with optional expansion to 51.2 TB NVMe raw storage


For more information on the technical specification loot at the ODA X7-2 S/M Data Sheet at:

http://www.oracle.com/technetwork/database/database-appliance/learnmore/odax7-2sm-ds-3933491.pdf


Wednesday 4 October 2017

Exadata Database Machine X7-2 - First look

Exadata Database Machine X7-2

On October 2nd at Oracle Open World, Oracle announced the next-generation Oracle Exadata Database Machine X7 with significant hardware and software enhancements in overall performance, storage capacity, network bandwidth, and automation. Exadata X7 delivers extreme performance and reliability to run the largest, most business-critical database workloads.

Exadata X7-2 quick glance:
  • Latest Intel Xeon Scalable Processors (384 core in a Full Rack)
  • 50% increase in Physical memory (upto 12TB in a full Rack)
  • 100% increase in the capacity of Extreme Flash storage (716.8TB in a full Rack)
  • 25% increase in disk capacity (1680TB in a full Rack)
  • A full rack Exadata X7 system has: 
    • Raw capacity of 1.7 petabytes of disk storage or
    • 720 terabytes of NVMe all-Flash storage.
  • Ethernet network bandwidth has increased by 150 percent from 10 to 25Gb/s

Exadata X7-2 pictorial representation


For detail on Exadata X7-2 and it's models visit:

https://www.oracle.com/corporate/pressrelease/oow17-oracle-exadata-x7-100217.html

http://www.oracle.com/technetwork/database/exadata/exadata-x7-2-ds-3908482.pdf

Comparing Oracle Database Appliance X8-2 Model Family

September 2019 Oracle announced Oracle Database Appliance X8-2 (Small, Medium and HA). ODA X8-2 comes with more computing resources com...