Category: Database Management Services

Learn whats in and whats out of the database management eco-system

Exadata On-Premises Vs Exadata Cloud Service Vs Exadata Cloud at Customer | Whats Best For You?
What are the different Exadata Deployment Option available?

– Exadata On-Premises

– Exadata Cloud Service

– Exadata Cloud at Customer

What is Oracle Exadata Database Machine?

Exadata Database Machine is an Engineered System which consists of Compute nodes, Storage cells and Infiniband Switches or RoCE Switches (starting X8M).

Exadata Database Machine or simply known as Exadata is:
- – An Engineered System
  – A preconfigured combination of balanced Hardware and unique software
  
  – A unique platform for running Oracle Databases
  
  – Consists of Compute Grid, Storage Grid and Network Grid
  
  – A fully integrated platform for Oracle Database
  
  – Ideal for Database Consolidation platform
  
  – It provides High Availability and High Performance for all types of Workloads
The Oracle Exadata Database Machine is an Engineered System designed to deliver extreme performance and high availability for all type of Oracle database workloads (OLTP, OLAP & Mixed Workload).

Exadata Database Machine Components
- 1. Compute nodes (Database Server Grid)
- 2. Exadata Storage Server (Storage Server Grid)
- 3. Network (Network Grid)
- - – Exadata Infiniband switches
  - – Exadata RoCE switches – From Exadata X8M
- 4. Other Components
- - – Cisco Switch, PDUs
Oracle Exadata Cloud Service

Oracle Database Exadata Cloud Service delivers the world’s most advanced database cloud by combining the world’s #1 database technology and Exadata, the most powerful database platform, with the simplicity, agility and elasticity of a cloud-based deployment.

Oracle Exadata Cloud @ Customer

Exadata C@C is ideal for customers desiring cloud benefits but cannot move their databases to the public cloud due to sovereignty laws, industry regulations, corporate policies, security requirements, network latency, or organizations that find it impractical to move databases away from other tightly coupled on-premises IT infrastructure. Oracle Exadata C@C delivers the world’s most advanced database cloud to customers who require their databases to be located on-premises. It is identical to Oracle’s Exadata Cloud Service but located in customers’ own data centers and managed by Oracle.

Oracle Exadata Deployment Comparison

Let’s compare each Exadata deployment to learn about them in detail so we can choose the right deployment option for our Business need.
July 14, 2020
5 Reasons Why you Should Run your Oracle Database on Oracle Exadata

If you are looking for highest levels of database performance for your Oracle database then, Oracle Exadata is an outstanding solution. It delivers finest performance for mixed data, data warehousing (DW), analytics, and OLTP (online transaction processing) workloads. Enriched with a variety of deployment options, it lets you run your Oracle Database and other data workloads anywhere you need, whether its on-premises or in the Oracle Cloud. Oracle Exadata storage provides a cutting-edge technology which is simple to use, manage and provides mission-critical accessibility and reliability. Here are 5 reasons stating why should you run the Oracle Database on Oracle Exadata.

1. Bespoke for Oracle Database

Following a standard approach to build your database infrastructure will hamper your business growth. With time, databases grow, which means, your business needs more servers, more storage solutions and more labor to manage it. As a result, the management cost will go up and there is a huge exposure to risk of errors, ultimately hampering your business growth. That’s why each business, big or small, needs a new approach that’s engineered to cater the critical database workloads.

The only technique to handle these critical database workloads is through Oracle Exadata. It is specially equipped to provide high storage bandwidth to seamlessly manage the Oracle Database and other data workloads. Oracle Exadata, as a part of Oracle Engineered System offers a highly integrated platform that delivers more power with less hardware. It eliminates the IT complexity while supplying greater performance, scalability, security and data protection.

2. Increase Employee Productivity

Timely delivery of persuasive data that supports business operations and lessens the time required to deliver new business applications will surely result in better revenue. Oracle Exadata’s congregated and optimized infrastructure platform for database workloads helps the IT staff to spend less time on everyday operations and work more towards other IT development efforts. Accidental outages have less effect on employees and business operations that have lesser database related failures.

The consolidated Oracle Exadata platform provides an economical base for Oracle database operations. It increases employee productivity and helps grow revenues with less cost and complexity. With an enhanced performance up to 100X faster, accessing the data becomes easy and you can engage with customers quickly. With the same power, you can consolidate your databases onto a single platform, and deliver more than four times the density

3. Achieve Operational Benefits

Businesses that rely on multiple vendors may face problems in managing a complex database infrastructure. Retaining and managing each database and server overstrains IT staff, and establishing new applications can take longer than usual. You may also need IT specialists to take care of each different component. As the number of applications and their associated databases increases, your admin costs go up, and so will your data center footprint.

Oracle Exadata delivers greater database and application performance with less hardware—and fewer licenses. Oracle Exadata, from Oracle Engineered Systems means easier upgrades, tuning, patching, observing and support, so you can manage your costs. They process transactions faster, complete queries in less time, and have decreased load and backup recovery times.

4. Maximize Accessibility

Positive data security and database uptime are critical components that directly impact the business operations and revenue progress. Database collapse makes it tough to establish dependable security, plan and policies for sensitive data. There are too many points of control to monitor and maintain. A larger base is vulnerable to attack and there’s hardly enough budget for the specialist skills vital to manage it.

That’s the reason; businesses use Oracle Exadata to run their most important Oracle database and other data workloads. With software and hardware operational together, Oracle Exadata eliminates system downtime, using its in-built flexibility and redundancy. With Oracle Maximum Availability Architecture, you can get the ultimate in invincible uptime. The benefits include, less business impact from outages, less IT impact in managing downtime and reliable application and developer productivity.

5. Invest in the Cloud

Businesses always plan for a simple and comprehensive cloud strategy and application. Ideally, businesses strategize to invest in an architecture offering an apt pathway to a cloud consumption model for the future. A full-proof plan that is flexible to mix and match on-premises deployment with a well-matched public cloud option, whether that’s for development, improvement and testing or ensuring business endurance.

Oracle Exadata offers the best of both worlds for the database and the business. Businesses can either purchase and manage on-premises Oracle Exadata or choose an Oracle Database Cloud Exadata Service. Oracle Cloud service is equivalent to an on-premises Oracle Exadata, just with a different consumption model. That’s why all the components of Oracle Engineered System are a powerful set of options. They are designed with the same architecture, with all the same benefits. All you need to do is choose which consumption model works best for you.

About Netsoftmate Technologies Inc.

Netsoftmate is an Oracle Gold Partner and a boutique IT services company specializing in installation, implementation and 24/7 support for Oracle Engineered Systems like Oracle Exadata, Oracle Database Appliance, Oracle ZDLRA, Oracle ZFS Storage and Oracle Private Cloud Appliance. Apart from OES, we have specialized teams of experts providing round the clock remote database administration support for any type of database and cyber security compliance and auditing services.

Feel free to get in touch with us by signing up on the link below –

May 5, 2020
All You Need To Know About Oracle Autonomous Health Framework Execution
Recently Oracle introduced “Autonomous Health Framework”. Oracle Autonomous Health Framework contains Oracle ORAchk, Oracle EXAchk, and Oracle Trace File Analyzer.

You have access to Oracle Autonomous Health Framework as a value add-on to your existing support contract. There is no additional fee or license required to run Oracle Autonomous Health Framework.

In this article we will learn how to Install, setup and execute AHF for Oracle Exadata Database machine in detail.

Step 1: Download AHF for Linux operating system as shown below. Here we are using the wget command to download file directly to the server. If you don’t have proxy you can download the file MOS to your desktop and copy it the server using WinSCP.

[root@dm01db01 ~]# cd /u01/app/oracle/software/

[root@dm01db01 software]# mkdir Exachk

[root@dm01db01 software]# cd Exachk/

[root@dm01db01 Exachk]# export use_proxy=on

[root@dm01db01 Exachk]# export http_proxy=”webproxy.netsoftmate.come:80/”
- Download the AHF zip file
[root@dm01db01 Exachk]# wget –http-user=abdul.mohammed@netsoftmate.com –http-password=************ –no-check-certificate –output-document=AHF-LINUX_v20.1.1.zip “https://updates.oracle.com/Orion/Services/download/AHF-LINUX_v20.1.1.zip?aru=23443431&patch_file=AHF-LINUX_v20.1.1.zip”
- Download the latest cvu. This will be used by the exachk to run the cluster verification
[root@dm01db01 Exachk]# wget –http-user=abdul.mohammed@netsoftmate.com –http-password=************ –no-check-certificate –output-document=cvupack_Linux_x86_64.zip “https://download.oracle.com/otndocs/products/clustering/cvu/cvupack_Linux_x86_64.zip”

[root@dm01db01 Exachk]# ls -ltr

total 356748

-rw-r–r– 1 root root 365267646 Mar 17 16:02 AHF-LINUX_v20.1.1.zip

-rw-r–r– 1 root root 293648959 Jul 13 2018 cvupack_Linux_x86_64.zip

Step 2: Unzip the AHF zip file

[root@dm01db01 Exachk]# unzip AHF-LINUX_v20.1.1.zip

Archive: AHF-LINUX_v20.1.1.zip

inflating: README.txt

inflating: ahf_setup

[root@dm01db01 Exachk]# ./ahf_setup -v

AHF Build ID : 20110020200317092524

AHF Build Platform : Linux

AHF Build Architecture : x86_64

Step 3: Execute the AHF setup

[root@dm01db01 Exachk]# ./ahf_setup

AHF Installer for Platform Linux Architecture x86_64

AHF Installation Log : /tmp/ahf_install_344489_2020_04_06-12_20_51.log

Starting Autonomous Health Framework (AHF) Installation

AHF Version: 20.1.1.0.0 Build Date: 202003170925

TFA is already installed at : /u01/app/11.2.0.4/grid/tfa/dm01db01/tfa_home

Installed TFA Version : 122111 Build ID : 20170612164756

Default AHF Location : /opt/oracle.ahf

Do you want to install AHF at [/opt/oracle.ahf] ? [Y]|N : Y

AHF Location : /opt/oracle.ahf

AHF Data Directory stores diagnostic collections and metadata.

AHF Data Directory requires at least 5GB (Recommended 10GB) of free space.

Choose Data Directory from below options :
1. /u01/app/oracle [Free Space : 50454 MB]
2. Enter a different Location
Choose Option [1 – 2] : 1

AHF Data Directory : /u01/app/oracle/oracle.ahf/data

exachk scheduler is already running at : /root/Exachk

Installed exachk version : EXACHK VERSION: 19.2.0_20190717

Stopping exachk scheduler

Copying exachk configuration from /root/Exachk

Shutting down TFA : /u01/app/11.2.0.4/grid/tfa/dm01db01/tfa_home

Copying TFA Data Files from /u01/app/11.2.0.4/grid/tfa/dm01db01/tfa_home

Uninstalling TFA : /u01/app/11.2.0.4/grid/tfa/dm01db01/tfa_home

Do you want to add AHF Notification Email IDs ? [Y]|N : Y

Enter Email IDs separated by space : abdul.mohammed@netsoftmate.com

AHF will also be installed/upgraded on these Cluster Nodes :
1. dm01db02
2. dm01db03
3. dm01db04
The AHF Location and AHF Data Directory must exist on the above nodes

AHF Location : /opt/oracle.ahf

AHF Data Directory : /u01/app/oracle/oracle.ahf/data

Do you want to install/upgrade AHF on Cluster Nodes ? [Y]|N : Y

Extracting AHF to /opt/oracle.ahf

Configuring TFA Services

Copying TFA Data Files to AHF

Discovering Nodes and Oracle Resources

TFA will configure Storage Cells using SSH Setup:

.———————————–.

|   | EXADATA CELL | CURRENT STATUS |

+—+————–+—————-+

| 1 | dm01cel01   | ONLINE         |

| 2 | dm01cel02   | ONLINE         |

| 3 | dm01cel03   | ONLINE         |

| 4 | dm01cel04   | ONLINE         |

| 5 | dm01cel05   | ONLINE         |

| 6 | dm01cel06   | ONLINE         |

| 7 | dm01cel07   | ONLINE         |

‘—+————–+—————-‘

Not generating certificates as GI discovered

Starting TFA Services

.——————————————————————————-.

| Host      | Status of TFA | PID    | Port | Version    | Build ID             |

+———–+—————+——–+——+————+———————-+

| dm01db01 | RUNNING       | 365382 | 5000 | 20.1.1.0.0 | 20110020200317092524 |

‘———–+—————+——–+——+————+———————-‘

Running TFA Inventory…

Adding default users to TFA Access list…

.——————————————————————.

|                   Summary of AHF Configuration                   |

+—————–+————————————————+

| Parameter       | Value                                          |

+—————–+————————————————+

| AHF Location    | /opt/oracle.ahf                                |

| TFA Location    | /opt/oracle.ahf/tfa                            |

| Exachk Location | /opt/oracle.ahf/exachk                         |

| Data Directory | /u01/app/oracle/oracle.ahf/data                |

| Repository      | /u01/app/oracle/oracle.ahf/data/repository     |

| Diag Directory | /u01/app/oracle/oracle.ahf/data/dm01db01/diag |

‘—————–+————————————————‘

Retrieving legacy exachk wallet details …

Storing exachk wallet details into AHF config/wallet …

Starting exachk daemon from AHF …

AHF install completed on dm01db01

Installing AHF on Remote Nodes :

AHF will be installed on dm01db02, Please wait.

Installing AHF on dm01db02 :

[dm01db02] Copying AHF Installer

[dm01db02] Running AHF Installer

AHF will be installed on dm01db03, Please wait.

Installing AHF on dm01db03 :

[dm01db03] Copying AHF Installer

[dm01db03] Running AHF Installer

AHF will be installed on dm01db04, Please wait.

Installing AHF on dm01db04 :

[dm01db04] Copying AHF Installer

[dm01db04] Running AHF Installer

AHF binaries are available in /opt/oracle.ahf/bin

AHF is successfully installed

Moving /tmp/ahf_install_251936_2020_04_06-13_07_32.log to /u01/app/oracle/oracle.ahf/data/dm01db01/diag/ahf/

Step 4: Verify AHF setup

[root@dm01db01 Exachk]# cd /opt/oracle.ahf/

[root@dm01db01 oracle.ahf]# ls -ltr

total 36

drwxr-xr-x 7 root root 4096 Nov 19 02:38 python

drwxr-xr-x 5 root root 4096 Mar 17 11:25 ahf

drwxr-xr-x 6 root root 4096 Mar 17 11:25 common

drwxr-x–x 5 root root 4096 Mar 17 11:25 jre

drwxr-xr-x 8 root root 4096 Apr 6 12:28 exachk

drwxr-x–x 2 root root 4096 Apr 6 12:28 analyzer

-rw-r–r– 1 root root 1057 Apr 6 12:28 install.properties

drwxr-x–x 9 root root 4096 Apr 6 12:28 tfa

drwxr-x–x 2 root root 4096 Apr 6 12:28 bin

[root@dm01db01 oracle.ahf]# cd exachk/

[root@dm01db01 exachk]# ls -ltr

total 81772

-rw-r–r– 1 root root   186651 Mar 17 11:20 exachk.pyc

-rw-r–r– 1 root root 65423079 Mar 17 11:23 collections.dat

-rw-r–r– 1 root root 9674765 Mar 17 11:23 rules.dat

-rw-r–r– 1 root root 8341706 Mar 17 11:24 Apex5_CollectionManager_App.sql

-rw-r–r– 1 root root    43473 Mar 17 11:24 sample_user_defined_checks.xml

-r–r–r– 1 root root     3217 Mar 17 11:24 user_defined_checks.xsd

drwxr-xr-x 2 root root     4096 Mar 17 11:24 messages

drwxr-xr-x 2 root root     4096 Mar 17 11:25 web

drwxr-xr-x 3 root root     4096 Mar 17 11:25 lib

drwxr-xr-x 2 root root     4096 Mar 17 11:25 build

drwxr-xr-x 2 root root     4096 Apr 6 12:28 bash

-rwxr-xr-x 1 root root    25788 Apr 6 12:28 exachk

Step 5: unzip the cvu zip file under AHF home as show below

[root@dm01db01 Exachk]# unzip cvupack_Linux_x86_64.zip -d /opt/oracle.ahf/common/cvu

[root@dm01db01 Exachk]# ls -ltr /opt/oracle.ahf/common/cvu

total 92

drwxrwxr-x 7 root root 4096 Jun 13 2018 jdk

drwxrwxr-x 3 root root 4096 Jun 13 2018 srvm

drwxrwxr-x 3 root root 4096 Jun 13 2018 has

drwxrwxr-x 3 root root 4096 Jun 13 2018 crs

drwxrwxr-x 3 root root 4096 Jun 13 2018 suptools

drwxrwxr-x 3 root root 4096 Jun 13 2018 oss

drwxrwxr-x 7 root root 4096 Jun 13 2018 cv

drwxrwxr-x 3 root root 4096 Jun 13 2018 xdk

drwxrwxr-x 2 root root 4096 Jun 13 2018 utl

drwxrwxr-x 4 root root 4096 Jun 13 2018 rdbms

drwxrwxr-x 6 root root 4096 Jun 13 2018 install

drwxrwxr-x 4 root root 4096 Jun 13 2018 deinstall

drwxrwxr-x 4 root root 4096 Jun 13 2018 clone

drwxrwxr-x 8 root root 4096 Jun 13 2018 oui

drwxrwxr-x 3 root root 4096 Jun 13 2018 diagnostics

drwxrwxr-x 3 root root 4096 Jun 13 2018 oracore

drwxrwxr-x 3 root root 4096 Jun 13 2018 nls

drwxrwxr-x 3 root root 4096 Jun 13 2018 jdbc

drwxrwxr-x 3 root root 4096 Jun 13 2018 dbjava

drwxrwxr-x 6 root root 4096 Jun 13 2018 network

drwxrwxr-x 2 root root 4096 Jun 13 2018 jlib

drwxrwxr-x 2 root root 4096 Jun 13 2018 lib

drwxrwxr-x 2 root root 4096 Jun 13 2018 bin

Note: If you don’t download and extract the cvupack you will get the following warning message.

“Either Cluster Verification Utility pack (cvupack) does not exist at /opt/oracle.ahf/common/cvu or it is an old or invalid cvupack”

Step 6: Execute Exachk for Exadata

[root@dm01db01 ~]# cd /opt/oracle.ahf/exachk/

[root@dm01db01 exachk]# ./exachk

Checking ssh user equivalency settings on all nodes in cluster for root

Node dm01db02 is configured for ssh user equivalency for root user

Node dm01db03 is configured for ssh user equivalency for root user

Node dm01db04 is configured for ssh user equivalency for root user

Searching for running databases . . . . .

. . . .

List of running databases registered in OCR
1. testdb
2. orcldb
3. All of above
4. None of above
Select databases from list for checking best practices. For multiple databases, select 3 for All or comma separated number like 1,2 etc [1-4][3].

Searching out ORACLE_HOME for selected databases.

. . . . . . .

.

Checking Status of Oracle Software Stack – Clusterware, ASM, RDBMS

. . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

——————————————————————————————————-

                                                 Oracle Stack Status

——————————————————————————————————-

Host Name       CRS Installed RDBMS Installed    CRS UP    ASM UP RDBMS UP    DB Instance Name

——————————————————————————————————-

dm01db01                  Yes          Yes          Yes      Yes      Yes          orcldb1 testdb1

dm01db02                  Yes          Yes         Yes      Yes      Yes          testdb2 orcldb2

dm01db03                  Yes          Yes          Yes      Yes      Yes          orcldb3 testdb3

dm01db04                  Yes          Yes          Yes      Yes      Yes          testdb4 orcldb4

——————————————————————————————————-

Copying plug-ins

. .

Node dm01cel01-priv2 is configured for ssh user equivalency for root user

Node dm01cel02-priv2 is configured for ssh user equivalency for root user

Node dm01cel03-priv2 is configured for ssh user equivalency for root user

Node dm01cel04-priv2 is configured for ssh user equivalency for root user

Node dm01cel05-priv2 is configured for ssh user equivalency for root user

Node dm01cel06-priv2 is configured for ssh user equivalency for root user

Node dm01cel07-priv2 is configured for ssh user equivalency for root user

. . . . . . . . . . . . . . . . . . . . . . . . . .

dm01sw-ibb01 is configured for ssh user equivalency for root user

.

dm01sw-iba01 is configured for ssh user equivalency for root user

dm01sw-iba01 is configured for ssh user equivalency for root user

*** Checking Best Practice Recommendations ( Pass / Warning / Fail ) ***

. .

Collections and audit checks log file is

/u01/app/oracle/oracle.ahf/data/dm01db01/exachk/exachk_dm01db01_orcldb_040620_12376/log/exachk.log

Starting to run exachk in background on dm01db02

Starting to run exachk in background on dm01db03

Starting to run exachk in background on dm01db04

============================================================

              Node name – dm01db01

============================================================

Collecting – ASM Disk Group for Infrastructure Software and Configuration

Collecting – ASM Diskgroup Attributes

Collecting – ASM diskgroup usable free space

Collecting – ASM initialization parameters

Collecting – Database Parameters for testdb database

Collecting – Database Parameters for orcldb database

Collecting – Database Undocumented Parameters for orcldb database

Collecting – RDBMS Feature Usage for orcldb database

Collecting – CPU Information

Collecting – Clusterware and RDBMS software version

Collecting – Compute node PCI bus slot speed for infiniband HCAs

Collecting – Kernel parameters

Collecting – Maximum number of semaphore sets on system

Collecting – Maximum number of semaphores on system

Collecting – OS Packages

Collecting – Patches for Grid Infrastructure

Collecting – Patches for RDBMS Home

Collecting – RDBMS patch inventory

Collecting – Switch Version Information

Collecting – number of semaphore operations per semop system call

Collecting – CRS user limits configuration

Collecting – CRS user time zone check

Collecting – Check alerthistory for non-test open stateless alerts [Database Server]

Collecting – Check alerthistory for stateful alerts not cleared [Database Server]

Collecting – Clusterware patch inventory

Collecting – Discover switch type(spine or leaf)

Collecting – Enterprise Manager agent targets

Collecting – Exadata Critical Issue DB09

Collecting – Exadata Critical Issue EX30

Collecting – Exadata Critical Issue EX36

Collecting – Exadata Critical Issue EX56

Collecting – Exadata Critical Issue EX57

Collecting – Exadata Critical Issue EX58

Collecting – Exadata critical issue EX48

Collecting – Exadata critical issue EX55

Collecting – Exadata software version on database server

Collecting – Exadata system model number

Collecting – Exadata version on database server

Collecting – HCA firmware version on database server

Collecting – HCA transfer rate on database server

Collecting – Infrastructure Software and Configuration for compute

Collecting – MaxStartups setting in sshd_config

Collecting – OFED Software version on database server

Collecting – Obtain hardware information

Collecting – Operating system and Kernel version on database server

Collecting – Oracle monitoring agent and/or OS settings on ADR diagnostic directories

Collecting – Raid controller bus link speed

Collecting – Review Non-Exadata components in use on the InfiniBand fabric

Collecting – System Event Log

Collecting – Validate key sysctl.conf parameters on database servers

Collecting – Verify Data Network is Separate from Management Network

Collecting – Verify Database Server Disk Controller Configuration

Collecting – Verify Database Server Physical Drive Configuration

Collecting – Verify Database Server Virtual Drive Configuration

Collecting – Verify Disk Cache Policy on database server

Collecting – Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Database Server]

Collecting – Verify ILOM Power Up Configuration for HOST_AUTO_POWER_ON

Collecting – Verify ILOM Power Up Configuration for HOST_LAST_POWER_STATE

Collecting – Verify IP routing configuration on database servers

Collecting – Verify InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers

Collecting – Verify Master (Rack) Serial Number is Set [Database Server]

Collecting – Verify Quorum disks configuration

Collecting – Verify RAID Controller Battery Temperature [Database Server]

Collecting – Verify RAID disk controller CacheVault capacitor condition [Database Server]

Collecting – Verify RAID disk controller CacheVault capacitor condition [Database Server]

Collecting – Verify TCP Segmentation Offload (TSO) is set to off

Collecting – Verify available ksplice fixes are installed [Database Server]

Collecting – Verify basic Logical Volume(LVM) system devices configuration

Collecting – Verify database server InfiniBand network MTU size

Collecting – Verify database server disk controllers use writeback cache

Collecting – Verify database server file systems have Check interval = 0

Collecting – Verify database server file systems have Maximum mount count = -1

Collecting – Verify imageinfo on database server

Collecting – Verify imageinfo on database server to compare systemwide

Collecting – Verify installed rpm(s) kernel type match the active kernel version

Collecting – Verify key InfiniBand fabric error counters are not present

Collecting – Verify no database server kernel out of memory errors

Collecting – Verify proper ACFS drivers are installed for Spectre v2 mitigation

Collecting – Verify service exachkcfg autostart status on database server

Collecting – Verify the localhost alias is pingable [Database Server]

Collecting – Verify the InfiniBand Fabric Topology (verify-topology)

Collecting – Verify the Master Subnet Manager is running on an InfiniBand switch

Collecting – Verify the Name Service Cache Daemon (NSCD) configuration

Collecting – Verify the Subnet Manager is properly disabled [Database Server]

Collecting – Verify the currently active image status [Database Server]

Collecting – Verify the ib_sdp module is not loaded into the kernel

Collecting – Verify the storage servers in use configuration matches across the cluster

Collecting – Verify the vm.min_free_kbytes configuration

Collecting – Verify there are no files present that impact normal firmware update procedures [Database Server]

Collecting – collect time server data [Database Server]

Collecting – root time zone check

Collecting – verify asr exadata configuration check via ASREXACHECK on database server

Starting to run root privileged commands in background on storage server dm01cel01 (192.168.1.6)

Starting to run root privileged commands in background on storage server dm01cel02 (192.168.1.8)

Starting to run root privileged commands in background on storage server dm01cel03 (192.168.1.10)

Starting to run root privileged commands in background on storage server dm01cel04 (192.168.1.16)

Starting to run root privileged commands in background on storage server dm01cel05 (192.168.1.18)

Starting to run root privileged commands in background on storage server dm01cel06 (192.168.1.20)

Starting to run root privileged commands in background on storage server dm01cel07 (192.168.1.22)

Starting to run root privileged commands in background on infiniband switch (dm01sw-ibb01)

Starting to run root privileged commands in background on infiniband switch (dm01sw-iba01)

Collections from storage server:

————————————————————

Collections from Infiniband Switch:

————————————————————

Collecting – Exadata Critical Issue IB5

Collecting – Exadata Critical Issue IB6

Collecting – Exadata Critical Issue IB8

Collecting – Hostname in /etc/hosts

Collecting – Infiniband Switch NTP configuration

Collecting – Infiniband subnet manager status

Collecting – Infiniband switch HCA status

Collecting – Infiniband switch HOSTNAME configuration

Collecting – Infiniband switch firmware version

Collecting – Infiniband switch health

Collecting – Infiniband switch localtime configuration

Collecting – Infiniband switch module configuration

Collecting – Infiniband switch subnet manager configuration

Collecting – Infiniband switch type(Spine or leaf)

Collecting – Infrastructure Software and Configuration for switch

Collecting – Verify average ping times to DNS nameserver [IB Switch]

Collecting – Verify no IB switch ports disabled due to excessive symbol errors

Collecting – Verify the localhost alias is pingable [IB Switch]

Collecting – Verify there are no unhealthy InfiniBand switch sensors

Collecting – sm_priority configuration on Infiniband switch

Data collections completed. Checking best practices on dm01db01.

————————————————————

FAIL =>     Exadata software version on database server does not meet certified platinum configuration

FAIL =>     Oracle database does not meet certified platinum configuration for /u01/app/oracle/product/11.2.0.4/dbhome

WARNING => Database parameter AUDIT_SYS_OPERATIONS should be set to the recommended value on testdb1 instance

WARNING => Database parameter AUDIT_SYS_OPERATIONS should be set to the recommended value on orcldb1 instance

INFO =>     Oracle GoldenGate failure prevention best practices

INFO =>     One or more non-default AWR baselines should be created for orcldb

WARNING => Non-default database Services are not configured for orcldb

WARNING => Database parameter processes should be set to recommended value on testdb1 instance

WARNING => Database parameter processes should be set to recommended value on orcldb1 instance

FAIL =>     _reconnect_to_cell_attempts parameter in cellinit.ora is not set to recommended value

FAIL =>     Oracle monitoring agent and Operating systems settings on Automatic diagnostic repository directories are not correct or not all targets have been scanned or not all diagnostic directories found

FAIL =>     Storage Server user “CELLDIAG” should exist

FAIL =>     Downdelay attribute is not set to recommended value on bonded client interface

FAIL =>     One or more of SYSTEM, SYSAUX, USERS, TEMP tablespaces are not of type bigfile for orcldb

FAIL =>     The initialization parameter cluster_database_instances should be at the default value for testdb

FAIL =>     The initialization parameter cluster_database_instances should be at the default value for orcldb

WARNING => SYS or SYSTEM objects were found to be INVALID for orcldb

WARNING => There are non-Exadata components in use on the InfiniBand fabric

INFO =>     Database parameter AUDIT_TRAIL should be set to the recommended value for testdb

INFO =>     Database parameter AUDIT_TRAIL should be set to the recommended value for orcldb

FAIL =>     Memlock settings do not meet the Oracle best practice recommendations for /u01/app/oracle/product/11.2.0.4/dbhome

WARNING => All disk groups should have compatible.advm attribute set to recommended values

WARNING => All disk groups should have compatible.rdbms attribute set to recommended values

WARNING => Database has one or more dictionary managed tablespace for orcldb

CRITICAL => System is exposed to Exadata Critical Issue EX58

CRITICAL => System is exposed to Exadata Critical Issue EX58

FAIL =>     Some data or temp files are not autoextensible for orcldb

WARNING => Key InfiniBand fabric error counters should not be present

CRITICAL => One or more log archive destination and alternate log archive destination settings are not as recommended for orcldb

FAIL =>     Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on testdb1 instance

FAIL =>     Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on orcldb1 instance

FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on testdb1 instance

FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on orcldb1 instance

FAIL =>     Database parameter PARALLEL_ADAPTIVE_MULTI_USER is not set to recommended value on testdb1 instance

FAIL =>     Database parameter PARALLEL_ADAPTIVE_MULTI_USER is not set to recommended value on orcldb1 instance

FAIL =>     Database parameter PARALLEL_THREADS_PER_CPU is not set to recommended value on testdb1 instance

FAIL =>     Database parameter PARALLEL_THREADS_PER_CPU is not set to recommended value on orcldb1 instance

FAIL =>     Database parameter OS_AUTHENT_PREFIX is not set to recommended value on testdb1 instance

FAIL =>     Database parameter OS_AUTHENT_PREFIX is not set to recommended value on orcldb1 instance

FAIL =>     Database parameter sql92_security is not set to recommended value on testdb1 instance

FAIL =>     Database parameter sql92_security is not set to recommended value on orcldb1 instance

FAIL =>     Database parameter COMPATIBLE should be set to recommended value for testdb

FAIL =>     Database parameter COMPATIBLE should be set to recommended value for orcldb

CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for orcldb

CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for testdb

FAIL =>     Flashback on PRIMARY is not configured for orcldb

FAIL =>     Flashback on STANDBY is not configured for testdb

INFO =>     Operational Best Practices

INFO =>     Database Consolidation Best Practices

INFO =>     Computer failure prevention best practices

INFO =>     Data corruption prevention best practices

INFO =>     Logical corruption prevention best practices

INFO =>    Database/Cluster/Site failure prevention best practices

INFO =>     Client failover operational best practices

INFO =>     Verify the percent of available celldisk space used by the griddisks

WARNING => Application objects were found to be invalid for orcldb

CRITICAL => Database control files are not configured as recommended for testdb

CRITICAL => Database control files are not configured as recommended for orcldb

WARNING => ASM parameter ASM_POWER_LIMIT is not set to the default value.

INFO =>    While initialization parameter LOG_ARCHIVE_CONFIG is set it should be verified for your environment on Standby Database for testdb

WARNING => Redo log files should be appropriately sized for testdb

WARNING => Redo log files should be appropriately sized for orcldb

FAIL =>     Table AUD$[FGA_LOG$] should use Automatic Segment Space Management for orcldb

INFO =>     Database failure prevention best practices

WARNING => Database has one or more dictionary managed tablespace for orcldb

FAIL =>     Primary database is not protected with Data Guard (standby database) for real-time data protection and availability for orcldb

FAIL =>     Database parameter LOG_BUFFER is not set to recommended value on orcldb1 instance

INFO =>     Storage failures prevention best practices

INFO =>     Software maintenance best practices

CRITICAL => The data files should be recoverable for testdb

CRITICAL => The data files should be recoverable for orcldb

FAIL =>     FRA space management problem file types are present without an RMAN backup completion within the last 7 days for testdb

INFO =>     Oracle recovery manager(rman) best practices

WARNING => control_file_record_keep_time should be within recommended range [1-9] for testdb

INFO =>     Exadata Critical Issues (Doc ID 1270094.1):- DB1-DB4,DB6,DB9-DB44, EX1-EX60 and IB1-IB3,IB5-IB8

Collecting patch inventory on CRS_HOME /u01/app/11.2.0.4/grid

Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/11.2.0.4/dbhome

Copying results from dm01db02 and generating report. This might take a while. Be patient.

.

============================================================

              Node name – dm01db02

============================================================

Collecting – CPU Information

Collecting – Clusterware and RDBMS software version

Collecting – Compute node PCI bus slot speed for infiniband HCAs

Collecting – Kernel parameters

Collecting – Maximum number of semaphore sets on system

Collecting – Maximum number of semaphores on system

Collecting – OS Packages

Collecting – Patches for Grid Infrastructure

Collecting – Patches for RDBMS Home

Collecting – RDBMS patch inventory

Collecting – number of semaphore operations per semop system call

Collecting – CRS user limits configuration

Collecting – CRS user time zone check

Collecting – Check alerthistory for non-test open stateless alerts [Database Server]

Collecting – Check alerthistory for stateful alerts not cleared [Database Server]

Collecting – Clusterware patch inventory

Collecting – Exadata Critical Issue DB09

Collecting – Exadata Critical Issue EX30

Collecting – Exadata Critical Issue EX36

Collecting – Exadata Critical Issue EX56

Collecting – Exadata Critical Issue EX57

Collecting – Exadata Critical Issue EX58

Collecting – Exadata critical issue EX48

Collecting – Exadata critical issue EX55

Collecting – Exadata software version on database server

Collecting – Exadata system model number

Collecting – Exadata version on database server

Collecting – HCA firmware version on database server

Collecting – HCA transfer rate on database server

Collecting – Infrastructure Software and Configuration for compute

Collecting – MaxStartups setting in sshd_config

Collecting – OFED Software version on database server

Collecting – Obtain hardware information

Collecting – Operating system and Kernel version on database server

Collecting – Oracle monitoring agent and/or OS settings on ADR diagnostic directories

Collecting – Raid controller bus link speed

Collecting – System Event Log

Collecting – Validate key sysctl.conf parameters on database servers

Collecting – Verify Data Network is Separate from Management Network

Collecting – Verify Database Server Disk Controller Configuration

Collecting – Verify Database Server Physical Drive Configuration

Collecting – Verify Database Server Virtual Drive Configuration

Collecting – Verify Disk Cache Policy on database server

Collecting – Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Database Server]

Collecting – Verify ILOM Power Up Configuration for HOST_AUTO_POWER_ON

Collecting – Verify ILOM Power Up Configuration for HOST_LAST_POWER_STATE

Collecting – Verify IP routing configuration on database servers

Collecting – Verify InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers

Collecting – Verify Master (Rack) Serial Number is Set [Database Server]

Collecting – Verify Quorum disks configuration

Collecting – Verify RAID Controller Battery Temperature [Database Server]

Collecting – Verify RAID disk controller CacheVault capacitor condition [Database Server]

Collecting – Verify RAID disk controller CacheVault capacitor condition [Database Server]

Collecting – Verify TCP Segmentation Offload (TSO) is set to off

Collecting – Verify available ksplice fixes are installed [Database Server]

Collecting – Verify basic Logical Volume(LVM) system devices configuration

Collecting – Verify database server InfiniBand network MTU size

Collecting – Verify database server disk controllers use writeback cache

Collecting – Verify database server file systems have Check interval = 0

Collecting – Verify database server file systems have Maximum mount count = -1

Collecting – Verify imageinfo on database server

Collecting – Verify imageinfo on database server to compare systemwide

Collecting – Verify installed rpm(s) kernel type match the active kernel version

Collecting – Verify no database server kernel out of memory errors

Collecting – Verify proper ACFS drivers are installed for Spectre v2 mitigation

Collecting – Verify service exachkcfg autostart status on database server

Collecting – Verify the localhost alias is pingable [Database Server]

Collecting – Verify the InfiniBand Fabric Topology (verify-topology)

Collecting – Verify the Name Service Cache Daemon (NSCD) configuration

Collecting – Verify the Subnet Manager is properly disabled [Database Server]

Collecting – Verify the currently active image status [Database Server]

Collecting – Verify the ib_sdp module is not loaded into the kernel

Collecting – Verify the storage servers in use configuration matches across the cluster

Collecting – Verify the vm.min_free_kbytes configuration

Collecting – Verify there are no files present that impact normal firmware update procedures [Database Server]

Collecting – collect time server data [Database Server]

Collecting – root time zone check

Collecting – verify asr exadata configuration check via ASREXACHECK on database server

list index out of range

Data collections completed. Checking best practices on dm01db02.

————————————————————

FAIL =>     Exadata software version on database server does not meet certified platinum configuration

FAIL =>     Oracle database does not meet certified platinum configuration for /u01/app/oracle/product/11.2.0.4/dbhome

WARNING => Database parameter AUDIT_SYS_OPERATIONS should be set to the recommended value on testdb2 instance

WARNING => Database parameter AUDIT_SYS_OPERATIONS should be set to the recommended value on orcldb2 instance

INFO =>     Oracle GoldenGate failure prevention best practices

WARNING => Non-default database Services are not configured for orcldb

WARNING => Database parameter processes should be set to recommended value on testdb2 instance

WARNING => Database parameter processes should be set to recommended value on orcldb2 instance

FAIL =>     _reconnect_to_cell_attempts parameter in cellinit.ora is not set to recommended value

FAIL =>     Oracle monitoring agent and Operating systems settings on Automatic diagnostic repository directories are not correct or not all targets have been scanned or not all diagnostic directories found

FAIL =>     Downdelay attribute is not set to recommended value on bonded client interface

FAIL =>     One or more of SYSTEM, SYSAUX, USERS, TEMP tablespaces are not of type bigfile for orcldb

FAIL =>     The initialization parameter cluster_database_instances should be at the default value for testdb

FAIL =>     The initialization parameter cluster_database_instances should be at the default value for orcldb

INFO =>     Database parameter AUDIT_TRAIL should be set to the recommended value for testdb

INFO =>     Database parameter AUDIT_TRAIL should be set to the recommended value for orcldb

FAIL =>     Memlock settings do not meet the Oracle best practice recommendations for /u01/app/oracle/product/11.2.0.4/dbhome

CRITICAL => System is exposed to Exadata Critical Issue EX58

CRITICAL => One or more log archive destination and alternate log archive destination settings are not as recommended

CRITICAL => One or more disk groups which contain critical files do not use high redundancy

FAIL =>     Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on testdb2 instance

FAIL =>     Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on orcldb2 instance

FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on testdb2 instance

FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on orcldb2 instance

FAIL =>     Database parameter PARALLEL_ADAPTIVE_MULTI_USER is not set to recommended value on testdb2 instance

FAIL =>     Database parameter PARALLEL_ADAPTIVE_MULTI_USER is not set to recommended value on orcldb2 instance

FAIL =>     Database parameter PARALLEL_THREADS_PER_CPU is not set to recommended value on testdb2 instance

FAIL =>     Database parameter PARALLEL_THREADS_PER_CPU is not set to recommended value on orcldb2 instance

FAIL =>     Database parameter OS_AUTHENT_PREFIX is not set to recommended value on testdb2 instance

FAIL =>     Database parameter OS_AUTHENT_PREFIX is not set to recommended value on orcldb2 instance

FAIL =>    Database parameter sql92_security is not set to recommended value on testdb2 instance

FAIL =>     Database parameter sql92_security is not set to recommended value on orcldb2 instance

FAIL =>     Database parameter COMPATIBLE should be set to recommended value for testdb

FAIL =>     Database parameter COMPATIBLE should be set to recommended value for orcldb

CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for orcldb

CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for testdb

CRITICAL => Database control files are not configured as recommended

WARNING => ASM parameter ASM_POWER_LIMIT is not set to the default value.

INFO =>     While initialization parameter LOG_ARCHIVE_CONFIG is set it should be verified for your environment on Standby Database for testdb

WARNING => Redo log files should be appropriately sized for testdb

WARNING => Redo log files should be appropriately sized for orcldb

FAIL =>     Database parameter LOG_BUFFER is not set to recommended value on orcldb2 instance

Collecting patch inventory on CRS_HOME /u01/app/11.2.0.4/grid

Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/11.2.0.4/dbhome

Copying results from dm01db03 and generating report. This might take a while. Be patient.

.

============================================================

              Node name – dm01db03

============================================================

Collecting – CPU Information

Collecting – Clusterware and RDBMS software version

Collecting – Compute node PCI bus slot speed for infiniband HCAs

Collecting – Kernel parameters

Collecting – Maximum number of semaphore sets on system

Collecting – Maximum number of semaphores on system

Collecting – OS Packages

Collecting – Patches for Grid Infrastructure

Collecting – Patches for RDBMS Home

Collecting – RDBMS patch inventory

Collecting – number of semaphore operations per semop system call

Collecting – CRS user limits configuration

Collecting – CRS user time zone check

Collecting – Check alerthistory for non-test open stateless alerts [Database Server]

Collecting – Check alerthistory for stateful alerts not cleared [Database Server]

Collecting – Clusterware patch inventory

Collecting – Exadata Critical Issue DB09

Collecting – Exadata Critical Issue EX30

Collecting – Exadata Critical Issue EX36

Collecting – Exadata Critical Issue EX56

Collecting – Exadata Critical Issue EX57

Collecting – Exadata Critical Issue EX58

Collecting – Exadata critical issue EX48

Collecting – Exadata critical issue EX55

Collecting – Exadata software version on database server

Collecting – Exadata system model number

Collecting – Exadata version on database server

Collecting – HCA firmware version on database server

Collecting – HCA transfer rate on database server

Collecting – Infrastructure Software and Configuration for compute

Collecting – MaxStartups setting in sshd_config

Collecting – OFED Software version on database server

Collecting – Obtain hardware information

Collecting – Operating system and Kernel version on database server

Collecting – Oracle monitoring agent and/or OS settings on ADR diagnostic directories

Collecting – Raid controller bus link speed

Collecting – System Event Log

Collecting – Validate key sysctl.conf parameters on database servers

Collecting – Verify Data Network is Separate from Management Network

Collecting – Verify Database Server Disk Controller Configuration

Collecting – Verify Database Server Physical Drive Configuration

Collecting – Verify Database Server Virtual Drive Configuration

Collecting – Verify Disk Cache Policy on database server

Collecting – Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Database Server]

Collecting – Verify ILOM Power Up Configuration for HOST_AUTO_POWER_ON

Collecting – Verify ILOM Power Up Configuration for HOST_LAST_POWER_STATE

Collecting – Verify IP routing configuration on database servers

Collecting – Verify InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers

Collecting – Verify Master (Rack) Serial Number is Set [Database Server]

Collecting – Verify Quorum disks configuration

Collecting – Verify RAID Controller Battery Temperature [Database Server]

Collecting – Verify RAID disk controller CacheVault capacitor condition [Database Server]

Collecting – Verify RAID disk controller CacheVault capacitor condition [Database Server]

Collecting – Verify TCP Segmentation Offload (TSO) is set to off

Collecting – Verify available ksplice fixes are installed [Database Server]

Collecting – Verify basic Logical Volume(LVM) system devices configuration

Collecting – Verify database server InfiniBand network MTU size

Collecting – Verify database server disk controllers use writeback cache

Collecting – Verify database server file systems have Check interval = 0

Collecting – Verify database server file systems have Maximum mount count = -1

Collecting – Verify imageinfo on database server

Collecting – Verify imageinfo on database server to compare systemwide

Collecting – Verify installed rpm(s) kernel type match the active kernel version

Collecting – Verify no database server kernel out of memory errors

Collecting – Verify proper ACFS drivers are installed for Spectre v2 mitigation

Collecting – Verify service exachkcfg autostart status on database server

Collecting – Verify the localhost alias is pingable [Database Server]

Collecting – Verify the InfiniBand Fabric Topology (verify-topology)

Collecting – Verify the Name Service Cache Daemon (NSCD) configuration

Collecting – Verify the Subnet Manager is properly disabled [Database Server]

Collecting – Verify the currently active image status [Database Server]

Collecting – Verify the ib_sdp module is not loaded into the kernel

Collecting – Verify the storage servers in use configuration matches across the cluster

Collecting – Verify the vm.min_free_kbytes configuration

Collecting – Verify there are no files present that impact normal firmware update procedures [Database Server]

Collecting – collect time server data [Database Server]

Collecting – root time zone check

Collecting – verify asr exadata configuration check via ASREXACHECK on database server

list index out of range

Data collections completed. Checking best practices on dm01db03.

————————————————————

FAIL =>     Exadata software version on database server does not meet certified platinum configuration

FAIL =>     Oracle database does not meet certified platinum configuration for /u01/app/oracle/product/11.2.0.4/dbhome

WARNING => Database parameter AUDIT_SYS_OPERATIONS should be set to the recommended value on testdb3 instance

WARNING => Database parameter AUDIT_SYS_OPERATIONS should be set to the recommended value on orcldb3 instance

INFO =>     Oracle GoldenGate failure prevention best practices

WARNING => Non-default database Services are not configured for orcldb

WARNING => Database parameter processes should be set to recommended value on testdb3 instance

WARNING => Database parameter processes should be set to recommended value on orcldb3 instance

FAIL =>     _reconnect_to_cell_attempts parameter in cellinit.ora is not set to recommended value

FAIL =>     Oracle monitoring agent and Operating systems settings on Automatic diagnostic repository directories are not correct or not all targets have been scanned or not all diagnostic directories found

FAIL =>     Downdelay attribute is not set to recommended value on bonded client interface

WARNING => The IP routing configuration is not correct

FAIL =>     One or more of SYSTEM, SYSAUX, USERS, TEMP tablespaces are not of type bigfile for orcldb

FAIL =>     The initialization parameter cluster_database_instances should be at the default value for testdb

FAIL =>     The initialization parameter cluster_database_instances should be at the default value for orcldb

INFO =>     Database parameter AUDIT_TRAIL should be set to the recommended value for testdb

INFO =>     Database parameter AUDIT_TRAIL should be set to the recommended value for orcldb

FAIL =>     Memlock settings do not meet the Oracle best practice recommendations for /u01/app/oracle/product/11.2.0.4/dbhome

CRITICAL => System is exposed to Exadata Critical Issue EX58

FAIL =>     Management network is not separate from data network

CRITICAL => One or more log archive destination and alternate log archive destination settings are not as recommended

CRITICAL => One or more disk groups which contain critical files do not use high redundancy

FAIL =>     Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on testdb3 instance

FAIL =>     Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on orcldb3 instance

FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on testdb3 instance

FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on orcldb3 instance

FAIL =>     Database parameter PARALLEL_ADAPTIVE_MULTI_USER is not set to recommended value on testdb3 instance

FAIL =>     Database parameter PARALLEL_ADAPTIVE_MULTI_USER is not set to recommended value on orcldb3 instance

FAIL =>     Database parameter PARALLEL_THREADS_PER_CPU is not set to recommended value on testdb3 instance

FAIL =>     Database parameter PARALLEL_THREADS_PER_CPU is not set to recommended value on orcldb3 instance

FAIL =>     Database parameter OS_AUTHENT_PREFIX is not set to recommended value on testdb3 instance

FAIL =>     Database parameter OS_AUTHENT_PREFIX is not set to recommended value on orcldb3 instance

FAIL =>     Database parameter sql92_security is not set to recommended value on testdb3 instance

FAIL =>     Database parameter sql92_security is not set to recommended value on orcldb3 instance

FAIL =>     Database parameter COMPATIBLE should be set to recommended value for testdb

FAIL =>     Database parameter COMPATIBLE should be set to recommended value for orcldb

CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for orcldb

CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for testdb

CRITICAL => Database control files are not configured as recommended

WARNING => ASM parameter ASM_POWER_LIMIT is not set to the default value.

INFO =>     While initialization parameter LOG_ARCHIVE_CONFIG is set it should be verified for your environment on Standby Database for testdb

WARNING => Redo log files should be appropriately sized for testdb

WARNING => Redo log files should be appropriately sized for orcldb

FAIL =>     Database parameter LOG_BUFFER is not set to recommended value on orcldb3 instance

Collecting patch inventory on CRS_HOME /u01/app/11.2.0.4/grid

Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/11.2.0.4/dbhome

Copying results from dm01db04 and generating report. This might take a while. Be patient.

.

============================================================

              Node name – dm01db04

============================================================

Collecting – CPU Information

Collecting – Clusterware and RDBMS software version

Collecting – Compute node PCI bus slot speed for infiniband HCAs

Collecting – Kernel parameters

Collecting – Maximum number of semaphore sets on system

Collecting – Maximum number of semaphores on system

Collecting – OS Packages

Collecting – Patches for Grid Infrastructure

Collecting – Patches for RDBMS Home

Collecting – RDBMS patch inventory

Collecting – number of semaphore operations per semop system call

Collecting – CRS user limits configuration

Collecting – CRS user time zone check

Collecting – Check alerthistory for non-test open stateless alerts [Database Server]

Collecting – Check alerthistory for stateful alerts not cleared [Database Server]

Collecting – Clusterware patch inventory

Collecting – Exadata Critical Issue DB09

Collecting – Exadata Critical Issue EX30

Collecting – Exadata Critical Issue EX36

Collecting – Exadata Critical Issue EX56

Collecting – Exadata Critical Issue EX57

Collecting – Exadata Critical Issue EX58

Collecting – Exadata critical issue EX48

Collecting – Exadata critical issue EX55

Collecting – Exadata software version on database server

Collecting – Exadata system model number

Collecting – Exadata version on database server

Collecting – HCA firmware version on database server

Collecting – HCA transfer rate on database server

Collecting – Infrastructure Software and Configuration for compute

Collecting – MaxStartups setting in sshd_config

Collecting – OFED Software version on database server

Collecting – Obtain hardware information

Collecting – Operating system and Kernel version on database server

Collecting – Oracle monitoring agent and/or OS settings on ADR diagnostic directories

Collecting – Raid controller bus link speed

Collecting – System Event Log

Collecting – Validate key sysctl.conf parameters on database servers

Collecting – Verify Data Network is Separate from Management Network

Collecting – Verify Database Server Disk Controller Configuration

Collecting – Verify Database Server Physical Drive Configuration

Collecting – Verify Database Server Virtual Drive Configuration

Collecting – Verify Disk Cache Policy on database server

Collecting – Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Database Server]

Collecting – Verify ILOM Power Up Configuration for HOST_AUTO_POWER_ON

Collecting – Verify ILOM Power Up Configuration for HOST_LAST_POWER_STATE

Collecting – Verify IP routing configuration on database servers

Collecting – Verify InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers

Collecting – Verify Master (Rack) Serial Number is Set [Database Server]

Collecting – Verify Quorum disks configuration

Collecting – Verify RAID Controller Battery Temperature [Database Server]

Collecting – Verify RAID disk controller CacheVault capacitor condition [Database Server]

Collecting – Verify RAID disk controller CacheVault capacitor condition [Database Server]

Collecting – Verify TCP Segmentation Offload (TSO) is set to off

Collecting – Verify available ksplice fixes are installed [Database Server]

Collecting – Verify basic Logical Volume(LVM) system devices configuration

Collecting – Verify database server InfiniBand network MTU size

Collecting – Verify database server disk controllers use writeback cache

Collecting – Verify database server file systems have Check interval = 0

Collecting – Verify database server file systems have Maximum mount count = -1

Collecting – Verify imageinfo on database server

Collecting – Verify imageinfo on database server to compare systemwide

Collecting – Verify installed rpm(s) kernel type match the active kernel version

Collecting – Verify no database server kernel out of memory errors

Collecting – Verify proper ACFS drivers are installed for Spectre v2 mitigation

Collecting – Verify service exachkcfg autostart status on database server

Collecting – Verify the localhost alias is pingable [Database Server]

Collecting – Verify the InfiniBand Fabric Topology (verify-topology)

Collecting – Verify the Name Service Cache Daemon (NSCD) configuration

Collecting – Verify the Subnet Manager is properly disabled [Database Server]

Collecting – Verify the currently active image status [Database Server]

Collecting – Verify the ib_sdp module is not loaded into the kernel

Collecting – Verify the storage servers in use configuration matches across the cluster

Collecting – Verify the vm.min_free_kbytes configuration

Collecting – Verify there are no files present that impact normal firmware update procedures [Database Server]

Collecting – collect time server data [Database Server]

Collecting – root time zone check

Collecting – verify asr exadata configuration check via ASREXACHECK on database server

list index out of range

Data collections completed. Checking best practices on dm01db04.

————————————————————

FAIL =>     Exadata software version on database server does not meet certified platinum configuration

FAIL =>     Oracle database does not meet certified platinum configuration for /u01/app/oracle/product/11.2.0.4/dbhome

WARNING => Database parameter AUDIT_SYS_OPERATIONS should be set to the recommended value on testdb4 instance

WARNING => Database parameter AUDIT_SYS_OPERATIONS should be set to the recommended value on orcldb4 instance

INFO =>     Oracle GoldenGate failure prevention best practices

WARNING => Non-default database Services are not configured for orcldb

WARNING => Database parameter processes should be set to recommended value on testdb4 instance

WARNING => Database parameter processes should be set to recommended value on orcldb4 instance

FAIL =>     _reconnect_to_cell_attempts parameter in cellinit.ora is not set to recommended value

FAIL =>     Oracle monitoring agent and Operating systems settings on Automatic diagnostic repository directories are not correct or not all targets have been scanned or not all diagnostic directories found

FAIL =>     Downdelay attribute is not set to recommended value on bonded client interface

WARNING => The IP routing configuration is not correct

FAIL =>     One or more of SYSTEM, SYSAUX, USERS, TEMP tablespaces are not of type bigfile for orcldb

FAIL =>     The initialization parameter cluster_database_instances should be at the default value for testdb

FAIL =>     The initialization parameter cluster_database_instances should be at the default value for orcldb

INFO =>     Database parameter AUDIT_TRAIL should be set to the recommended value for testdb

INFO =>     Database parameter AUDIT_TRAIL should be set to the recommended value for orcldb

FAIL =>     Memlock settings do not meet the Oracle best practice recommendations for /u01/app/oracle/product/11.2.0.4/dbhome

CRITICAL => System is exposed to Exadata Critical Issue EX58

FAIL =>     Management network is not separate from data network

CRITICAL => One or more log archive destination and alternate log archive destination settings are not as recommended

CRITICAL => One or more disk groups which contain critical files do not use high redundancy

FAIL =>     Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on testdb4 instance

FAIL =>     Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on orcldb4 instance

FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on testdb4 instance

FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on orcldb4 instance

FAIL =>     Database parameter PARALLEL_ADAPTIVE_MULTI_USER is not set to recommended value on testdb4 instance

FAIL =>     Database parameter PARALLEL_ADAPTIVE_MULTI_USER is not set to recommended value on orcldb4 instance

FAIL =>     Database parameter PARALLEL_THREADS_PER_CPU is not set to recommended value on testdb4 instance

FAIL =>     Database parameter PARALLEL_THREADS_PER_CPU is not set to recommended value on orcldb4 instance

FAIL =>     Database parameter OS_AUTHENT_PREFIX is not set to recommended value on testdb4 instance

FAIL =>     Database parameter OS_AUTHENT_PREFIX is not set to recommended value on orcldb4 instance

FAIL =>     Database parameter sql92_security is not set to recommended value on testdb4 instance

FAIL =>     Database parameter sql92_security is not set to recommended value on orcldb4 instance

FAIL =>     Database parameter COMPATIBLE should be set to recommended value for testdb

FAIL =>     Database parameter COMPATIBLE should be set to recommended value for orcldb

CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for orcldb

CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for testdb

CRITICAL => Database control files are not configured as recommended

WARNING => ASM parameter ASM_POWER_LIMIT is not set to the default value.

INFO =>     While initialization parameter LOG_ARCHIVE_CONFIG is set it should be verified for your environment on Standby Database for testdb

WARNING => Redo log files should be appropriately sized for testdb

WARNING => Redo log files should be appropriately sized for orcldb

FAIL =>     Database parameter LOG_BUFFER is not set to recommended value on orcldb4 instance

Collecting patch inventory on CRS_HOME /u01/app/11.2.0.4/grid

Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/11.2.0.4/dbhome

————————————————————

                      CLUSTERWIDE CHECKS

————————————————————

————————————————————

Detailed report (html) – /u01/app/oracle/oracle.ahf/data/dm01db01/exachk/exachk_dm01db01_orcldb_040620_12376/exachk_dm01db01_orcldb_040620_12376.html

UPLOAD [if required] – /u01/app/oracle/oracle.ahf/data/dm01db01/exachk/exachk_dm01db01_orcldb_040620_12376.zip

Step 7: Review the Exachk report or Upload file to Oracle Support

[root@dm01db01 Exachk]# curl -x webproxy.netsoftmate.com:80 -T /u01/app/oracle/oracle.ahf/data/dm01db01/exachk/exachk_dm01db01_orcldb_040620_12376.zip -u abdul.mohammed@netsoftmate.com   https://transport.oracle.com/upload/issue/3-XXXXXXXX/ -v

Sample Exadata Output:

To Uninstall AHF

[root@dm01db01 ~]# cd /opt/oracle.ahf/ahf/bin

[root@dm01db01 bin]# ls -ltr

total 88

-r-xr-xr-x 1 root root 19623 Mar 17 11:25 uninstallahf.sh

-r-xr-xr-x 1 root root 14504 Mar 17 11:25 uninstallahf.pl

-rwxr-xr-x 1 root root 3296 Mar 17 11:25 tfactl

-r-xr-xr-x 1 root root 45597 Mar 17 11:25 installAHF.pl

[root@dm01db01 bin]# ./uninstallahf.sh -h

   Usage for ./uninstallahf.sh

   ./uninstallahf.sh [-local] [-silent] [-deleterepo]

        -local            –    Uninstall AHF only on the local node

        -silent           –    Do not ask any uninstall questions

        -deleterepo       –    Delete AHF repository

   Note: If -local is not passed, AHF will be uninstalled from all configured nodes.

[root@dm01db01 bin]# ./uninstallahf.sh -deleterepo

Starting AHF Uninstall

AHF will be uninstalled on:

dm01db01

dm01db02

Do you want to continue with AHF uninstall ? [Y]|N : Y

Stopping AHF service on local node dm01db01…

Stopping TFA Support Tools…

TFA-00002 Oracle Trace File Analyzer (TFA) is not running

Stopping exachk scheduler …

Removing exachk cache discovery….

No exachk cache discovery found.

Removed exachk from inittab

Stopping and removing AHF in dm01db02…

TFA-00002 Oracle Trace File Analyzer (TFA) is not running

Removing exachk cache discovery….

Successfully completed exachk cache discovery removal.

Removed exachk from inittab

Successfully uninstalled AHF on node dm01db02

Removing AHF setup on dm01db01:

Removing /etc/rc.d/rc0.d/K17init.tfa

Removing /etc/rc.d/rc1.d/K17init.tfa

Removing /etc/rc.d/rc2.d/K17init.tfa

Removing /etc/rc.d/rc4.d/K17init.tfa

Removing /etc/rc.d/rc6.d/K17init.tfa

Removing /etc/init.d/init.tfa…

Removing /opt/oracle.ahf/jre

Removing /opt/oracle.ahf/common

Removing /opt/oracle.ahf/bin

Removing /opt/oracle.ahf/python

Removing /opt/oracle.ahf/analyzer

Removing /opt/oracle.ahf/tfa

Removing /opt/oracle.ahf/ahf

Removing /opt/oracle.ahf/exachk

Removing /u01/app/oracle/oracle.ahf/data/dm01db01

Removing /opt/oracle.ahf/install.properties

Removing /u01/app/oracle/oracle.ahf/data/repository

Removing /u01/app/oracle/oracle.ahf/data

Removing /u01/app/oracle/oracle.ahf

Removing AHF Home : /opt/oracle.ahf

Conclusion:

In this article we have learned how to install, setup and execute Autonomous Health Check Frame work for Exadata Database Machines. We have also seen how to uninstall the AHF software.

About Netsoftmate:

Netsoftmate is an Oracle Gold Partner and a boutique IT services company specializing in installation, implementation and 24/7 support for Oracle Engineered Systems like Oracle Exadata, Oracle Database Appliance, Oracle ZDLRA, Oracle ZFS Storage and Oracle Private Cloud Appliance. Apart from OES, we have specialized teams of experts providing round the clock remote database administration support for any type of database and cyber security compliance and auditing services.

Feel free to get in touch with us by signing up on the link below –
April 16, 2020
10 Easy Steps To Patch Oracle Exadata X8M RoCE Switch
The Oracle Exadata X8M release implements 100 Gb/sec RoCE network fabric, making the world’s fastest database machine even faster.

Oracle Exadata Database Machine X8M introduces a brand new high-bandwidth low-latency 100 Gb/sec RDMA over Converged Ethernet (RoCE) Network Fabric that connects all the components inside an Exadata Database Machine. Specialized database networking protocols deliver much lower latency and higher bandwidth than is possible with generic communication protocols for faster response time for OLTP operations and higher throughput for analytic workloads.

The ORacle Exadata X8M release provides the next generation in ultra-fast cloud scale networking fabric, RDMA over Converged Ethernet (RoCE). RDMA (Remote Direct Memory Access) allows one computer to directly access data from another without Operating System or CPU involvement, for high bandwidth and low latency. The network card directly reads/writes memory with no extra copying or buffering and very low latency.

RDMA is an integral part of the Exadata high-performance architecture, and has been tuned and enhanced over the past decade, underpinning several Exadata-only technologies such as Exafusion Direct-to-Wire Protocol and Smart Fusion Block Transfer. As the RoCE API infrastructure is identical to InfiniBand’s, all existing Exadata performance features are available on RoCE.

Oracle Exadata RoCE Switch Image:
In this article we see practically how to patch Exadata X8M RoCE Switches

1. Create a file containing RoCE switch hostname

[root@dm01dbadm01 ~]# cat roce_list

dm01sw-rocea01

dm01sw-roceab1

2. Get the current RoCE Switch software version

[root@dm01dbadm01 ~]# ssh admin@dm01sw-rocea01 show version

User Access Verification

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Copyright (C) 2002-2019, Cisco and/or its affiliates.

All rights reserved.

The copyrights to certain works contained in this software are

owned by other third parties and used and distributed under their own

licenses, such as open source. This software is provided “as is,” and unless

otherwise stated, there is no warranty, express or implied, including but not

limited to warranties of merchantability and fitness for a particular purpose.

Certain components of this software are licensed under

the GNU General Public License (GPL) version 2.0 or

GNU General Public License (GPL) version 3.0 or the GNU

Lesser General Public License (LGPL) Version 2.1 or

Lesser General Public License (LGPL) Version 2.0.

A copy of each such license is available at

http://www.opensource.org/licenses/gpl-2.0.php and

http://opensource.org/licenses/gpl-3.0.html and

http://www.opensource.org/licenses/lgpl-2.1.php and

http://www.gnu.org/licenses/old-licenses/library.txt.

Software

BIOS: version 05.39

NXOS: version 7.0(3)I7(6)

BIOS compile time: 08/30/2019

NXOS image file is: bootflash:///nxos.7.0.3.I7.6.bin

NXOS compile time: 3/5/2019 13:00:00 [03/05/2019 22:04:55]

Hardware

cisco Nexus9000 C9336C-FX2 Chassis

Intel(R) Xeon(R) CPU D-1526 @ 1.80GHz with 24571632 kB of memory.

Processor Board ID FDO23380VQS

Device name: dm01sw-rocea01

bootflash: 115805708 kB

Kernel uptime is 8 day(s), 3 hour(s), 14 minute(s), 49 second(s)

Last reset at 145297 usecs after Wed Apr 1 09:29:43 2020

Reason: Reset Requested by CLI command reload

System version: 7.0(3)I7(6)

Service:

plugin

Core Plugin, Ethernet Plugin

Active Package(s):

[root@dm01dbadm01 ~]# ssh admin@dm01sw-rocea01 show version | grep “System version:”

User Access Verification

System version: 7.0(3)I7(6)

3. Download the the RoCE switch software from MOS note 888828.1 and copy it Exadata compute node 1

[root@dm01dbadm01 ~]# cd /u01/stage/ROCE/

[root@dm01dbadm01 ROCE]# ls -ltr

total 2773832

-rw-r–r– 1 root root 2840400612 Apr 9 00:42 p30893922_193000_Linux-x86-64.zip

4. Unzip the RoCE patch

[root@dm01dbadm01 ROCE]# unzip p30893922_193000_Linux-x86-64.zip

Archive: p30893922_193000_Linux-x86-64.zip

   creating: patch_switch_19.3.6.0.0.200317/

inflating: patch_switch_19.3.6.0.0.200317/dcli

inflating: patch_switch_19.3.6.0.0.200317/exadata.img.hw

inflating: patch_switch_19.3.6.0.0.200317/sundcs_36p_repository_2.2.7_2.pkg

inflating: patch_switch_19.3.6.0.0.200317/imageLogger

inflating:

…

…

patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch_multi.cfg

inflating: patch_switch_19.3.6.0.0.200317/sundcs_36p_repository_2.2.14_1.pkg

inflating: patch_switch_19.3.6.0.0.200317/README.txt

5. Verify the patch directory content after unzip

[root@dm01dbadm01 ROCE]# cd patch_switch_19.3.6.0.0.200317/

[root@dm01dbadm01 patch_switch_19.3.6.0.0.200317]# ls -ltr

total 2794980

-r-xr-x— 1 root root      50674 Mar 18 05:48 exadata.img.hw

-r–r–r– 1 root root       8664 Mar 18 05:48 exadata.img.env

-r–r–r– 1 root root      45349 Mar 18 05:48 imageLogger

-r–r—– 1 root root       6133 Mar 18 05:48 ExaXMLNode.pm

-r–r—– 1 root root      51925 Mar 18 05:48 exadata_img_pylogger.py

-r-xr-xr-x 1 root root      17482 Mar 18 05:48 libxcp.so.1

-r-xr-xr-x 1 root root       4385 Mar 18 05:48 kernelupgrade_oldbios.sh

-r-xr-xr-x 1 root root     176994 Mar 18 05:48 installfw_exadata_ssh

-r-xr-xr-x 1 root root        426 Mar 18 05:48 fwverify

-r-xr-xr-x 1 root root       1570 Mar 18 05:48 ExadataSendNotification.pm

-r-xr-xr-x 1 root root      62499 Mar 18 05:48 ExadataImageNotification.pl

-r-xr-xr-x 1 root root      51616 Mar 18 05:48 dcli

-rw-r–r– 1 root root 1011037696 Mar 18 05:48 nxos.7.0.3.I7.6.bin

-r-xr-xr-x 1 root root      16544 Mar 18 05:48 patchmgr_functions

-rwxr-xr-x 1 root root      11600 Mar 18 05:48 patch_bug_26678971

-rw-r–r– 1 root root 975383040 Mar 18 05:48 nxos.7.0.3.I7.7.bin

-r-xr-xr-x 1 root root 171545108 Mar 18 05:48 sundcs_36p_repository_2.2.13_2.pkg

-r-xr-xr-x 1 root root 172863012 Mar 18 05:48 sundcs_36p_repository_2.2.14_1.pkg

-rwxr-xr-x 1 root root 172946493 Mar 18 05:48 sundcs_36p_repository_2.2.7_2.pkg

-rwxr-xr-x 1 root root 172947929 Mar 18 05:48 sundcs_36p_repository_2.2.7_2_signed.pkg

-r-xr-xr-x 1 root root      15001 Mar 18 05:48 xcp

-rwxr-xr-x 1 root root 184111553 Mar 18 05:48 sundcs_36p_repository_upgrade_2.1_to_2.2.7_2.pkg

-r-xr-xr-x 1 root root     168789 Mar 18 06:05 upgradeIBSwitch.sh

drwxr-xr-x 2 root root        103 Mar 18 06:05 roce_switch_templates

drwxr-xr-x 2 root root         98 Mar 18 06:05 roce_switch_api

drwxr-xr-x 6 root root      4096 Mar 18 06:05 ibdiagtools

drwxrwxr-x 3 root root         20 Mar 18 06:05 etc

-r-xr-xr-x 1 root root     457738 Mar 18 06:05 patchmgr

-rw-rw-r– 1 root root       5156 Mar 18 06:05 md5sum_files.lst

-rwxrwxrwx 1 root root        822 Mar 18 07:15 README.txt

6. Navigate to the patch directory and execute the following to get the patch syntax

[root@dm01dbadm01 patch_switch_19.3.6.0.0.200317]# ./patchmgr -h

Usage:

./patchmgr –roceswitches [roceswitch_list_file]

           –upgrade [–verify-config [yes|no]] [–roceswitch-precheck] [–force] |

           –downgrade [–verify-config [yes|no]] [–roceswitch-precheck] [–force] |

           –verify-config [yes|no]

           [-log_dir <fullpath> ]

./patchmgr –ibswitches [ibswitch_list_file]

          <–upgrade | –downgrade> [–ibswitch_precheck] [–unkey] [–force [yes|no]]

7. Execute the following command to perform configuration verification

Note: The patching should be performed by a non-root user. In this case I am using oracle user to perform the patching

[root@dm01dbadm01 stage]# chown -R oracle:oinstall ROCE/

[root@dm01dbadm01 stage]# su – oracle

Last login: Thu Apr 9 16:17:25 +03 2020

[oracle@dm01dbadm01 ~]$ cd /u01/stage/ROCE/

[oracle@dm01dbadm01 ROCE]$ ls -ltr

total 2773836

-rw-r–r– 1 oracle oinstall 2840400612 Apr 9 00:42 p30893922_193000_Linux-x86-64.zip

drwxrwxr-x 6 oracle oinstall       4096 Apr 9 16:31 patch_switch_19.3.6.0.0.200317

[oracle@dm01dbadm01 ROCE]$ cd patch_switch_19.3.6.0.0.200317/

[oracle@dm01dbadm01 ~]$ vi roce_list

dm01sw-rocea01

dm01sw-roceab1

[oracle@dm01dbadm01 ~]$ cd /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317

[oracle@dm01dbadm01 patch_switch_19.3.6.0.0.200317]$ ./patchmgr –roceswitches ~/roce_list –verify-config –log_dir /u01/stage/ROCE

2020-04-09 16:59:52 +0300        :Working: Initiate config verify on RoCE switches from . Expect up to 6 minutes for each switch

2020-04-09 16:59:53 +0300 1 of 2 :Verifying config on switch dm01sw-rocea01

2020-04-09 16:59:53 +0300:        [INFO     ] Dumping current running config locally as file: /u01/stage/ROCE/run.dm01sw-rocea01.cfg

2020-04-09 16:59:54 +0300:        [SUCCESS ] Backed up switch config successfully

2020-04-09 16:59:54 +0300:        [INFO     ] Validating running config against template [1/3]: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 16:59:54 +0300:        [INFO     ] Config matches template: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 16:59:54 +0300:        [SUCCESS ] Config validation successful!

2020-04-09 16:59:54 +0300 2 of 2 :Verifying config on switch dm01sw-roceb01

2020-04-09 16:59:54 +0300:        [INFO     ] Dumping current running config locally as file: /u01/stage/ROCE/run.dm01sw-roceb01.cfg

2020-04-09 16:59:55 +0300:        [SUCCESS ] Backed up switch config successfully

2020-04-09 16:59:55 +0300:        [INFO     ] Validating running config against template [1/3]: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 16:59:55 +0300:        [INFO     ] Config matches template: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 16:59:55 +0300:        [SUCCESS ] Config validation successful!

2020-04-09 16:59:55 +0300        :SUCCESS: Config check on RoCE switch(es)

2020-04-09 16:59:56 +0300        :SUCCESS: Completed run of command: ./patchmgr –roceswitches /home/oracle/roce_list –verify-config –log_dir /u01/stage/ROCE

2020-04-09 16:59:56 +0300        :INFO   : config attempted on nodes in file /home/oracle/roce_list: [dm01sw-rocea01 dm01sw-roceb01]

2020-04-09 16:59:56 +0300        :INFO   : For details, check the following files in /u01/stage/ROCE:

2020-04-09 16:59:56 +0300        :INFO   : – updateRoceSwitch.log

2020-04-09 16:59:56 +0300        :INFO   : – updateRoceSwitch.trc

2020-04-09 16:59:56 +0300        :INFO   : – patchmgr.stdout

2020-04-09 16:59:56 +0300        :INFO   : – patchmgr.stderr

2020-04-09 16:59:56 +0300        :INFO   : – patchmgr.log

2020-04-09 16:59:56 +0300        :INFO   : – patchmgr.trc

2020-04-09 16:59:56 +0300        :INFO   : Exit status:0

2020-04-09 16:59:56 +0300        :INFO   : Exiting.

8. Execute the following command to perform prerequisite checks.

Note: During this step it will prompt you setup the SSH between oracle user and RoCE switch. Please enter the admin user password of RoCE switch.

[oracle@dm01dbadm01 patch_switch_19.3.6.0.0.200317]$ ./patchmgr –roceswitches ~/roce_list –upgrade –roceswitch-precheck –log_dir /u01/stage/ROCE

[NOTE     ] Password equivalency is NOT setup for user ‘oracle’ to dm01sw-rocea01 from ‘dm01dbadm01.netsoftmate.com’. Set it up? (y/n): y

enter switch ‘admin’ password:

checking if ‘dm01sw-rocea01’ is reachable… [OK]

setting up SSH equivalency for ‘oracle’ from dm01dbadm01.netsoftmate.com to ‘dm01sw-rocea01’… [OK]

[NOTE     ] Password equivalency is NOT setup for user ‘oracle’ to dm01sw-roceb01 from ‘dm01dbadm01.netsoftmate.com’. Set it up? (y/n): y

enter switch ‘admin’ password:

checking if ‘dm01sw-roceb01’ is reachable… [OK]

setting up SSH equivalency for ‘oracle’ from dm01dbadm01.netsoftmate.com to ‘dm01sw-roceb01’… [OK]

2020-04-09 16:47:46 +0300        :Working: Initiate pre-upgrade validation check on 2 RoCE switch(es).

2020-04-09 16:47:47 +0300 1 of 2 :Updating switch dm01sw-rocea01

2020-04-09 16:47:49 +0300:        [INFO     ] Switch dm01sw-rocea01 will be upgraded from nxos.7.0.3.I7.6.bin to nxos.7.0.3.I7.7.bin

2020-04-09 16:47:49 +0300:        [INFO     ] Checking for free disk space on switch

2020-04-09 16:47:50 +0300:        [INFO     ] disk is 96.00% free, available: 112371744768 bytes

2020-04-09 16:47:50 +0300:        [SUCCESS ] There is enough disk space to proceed

2020-04-09 16:47:52 +0300:        [INFO     ] Copying nxos.7.0.3.I7.7.bin onto dm01sw-rocea01 (eta: 1-5 minutes)

2020-04-09 16:50:40 +0300:        [SUCCESS ] Finished copying image to switch

2020-04-09 16:50:40 +0300:        [INFO     ] Verifying sha256sum of bin file on switch

2020-04-09 16:50:54 +0300:        [SUCCESS ] sha256sum matches: dce664f1a90927e9dbd86419681d138d3a7a83c5ea7222718c3f6565488ac6d0

2020-04-09 16:50:54 +0300:        [INFO     ] Performing FW install pre-check of nxos.7.0.3.I7.7.bin (eta: 2-3 minutes)

2020-04-09 16:52:55 +0300:        [SUCCESS ] FW install pre-check completed successfully

2020-04-09 16:52:55 +0300 2 of 2 :Updating switch dm01sw-roceb01

2020-04-09 16:58:26 +0300:        [INFO     ] Dumping current running config locally as file: /u01/stage/ROCE/run.dm01sw-roceb01.cfg

2020-04-09 16:58:27 +0300:        [SUCCESS ] Backed up switch config successfully

2020-04-09 16:58:27 +0300:        [INFO     ] Validating running config against template [1/3]: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 16:58:27 +0300:        [INFO     ] Config matches template: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 16:58:27 +0300:        [SUCCESS ] Config validation successful!

2020-04-09 16:58:27 +0300        :SUCCESS: Config check on RoCE switch(es)

2020-04-09 16:58:27 +0300        :SUCCESS: Initiate pre-upgrade validation check on RoCE switch(es).

2020-04-09 16:58:27 +0300        :SUCCESS: Completed run of command: ./patchmgr –roceswitches /home/oracle/roce_list –upgrade –roceswitch-precheck –log_dir /u01/stage/ROCE

2020-04-09 16:58:27 +0300        :INFO   : upgrade attempted on nodes in file /home/oracle/roce_list: [dm01sw-rocea01 dm01sw-roceb01]

2020-04-09 16:58:27 +0300        :INFO   : For details, check the following files in /u01/stage/ROCE:

2020-04-09 16:58:27 +0300        :INFO : – updateRoceSwitch.log

2020-04-09 16:58:27 +0300        :INFO   : – updateRoceSwitch.trc

2020-04-09 16:58:27 +0300        :INFO   : – patchmgr.stdout

2020-04-09 16:58:27 +0300        :INFO   : – patchmgr.stderr

2020-04-09 16:58:27 +0300        :INFO   : – patchmgr.log

2020-04-09 16:58:27 +0300        :INFO   : – patchmgr.trc

2020-04-09 16:58:27 +0300        :INFO   : Exit status:0
- 6:58:27 +0300 :INFO : Exiting.
9. Execute the following command to patch RoCE switches.

[oracle@dm01dbadm01 patch_switch_19.3.6.0.0.200317]$ ./patchmgr –roceswitches ~/roce_list –upgrade –log_dir /u01/stage/ROCE

[NOTE     ] Password equivalency is NOT setup for user ‘oracle’ to dm01sw-rocea01 from ‘dm01dbadm01.netsoftmate.com’. Set it up? (y/n): y

enter switch ‘admin’ password:

checking if ‘dm01sw-rocea01’ is reachable… [OK]

setting up SSH equivalency for ‘oracle’ from dm01dbadm01.netsoftmate.com to ‘dm01sw-rocea01’… [OK]

[NOTE     ] Password equivalency is NOT setup for user ‘oracle’ to dm01sw-roceb01 from ‘dm01dbadm01.netsoftmate.com’. Set it up? (y/n): y

enter switch ‘admin’ password:

checking if ‘dm01sw-roceb01’ is reachable… [OK]

setting up SSH equivalency for ‘oracle’ from dm01dbadm01.netsoftmate.com to ‘dm01sw-roceb01’… [OK]

2020-04-09 17:02:26 +0300        :Working: Initiate upgrade of 2 RoCE switches to 7.0(3)I7(7) Expect up to 15 minutes for each switch

2020-04-09 17:02:26 +0300 1 of 2 :Updating switch dm01sw-rocea01

2020-04-09 17:02:28 +0300:        [INFO     ] Switch dm01sw-rocea01 will be upgraded from nxos.7.0.3.I7.6.bin to nxos.7.0.3.I7.7.bin

2020-04-09 17:02:28 +0300:        [INFO     ] Checking for free disk space on switch

2020-04-09 17:02:28 +0300:        [INFO     ] disk is 95.00% free, available: 111395401728 bytes

2020-04-09 17:02:28 +0300:        [SUCCESS ] There is enough disk space to proceed

2020-04-09 17:02:29 +0300:        [INFO     ] Found nxos.7.0.3.I7.7.bin on switch, skipping download

2020-04-09 17:02:29 +0300:        [INFO     ] Verifying sha256sum of bin file on switch

2020-04-09 17:02:43 +0300:        [SUCCESS ] sha256sum matches: dce664f1a90927e9dbd86419681d138d3a7a83c5ea7222718c3f6565488ac6d0

2020-04-09 17:02:43 +0300:        [INFO     ] Performing FW install pre-check of nxos.7.0.3.I7.7.bin (eta: 2-3 minutes)

2020-04-09 17:04:44 +0300:        [SUCCESS ] FW install pre-check completed successfully

2020-04-09 17:04:44 +0300:        [INFO     ] Performing FW install of nxos.7.0.3.I7.7.bin on dm01sw-rocea01 (eta: 3-7 minutes)

2020-04-09 17:09:51 +0300:        [SUCCESS ] FW install completed

2020-04-09 17:09:51 +0300:        [INFO     ] Waiting for switch to come back online (eta: 6-8 minutes)

2020-04-09 17:17:51 +0300:        [INFO     ] Verifying if FW install is successful

2020-04-09 17:17:53 +0300:        [SUCCESS ] dm01sw-rocea01 has been successfully upgraded to nxos.7.0.3.I7.7.bin!

2020-04-09 17:17:53 +0300 2 of 2 :Updating switch dm01sw-roceb01

2020-04-09 17:17:56 +0300:        [INFO     ] Switch dm01sw-roceb01 will be upgraded from nxos.7.0.3.I7.6.bin to nxos.7.0.3.I7.7.bin

2020-04-09 17:17:56 +0300:        [INFO     ] Checking for free disk space on switch

2020-04-09 17:17:57 +0300:        [INFO     ] disk is 95.00% free, available: 111542112256 bytes

2020-04-09 17:17:57 +0300:        [SUCCESS ] There is enough disk space to proceed

2020-04-09 17:17:58 +0300:        [INFO     ] Found nxos.7.0.3.I7.7.bin on switch, skipping download

2020-04-09 17:17:58 +0300:        [INFO     ] Verifying sha256sum of bin file on switch

2020-04-09 17:18:12 +0300:        [SUCCESS ] sha256sum matches: dce664f1a90927e9dbd86419681d138d3a7a83c5ea7222718c3f6565488ac6d0

2020-04-09 17:18:12 +0300:        [INFO     ] Performing FW install pre-check of nxos.7.0.3.I7.7.bin (eta: 2-3 minutes)

2020-04-09 17:20:12 +0300:        [SUCCESS ] FW install pre-check completed successfully

2020-04-09 17:20:12 +0300:        [INFO     ] Checking if previous switch dm01sw-rocea01 is fully up before proceeding (attempt 1 of 3)

2020-04-09 17:20:13 +0300:        [SUCCESS ] dm01sw-rocea01 switch is fully up and running

2020-04-09 17:20:13 +0300:        [INFO     ] Performing FW install of nxos.7.0.3.I7.7.bin on dm01sw-roceb01 (eta: 3-7 minutes)

2020-04-09 17:23:20 +0300:        [SUCCESS ] FW install completed

2020-04-09 17:23:20 +0300:        [INFO     ] Waiting for switch to come back online (eta: 6-8 minutes)

2020-04-09 17:31:20 +0300:        [INFO     ] Verifying if FW install is successful

2020-04-09 17:31:22 +0300:        [SUCCESS ] dm01sw-roceb01 has been successfully upgraded to nxos.7.0.3.I7.7.bin!

2020-04-09 17:31:22 +0300        :Working: Initiate config verify on RoCE switches from . Expect up to 6 minutes for each switch

2020-04-09 17:31:25 +0300 1 of 2 :Verifying config on switch dm01sw-rocea01

2020-04-09 17:31:25 +0300:        [INFO     ] Dumping current running config locally as file: /u01/stage/ROCE/run.dm01sw-rocea01.cfg

2020-04-09 17:31:26 +0300:        [SUCCESS ] Backed up switch config successfully

2020-04-09 17:31:26 +0300:        [INFO     ] Validating running config against template [1/3]: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 17:31:26 +0300:        [INFO     ] Config matches template: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 17:31:26 +0300:        [SUCCESS ] Config validation successful!

2020-04-09 17:31:26 +0300 2 of 2 :Verifying config on switch dm01sw-roceb01

2020-04-09 17:31:26 +0300:        [INFO     ] Dumping current running config locally as file: /u01/stage/ROCE/run.dm01sw-roceb01.cfg

2020-04-09 17:31:27 +0300:        [SUCCESS ] Backed up switch config successfully

2020-04-09 17:31:27 +0300:        [INFO     ] Validating running config against template [1/3]: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 17:31:27 +0300:        [INFO     ] Config matches template: /u01/stage/ROCE/patch_switch_19.3.6.0.0.200317/roce_switch_templates/roce_leaf_switch.cfg

2020-04-09 17:31:27 +0300:        [SUCCESS ] Config validation successful!

2020-04-09 17:31:27 +0300        :SUCCESS: Config check on RoCE switch(es)

2020-04-09 17:31:27 +0300        :SUCCESS: upgrade 2 RoCE switch(es) to 7.0(3)I7(7)

2020-04-09 17:31:27 +0300        :SUCCESS: Completed run of command: ./patchmgr –roceswitches /home/oracle/roce_list –upgrade –log_dir /u01/stage/ROCE

2020-04-09 17:31:27 +0300        :INFO   : upgrade attempted on nodes in file /home/oracle/roce_list: [dm01sw-rocea01 dm01sw-roceb01]

2020-04-09 17:31:27 +0300        :INFO   : For details, check the following files in /u01/stage/ROCE:

2020-04-09 17:31:27 +0300        :INFO   : – updateRoceSwitch.log

2020-04-09 17:31:27 +0300        :INFO   : – updateRoceSwitch.trc

2020-04-09 17:31:27 +0300        :INFO   : – patchmgr.stdout

2020-04-09 17:31:27 +0300        :INFO   : – patchmgr.stderr

2020-04-09 17:31:27 +0300        :INFO   : – patchmgr.log

2020-04-09 17:31:27 +0300        :INFO   : – patchmgr.trc

2020-04-09 17:31:27 +0300        :INFO   : Exit status:0

2020-04-09 17:31:27 +0300        :INFO   : Exiting.

10. Verify the new patch version on both RoCE switches

[oracle@dm01dbadm01 patch_switch_19.3.6.0.0.200317]$ ssh admin@dm01sw-rocea01 show version

The authenticity of host ‘dm01sw-rocea01 (dm01sw-rocea01)’ can’t be established.

RSA key fingerprint is SHA256:N3/OT3xe4A8xi1zd+bkTfDyqE6yibk2zVlhXHvCk/Jk.

RSA key fingerprint is MD5:c4:1f:ef:f5:f5:ab:f1:29:c0:de:42:19:0e:f3:14:8c.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added ‘dm01sw-rocea01’ (RSA) to the list of known hosts.

User Access Verification

Password:

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Copyright (C) 2002-2019, Cisco and/or its affiliates.

All rights reserved.

The copyrights to certain works contained in this software are

owned by other third parties and used and distributed under their own

licenses, such as open source. This software is provided “as is,” and unless

otherwise stated, there is no warranty, express or implied, including but not

limited to warranties of merchantability and fitness for a particular purpose.

Certain components of this software are licensed under

the GNU General Public License (GPL) version 2.0 or

GNU General Public License (GPL) version 3.0 or the GNU

Lesser General Public License (LGPL) Version 2.1 or

Lesser General Public License (LGPL) Version 2.0.

A copy of each such license is available at

http://www.opensource.org/licenses/gpl-2.0.php and

http://opensource.org/licenses/gpl-3.0.html and

http://www.opensource.org/licenses/lgpl-2.1.php and

http://www.gnu.org/licenses/old-licenses/library.txt.

Software

BIOS: version 05.39

NXOS: version 7.0(3)I7(7)

BIOS compile time: 08/30/2019

NXOS image file is: bootflash:///nxos.7.0.3.I7.7.bin

NXOS compile time: 3/5/2019 13:00:00 [03/05/2019 22:04:55]

Hardware

cisco Nexus9000 C9336C-FX2 Chassis

Intel(R) Xeon(R) CPU D-1526 @ 1.80GHz with 24571632 kB of memory.

Processor Board ID FDO23380VQS

Device name: dm01sw-rocea01

bootflash: 115805708 kB

Kernel uptime is 8 day(s), 5 hour(s), 1 minute(s), 41 second(s)

Last reset at 145297 usecs after Wed Apr 1 09:29:43 2020

Reason: Reset Requested by CLI command reload

System version: 7.0(3)I7(7)

Service:

plugin

Core Plugin, Ethernet Plugin

Active Package(s):

[oracle@dm01dbadm01 patch_switch_19.3.6.0.0.200317]$ ssh admin@dm01sw-rocea01 show version | grep “System version:”

User Access Verification

Password:

System version: 7.0(3)I7(7)

Conclusion

In this article we have learned how to patch an Exadata X8M RoCE switches. Oracle continues to use the patchmgr utility to patch the Exadata RoCE switch to simplify the process. The Exadata X8M 100 Gb/sec RoCE network fabric, making the world’s fastest database machine even faster.

About Netsoftmate:

Netsoftmate is an Oracle Gold Partner and a boutique IT services company specializing in installation, implementation and 24/7 support for Oracle Engineered Systems like Oracle Exadata, Oracle Database Appliance, Oracle ZDLRA, Oracle ZFS Storage and Oracle Private Cloud Appliance. Apart from OES, we have specialized teams of experts providing round the clock remote database administration support for any type of database and cyber security compliance and auditing services.

Feel free to get in touch with us by signing up on the link below –
April 16, 2020
5 Reasons Why Exadata is Important for Your Business Continuity

Cloud is an innovative operational model for IT and its transforming the business coordination. Attain superior results today and plan for better tomorrow with the help of a cloud-ready IT infrastructure. Oracle engineered systems are fabricated, integrated, tested, and optimized to work collectively. They are co-created with Oracle software for cloud-engineered integration. Oracle Exadata as a part of Oracle Engineered Systems is the only channel that provides optimal database performance and proficiency for analytics, mixed data and OLTP workloads.

Here are five top reasons stating why Oracle Exadata is important for Business Continuity.

Oracle Exadata for Business

Information is an important component of a business and most of it is available in the databases that power the business’ growth. Cloud-ready Oracle Exadata makes sure that your business is getting the most from your valuable information. Exadata for business provides amplified database performance, improved efficiency and operational flexibility for your business strategy around IoT, digital transformation, or agile IT. It diminishes the complexity of your database infrastructure and arranges for cloud migration, improving effectiveness and efficiency and helping you show a financial return.

Enhance Business Operations

Database Management is a crucial effort and includes appropriate administration of database infrastructure. However, generic infrastructure can create problems that delay application deployment and query revert times, affecting business and revenue growth.

Oracle Exadata enhances business operations and makes application development teams more productive. It also ensures that database administrator teams become more efficient. It helps in providing more value by establishing new business applications quickly and getting data that supports business operations. Oracle Exadata also improves database management, accessibility and dependability to enhance business operations altogether.

Massively Reduce Capital Expenses

With increasing demand for more data storage, there are more chances of increasing complexity, greater costs and less efficiency. A larger data center requires more power, floor space to pay for without any assurance of error-free management.

Oracle engineered systems’ Exadata is an engineered system that delivers more database and application performance with less hardware and reduced licenses. This means, you can get increased productivity, better services and massively reduce capital expenses. Oracle Exadata makes it possible without any increase in headcount or IT specialization. It reduces capital expenditure and operational costs, so you get the most from Oracle Database licenses.

Deliver Greater Business Value

Oracle Exadata increases business value by reducing deployment time, delivering better performance and enabling deeper customer insights. The long-term costs of DIY infrastructure are 53% higher than the integrated Oracle Exadata system. It integrates exceptional capabilities and operational mechanization to enable extreme performance, and significant cost savings. It empowers a business to revolutionize, drive innovative digital transformations and deliver greater business value. According to IDC, Exadata delivers 94% less unplanned downtime with the help of its built-in resilience and redundancy. Oracle Engineered System’s Exadata is a single entity closed system, making it more secure by design, with integral encryption.

Get the Benefits of Cloud

Exadata Cloud Service delivers the most advanced database cloud by combining the world’s top database technology and Exadata. It is the most powerful database platform, with the simplicity, agility and resistance of a cloud-based deployment. Businesses can now access Oracle databases on Oracle Exadata without capital investments for IT infrastructure such as space, power, compute servers, storing, networks and software. Exadata Cloud Service is fully compatible with on-premises Oracle databases and all existing applications. With Exadata Cloud Service, businesses can easily embrace a pure cloud or hybrid cloud strategy. Choose the Oracle Engineered System’s Exadata Cloud Service that’s equal to an on-premises Exadata, but in a cloud form.

About Netsoftmate Technologies Inc.

Netsoftmate is an Oracle Gold Partner and a boutique IT services company specializing in installation, implementation and 24/7 support for Oracle Engineered Systems like Oracle Exadata, Oracle Database Appliance, Oracle ZDLRA, Oracle ZFS Storage and Oracle Private Cloud Appliance. Apart from OES, we have specialized teams of experts providing round the clock remote database administration support for any type of database and cyber security compliance and auditing services.

Feel free to get in touch with us by signing up on the link below –

April 14, 2020
7 Easy Steps to Verify RoCE Cabling on Oracle Exadata X8M

Oracle has provided the verify_roce_cables.py to verify if the rack is cabled correctly for Transport Layer systems based on a RDMA over Converged Ethernet (RoCE) Network Layer network on Exadata Database Machine X8M-2/X8M-8 and later hardware.

Here is the step by step procedure to verify RoCE cabling on Oracle Exadata X8M Database Machine.

Exadata Infrastrure details:

Exadata Model : Exadata X8M-2 half rack

Exadata Software version: 19.3.3.0.0

Step 1: Download 30323660 for your Exadata smart software. In my case I have downloaded it for 19.3.3

Step 2: Copy the patch to staging area and unzip

[root@dm01db01 ~]# cd /u01/app/oracle/software

[root@dm01db01 software]# ls -l

total 8

-rw-r–r– 1 root root 8143 Feb 10 08:12 p30323660_193300_Linux-x86-64.zip

[root@dm01db01 software]# unzip p30323660_193300_Linux-x86-64.zip

Archive: p30323660_193300_Linux-x86-64.zip

inflating: setup_roce_switch_passwordless.sh

inflating: verify_roce_cables.py

inflating: README.txt

[root@dm01db01 software]# ls -ltr

total 40

-r-xr-xr-x 1 root root 2895 Oct 1 17:38 setup_roce_switch_passwordless.sh

-rwxr-xr-x 1 root root 22637 Jan 28 07:51 verify_roce_cables.py

-rw-r–r– 1 root root   673 Jan 28 08:45 README.txt

-rw-r–r– 1 root root 8143 Feb 10 08:12 p30323660_193300_Linux-x86-64.zip

Step 3: Read the readme.html file carefully

Step 4: setup password-less ssh to RoCE switches

[root@dm01db01 software]# ./setup_roce_switch_passwordless.sh dm01sw-rocea01

enter switch ‘dm01sw-rocea01’ ‘admin’ password:

checking if ‘dm01sw-rocea01’ is reachable… [OK]

setting up SSH equivalency for ‘admin’ on ‘dm01sw-rocea01’… [OK]

[root@dm01db01 software]# ./setup_roce_switch_passwordless.sh dm01sw-roceb01

enter switch ‘dm01sw-roceb01’ ‘admin’ password:

checking if ‘dm01sw-roceb01’ is reachable… [OK]

setting up SSH equivalency for ‘admin’ on ‘dm01sw-roceb01’… [OK]

“RECOMMENDED READ: HERE’S EVERYTHING YOU NEED TO KNOW ABOUT ORACLE AUTONOMOUS DATABASE CLOUD”

Step 5: setup passwordless ssh to all compute nodes and storage cells

[root@dm01db01 software]# cd /opt/oracle.SupportTools/

[root@dm01db01 oracle.SupportTools]# ls -ltr setup_ssh_eq.sh

-r-xr-x— 1 root root 1518 Dec 11 22:53 setup_ssh_eq.sh

[root@dm01db01 oracle.SupportTools]# ./setup_ssh_eq.sh ~/all_group root welcome1

[root@dm01db01 oracle.SupportTools]# dcli -g ~/all_group -l root uptime

dm01cel01: 09:11:46 up 5 days, 21:30, 0 users, load average: 2.44, 2.31, 2.05

dm01cel02: 09:11:46 up 5 days, 21:30, 0 users, load average: 2.31, 1.74, 1.97

dm01cel03: 09:11:46 up 5 days, 21:30, 0 users, load average: 2.97, 2.67, 2.60

dm01cel04: 09:11:46 up 5 days, 21:30, 0 users, load average: 2.78, 1.95, 1.71

dm01cel05: 09:11:46 up 5 days, 21:30, 0 users, load average: 3.83, 2.54, 2.05

dm01cel06: 09:11:46 up 5 days, 21:30, 0 users, load average: 0.82, 1.30, 1.68

dm01cel07: 09:11:46 up 5 days, 21:30, 0 users, load average: 1.55, 1.67, 1.71

dm01db01: 09:11:46 up 5 days, 21:37, 1 user, load average: 0.63, 0.48, 0.39

dm01db02: 09:11:46 up 5 days, 21:36, 0 users, load average: 0.23, 0.39, 0.34

dm01db03: 09:11:46 up 5 days, 21:36, 0 users, load average: 0.41, 0.32, 0.34

dm01db04: 09:11:46 up 5 days, 21:36, 0 users, load average: 0.19, 0.32, 0.29

Step 6: Create the file with compute nodes and storage cells in the formate given below

Lines in in nodes_list should be of format

adm<num>: <db1-hostname>

or

celadm<num>: <cell1-hostname>

[root@dm01db01 ~]# cat nodes_list

adm01: dm01db01

adm02: dm01db02

adm03: dm01db03

adm04: dm01db04

celadm01: dm01cel01

celadm02: dm01cel02

celadm03: dm01cel03

celadm04: dm01cel04

celadm05: dm01cel05

celadm06: dm01cel06

celadm07: dm01cel07

[root@dm01db01 ~]# cat roce_list

dm01sw-rocea01

dm01sw-roceb01

Step 7: Execute the RoCE Verify tool

[root@dm01db01 software]# cd /u01/app/oracle/software

[root@dm01db01 software]# ./verify_roce_cables.py -n ~/nodes_list -s ~/roce_list

Enter dm01sw-rocea01 admin password

User Access Verification

Enter dm01sw-roceb01 admin password

User Access Verification

Enter dm01sw-rocea01 admin password

User Access Verification

Enter dm01sw-roceb01 admin password

User Access Verification

SWITCH PORT (EXPECTED PEER)                      LEAF-1 (dm01sw-rocea01) : CABLE OK?                    LEAF-2 (dm01sw-roceb01) : CABLE OK?

———– —————             ——————————– : ——–            ——————————– : ———

    Eth1/4 (ISL peer switch)   :               dm01sw-roceb01 Ethernet1/4 : OK                       dm01sw-rocea01 Ethernet1/4 : OK

    Eth1/5 (ISL peer switch)   :               dm01sw-roceb01 Ethernet1/5 : OK                        dm01sw-rocea01 Ethernet1/5 : OK

    Eth1/6 (ISL peer switch)   :               dm01sw-roceb01 Ethernet1/6 : OK                        dm01sw-rocea01 Ethernet1/6 : OK

    Eth1/7 (ISL peer switch)   :               dm01sw-roceb01 Ethernet1/7 : OK                        dm01sw-rocea01 Ethernet1/7 : OK

    Eth1/8 ()                  :                                       – : –                                                  – : –

    Eth1/9 ()                  :                                       – : –                                                  – : –

   Eth1/10 ()                  :                                       – : –                                                  – : –

   Eth1/11 ()                  :                                       – : –                                                  – : –

   Eth1/12 ()                  :                                       – : –                                                  – : –

   Eth1/13 ()                  :                                       – : –                                                  – : –

   Eth1/14 ()                  :                                       – : –                                                  – : –

   Eth1/15 ()                  :                                       – : –                                                  – : –

   Eth1/16 ()                  :                                       – : –                                                  – : –

   Eth1/17 ()                  :                                       – : –                                                  – : –

   Eth1/18 ()                  :                                       – : –                                                  – : –

   Eth1/19 (adm04)             :                         dm01db04 port-1 : OK                                   dm01db04 port-2 : OK

   Eth1/20 (adm03)             :                         dm01db03 port-1 : OK                                   dm01db03 port-2 : OK

   Eth1/21 (adm02)             :                         dm01db02 port-1 : OK                                   dm01db02 port-2 : OK

   Eth1/22 (adm01)             :                         dm01db01 port-1 : OK                                   dm01db01 port-2 : OK

   Eth1/23 (celadm07)          :                        dm01cel07 port-1 : OK                                  dm01cel07 port-2 : OK

   Eth1/24 (celadm06)          :                        dm01cel06 port-1 : OK                                  dm01cel06 port-2 : OK

   Eth1/25 (celadm05)          :                        dm01cel05 port-1 : OK                                  dm01cel05 port-2 : OK

   Eth1/26 (celadm04)          :                        dm01cel04 port-1 : OK                                  dm01cel04 port-2 : OK

   Eth1/27 (celadm03)          :                        dm01cel03 port-1 : OK                                  dm01cel03 port-2 : OK

   Eth1/28 (celadm02)          :                        dm01cel02 port-1 : OK                                  dm01cel02 port-2 : OK

   Eth1/29 (celadm01)          :                        dm01cel01 port-1 : OK                                  dm01cel01 port-2 : OK

   Eth1/30 (ISL peer switch)   :             dm01sw-roceb01 Ethernet1/30 : OK                         dm01sw-rocea01 Ethernet1/30 : OK

   Eth1/31 (ISL peer switch)   :             dm01sw-roceb01 Ethernet1/31 : OK                        dm01sw-rocea01 Ethernet1/31 : OK

   Eth1/32 (ISL peer switch)   :             dm01sw-roceb01 Ethernet1/32 : OK                        dm01sw-rocea01 Ethernet1/32 : OK

   Eth1/33 (ISL peer switch)   :             dm01sw-roceb01 Ethernet1/33 : OK                        dm01sw-rocea01 Ethernet1/33 : OK

From the above output we can see the cabling is OK which means it is good. There are no errors/failure reported for cabling.

The following states are applicable for “CABLE OK”

OK : Cabling looks good

SWAPPED : Cables have been crossed on same host

FAIL : Cabling check failed due to cabling error, discovery issues, etc.

– : If any of the table entry has a ‘-‘, it can be treated as a don’t care or not applicable

Conclusion

In this article we have learned how to verify the cabling for Transport Layer systems based on a RDMA over Converged Ethernet (RoCE) Network Layer network on Exadata Database Machine X8M-2/X8M-8 and later hardware.

Have more queries related Exadata Database Machines? Get in touch with Netsoftmate’s Oracle Engineered Systems experts to get the best solution on how to implement and maintain your Oracle Exadata Database Machines. Sign-up for a 30 mins free consultation by clicking the image below –

March 25, 2020

How to Restore Compute node from Snapshot Backup for Oracle Exadata

Netsoftmate experts are back again with another interesting article which will help you setup and restore compute node from snapshot backup of Oracle Exadata. In our previous blog we have demonstrated a step-by-step process of how to take a snapshot based back-up of compute node to NFS share.

If you haven’t yet read the previous article, here’s the link for reference –

Step-by-step guide of exadata sanpshot based backup of compute node to nfs share

In this article, we will be focussing on how to setup and restore the compute node from the snapshot backup on a live Oracle Exadata Database Machine.

Introduction

You have Oracle Exadata compute snapshot backup, but you don’t know the procedure to restore the compute node. How would you restore your compute node?

Snapshot backup is very helpful in case of OS failure or any other failure that causes Compute node failure. With the snapshot backup you can restore the compute node with few simple steps without having to go through the complex Oracle Exadata BareMetal restore.

Environment Details

Exadata Model	X5-2 Full Rack
Exadata Components	8 – Compute nodes, 14 – Storage cells & 2 – IB switches
Exadata Storage cells	DBM01CEL01 – DBM01CEL14
Exadata Compute nodes	DBM01DB01 – DBM01DB08
Exadata Software Version	12.1.2.3
Exadata DB Version	11.2.0.4.180717

Prerequisites

– Root user access on Compute nodes
– Snapshot backup taken before the failure
– NFS mount storing the snapshot backup

Note: We can’t use Infiniband interface to mount the NFS file system. Only Management interface can be used to mount the NFS file system.

Step 1

Copy snapshot backup to the NFS mount mounted using management interface.

In this example: I have mounted the NFS share using the following directory

/nfssa/dm01/os_snapshot

[root@dm01db07 os_snapshot]# cd /nfssa/dm01/os_snapshot

[root@dm01db07 os_snapshot]# ls -lrt|grep Rt_U01

-rw-r–r– 1 4294967294 4294967294 24268161485 Jun 17 04:36 Rt_U01_20190617_dm01db07_bkp.tar.bz2

Step 2

Copy diag.iso from MOS or from another goo compute node to the NFS mount.

[root@dm01db07 os_snapshot]# cd /nfssa/dm01/os_snapshot

[root@dm01db07 os_snapshot]# ls -lrt|grep diag.iso

-r–r—– 1 4294967294 4294967294 78139392 Jul 12 2019 diag.iso

Step 3:

During the restore process you will be prompted to provide the following details. Make a note of these inputs before proceeding to the next step

i. The full path of the backup

10.10.2.21:/export/dm01/os_snapshot/ Rt_U01_20190617_dm01db07_bkp.tar.bz2

ii. Host IP: 10.2.15

iii. Netmask: 255.255.192
iii. Gateway: 10.2.100

Step 4

a) Log in to the Oracle ILOM CLI

[root@dm01db06 ~]# ssh dm01db06-ilom

Password:

Oracle(R) Integrated Lights Out Manager

Version 3.2.8.24 r114580

Warning: HTTPS certificate is set to factory default.

Hostname: dm01db06-ilom

b) Run the following command on CLI to mount ISO from NFS server

-> cd /SP/services/kvms/host_storage_device/remote/

/SP/services/kvms/host_storage_device/remote

-> set server_URI=nfs://10.10.2.21:/export/dm01/os_snapshot/diag.iso

Set ‘server_URI’ to ‘nfs://10.10.2.21:/export/dm01/os_snapshot/diag.iso’

-> show server_URI

/SP/services/kvms/host_storage_device/remote

Properties:

server_URI = nfs://10.10.2.21:/export/dm01/os_snapshot/diag.iso

c) Enable storage redirection by typing:

-> set /SP/services/kvms/host_storage_device/ mode=remote

Set ‘mode’ to ‘remote’

To view the status of redirection, type the command:

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

d) Set the next boot device to cdrom

-> set /HOST boot_device=cdrom

Set ‘boot_device’ to ‘cdrom’

To ensure next boot device, check

-> show /HOST

/HOST

Targets:

console

diag

provisioning

Properties:

boot_device = cdrom

generate_host_nmi = (Cannot show property)

Commands:

set

show

e) Reboot Server

-> reset /SYS

Are you sure you want to reset /SYS (y/n)? y

Performing hard reset on /SYS

Step 5

Start the serial console using the command below:

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

Serial console started. To stop, type ESC (

Note: optionally you can also start the Remote direction using Web ILOM.

Wait for the server to boot from the diag.iso

On both the Remote Console window and the putty/SSH session window you will see the server going through BIOS POST, then the kernel boot messages.

At the end of the boot up sequence, there should be the menu prompt such as the one below.:

– Input (r) for restore
– ‘y’ to continue
– Rescue password: sos1Exadata

Next prompt would be for path of backup file provide as follows from Step 3:

10.10.2.21:/export/dm01/os_snapshot/ Rt_U01_20190617_dm01db07_bkp.tar.bz2

Next prompt for LVM schema say (y). Type y and hit return

Next prompt input interface, IP address of host and gateway taken from Step 3

At the end of this step, the server would enter recovery phase which may take about 3 hours.

Step 6:

When the recovery completes, the login screen appears. Verify the file system.

This concludes a successful recovery

Step 7:

Disable cd 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

-> 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)

-> show /HOST

/HOST

Targets:

console

diag

provisioning

Properties:

boot_device = default

generate_host_nmi = (Cannot show property)

Commands:

set

show

Reboot server to use default BIO image

-> reset /SYS

Are you sure you want to reset /SYS (y/n)? y

Performing hard reset on /SYS

Step 8:

Verify server

[root@dm01db07 ~]# imageinfo
Kernel version: 2.6.39-400.294.1.el6uek.x86_64 #1 SMP Wed Jan 11 08:46:38 PST 2017 x86_64
Image kernel version: 2.6.39-400.294.1.el6uek
Image version: 12.1.2.3.4.170111
Image activated: 2017-09-19 13:23:57 -0500
Image status: success
System partition on device: /dev/mapper/VGExaDb-LVDbSys1

If the image status post restore shows failure then perform the following addition steps to make it success.

Image status: failure

# /usr/sbin/ubiosconfig export all -x /tmp/bios_current.xml –expert_mode -y
If it still fails, then try reset the SP and try above the command again.
If the command ran successful without error, then reboot the system.
After system comes back up, wait for approximately 10min, and check and confirm that the output of imageinfo command is “Image status: success”

Conclusion:

In this article we have learned how to restore an Exadata Compute node from Exadata Compute node snapshot backup

March 12, 2020

Step-by-step Guide of Exadata Snapshot Based Backup of Compute Node to NFS Share

Backing up file systems on Oracle Exadata compute can be a daunting task if you are unaware of the prerequisites and best practices. To help you backup your file systems effectively and with least discrepancies, we are bringing you this interesting step-by-step guide on how to back up your file system using Oracle Exadata Sanpshot Based Backup of Compute Node to NFS Share

It is very important to take file system backup on Oracle Exadata compute nodes before we make any major changes to the operating system or critical software. On Oracle Exadata Compute nodes / (root) and /u01 file systems contains the operating system and GI/DB software respectively. These are the most critical file systems on Oracle Exadata computes.

By default, the / (root) and /u01 file system are sized 30GB and 100GB respectively.

Scenarios in which we must take file system backup are:

– Operating System Patching or Upgrade
– Grid Infrastructure Patching or Upgrade
– Database Patching or Upgrade
– Operating System configuration changes
– Increasing/decreasing file system size

In this article, we will demonstrate how to backup file system on Oracle Exadata Compute nodes running Linux Operating System to external storage NFS Share.

Environment Details

Exadata Model	X4-2 Half Rack HP 4 TB
Exadata Components	4 – Compute nodes, 7 – Storage cells & 2 – IB switches
Exadata Storage cells	DBM01CEL01 – DBM01CEL07
Exadata Compute nodes	DBM01DB01 – DBM01DB04
Exadata Software Version	19.2.3.0
Exadata DB Version	11.2.0.4.180717

Prerequisites

– Root user access on Compute nodes
– NFS mount with sufficient storage to storing file system backup

Current root and /u01 file system sizes

[root@ip01db01 ~]# df -h / /u01

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/VGExaDb-LVDbSys1 59G 39G 18G 70% /

/dev/mapper/VGExaDb-LVDbOra1 197G 171G 17G 92% /u01

NFS share details

10.10.10.1:/nfs/backup/

1. As root user, log in to the Exadata Compute node you wish to backup

[root@ip01db01 ~]# id root

uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)

2. Create a mount point to mount NFS share

[root@dm01db01 ~]# mkdir -p /mnt/backup

[root@dm01db01 ~]# mount -t nfs -o rw,intr,soft,proto=tcp,nolock 10.10.10.1:/nfs/backup/ /mnt/backup

3. Determine the file system type extension root and u01 file system

[root@ip01db01 ~]# mount -l

sysfs on /sys type sysfs (rw,relatime)

proc on /proc type proc (rw,relatime)

devtmpfs on /dev type devtmpfs (rw,nosuid,size=131804372k,nr_inodes=32951093,mode=755)

securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)

tmpfs on /dev/shm type tmpfs (rw,size=264225792k)

/dev/mapper/VGExaDb-LVDbSys1 on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered) [DBSYS]

/dev/mapper/VGExaDb-LVDbOra1 on /u01 type ext3 (rw,nodev,relatime,errors=continue,barrier=1,data=ordered) [DBORA]

/dev/sda1 on /boot type ext3 (rw,nodev,relatime,errors=continue,barrier=1,data=ordered) [BOOT]

4. Note down the file system type for root and /u01: ext3. Take a snapshot-based of the root and u01 directories, Label the snapshot and Mount the snapshot

[root@dm01db01 ~]# lvcreate -L5G -s -n root_snap /dev/VGExaDb/LVDbSys1

Logical volume “root_snap” created.

[root@dm01db01 ~]# lvcreate -L5G -s -n u01_snap /dev/VGExaDb/LVDbOra1

Logical volume “u01_snap” created.

[root@dm01db01 ~]# e2label /dev/VGExaDb/root_snap DBSYS_SNAP

[root@dm01db01 ~]# e2label /dev/VGExaDb/u01_snap DBORA_SNAP

[root@dm01db01 ~]# mkdir -p /mnt/snap/root

[root@dm01db01 ~]# mkdir -p /mnt/snap/u01

[root@dm01db01 ~]# mount /dev/VGExaDb/root_snap /mnt/snap/root -t ext3

[root@dm01db01 ~]# mount /dev/VGExaDb/u01_snap /mnt/snap/u01 -t ext3

[root@dm01db01 ~]# df -h /mnt/snap/root

[root@dm01db01 ~]# df -h /mnt/snap/u01

5. Change to the directory for the backup and Create the backup file

[root@dm01db01 ~]# cd /mnt/backup

[root@dm01db01 ~]# tar -pjcvf /mnt/backup/mybackup.tar.bz2 * /boot –exclude /mnt/backup/mybackup.tar.bz2 > /tmp/backup_tar.stdout 2> /tmp/backup_tar.stderr

6. Monitor the /tmp/backup_tar.stderr file for errors. Errors such as failing to tar open sockets can be ignored.

7. Unmount the snapshots and remove the snapshots for the root and /01 directories.

[root@dm01db01 ~]# cd /

[root@dm01db01 /]# umount /mnt/snap/u01

[root@dm01db01 /]# umount /mnt/snap/root

[root@dm01db01 /]# df -h /mnt/snap/u01

[root@dm01db01 /]# df -h /mnt/snap/root

[root@dm01db01 /]# ls -l /mnt/snap

[root@dm01db01 /]# rm -rf /mnt/snap

[root@dm01db01 /]# lvremove /dev/VGExaDb/u01_snap

Do you really want to remove active logical volume u01_snap? [y/n]: y

Logical volume “u01_snap” successfully removed

[root@dm01db01 /]# lvremove /dev/VGExaDb/root_snap

Do you really want to remove active logical volume root_snap? [y/n]: y

Logical volume “root_snap” successfully removed

8. Unmount the NFS share

[root@dm01db01 /] umount /mnt/backup

Repeat the above steps on the remaining compute nodes to backup root & u01 file system

We hope this article helps you smoothly backup your file system on Oracle Exadata Compute node running Oracle Linux using NFS Share. Stay tuned for more step-by-step guides on implementing and using Oracle Database Systems exclusively on Netsoftmate

Netsoftmate provides the best standard services when it comes to Oracle databases management, covering all comples database products. Sign-up for a free 30 minutes call by clicking on the link below –

Click here and fill the contact us form for a free 30 minutes consultation

February 1, 2020

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 compared with X7-2 Models.

Let’s take a quick look at few benefits of ODA followed by the technical specification on ODA X8-2 Small/Medium and HA.

Oracle Database Appliance is an Engineered System. Software, server, storage, and networking, all co-engineered and optimized to run Oracle Database and applications.

Benefits of Oracle Database Appliance (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.
Ease of deployment, patching, management, and support.
Increased performance and reliability with NVMe flash storage.
Reliable hardware architecture with redundant power, cooling, networking, and storage.
Browser User Interface (BUI)

In this article we will compare the technical specifications of ODA X8-2 model family (Small, Medium and HA). This comparison table comes handy when you want to quickly take a look at the resources available for a given model.

For more information on the technical specification loot at the ODA X8-2 HA and Small/Medium Data Sheet at:

https://www.oracle.com/technetwork/database/database-appliance/oda-x8-2-ha-datasheet-5730739.pdf

https://www.oracle.com/technetwork/database/database-appliance/oda-x8-2sm-datasheet-5730738.pdf

Component	ODA X8-2 Small	ODA X8-2 Medium	ODA X8-2 HA
Database Server	1	1	2
Storage Shelf	NA	NA	1 4U DE3-24C Storage Shelf per System Optional Second Storage Shelf for Expansion
Rack Size	1 2RU Server	1 2RU Server	2 2RU Servers & 1 4U Storage Shelf
Processor	One 16-core Intel Xeon Gold 5218	Two 16-core Intel Xeon Gold 5218	Two 16-core Intel Xeon Gold 5218 Per Server
Physical Memory	192 GB Expandable to 384 GB	384 GB Expandable to 768 GB	384 GB Expandable to 768 GB per server
Storage	Two 6.4 TB NVMe SSDs 12.8 TB (raw)	Base: Two 6.4 TB NVMe SSDs 12.8 TB (raw)	Base: Six 7.68 TB SSDs 46 TB (raw)
Storage Expansion	Not expandable	Expandable up to 76.8 TB (raw)	Expandable up to 369 TB SSD or up to 92 TB SSD / 504 TB HDD (Raw)
Network	4 x 10GBase-T ports (RJ45) expandable up to 12 x 10GBase-T ports or 2 x 10/25 GbE ports (SFP28) expandable up to 6 x 10/25 GbE ports	4 x 10GBase-T ports (RJ45) expandable up to 12 x 10GBase-T ports or 2 x 10/25 GbE ports (SFP28) expandable up to 6 x 10/25 GbE ports	4 x 10GBase-T ports (RJ45) expandable up to 12 x 10GBase-T ports or 2 x 10/25 GbE ports (SFP28) expandable up to 6 x 10/25 GbE ports
Oracle Database	Oracle Database 18c/19c EE & SE 2 Oracle Database 12c R1/R2 EE & SE 2 Oracle Database 11g R2 EE, SE & SE 1	Oracle Database 18c/19c EE & SE 2 Oracle Database 12c R1/R2 EE & SE 2 Oracle Database 11g R2 EE, SE & SE 1	Oracle Database 18c/19c EE & SE 2 Oracle Database 12c R1/R2 EE & SE 2 Oracle Database 11g R2 EE, SE & SE 1
Database Deployment	Single Instance	Single Instance	Single Instance, RAC & RAC One node
Virtualization	Oracle Linux KVM	Oracle Linux KVM	Oracle VM & Oracle Linux KVM
Operating System	Oracle Linux	Oracle Linux	Oracle Linux

Are you and your team considering setting up Oracle Database Appliance? Let Netsoftmate help you choose the right product keeping under consideration your budget, requirement and usage forecasting. Click on the image below to sign-up NOW!

October 24, 2019

Exclusive First Look into Oracle Database Appliance X8 Model Family
In September 2019, Oracle announced Oracle Database Appliance X8-2 (Small, Medium and HA). ODA X8-2 comes with more computing resources compared with X7-2 Models.

Let’s take a quick look at few benefits of ODA followed by the technical specification on ODA X8-2 Small/Medium and HA.

Oracle Database Appliance is an Engineered System. Software, server, storage, and networking, all co-engineered and optimized to run Oracle Database and applications.

Benefits of Oracle Database Appliance (ODA):
1. Software, server, storage, and networking engineered and optimized to run Oracle Database and applications.
2. Supports Oracle Database Standard Edition, Standard Edition One, Standard Edition 2, and Enterprise Edition.
3. Optimized for Cloud
4. Capacity on Demand Licensing – Reduced Cost
5. Ease of deployment, patching, management, and support
6. Increased performance and reliability with NVMe flash storage
7. Reliable hardware architecture with redundant power, cooling, networking, and storage
8. Browser User Interface (BUI)
Oracle Database Appliance X8-2 HA Benefits & Technical specification
1. Support mission-critical applications and consolidation of many databases
2. Built for high availability
3. Choice of high-performance flash or high-capacity drives
4. 32 cores per server (64 cores in total for 2 servers)
5. 384 GB physical memory per server expandable upto 768 (1.5 TB memory in total for 2 servers)
6. Storage Shelf
7. High Capacity: 46 TB SSD and 252 TB SDD raw capacity per shelf
8. High Performance: 184 TB SSD raw capacity per shelf
9. Choice of 10GBase-T or 10/25 GbE SFP28 public networking
10. 25GbE interconnect for cluster communication
For more information on the technical specification loot at the ODA X8-2 HA Data Sheet at:
https://www.oracle.com/technetwork/database/database-appliance/oda-x8-2-ha-datasheet-5730739.pdf
- Oracle Database Appliance X8-2 Small Technical specification
1. One server
2. 1 Intel Xeon processor, 16 Cores
3. 192GB Physical memory expandable upto 384GB
4. Choice of 10GBase-T or 10/25 GbE SFP28 public networking
5. 12.8TB NVMe raw storage
Oracle Database Appliance X8-2 Medium Technical specification
1. One server
2. 2 Intel Xeon processor, 32 Cores
3. 384 GB Physical memory expandable upto 768GB
4. Choice of 10GBase-T or 10/25 GbE SFP28 public networking
5. 12.8 TB NVMe raw storage capacity with optional expansion to 76.8 TB NVMe raw storage
For more information on the technical specification loot at the ODA X8-2 S/M Data Sheet at:
https://www.oracle.com/technetwork/database/database-appliance/oda-x8-2sm-datasheet-5730738.pdf

Conclusion

In this article we seen the benefits and the technical specification of latest Oracle Database Appliance X8 model family. ODA is the right choice for all type of Businesses as an on-premises solution and cloud ready option.

Are you and your team considering setting up Oracle Database Appliance? Let Netsoftmate help you choose the right product keeping under consideration your budget, requirement and usage forecasting. Click on the image below to sign-up NOW!
September 24, 2019

Category: Database Management Services

What are the different Exadata Deployment Option available?

What is Oracle Exadata Database Machine?

Exadata Database Machine or simply known as Exadata is:

Exadata Database Machine Components

Oracle Exadata Cloud Service

Oracle Exadata Cloud @ Customer

Oracle Exadata Deployment Comparison

1. Bespoke for Oracle Database

2. Increase Employee Productivity

3. Achieve Operational Benefits

4. Maximize Accessibility

5. Invest in the Cloud

About Netsoftmate Technologies Inc.

Oracle Exadata RoCE Switch Image:In this article we see practically how to patch Exadata X8M RoCE Switches

Here are five top reasons stating why Oracle Exadata is important for Business Continuity. Oracle Exadata for Business

Enhance Business Operations

Massively Reduce Capital Expenses

Deliver Greater Business Value

Get the Benefits of Cloud

Exadata Infrastrure details:

Step 1: Download 30323660 for your Exadata smart software. In my case I have downloaded it for 19.3.3

Step 2: Copy the patch to staging area and unzip

Step 3: Read the readme.html file carefully

Step 4: setup password-less ssh to RoCE switches

Step 5: setup passwordless ssh to all compute nodes and storage cells

Step 6: Create the file with compute nodes and storage cells in the formate given below

Step 7: Execute the RoCE Verify tool

Conclusion

Introduction

Environment Details

Prerequisites

Scenarios in which we must take file system backup are:

Environment Details

Prerequisites

Current root and /u01 file system sizes

NFS share details

1. As root user, log in to the Exadata Compute node you wish to backup

2. Create a mount point to mount NFS share

3. Determine the file system type extension root and u01 file system

4. Note down the file system type for root and /u01: ext3. Take a snapshot-based of the root and u01 directories, Label the snapshot and Mount the snapshot

5. Change to the directory for the backup and Create the backup file

6. Monitor the /tmp/backup_tar.stderr file for errors. Errors such as failing to tar open sockets can be ignored.

7. Unmount the snapshots and remove the snapshots for the root and /01 directories.

8. Unmount the NFS share

Repeat the above steps on the remaining compute nodes to backup root & u01 file system

Benefits of Oracle Database Appliance (ODA):

Benefits of Oracle Database Appliance (ODA):

Oracle Database Appliance X8-2 HA Benefits & Technical specification

Oracle Database Appliance X8-2 Small Technical specification

Oracle Database Appliance X8-2 Medium Technical specification

Oracle Exadata RoCE Switch Image:
In this article we see practically how to patch Exadata X8M RoCE Switches

Here are five top reasons stating why Oracle Exadata is important for Business Continuity.

Oracle Exadata for Business