Good Contents Are Everywhere, But Here, We Deliver The Best of The Best.Please Hold on!
Database Management Services, Oracle Database Management Solution, Oracle Databases, Oracle Exadata



An engineered system comprising of Compute Nodes, Storage Cells and Infiniband  – all of it packaged inside a single physical cabinet called “Exadata Rack


Exadata Hardware Generation At A Glance

 

Exadata Database Machine X8-2




0

Uncategorized
Oracle announced the next-generation Oracle Exadata X8 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.


Oracle Exadata X8-2 quick glance:


  • – Latest Intel Xeon (8260) Processors (2.4GHz) 2*24 cores per database server (384 core in a Full Rack)
  •  
  • – Exadata X8 Capacity-on-Demand enables at least 14 cores per server
  •  
  • – Delivers up to 60 percent faster throughput than previous models
  •  
  • – NO changes in Database server Physical memory (upto 12TB in a full Rack)
  •  
  • – Latest Intel Xeon (5218) Processors (2.3GHz) 2*16 cores per Storage server (448 core in a Full Rack)
  •  
  • – NO increase in the capacity of Extreme Flash storage (716.8TB in a full Rack)
  •  
  • – 40% increase in disk capacity (2352TB in a full Rack)
  •  
  • – Exadata X8 introduces new Exadata storage option – Extended (XT) Storage Server
  •  
  • – Each Exadata XT Storage Server includes twelve 14 TB SAS disk drives
  •  
  • – A full rack Exadata X8-2 system has:
    •  
    • – Raw capacity of 2.3 petabytes of disk storage & 358.4TB Flash
    •  
    • – 720 terabytes of NVMe all-Flash storage
    •  
    • – Raw capacity of 2.3 petabytes of disk storage & No flash
  •  
  • – Additional network 2x 10/25 Gb optical Ethernet (client – optional)
  •  
  • – Available in Oracle Public Cloud – Oracle Database Exadata Cloud Service





For more information please visit –

https://www.oracle.com/a/ocom/docs/engineered-systems/exadata/exadata-x8-2-ds.pdf
 

https://www.oracle.com/a/ocom/docs/engineered-systems/exadata/exadata-x8-8-ds.pdf



0

Oracle provides “Exachk” utility to conduct a comprehensive Health Check on Oracle SuperCluster to validate hardware, firmware and configuration. Exachk Utility is available for Oracle Engineered Systems such as Exadata (V2 and above), Exalogic, Exalytics, SuperCluster, MiniCluster, ZDLRA & Big Data. 

When Exachk is run from the primary LDOM as user ‘root’ it will discover and run exachk utility for each component:
  • Configuration checks for Compute nodes, Storage cells and InfiniBand Switches
  • Grid Infrastructure, Database and ASM and Operating System software checks

When Exachk is run in a Database zone or Virtualized environment it will collect data for:
  • All RAC Node
  • All Database Instance
  • Grid Infrastructure

You can also run Exachk on a specific component such as:
  • Database Servers
  • Storage Cells
  • Infiniband Switches
  • Grid Infrastructure, Database & ASM and so on

It is recommended to run Exachk as root user and have SSH equivalence setup in the SuperCluster. But you can run Exachk as ordinary user and without having root ssh setup.

It is recommended to execute the latest exachk at the following situation:
  • Monthly
  • Before any planned maintenance activity
  • Immediately after completion of planned maintenance activity
  • Immediately after an outage or incident

Exachk Binary and output file location:
  • Default Exachk Location: /opt/oracle.SupportTools/exachk
  • Defautl Exachk Output Location: /opt/oracle.SupportTools/exachk


Courtesy Oracle


Steps to Deploy and Execute Exachk utility on SuperCluster


  • Download Latest Exachk Utility
You can download the latest Exachk from MOS note 1070954.1

  • Download deploy_exachk.sh script to deploy and install Exachk in all Primary LDOM and in each Zone

  • Copy the downloaded Exachk utility and deploy_exachk.sh into /opt/oracle.SupportTools
# cd /opt/oracle.SupportTools
# mv exachk Exachk-bkp

  • Deploy Exachk as follows
# cd /opt/oracle.SupportTools/
# ./deploy_exachk.sh exachk.zip
# ls -ltr
# cd exachk
# ls -l exachk

As of writing the latest Exachk available is 18.2.0_20180518

  • Verify Exachk Version on LDOM
# cd /opt/oracle.SupportTools/exachk
# ./exachk -v

  • To verify Exachk version on all zones in a LDOM
# zoneadm list | grep -v global > zone_list
# hostname >> zone_list
# /opt/oracle.supercluster/bin/dcli -g zone_list -l root /opt/oracle.SupportTools/exachk/exachk -v

Note: root RSA keys should be set up for SSH

  • Execute Exachk on Primary LDOM or Global Zone
# cd /opt/oracle.SupportTools/exachk
# ./exachk

  • Execute Exachk in non-global zone local zone
Login to non-global zone local zone using zlogin and execute the following commands

# zlogin <hostname>
# cd /opt/oracle.SupportTools/exachk
# ./exachk

Important Note: In zones there is currently an issue with discovery, and so one must set the RAT_ORACLE_HOME and RAT_GRID_HOME environment variables in some cases.


Conclusion
In this article we have learned to perform Oracle SuperCluster Stack Health Check using Exachk utility. Exachk Utility is available for Oracle Engineered Systems such as Exadata (V2 and above), Exalogi, Exalytics, SuperCluster, MiniCluster, ZDLRA & Big Data.

1

ASRexacheck utility can be executed to verify the ASR deployment. Oracle Auto Service Request (ASR) is a secure, scalable, customer-installable software feature of warranty and Oracle Support Services that provides auto-case generation when common hardware component faults occur.

It is important to note that, ASR is not a system management or monitoring tool. It is developed & designed to open Oracle Automatic Service Requests when specific hardware faults are detected on Oracle products that are qualified for ASR. Oracle Exadata Database Machine is a qualified production for Oracle ASR.

You can execute ASRexacheck in any of the following 2 ways:
  • As part of the Oracle Exadata Database Machine exachk
  • Stand-alone mode on a single node or multiple nodes

In this article we will demonstrate how to execute ASRexacheck on in Stand-alone mode on a single server and mutliple servers using dcli.


  • Ensure that the ASRexacheck verison is 4.x. If is is older than 4.x, then download the latest ASRexacheck from the MOS note below.

Engineered Systems ASR Configuration Check tool (asrexacheck version 4.x) (Doc ID 2103715.1)

  • ASRexacheck Download and & Upgrade steps
    • Download the asrexacheck zip file from the MOS note.
    • Copy the asrexacheck zip to the following directory: /opt/oracle.SupportTools/
    • Unzip the asrexacheck utility
          # cd /opt/oracle.SupportTools/
          # unzip asrexacheck_43.zip
    • Change the running permissions to execute
                    # chmod 755 /opt/oracle.SupportTools/asrexacheck
    • Verify the asrexacheck version
                    # /opt/oracle.SupportTools/asrexacheck –v

  • ASRexacheck execution On a single Exadata server

[root@dm01db01 oracle.SupportTools]# /opt/oracle.SupportTools/asrexacheck
asrexacheck version: 4.0
Current time: 2018-04-09 10:42:51

================================================================================
SYSTEM CONFIGURATION
================================================================================
Product name           : Exadata X5-2
Product serial         : AK003XXXXX
Component name         : ORACLE SERVER X5-2
Component serial       : 1546XX111X
Engineered System type : Exadata
Server type            : COMPUTE
Image version          : 18.1.4.0.0.180125.3
OS IP Address          : 10.10.10.1
OS Hostname            : dm01db01
OS version             : 4.1.12-94.7.8.el6uek.x86_64
ILOM IP Address        : 10.10.10.14
ILOM Hostname          : dm01db01-ilom
ILOM version           : 4.0.0.24

================================================================================
NETWORK
================================================================================
Interface  IP Address                      Hostname        Route   fromIP
——————————————————————————–
bondeth0   10.20.16.1                     dm0101          NO
eth0       10.10.10.1                     dm01db01        YES

================================================================================
ASR
================================================================================
Destination     Hostname        Rule Type  DBMCLI Port Level   Community Version
——————————————————————————–
10.10.10.1     dm01db01          1               8162 minor   LocalMSV3user       3
192.168.10.1  oragwserver                   YES   162           public
192.168.10.1  oragwserver        2                162 minor     public      2c

[OK] Exactly one OS and ILOM IP coincide (192.168.10.1)
* Validation:
[OK] OS Test event sent to 192.168.10.1:162
[OK] ILOM Test event sent to 192.168.10.1:162

Time elapsed script execution: 00:04:44
Zipfile /var/log/asrexacheck/asrexacheck_dm01db01_20180409T154251.zip of the outputs created


  • ASRexacheck execution on all Exadata Compute nodes

[root@dm01db01 oracle.SupportTools]# dcli -g ~/dbs_group -l root ‘/opt/oracle.SupportTools/asrexacheck’
dm01db01: asrexacheck version: 4.0
dm01db01: Current time: 2018-04-09 10:42:51
dm01db01:
dm01db01: ================================================================================
dm01db01: SYSTEM CONFIGURATION
dm01db01: ================================================================================
dm01db01: Product name           : Exadata X5-2
dm01db01: Product serial         : AK003XXXXX
dm01db01: Component name         : ORACLE SERVER X5-2
dm01db01: Component serial       : 1546XX111X
dm01db01: Engineered System type : Exadata
dm01db01: Server type            : COMPUTE
dm01db01: Image version          : 18.1.4.0.0.180125.3
dm01db01: OS IP Address          : 10.10.10.1
dm01db01: OS Hostname            : dm01db01
dm01db01: OS version             : 4.1.12-94.7.8.el6uek.x86_64
dm01db01: ILOM IP Address        : 10.10.10.14
dm01db01: ILOM Hostname          : dm01db01-ilom
dm01db01: ILOM version           : 4.0.0.24
dm01db01:
dm01db01: ================================================================================
dm01db01: NETWORK
dm01db01: ================================================================================
dm01db01: Interface  IP Address                      Hostname        Route   fromIP
dm01db01: ——————————————————————————–
dm01db01: bondeth0   10.20.16.1                     dm0101          NO
dm01db01: eth0       10.10.10.1                     dm01db01        YES
dm01db01:
dm01db01: ================================================================================
dm01db01: ASR
dm01db01: ================================================================================
dm01db01: Destination     Hostname        Rule Type  DBMCLI Port Level   Community Version
dm01db01: ——————————————————————————–
dm01db01: 10.10.10.1     dm01db01          1               8162 minor   LocalMSV3user       3
dm01db01: 192.168.10.1  oragwserver                   YES   162           public
dm01db01: 192.168.10.1  oragwserver        2                162 minor     public      2c
dm01db01:
dm01db01: [OK] Exactly one OS and ILOM IP coincide (192.168.10.1)
dm01db01: * Validation:
dm01db01: [OK] OS Test event sent to 192.168.10.1:162
dm01db01: [OK] ILOM Test event sent to 192.168.10.1:162
dm01db01:
dm01db01: Time elapsed script execution: 00:04:44
dm01db01: Zipfile /var/log/asrexacheck/asrexacheck_dm01db01_20180409T154251.zip of the outputs created
dm01db02: asrexacheck version: 4.0
dm01db02: Current time: 2018-04-09 10:42:51
dm01db02:
dm01db02: ================================================================================
dm01db02: SYSTEM CONFIGURATION
dm01db02: ================================================================================
dm01db02: Product name           : Exadata X5-2
dm01db02: Product serial         : AK003XXXXX
dm01db02: Component name         : ORACLE SERVER X5-2
dm01db02: Component serial       : 1546XX11XX
dm01db02: Engineered System type : Exadata
dm01db02: Server type            : COMPUTE
dm01db02: Image version          : 18.1.4.0.0.180125.3
dm01db02: OS IP Address          : 10.10.10.2
dm01db02: OS Hostname            : dm01db02
dm01db02: OS version             : 4.1.12-94.7.8.el6uek.x86_64
dm01db02: ILOM IP Address        : 10.10.10.15
dm01db02: ILOM Hostname          : dm01db02-ilom
dm01db02: ILOM version           : 4.0.0.24
dm01db02:
dm01db02: ================================================================================
dm01db02: NETWORK
dm01db02: ================================================================================
dm01db02: Interface  IP Address                      Hostname        Route   fromIP
dm01db02: ——————————————————————————–
dm01db02: bondeth0   10.20.16.3                     dm0102          NO
dm01db02: eth0       10.10.10.2                     dm01db02        YES
dm01db02:
dm01db02: ================================================================================
dm01db02: ASR
dm01db02: ================================================================================
dm01db02: Destination     Hostname        Rule Type  DBMCLI Port Level   Community Version
dm01db02: ——————————————————————————–
dm01db02: 10.10.10.2     dm01db02          1               8162 minor   LocalMSV3user       3
dm01db02: 192.168.10.1  oragwserver                   YES   162           public
dm01db02: 192.168.10.1  oragwserver        2                162 minor     public      2c
dm01db02:
dm01db02: [OK] Exactly one OS and ILOM IP coincide (192.168.10.1)
dm01db02: * Validation:
dm01db02: [OK] OS Test event sent to 192.168.10.1:162
dm01db02: [OK] ILOM Test event sent to 192.168.10.1:162
dm01db02:
dm01db02: Time elapsed script execution: 00:04:46
dm01db02: Zipfile /var/log/asrexacheck/asrexacheck_dm01db02_20180409T154251.zip of the outputs created
dm01db03: asrexacheck version: 4.0
dm01db03: Current time: 2018-04-09 10:42:51
dm01db03:
dm01db03: ================================================================================
dm01db03: SYSTEM CONFIGURATION
dm01db03: ================================================================================
dm01db03: Product name           : Exadata X5-2
dm01db03: Product serial         : AK003XXXXX
dm01db03: Component name         : ORACLE SERVER X5-2
dm01db03: Component serial       : 1547XX10XX
dm01db03: Engineered System type : Exadata
dm01db03: Server type            : COMPUTE
dm01db03: Image version          : 18.1.4.0.0.180125.3
dm01db03: OS IP Address          : 10.10.10.3
dm01db03: OS Hostname            : dm01db03
dm01db03: OS version             : 4.1.12-94.7.8.el6uek.x86_64
dm01db03: ILOM IP Address        : 10.10.10.16
dm01db03: ILOM Hostname          : dm01db03-ilom
dm01db03: ILOM version           : 4.0.0.24
dm01db03:
dm01db03: ================================================================================
dm01db03: NETWORK
dm01db03: ================================================================================
dm01db03: Interface  IP Address                      Hostname        Route   fromIP
dm01db03: ——————————————————————————–
dm01db03: bondeth0   10.20.16.5                     dm0103          NO
dm01db03: eth0       10.10.10.3                     dm01db03        YES
dm01db03:
dm01db03: ================================================================================
dm01db03: ASR
dm01db03: ================================================================================
dm01db03: Destination     Hostname        Rule Type  DBMCLI Port Level   Community Version
dm01db03: ——————————————————————————–
dm01db03: 10.10.10.3     dm01db03          1               8162 minor   LocalMSV3user       3
dm01db03: 192.168.10.1  oragwserver                   YES   162           public
dm01db03: 192.168.10.1  oragwserver        2                162 minor     public      2c
dm01db03:
dm01db03: [OK] Exactly one OS and ILOM IP coincide (192.168.10.1)
dm01db03: * Validation:
dm01db03: [OK] OS Test event sent to 192.168.10.1:162
dm01db03: [OK] ILOM Test event sent to 192.168.10.1:162
dm01db03:
dm01db03: Time elapsed script execution: 00:04:43
dm01db03: Zipfile /var/log/asrexacheck/asrexacheck_dm01db03_20180409T154251.zip of the outputs created


  • At the end of successful ASRexacheck execution, you will receive 2 Test ASR emails, one from Management host and another from Management ILOM host. If you don’t receive the Test ASR emails then you must work with Oracle ASR Management team to resolve the ASR Manager issue.




  • You can also execute ASRexacheck on Exadata Storage cells using below commands.

[root@dm01cel01 ~]# /opt/oracle.SupportTools/asrexacheck
[root@dm01db01 ~]# dcli -g ~/cell_group -l root ‘/opt/oracle.SupportTools/asrexacheck’

Conclusion

In this article we have learned how to verify ASR deployment using ASRexacheck utility. ASR is not a monitoring tool, it is designed to open ASR when specific hardware faults are detected on Oracle products that are qualified for ASR. Oracle Exadata Database Machine is a qualified production for Oracle ASR.

0