You want to install some packages on the Exadata Compute nodes running Oracle Enterprise Linux and you don’t have internet access. In those cases you can create a local YUM repository using DVD Image. You simply download the DVD Image on the Desktop/Laptop where you have the internet access, copy it to the server and mount it.

In this article we will demonstrate how create a Local YUM Repository using ISO Image on Exadata Database Machines.

Prerequisites

System with Internet
Sufficient space on the server for Oracle Linux DVD ISO

Steps to create a Local YUM Repository using ISO Image on Exadata Database Machines

Step 1: Download Oracle Linux DVD Image from the Oracle Software Delivery Cloud at http://edelivery.oracle.com/linux

Here I am downloading:
V860937-01.iso Oracle Linux 6 Update 9 for x86 64 bit, 3.8 GB

Step 2: Copy the DVD image to the server to a staging directory using Winscp

Create a staging directory on the server

[root@dm01db01 ~]# mkdir -p /u01/app/oracle/software/ISO

Use Winscp to copy the ISO Image to the server

[root@dm01db01 ~]# ls -l /u01/app/oracle/software/ISO
total 3953672
-rw-r–r– 1 root root 4048551936 Mar 20 04:18 V860937-01.iso

Step 3: Create a mount point, for example /mnt/OEL6.9, and mount the DVD image on it.

[root@dm01db01 ~]# mkdir -p /mnt/OEL6.9

[root@dm01db01 ~]# ls -l /mnt/OEL6.9
total 0

[root@dm01db01 ~]# mount -o loop,ro /u01/app/oracle/software/ISO/V860937-01.iso /mnt/OEL6.9

[root@dm01db01 ~]# df -h /mnt/OEL6.9
Filesystem Size Used Avail Use% Mounted on
/u01/app/oracle/software/ISO/V860937-01.iso
3.8G 3.8G 0 100% /mnt/OEL6.9

[root@dm01db01 ~]# cd /mnt/OEL6.9

[root@dm01db01 OEL6.9]# ls -l
total 1686
drwxr-xr-x 3 root root 2048 Mar 24 2017 EFI
-rw-r–r– 1 root root 8529 Mar 24 2017 EULA
-rw-r–r– 1 root root 8529 Mar 24 2017 eula.en_US
-rw-r–r– 1 root root 3334 Mar 24 2017 eula.py
-rw-r–r– 1 root root 18390 Mar 24 2017 GPL
drwxr-xr-x 3 root root 2048 Mar 24 2017 HighAvailability
drwxr-xr-x 3 root root 2048 Mar 24 2017 images
drwxr-xr-x 2 root root 2048 Mar 24 2017 isolinux
drwxr-xr-x 3 root root 2048 Mar 24 2017 LoadBalancer
-rw-r–r– 1 root root 98 Mar 24 2017 media.repo
drwxr-xr-x 2 root root 716800 Mar 24 2017 Packages
-rw-r–r– 1 root root 7193 Mar 24 2017 README-en
-rw-r–r– 1 root root 6016 Mar 24 2017 README-en.html
-rw-r–r– 1 root root 81004 Mar 24 2017 RELEASE-NOTES-en
-rw-r–r– 1 root root 227548 Mar 24 2017 RELEASE-NOTES-en.html
-rw-r–r– 1 root root 81004 Mar 24 2017 RELEASE-NOTES-x86_64-en
-rw-r–r– 1 root root 227548 Mar 24 2017 RELEASE-NOTES-x86_64-en.html
-rw-r–r– 1 root root 81004 Mar 24 2017 RELEASE-NOTES-x86-en
-rw-r–r– 1 root root 227548 Mar 24 2017 RELEASE-NOTES-x86-en.html
lrwxrwxrwx 1 root root 15 Mar 24 2017 repodata -> Server/repodata
drwxr-xr-x 3 root root 2048 Mar 24 2017 ResilientStorage
-rw-r–r– 1 root root 1011 Mar 24 2017 RPM-GPG-KEY
-rw-r–r– 1 root root 1011 Mar 24 2017 RPM-GPG-KEY-oracle
drwxr-xr-x 3 root root 2048 Mar 24 2017 ScalableFileSystem
drwxr-xr-x 4 root root 2048 Mar 24 2017 Server
-rw-r–r– 1 root root 108 Mar 24 2017 supportinfo
-r–r–r– 1 root root 6517 Mar 24 2017 TRANS.TBL
drwxr-xr-x 3 root root 2048 Mar 24 2017 UEK4

Step 4: Add an entry to the /etc/fstab file, this will to auto mount the DVD image after a reboot.

/u01/app/oracle/software/ISO/V860937-01.iso /mnt/OEL6.9 iso9660 loop,ro 0 0

[root@dm01db01 ~]# vi /etc/fstab

[root@dm01db01 ~]# cat /etc/fstab
LABEL=DBSYS / ext4 defaults 1 1
LABEL=BOOT /boot ext4 defaults,nodev 1 1
LABEL=DBORA /u01 ext4 defaults,nodev 1 1
tmpfs /dev/shm tmpfs defaults,size=258341m 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP swap swap defaults 0 0
/u01/app/oracle/software/ISO/V860937-01.iso /mnt/OEL6.9 iso9660 loop,ro 0 0

Step 5: Navigate to /etc/yum.repos.d directory, you can edit the existing repository files public-yum-ol6.repo or create a new repo file such as ULN-base.repo, and disable all entries by setting enabled=0.

[root@dm01db01 ~]# cd /etc/yum.repos.d

[root@dm01db01 yum.repos.d]# ls -l
total 20
-rw-r—– 1 root root 291 Mar 31 22:43 Exadata-computenode.repo
-r–r—– 1 root root 896 Jan 26 06:19 Exadata-computenode.repo.sample
-rw-r–r– 1 root root 7299 Mar 20 05:57 public-yum-ol6.repo

Here I am going to create the OL69.repo repository file and add the entries

[root@dm01db01 yum.repos.d]# vi OL69.repo

[root@dm01db01 yum.repos.d]# cat OL69.repo
[OL69]
name=Oracle Linux 6.9 x86_64
baseurl=file:///mnt/OEL6.9
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY
gpgcheck=1
enabled=1

Step 7: Perform YUM Cache cleanup as below

[root@dm01db01 yum.repos.d]# yum clean all
Cleaning repos: OL69
Cleaning up Everything

Step 8: Perform a test to ensure you can access yum repository

[root@dm01db01 yum.repos.d]# yum repolist
OL69 | 3.7 kB 00:00 …
OL69/primary_db | 3.1 MB 00:00 …
repo id repo name status
OL69 Oracle Linux 6.9 x86_64 3,860
repolist: 3,860

Conclusion

In this article we have learned how to create local YUM repository using DVD ISO Image on Exadata Database Machine. Configuring a local YUM repository comes handy when you want to install packages on the server and you don’t have internet access from the server.

Mount External USB Drive On Exadata Compute Node

By Netsoftmate on

May 1, 2018

- Uncategorized

You have files on an External USB drive that you want to connect to Exadata Compute node to copy them over to the server file system. This can be done for several reasons such as Database Migration.

In this article I will demonstrate step by step how to mount an Exadata USB drive to Exadata Compute node.

Steps to mount External USB on Exadata Compute node

Connect the External USB drive to Exadata Compute node. This can be done easily by Data Center Engineer who has access to Data Center and Exadata Rack.

Once the USB is connected, Verify you can see it on the Exadata Compute node by running the following command.

[root@dm01db01 ~]# multipath -l
33e41384658514e52 dm-5 Seagate,Expansion Desk
size=3.6T features=’0′ hwhandler=’0′ wp=rw
`-+- policy=’round-robin 0′ prio=0 status=active
`- 7:0:0:0 sdb 8:16 active undef unknown

You can also use “fdisk -l” command to list the connected USB.

[root@dm01db01 ~]# fsdisk -l
….
Device Boot Start End Blocks Id System
/dev/mapper/33e41384658514e52p1 1 267350 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

[root@dm01db01 ~]# ls -l /dev/mapper/
total 0
lrwxrwxrwx 1 root root 7 Apr 24 18:53 33e41384658514e52 -> ../dm-5
lrwxrwxrwx 1 root root 7 Apr 24 18:53 33e41384658514e52p1 -> ../dm-6
crw-rw—- 1 root root 10, 236 Apr 22 14:23 control
lrwxrwxrwx 1 root root 7 Apr 24 18:53 VGExaDb-LVDbOra1 -> ../dm-3
lrwxrwxrwx 1 root root 7 Apr 24 18:53 VGExaDb-LVDbSwap1 -> ../dm-2
lrwxrwxrwx 1 root root 7 Apr 24 18:53 VGExaDb-LVDbSys1 -> ../dm-0
lrwxrwxrwx 1 root root 7 Apr 24 18:53 VGExaDb-LVDbSys2 -> ../dm-1
lrwxrwxrwx 1 root root 7 Apr 24 18:53 VGExaDb-LVDoNotRemoveOrUse -> ../dm-4

Create a mount point

[root@dm01db01 mnt]# mkdir -p /mnt/dbmigration

Verify the file system type for mounting purpose. Here the it is ext4

[root@dm01db01 mnt]# mount -l
/dev/mapper/VGExaDb-LVDbSys1 on / type ext4 (rw) [DBSYS]
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,size=775461m)
/dev/sda1 on /boot type ext4 (rw,nodev) [BOOT]
/dev/mapper/VGExaDb-LVDbOra1 on /u01 type ext4 (rw,nodev) [DBORA]
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)

Mount the External USB on the local mount point created.

[root@dm01db01 ~]# mount -t ext4 /dev/mapper/33e41384658514e52p1 /mnt/dbmigration

Verify the UBS is mounted successfully

[root@dm01db01 ~]# df -h /mnt/dbmigration
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/33e41384658514e52p1
2.0T 99G 1.8T 6% /mnt/dbmigration

Change directory permissions and ownership to Oracle

[root@dm01db01 ~]# chown oracle:oinstall -R /mnt/dbmigration

[root@dm01db01 ~]# chmod 775 -R /mnt/dbmigration

Verify the permissions and ownership

[root@dm01db01 ~]# ls -ld /mnt/dbmigration
drwxrwxr-x 4 oracle oinstall 4096 Apr 25 09:49 /mnt/dbmigration

Verify that that you can access and list the contents from USB.

[root@dm01db01 ~]# cd /mnt/dbmigration

[root@dm01db01 dbmigration]# ls -ltr
total 103004260
-rw-r—– 1 500 500 6786600960 Apr 25 11:25 expdp_full.dmp
-rw-r—– 1 500 500 7231434752 Apr 25 11:25 expdp_schema.dmp
-rw-r–r– 1 500 500 129609 Apr 25 11:30 expdp_schemas.log

Conclusion

In this article we have learned how to mount an External USB drive on Exadata Compute node.

Exadata Database Machine Health Check Using Exachk Utility

By Netsoftmate on

April 20, 2018

- Uncategorized

Oracle provides “Exachk” utility to conduct a comprehensive Exadata Health Check on Exadata Database Machine to validate hardware, firmware and configuration.

Exachk Utility is available for Oracle engineered systems such as Exadata (V2 and above), Exalogic, Exalytics, SuperCluster, MiniCluster, ZDLRA & Big Data. Exachk utility performs the following checks:

Configuration checks for Compute nodes, Storage cells and InfiniBand Switches
Grid Infrastructure, Database and ASM and Operating System software checks
MAA Scorecard which conducts an automatic MAA Review
Exadata Software Planner, Software prechecks, Exadata and Database Critical Issue alerts

It is recommended to execute the latest exachk at the following situation:

Monthly
Before any planned maintenance activity
Immediately after completion of planned maintenance activity
Immediately after an outage or incident

Steps to Exadata Health Exachk Using Exachk Utility

Download latest Exachk utility from the MOS note. As of writing the latest Exachk verion available is “12.2.0.1.4_20171212”

Oracle Exadata Database Machine exachk or Health Check (Doc ID 1070954.1)

Note: It is recommended to use latest Exachk to perform Exadata Health Check

As root user, create ‘Exachk’ directory on compute node 1 as follows

[root@dm01db01 ~]# cd /root

[root@dm01db01 ~]# mkdir Exachk

Using Winscp Copy the Downloaded Exachk utility from your desktop/laptop to the Exadata compute node 1 under /root/Exachk

As root user, Login to Exadata Compute node 1 and unzip the Exachk utility

[root@dm01db01 ~]# cd /root/Exachk/

[root@dm01db01 Exachk]# ls -ltr

total 112576

-rw-r–r– 1 root root 115158363 Apr 10 05:11 exachk.zip

[root@dm01db01 Exachk]# unzip exachk.zip

Ensure that the SSH is setup across all Compute nodes, Storage cells and Ibswitches

[root@dm01db01 Exachk]# dcli -g ~/all_group -l root ‘uptime’

To Setup SSH across the cluster, use the following command:

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

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

As root user, Execute the Exachk utility

[root@dm01db01 ~]# cd /root/Exachk/

[root@dm01db01 Exachk]# ls -ltr

[root@dm01db01 Exachk]# ./exachk

Depending on the Exadata Cluster Size and number of databases it may take several minutes to complete Exachk execution.

Using Winscp, copy the Exachk zip file and/or html file to your desktop/laptop to review

Open the html file, review it and take necessary action if necessary

Under the table of contents there are different component listed. Look out for the CRITICAL and FAIL components.

Click on the ‘view’ hyperlink for more details and the recommendation to fix the problem.

MAA Scorecard

Conclusion

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

Exadata Pocket Guide

By Netsoftmate on

April 17, 2018

- Uncategorized

Exadata Pocket Reference

By Netsoftmate on

April 17, 2018

- Uncategorized

Here is the Link to the Exadata Pocket Reference. Click on the Link to Download the file.

Exadata Pocket Reference

Exadata – Configure Compute Node and Storage Cell SMTP Email Notification

By Netsoftmate on

April 14, 2018

- Uncategorized

On Exadata Database Machine you can configure the following Compute Node and Storage Cell attributes to setup the database server and Storage cells to send notifications about alerts.

smtpServer
smtpFrom
smtpFromAddr
smtpToAddr
snmpSubscriber
notificationMethod
notificationPolicy

In this article we will demonstrate how to setup the database server and Storage cells to send notifications about alerts

Compute Nodes:

Configure Compute nodes SMTP email notification for alerts. This can be accomplished using dbmcli alter dbserver command

# Compute node 1

DBMCLI>alter dbserver smtpFrom=’Exadata – dm01db01′

DBMCLI>alter dbserver smtpFromAddr=’dbmadmin@dm01db01.netsoftmate.com’

DBMCLI>alter dbserver smtpToAddr=’oradba@netsoftmate.com’

DBMCLI>alter dbserver smtpServer=’smtp.server’

DBMCLI>alter dbserver snmpSubscriber=((host=192.168.10.1,port=162,community=public,type=ASR))

DBMCLI>alter dbserver notificationPolicy=’critical,warning,clear’

DBMCLI>alter dbserver notificationMethod=’mail,snmp’

DBMCLI>alter dbserver validate mail

Or you can use the following command

DBMCLI>alter dbserver smtpFrom=’Exadata – dm01db01′, smtpFromAddr=’dbmadmin@dm01db01.netsoftmate.com’, smtpToAddr=’oradba@netsoftmate.com’, smtpServer=’smtp.server’, snmpSubscriber=’host=192.168.10.1,port=162,community=public,type=ASR’, notificationPolicy=’critical,warning,clear’, notificationMethod=’mail,snmp’

DBMCLI>alter dbserver validate mail

*** Repeat the above step for all the Compute nodes in the cluster.

# verify

# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep smtpFrom”

# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep smtpFromAddr”

# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep smtpToAddr”

# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep smtpServer”

# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep notificationMethod”

or use the following command

Storage Cells:

Configure Compute nodes SMTP email notification for alerts. This can be accomplished using cellcli alter cell command

# Storage Cell 01

CELLCLI>alter cell smtpFrom=’Exadata – dm01cel01′

CELLCLI>alter cell smtpFromAddr=’celladmin@dm01cel01.netsoftmate.com’

CELLCLI>alter cell smtpToAddr=’oradba@netsoftmate.com’

CELLCLI>alter cell smtpServer=’smtp.server’

CELLCLI>alter cell snmpSubscriber=((host=192.168.10.1,port=162,community=public,type=ASR))

CELLCLI>alter dbserver notificationPolicy=’critical,warning,clear’

CELLCLI>alter cell notificationMethod=’mail,snmp’

CELLCLI>alter cell validate mail

or you can also use the following command

CELLCLI>alter cell smtpFrom=’Exadata – dm01cel01′, smtpFromAddr=’celladmin@dm01cel01.netsoftmate.com’, smtpToAddr=’oradba@netsoftmate.com’, smtpServer=’smtp.server’, notificationMethod=’mail,snmp’

CELLCLI>alter cell validate mail

# Verify

# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep smtpFrom”

# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep smtpFromAddr”

# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep smtpToAddr”

# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep smtpServer”

# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep notificationMethod”

or you can use the following command

*** Repeat the above step for all the Storage Cells in the cluster.

Conclusion

In this article we have learned how to Configure Compute nodes and Storage Cell SMTP email notification for alerts.

Exadata – Replace Failed Internal USB Drive on Exadata Storage Cell

By Netsoftmate on

April 13, 2018

- Uncategorized

While working on Exadata Storage cell patching, the patching failed due to failed internal USB drive on a storage cell.

Oracle uses internal USB drive to backup Exadata Storage cell automatically. We don’t have to backup Storage cell manually.

In this article I will demonstrate how to replace a failed USB drive an Exadata Storage cell

You will receive an automated smtp alert (if configured) similar to below.

You can also use the following command to check for USB drive failure

[root@dm01cel01 ~]# cellcli -e list alerthistory

1_1 2018-04-10T18:25:42-05:00 warning “Internal USB status is not present. Affected USB Slots : 0”

You can also use the following ILOM command to check for USB drive failure

[root@dm01cel01 ~]# ssh dm01cel01-ilom

Password: *******

Oracle(R) Integrated Lights Out Manager

Version 3.2.10.22.a r121524

Warning: HTTPS certificate is set to factory default.

Hostname: dm01cel01-ilom

-> show /SYS/MB/USB0

Open an SR with Oracle if an ASR is already generated
Upload sundgia.sh and ILOM Snapshot to the SR for investigation
Oracle confirms the that USB drive is faulted
Oracle opens a Field task
Oracle dispatch team contacts the SR owner with the hardware dispatch details
Confirm the Hardware replacement schedule over email and/or SR
Schedule the Hardware replacement
Oracle FE arrives at the data center with the new USB drive
Shutdown the storage cell by following the steps from the MOS below

Steps to shut down or reboot an Exadata storage cell without affecting ASM (Doc ID 1188080.1)

Oracle FE replaces the faulty USB drive and power up the storage cell
Confirm that the USB drive is good

-> show /SYS/MB/USB0

/SYS/MB/USB0

Targets:

Properties:

type = USB Port

fault_state = OK

clear_fault_action = (none)

Commands:

set

show

[root@dm01cel01 ~]# cellcli -e list alerthistory

1_2 2018-04-11T02:45:49-05:00 clear “Internal USB status is back to normal. Affected USB Slots : 0”

You will receive an automated smtp alert (if configured) similar to below that the USB status is back to normal

Conclusion

In this article we have learned how to replace a faulty USB drive in Exadata Storage cell. Oracle uses USB drive to backup Exadata Storage cell automatically. We don’t have to backup Storage cell manually.

Oracle Exadata Deployment Assistance (oedacli) Command Line Interface

By Netsoftmate on

January 11, 2018

- Uncategorized

Starting with Oracle ESS version 18c and OEDA August 2017 release Oracle introduced a new feature OEDA command-line (oedacli). The new OEDA command line interface allows you to update an existing es.xml file. These updates are called Actions and an action is a single atomic task.

OEDA command-line interface (oedacli) can help you with various Exadata life cycle management tasks, such as:

Add node to or remove node from a Virtual Cluster on Exadata
Add database home to or remove database home from physical cluster
Add or remove Storage cell
Resize Oracle ASM disk groups
Add or remove additional Databases
Add or remove additional database homes to an Oracle VM cluster

Software requirement:

OEDA, August 2017 release

You can operate oedacli in 2 mode:

Edit mode
Deploy mode

Using OEDACLI utility

oedacli utility can be used for various routine tasks on Exadata Database Machine.

Prerequisites

OEDA August 2017 release or later
Original OEDA configuration XML file used for deployment
Use default password for root, oracle and grid users on the compute nodes in cluster

To start the oedacli navigate to the directoy containing the oeda software.

# cd /u01/app/oracle/software/oeda

# unzip p26964044_181000_Linux-x86-64.zip

# cd linux-64

# ./oedacli

For more details read the OEDA Command-Line interface at:

http://docs.oracle.com/cd/E80920_01/DBMIN/exadata-deployment-assistant.htm#DBMIN-GUID-CCACB268-C707-4897-8C1C-0F3568FA456C

To Load an original OEDA xml Configuration file

[root@dm01db01 linux-x64]# ./oedacli

oedacli> LOAD FILE name=/u01/app/oracle/software/oeda/Netsoftmate-dm01.xml

SUCCESS – file loaded OK

Customer : Netsoftamte – QED -QA -IND

To List xmlactions

oedacli> list xmlactions

There are no actions in this XML file

To Display help using oedacli

[root@dm01db01 linux-x64]# ./oedacli

oedacli> help

HELP [topic]

Available Objects:

ACFSVOLUME

ADD ACFSVOLUME

ALTER ACFSVOLUME

DELETE ACFSVOLUME

LIST ACFSVOLUMES

CELL

CLONE CELL

DELETE CELL

LIST CELLS

CLUSTER

ALTER CLUSTER

UPGRADE CLUSTER

LIST CLUSTERS

DISKGROUP

ADD DISKGROUP

ALTER DISKGROUP

ALTER DISKGROUPS

DELETE DISKGROUP

LIST DISKGROUPS

DATABASE

ADD DATABASE

ALTER DATABASE

DELETE DATABASE

LIST DATABASES

DATABASEHOME

ADD DATABASEHOME

ALTER DATABASEHOME

CLONE DATABASEHOME

DELETE DATABASEHOME

LIST DATABASEHOMES

DOM0

LIST DOM0S

ALTER ES

GUEST

CLONE GUEST

DELETE GUEST

LIST GUESTS

ILOM

ALTER ILOM

LIST ILOMS

MACHINE

ALTER MACHINE

LIST MACHINES

NETWORK

ADD NETWORK

ALTER NETWORK

DELETE NETWORK

LIST NETWORKS

SCAN

ADD SCAN

ALTER SCAN

DELETE SCAN

LIST SCANS

SWITCH

ALTER SWITCH

LIST SWITCHES

VIP

ADD VIP

ALTER VIP

DELETE VIP

LIST VIPS

CLI COMMANDS

LOAD FILE

SAVE FILE

SAVE FILES

DELETE XMLACTION

LIST XMLACTIONS

SAVE ACTION

MERGE ACTIONS

DEPLOY ACTIONS

To Display help add database

oedacli> help add database

Usage:

ADD DATABASE

BLOCKSIZE = <blocksize> |

CHARSET = <characterset> |

DATADG = <datadg> |

DBLANG = <dblang> |

DBNAME = <dbname> |

DBTEMPLATE = <dbtemplate> |

DBTYPE = <dbtype> |

HOSTNAMES = <hostnames> |

RECODG = <recodg>

WHERE

DBHOMEID = <databasehomeid> |

CLUSTERNUMBER = <clusternumber> DBHOMELOC = <databasehomelocation> |

CLUSTERNAME = <clustername> DBHOMELOC = <databasehomelocation> |

CLUSTERID = <clusterid> DBHOMELOC = <databasehomelocation> |

CLUSTERNUMBER = <clusternumber> CDBNAME = <containerdbname>

CLUSTERNAME = <clusternumber> CDBNAME = <containerdbname>

CLUSTERID = <clusternumber> CDBNAME = <containerdbname>

Purpose:

Adds a database or a CDB or a PDB to an existing CDB

Arguments:

<blocksize> : Default: 8192, not required for PDB

<characterset> : Default: AL32UTF8, not required for PDB

<datadg> : *The DATA diskgroup, not required for PDB

<dblang> : Default: all_langs, not required for PDB

<dbname> : *Database name

<dbtemplate> : Default: ADMIN, otherwise ADMIN or DW, not required for PDB

<dbtype> : Default: normal DB, otherwise CDB or PDB

<hostnames> : Default: list of nodes from db home

<recodg> : *The RECO diskgroup, not required for PDB

Where:

<databasehomeid> : The es id for the databasehome

<clusternumber> : The cluster number in the es xml, starting at 1

<clustername> : The name of the cluster

<clusterid> : The es xml id of the cluster

<databasehomelocation> : The path for the target database home

<containerdbname> : The database name for the container – only required when DBTYPE is PDB

Comments: * indicates a mandatory parameter

To Display help add ASM Diskgroup

oedacli> help add diskgroup

Usage:

ADD DISKGROUP

ACFSNAME = <acfsname>

ACFSPATH = <acfspath>

ACFSSIZE = <acfssize>

CELLLIST = ‘<cellist>’

*DISKGROUPNAME = <diskgroupname>

*DISKGROUPSIZE = <diskgroupsize>

OCRVOTE = <ocrvote>

QUORUMDISK = <quorumdisk>

*REDUNDANCY = <redundancy>

*SLICESIZE = <slicesize>

SPARSE = <sparse>

SPARSEVIRTUALSIZE = <sparsevirtualsize>

TYPE = <diskgrouptype>

[DATABASENAME = <databasename>]

WHERE

CLUSTERNAME = <clustername> |

CLUSTERNUMBER = <clusternumber> |

CLUSTERID = <clusterid>

Purpose:

Adds a diskgroup

Arguments:

<acfsname> : The name of the acfs volume on this diskgroup

<acfspath> : The path for the acfs filesystem

<acfssize> : The size of the acfs volume

<cellist> : A comma separated list of cells for this diskgroup, the list enclosed in ‘

<diskgroupname> : The new name for the diskgroup

<ocrvote> : true if this diskgroup will host the ocrvote for clusterwear

<quorumdisk> : true if this diskgroup will require quorum

<redundancy> : Redundancy for this diskgroup : NORMAL or HIGH

<diskgroupsize> : The size of the diskgroup, specify in G or T. Only slice or diskgroup size, not both

<slicesize> : The slice size on disk for each griddisk for this diskgroup

<sparse> : true if this diskgroup has sparse enabled

<sparsevirtualsize> : The sparsevirtual size

<type> : Diskgroup type, DATA, RECO, DBFS or OTHER, default is other. If you want the database to be built using this diskgrouptype must be set to DATA or RECO

<databasename> : If type is DATA or RECO, the dbname of the target database

Where:

<clusternumber> : The cluster number in the es xml, starting at 1

<clustername> : The name of the cluster

<clusterid> : The es xml id of the cluster

Comments: * indicates a mandatory field

oedacli>

Conclusion:

In this article we have learned about new OEDA command-line (oedacli) utility. The new OEDA command line interface to update an existing es.xml file. These updates are called Actions and an action is a single atomic task.

Exadata Different Hardware Failures and Images

By Netsoftmate on

November 3, 2017

- Uncategorized

Introduction

Exadata Database Machine or simply known as Exadata is:

An Engineered System
A pre-configured 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

Exadata Database Machine consists of a storage grid, compute grid, and network grid. Each grid, or hardware layer, is built with multiple high-performing, industry-standard Oracle servers to provide hardware and system fault tolerance.

Exadata Hardware Components

The Exadata Storage Cells and Compute nodes consists of several hardware components, such as:

Hard disk
Flash disk
Physical Memory
Processor
IB ports
Mother Board
Batteries
Power Supply
and So on

All these hardware components are subjected to failure. Most common failure on Exadata is Hard Disk failure on Storage Cells. With the latest generation of Exadata the hardware failures are very minimal and less troublesome.

In this article I would like to show few different hardware failure I have encountered along with an image for easy understanding. This will help the DBAs who still didn’t get a change to work on Exadata Hardware side.

Different Exadata Hardware components failures

Battery Failure on Exadata X4-2

Flash Card Failure on Exadata V2

Flash Card Failure on Exadata X5-2

Flash Card Failure on Exadata V6-2

Hard Disk Failure on Exadata V2

Hard Disk Failure on Exadata X2-2

Hard Disk Failure on Exadata X4-2

Hard Disk Failure on Exadata X5-2

IB Port Failure on Exadata X2-2

IB Port Failure on Exadata X4-2

IB Port Failure on Exadata X5-2

Physical Memory (DIMM) Failure on Exadata X5-2

Physical Memory (DIMM) Failure on Exadata X6-2

Processor Failure on Exadata X4-2

Processor Failure on Exadata X5-2

Power Supply Failure on Exadata V2

Power Supply Failure on Exadata X4-2

Power Supply Failure on Exadata X5-2

Power Supply Failure on Exadata X6-2

Conclusion

In this article we have learned different Exadata components and also seen the images on different hardware failures. If you have configured the SMTP attributes of Compute nodes and Storage cells, whenever there is an hardware failure it will send you an email alert. This way it is very easy to monitor hardware failures and other software related failures.

Exadata: Clear Hardware Fault Post Hardware Replacement

By Netsoftmate on

October 26, 2017

- Uncategorized

Introduction

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

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

To identify faulty hardware, execute the ILOM following command:

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

-> Session closed
Disconnected

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

You can also check for hardware failures using Web ILOM

Steps to Clear a hardware fault post hardware replacement:

Identify the hardware fault

Connect to problematic Compute node ILOM

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

Oracle(R) Integrated Lights Out Manager

Version 3.2.8.24 r114580

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

Warning: HTTPS certificate is set to factory default.

Hostname: dm01db01-ilom

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

Execute the following command to clear the fault

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

Verify the fault is cleared

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

No Faulty hardware found.

Verify from Web ILOM

Exit from ILOM

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

Conclusion

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

PREVIOUS POSTSPage 4 of 6NEXT POSTS

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

Home

About

Services

Blog

Contact

Create a Local Yum Repository Using an ISO Image on Exadata Database Machine

Mount External USB Drive On Exadata Compute Node

Exadata Database Machine Health Check Using Exachk Utility

Exadata Pocket Guide

Exadata Pocket Reference

Exadata – Configure Compute Node and Storage Cell SMTP Email Notification

Exadata – Replace Failed Internal USB Drive on Exadata Storage Cell

Oracle Exadata Deployment Assistance (oedacli) Command Line Interface

Exadata Different Hardware Failures and Images

Exadata: Clear Hardware Fault Post Hardware Replacement

ABOUT US

Services

CONTACT US

Follow Us!