Tag: ODA
-
Patching Oracle Database Appliance (ODA) Stack
Oracle Database Appliance stack patching is very simple and straight forward. The ODA patching process is fully automated and single patch contains updates for all system components such as OS, Firmware, BIOS, ILOM, Storage, Grid Infrastructure and Database. ODA patches are released every quarter and one should always consult the MOS note 888888.1 for recommended patches.Oracle Database Appliance stack Patching consists of following major steps:- Patching ODA Nodes (Includes Grid Infrastructure Patching)
- Patching Storage Shelve(s)
- Patching Database
In this article we will demonstrate the steps for patching entire Oracle Database Appliance stack to 12.2.1.2.0.Steps for Patching Oracle Database Appliance (ODA) StackStep 1: ODA Nodes Patching- As root user, note down the current version of the ODA on both nodes
# oakcli show version -detail- As root user, Verify the shared disks status on both nodes. There shouldn’t be any bad disk.
# oakcli show disk# oakcli show diskgroup- As root user, Validate the ODA infrastructure on both nodes
# oakcli validate -d- Ensure that sufficient space is available in the following file sytems on both nodes
# df -h -P / /opt /u01 /boot- Download and stage the ODA patches on the both nodes
# mkdir -p /u01/app/oracle/software/ODA- Ensure root user equivalence is working on both nodes
From node 1ssh 192.168.16.25 hostnameFrom node 2ssh 192.168.16.24 hostname- Copy software to node 2
# mkdir -p /u01/app/oracle/software/ODA# scp /u01/app/oracle/software/ODA/p* 192.168.16.25:/u01/app/oracle/software/ODA/- Unpack software on both nodes
# /opt/oracle/oak/bin/oakcli unpack –package /u01/app/oracle/software/ODA/p27119652_122120_Linux-x86-64_1of3.zip# /opt/oracle/oak/bin/oakcli unpack –package /u01/app/oracle/software/ODA/p27119652_122120_Linux-x86-64_2of3.zip# /opt/oracle/oak/bin/oakcli unpack –package /u01/app/oracle/software/ODA/p27119652_122120_Linux-x86-64_3of3.zip- Stop databases
$ srvctl stop database -d <name>- Umount the NFS mounts if any
# umount /nsf- Verify the patch
# oakcli update -patch 12.2.1.2.0 -verify- Run from the patching from ILOM CLI
ssh odanode1-ilomenter the root password when prompted-> start /SP/consoleenter y and hit return to confirm# oakcli update -patch 12.2.1.2.0 -server -localNote: Node will be rebooted as part of patching- Ensure that CRS is Up and Running
# $GRID_HOME/bin/crsctl stat res -t- Perform patching post checks
# oakcli update -patch 12.2.1.2.0 -verify- Check the inventory looks as expected:
# oakcli show version -detail- Check GI patches
$ $GRID_HOME/OPatch/opatch lspatches*****Repeat the above steps on the second node before continuing…*******Step 2: Storage patchingOnce both ODA nodes are patched successfully, we can continue with the storage patching.- As root user on node 1 only, execute the following command:
# oakcli update -patch 12.2.1.2.0 -storage- Post Storage Patching, ensure that CRS is up and running on both nodes
# $GRID_HOME/bin/crsctl stat res -t- Verify that the patching sucessful on both nodes.
# oakcli show version -detailStep 3: Database Patching:Once both ODA nodes and Storage Patching completed successfully, we can now patch databases.- As root user on execute the following command:
# /opt/oracle/oak/bin/oakcli update -patch 12.2.1.2.0 –database –local- Verify the versions of the databsae homes
# oakcli show databases -detail# oakcli show dbhomes -detailConclusionIn this article we have learned to patch an Oracle Database Appliance. Oracle Database Appliance stack patching is very simple and straight forward. The ODA patching process is fully automated and single patch contains updates for all system components. The Patching is also known as One-Button patching process as it is fully automated with just few steps. -
Oracle Database Appliance Odacli & Odaadmcli Utilities
Oracle Database Appliance consists of two physical servers (Node 0 and Node 1), a storage shelf and optionally an additional storage shelf. The two independent physical servers are interconnected and direct attached to SAS and SSD storage.ODA is basically a 2-node RAC cluster database system running Oracle Linux operating (OEL), Oracle Database Enterprise Edition, Oracle Grid Infrastructure (Clusterware and ASM). All these together provides the Oracle Database high availability running on ODA.In 2016, Oracle added 3 new models to expand Oracle Database Appliance portfolio. These 3 new models are:
- Oracle Database Appliance X6-2S (single-instance database)
- Oracle Database Appliance X6-2M (single-instance database)
- Oracle Database Appliance X6-2L (single-instance database)
The High Available ODA x6-2 is now known as X6-2 HA which consists of 2 nodes and a storage shelf and optionally an additional storage shelf.Courtesy OracleThe Oracle Database Appliance X6-2 model family offers the lowest hardware price for an Oracle Engineered System. Combined with flexible Oracle Database software licensing, the Oracle Database Appliance X6-2 model family brings Oracle Engineered Systems to within reach of every organization.
In October 2017, Oracle announced Oracle Database Appliance X7-2 (Small, Medium and HA). ODA X7-2 comes with more computing resources compared with X6-2 Models.
- Oracle Database Appliance X7-2S (single-instance database)
- Oracle Database Appliance X7-2M (single-instance database)
- Oracle Database Appliance X7-2 HA
Courtesy OracleNote: With ODA x7-2, looks like the ODA Large configuration is discontinued.
In this article we will demonstrate several different odacli and odaadmcli commands along with output that can be used to manage and administer an Oracle Database Appliance Small, Medium and Large models.
ODACLI: It is used for Hardware and administrative tasks on the Oracle Database Appliance, Example: Hardware monitoring and Storage Configuration
ODAADMICLI: It is used for everyday task on the Oracle Database Appliance, Example: Database Creation, Patches and upgrades, Job creation and manage and so on
ODACLI Commands
- To display list of commands and options that can be used with odacli execute the following command
[root@odanode1 ~]# odacli -hodacli <command> <options>Commands list (use –help option for help on any command):appliance:create-appliancedescribe-applianceasr:configure-asrdelete-asrdescribe-asrtest-asrupdate-asrcomponent:describe-componentcpucore:describe-cpucorelist-cpucoresupdate-cpucorecredential:set-credentialdatabase:create-databasedelete-databasedescribe-databaselist-databasesregister-databasedbhome:create-dbhomedelete-dbhomedescribe-dbhomelist-dbhomesupdate-dbhomedbstorage:create-dbstoragedelete-dbstoragedescribe-dbstoragelist-dbstoragesdcsagent:update-dcsagentjob:describe-joblist-jobslatestpatch:describe-latestpatchnetwork:create-networkdelete-networkdescribe-networklist-networksupdate-networknetworkinterface:describe-networkinterfacelist-networkinterfacesrepository:update-repositoryserver:update-server- To describe ODA execute the following command
[root@odanode1 ~]# odacli describe-applianceAppliance Information
—————————————————————-ID: 9aef262c-xxxx-xxxx-xxxx-0d877c03d762Platform: ODAData Disk Count: 2CPU Core Count: 10Created: May 23, 2017 3:08:03 AM CSTSystem Information
—————————————————————-Name: odanodeDomain Name: netsoftmate.comTime Zone: Asia/PacificDB Edition: EEDNS Servers: 10.1.1.1NTP Servers: ntp1.netsoftmate.comDisk Group Information
—————————————————————-DG Name Redundancy Percentage————————- ————————- ————Data Normal 80Reco Normal 20Options:
–details, -dDetail Info- To describe ODA in details execute the following command
[root@odanode1 ~]# odacli describe-appliance -dAppliance Information
—————————————————————-ID: 9aef262c-xxxx-xxxx-xxxx-0d877c03d762Platform: ODAData Disk Count: 2CPU Core Count: 10Created: May 23, 2017 3:08:03 AM CSTSystem Information
—————————————————————-Name: odanodeDomain Name: netsoftmate.comTime Zone: Asia/PacificDB Edition: EEDNS Servers: 10.1.1.1NTP Servers: ntp1.netsoftmate.comDisk Group Information
—————————————————————-DG Name Redundancy Percentage————————- ————————- ————Data Normal 80Reco Normal 20DcsCli Details
—————————————————————-Version: 12.1.2.10-SNAPSHOTBuildNumber: jenkins-ol-dcs-cli-release-13GitNumber: f91373b8574e383e033301d82b8424115350d065BuildTime: nullDcsAgent Details
—————————————————————-Version: 12.1.2.10-SNAPSHOTBuildNumber: jenkins-ol-dcs-agent-release-31GitNumber: fb8b1776013457d4d80d7acac3ad96fa5ca52327BuildTime: null
- To list ASR details execute the following command
[root@odanode1 ~]# odacli describe-asrASR details
—————————————————————-ID: b8606dd5-99b4-xxxx-aabd-be8cd422754cName: ASRASR Type: InternalExternal ASR Manager IP :UserName: john.smith@example.comProxyServerName: www-proxy.example.comProxyPort: 80ProxyUserName:SnmpVersion: V3State: ConfiguredCreated: May 23, 2017 3:08:03 AM CSTUpdated: May 23, 2017 3:42:43 AM CSTOptions :
–json, -jjson output
- To list CPU Cores execute the following command
[root@odanode1 ~]# odacli list-cpucoresNode Cores Modified Job Status
—– —— —————————— —————0 10 May 23, 2017 10:58:52 AM CST ConfiguredOptions:–json, -j
json output
- To list all the job configured and to check their status execute the following command
[root@odanode1 ~]# odacli list-jobsID Description Created Status
—————————————- ————————————————————————— ———————————– ———-65b60824-cb18-4fec-bdec-baf7e440efc9 Provisioning service creation May 23, 2017 3:08:03 AM CST Success74d38c8e-98aa-4ff3-9b04-ef96bdfd35bd Database service deletion with db name: demodb1 with id : c0cdc82d-02e5-4980-9952-36b6d4adf28a May 23, 2017 4:01:02 PM CST Success26de75bb-e525-4356-9828-6056d55b5f56 Database Home OraDB12102_home1 Deletion with id 8f5944b1-e953-4c78-89f4-ba4daa8110ca May 23, 2017 4:04:59 PM CST Success
Options:
–json, -j
json output- To list the patches for all the ODA components execute the following command
[root@odanode1 ~]# odacli describe-latestpatchcomponentType availableVersion
————— ——————–gi 12.1.0.2.170117db 11.2.0.4.161018db 12.1.0.2.170117oak 12.1.2.10.0ilom 3.2.8.24.r114611os 6.8bios 38070000
Options :–json, -jjson output
- To list all the network details execute the following command
[root@odanode1 ~]# odacli list-networksID Name NIC IP Address Subnet Mask Gateway
—————————————- ——————– ———- —————— —————— ——————49976a55-4e1a-440a-94c3-289b69d9afcc Private-network priv0 192.168.16.24 255.255.255.240219953e6-3473-46f9-b21b-53e89bc8cf49 Public-network btbond1.198 10.10.10.18 255.255.255.0 10.1.1.2
- To list all the network interfaces execute the following command
[root@odanode1 ~]# odacli list-networkinterfacesID Name NIC Type
—————————————- ——————– ————- ———-724e42a6-c9f7-xxxx-9e34-7b0952f8e3e1 btbond1 btbond1 Bond543aba2a-0cb0-xxxx-b23a-3f035aa401c0 btbond1.198 btbond1.198 Bond18933aa5-b02d-xxxx-a31b-5ad988d6396b em1 em1 Physicalce059f61-7529-xxxx-9cd4-ef94fdd3ec54 em2 em2 Physical2622ea10-508a-xxxx-86a8-351fe0a58e6f p3p1 p3p1 Physical8ddd6b36-ff32-xxxx-9d1f-a90c14216bf7 p3p2 p3p2 Physicalf03a424e-8c7e-xxxx-901f-3b81f9642cfa sfpbond1 sfpbond1 Bond
ODAADMCLI Commands
- To display list of commands and options that can be used with odaadmcli execute the following command
[root@odanode1 ~]# odaadmcli -hUsage: odaadmcli <command> <object> [<options>]commands: show|manage|stordiag|power|expandobjects : disk|diskgroup|controller|server|processor|memory|iraid|power|cooling|network|storage|fs|raidsyncstatus|env_hwUsage: odaadmcli show – Shows disk, diskgroup, controller, server, processor, memory, iraid, power, cooling, network, storage, fs, raidsyncstatus, env_hw
odaadmcli manage – Manages the OAK repository, diagcollect etc.,odaadmcli stordiag – Run storage diagnostic tool on this Nodeodaadmcli power – Power on|off|status diskodaadmcli expand – Expand storage
- To display list of commands and options that can be used with odaadmcli show execute the following command
[root@odanode1 ~]# odaadmcli show -hUsage:odaadmcli show {disk|diskgroup|fs|raidsyncstatus|controller|storage|env_hw|server|processor|memory|iraid|power|cooling|network} [<options>]where:disk – About the diskdiskgroup – ASM disk groupfs – Filesystemcontroller – Controllerstorage – All storage componentsenv_hw – Environment and Hardware informationserver – Details of server sub-systemprocessor – Details of processor sub-systemmemory – Details of memory sub-systemiraid – Details of internal RAIDs sub-systempower – Details of power supply sub-systemcooling – Details of cooling sub-systemnetwork – Details of network sub-systemraidsyncstatus – RAID sync status informationFor detailed help on each command and object and its options use:odaadmcli <command> <object> -h
- To list local disk on compute node execute the following command
[root@odanode1 ~]# odaadmcli show diskNAME PATH TYPE STATE STATE_DETAILSpd_00 /dev/nvme0n1 NVD ONLINE Good
pd_01 /dev/nvme1n1 NVD ONLINE Good
- To list all shared disk execute the following command
[root@odanode1 ~]# odaadmcli show disk -sharedNAME PATH TYPE STATE STATE_DETAILSpd_00 /dev/nvme0n1 NVD ONLINE Good
pd_01 /dev/nvme1n1 NVD ONLINE Good
- To list ASM Disk Groups execute the following command
[root@odanode1 ~]# odaadmcli show diskgroupDiskGroups———-DATARECO
- To list details of an ASM Disk Group execute the following command
[root@odanode1 ~]# odaadmcli show diskgroup DATAASM_DISK PATH DISK STATE STATE_DETAILSdata_00 /dev/NVD_S00_S2LHNA0HC05601p1 pd_00 ONLINE Good
data_01 /dev/NVD_S01_S2LHNA0HC05809p1 pd_01 ONLINE Good[root@odanode1 ~]# odaadmcli show diskgroup RECO
ASM_DISK PATH DISK STATE STATE_DETAILSreco_00 /dev/NVD_S00_S2LHNA0HC05601p2 pd_00 ONLINE Good
reco_01 /dev/NVD_S01_S2LHNA0HC05809p2 pd_01 ONLINE Good
- To list file system details execute the following command
[root@odanode1 ~]# odaadmcli show fsType Total Space Free Space Total DG Space Free DG Space Diskgroup Mount Pointext3 30109M 13215M – – /ext3 476M 405M – – /bootext3 60347M 43274M – – /optext3 302252M 235296M – – /u01acfs 5120M 5071M 4894016M 70220M DATA /opt/oracle/dcs/commonstoreacfs 2406400M 1699624M 4894016M 70220M DATA /u02/app/oracle/oradata/datastoreacfs 306176M 292685M 1231176M 14372M RECO /u01/app/oracle/fast_recovery_area/datastoreacfs 302080M 294707M 1231176M 14372M RECO /u01/app/oracle/oradata/datastore
- To list storage details execute the following command
[root@odanode1 ~]# odaadmcli show storage==== BEGIN STORAGE DUMP ========Host Description: Oracle Corporation:ORACLE SERVER X6-2Total number of controllers: 2Id = 0Pci Slot = 10Serial Num = xxxxxxxxxxVendor = SamsungModel = MS1PC2DD3ORA3.2TFwVers = KPYABR3QstrId = nvme:19:00.00Pci Address = 19:00.0Id = 1
Pci Slot = 11Serial Num = xxxxxxxxxxxVendor = SamsungModel = MS1PC2DD3ORA3.2TFwVers = KPYABR3QstrId = nvme:1b:00.00Pci Address = 1b:00.0
Total number of expanders: 0
Total number of PDs: 2/dev/nvme0n1 Samsung NVD 3200gb slot: 0 pci : 19/dev/nvme1n1 Samsung NVD 3200gb slot: 1 pci : 1b==== END STORAGE DUMP =========
- To ODA hardware details execute the following command
[root@odanode1 ~]# odaadmcli show env_hwBM ODA X6-2 Small
- To list ODA server details execute the following command
[root@odanode1 ~]# odaadmcli show serverPower State : On
Open Problems : 0Model : ODA X6-2SType : Rack MountPart Number : ODA X6-2SSerial Number : xxxxxxxxxPrimary OS : Not AvailableILOM Address : 10.10.10.11ILOM MAC Address : 00:10:E0:BF:1C:38Description : Oracle Database Appliance X6-2 Small xxxxxxxLocator Light : OffActual Power Consumption : 135 wattsAmbient Temperature : 27.000 degree COpen Problems Report : System is healthy
- To check processor status the following command
[root@odanode1 ~]# odaadmcli show processorNAME HEALTH HEALTH_DETAILS PART_NO. LOCATION MODEL MAX_CLK_SPEED TOTAL_CORES ENABLED_CORES
CPU_0 OK – 060F P0 (CPU 0) Intel(R) Xeon(R) CPU E5-2630 2.200 GHz 10 NA
- To check Memory status execute the following command
[root@odanode1 ~]# odaadmcli show memoryNAME HEALTH HEALTH_DETAILS PART_NO. SERIAL_NO. LOCATION MANUFACTURER MEMORY_SIZE CURR_CLK_SPEED ECC_Errors
DIMM_0 OK – 3A4K40BB1-CRC 00CE02164433E98884 P0/D0 Samsung 32 GB 2400 MHz 0
DIMM_11 OK – 3A4K40BB1-CRC 00CE02164433E986FB P0/D1 Samsung 32 GB 2400 MHz 0DIMM_3 OK – 3A4K40BB1-CRC 00CE02164433E9863B P0/D3 Samsung 32 GB 2400 MHz 0DIMM_8 OK – 3A4K40BB1-CRC 00CE02164433E98689 P0/D8 Samsung 32 GB 2400 MHz 0
- To check raid status execute the following command
[root@odanode1 ~]# odaadmcli show iraidNAME CTRL# PRODUCT SERIAL_NO BIOS_VER FW_VER VDISK_TYPE VDISK_STATE PDISK_MODEL EID:SLT PDISK_STATE SIZE
CV_MODEL CV_STATE CV_TEMPIR_0_0_0 0 LSI MegaRAID 9361-8i SV62214495 6.17.04.2_4.16.08.00_0x06060A 4.230.40-3739 RAID1 Optl MS4SC2JH2ORA480G 252:0 Onln 446.102 GB
CVPM02 Optimal 27CIR_0_0_1 0 LSI MegaRAID 9361-8i SV62214495 6.17.04.2_4.16.08.00_0x06060A 4.230.40-3739 RAID1 Optl MS4SC2JH2ORA480G 252:1 Onln 446.102 GBCVPM02 Optimal 27C- To check power status execute the following command
[root@odanode1 ~]# odaadmcli show powerNAME HEALTH HEALTH_DETAILS PART_NO. SERIAL_NO. LOCATION INPUT_POWER OUTPUT_POWER INLET_TEMP EXHAUST_TEMP
Power_Supply_0 OK – 7079395 476856Z+1644CE006L PS0 Present 60 watts 27.000 degree C 33.812 degree C
Power_Supply_1 OK – 7079395 476856Z+1644CE000A PS1 Present 56 watts 27.000 degree C 32.938 degree C
- To check network status execute the following command
[root@odanode1 ~]# odaadmcli show networkNAME HEALTH HEALTH_DETAILS LOCATION PART_NO MANUFACTURER MAC_ADDRESS LINK_DETECTED DIE_TEMP
Ethernet_NIC_0 OK – NET0 X540 INTEL 00:10:E0:BF:1C:34 yes (em1) 61.250 degree C
Ethernet_NIC_1 OK – NET1 X540 INTEL 00:10:E0:BF:1C:35 yes (em2) 61.250 degree CEthernet_NIC_2 – – NET2 X540 INTEL 90:E2:BA:D9:7D:B9 no (p3p2) –Ethernet_NIC_3 – – NET3 X540 INTEL 90:E2:BA:D9:7D:B8 no (p3p1) –
Conclusion
In this article we have learned about Oracle Database Appliance X6-2 and X7-2 model family. Also we have learned how to use the odacli and odaadmcli command line utilities to manage and administer an Oracle Database Appliance. odacli is used for Hardware and administrative tasks on the Oracle Database Appliance, Example: Hardware monitoring and Storage Configuration whereas odaadmcli is used for everyday task on the Oracle Database Appliance, Example: Database Creation, Patches and upgrades, Job creation and manage and so on.
-
Exadata: How To Mount diag.iso On An Exadata X5 Server From A NFS Server
Introduction
I was testing Exadata Compute node snapshot restore procedure on an Exadata X5-2. As per of testing I had to start the machine in special mode using diag.iso, the easiest option is to use WEB ILOM to mount he diag.iso, but for some technical reason or BUG I was unable to mount diag.iso using WEB ILOM. Oracle provided a procedure to mount the diag.iso image using an NFS server.
In this article I will demonstrate step by step procedure on how mount diag.iso image using NFS Server along with the output.
Steps to mount diag.iso on an Exadata Compute node from NFS server:
- First login to the Compute node ILOM CLI or SSH from another Compute node
[root@dm01db01 ~]# ssh dm01db01-ilom
Password:
Oracle(R) Integrated Lights Out Manager
Version 3.2.8.24 r114580
Copyright (c) 2016, Oracle and/or its affiliates. All rights reserved.
Warning: HTTPS certificate is set to factory default.
Hostname: dm01db01-ilom
->
- Execute the following command to mount diag.iso from a NFS server
Syntax:
set /SP/services/kvms/host_storage_device/remote/ server_URI=NFS_or_Samba_URI_file_location
-> set /SP/services/kvms/host_storage_device/remote server_URI=nfs://10.10.10.1:/export/dm01/backup1/diag.iso
Set ‘server_URI’ to ‘nfs://10.10.10.1:/export/dm01/backup1/diag.iso’
- Verify the server_URI to make it is poing to correct NFS location
-> show /SP/services/kvms/host_storage_device/remote server_URI
/SP/services/kvms/host_storage_device/remote
Properties:
server_URI = nfs://10.10.10.1:/export/dm01/backup1/diag.iso
- Execute the following command to Enable storage redirection:
-> set /SP/services/kvms/host_storage_device/ mode=remote
Set ‘mode’ to ‘remote’
- Check the status of redirection:
-> show /SP/services/kvms/host_storage_device/ status
/SP/services/kvms/host_storage_device
Properties:
status = operational
Note – Redirection is active if the status is set to either Operational or Connecting.
- Now set the next boot device to cdrom
-> set /HOST boot_device=cdrom
Set ‘boot_device’ to ‘cdrom’
- Verify the next boot device is pointing to cdrom:
-> show /HOST
/HOST
Targets:
console
diag
provisioning
Properties:
boot_device = cdrom
generate_host_nmi = (Cannot show property)
Commands:
cd
set
show
- Execute the following command to Reboot the Server:
-> reset /SYS
Are you sure you want to reset /SYS (y/n)? y
Performing hard reset on /SYS
At this time the server boot from diag.iso, enter into interactive mode, restore/recovery the machine or correct the OS configuration that you have and when you are done, disable redirection.
Steps to Disable steps Server_URI and Storage redirection
- Execute the following command to disable Storage redirection:
-> set /SP/services/kvms/host_storage_device/ mode=disabled
Set ‘mode’ to ‘disabled’
-> show /SP/services/kvms/host_storage_device/ mode
/SP/services/kvms/host_storage_device
Properties:
mode = disabled
- Execute the following command to disable Server_URI:
-> set /SP/services/kvms/host_storage_device/remote server_URI=”
Set ‘server_URI’ to ”
-> show /SP/services/kvms/host_storage_device/remote server_URI
/SP/services/kvms/host_storage_device/remote
Properties:
server_URI = (none)
- Verify the Next boot device:
-> show /HOST
/HOST
Targets:
console
diag
provisioning
Properties:
boot_device = default
generate_host_nmi = (Cannot show property)
Commands:
cd
set
show
- Reboot the server to boot with the normal Exadata kernel
-> reset /SYS
Are you sure you want to reset /SYS (y/n)? y
Performing hard reset on /SYS
Conclusion
In this article we have learned how to mount diag.iso on Exadata compute node from NFS Server. If the WEB ILOM is not working for some reason then mounting the diag.iso using NFS server comes handy. The process to mount is diag.iso from NFS Server is very simply and much faster. -
Oracle Database Appliance X7-2 Family – First Look
Oracle Database Appliance X7-2 HA – First look
October 2017 Oracle announced Oracle Database Appliance X7-2 (Small, Medium and HA). ODA X7-2 comes with more computing resources compared with X6-2 Models.
Let’s take a quick look at few benefits of ODA followed by the technical specification on ODA X7-2 Small/Medium and HA.
Benfits of ODA:- Software, server, storage, and networking engineered and optimized to run Oracle Database and applications.
- Supports Oracle Database Standard Edition, Standard Edition One, Standard Edition 2, and Enterprise Edition.
- Optimized for Cloud
- Capacity on Demand Licensing – Reduced Cost
- Easy Deployment and management
Oracle Database Appliance X7-2 HA specification- 32 cores per server (72 cores in total for 2 servers)
- 384 GB physical memory per server expandable upto 1.5TB (768 GB memory in total for 2 servers)
- Storage Shelf
- High Capacity: 150 TB HDD raw capacity per shelf
- High Performance: 64 TB SDD raw capacity per shelf
- 3.2 TB raw capacity for redo log storage per shelf
- Choice of 10GBase-T or 10/25 GbE SFP28 public networking
For more information on the technical specification loot at the ODA X7-2 HA Data Sheet at:
http://www.oracle.com/technetwork/database/database-appliance/learnmore/odax7-2-ha-ds-3933489.pdf
https://www.oracle.com/engineered-systems/database-appliance/x7-2-ha/index.html#ct07tabcontent2
Oracle Database Appliance X7-2 Small specification- One server
- 1 Intel Xeon processor, 10 Cores
- 192GB Physical memory expandable upto 384GB
- Choice of 10GBase-T or 10/25 GbE SFP28 public networking
- 12.8TB NVMe raw storage
Oracle Database Appliance X7-2 Medium specification- One server
- 2 Intel Xeon processor, 36 Cores
- 384 GB Physical memory expandable upto 768GB
- Choice of 10GBase-T or 10/25 GbE SFP28 public networking
- 12.8 TB NVMe raw storage with optional expansion to 51.2 TB NVMe raw storage
For more information on the technical specification loot at the ODA X7-2 S/M Data Sheet at:http://www.oracle.com/technetwork/database/database-appliance/learnmore/odax7-2sm-ds-3933491.pdf
-
Oracle Database Appliance Hardware Generation
Oracle Database Appliance
Oracle Database Appliance (ODA) is a pre-configured, highly available Oracle Database Engineered system. ODA system consists of hardware, software, storage and networking. The hardware configuration is designed to provide redundancy and protection against single points of failures in the system.
The Oracle Database Appliance saves time and money by simplifying deployment, maintenance, and support of high availability Database solutions.
ODA consists of two physical servers (Node 0 and Node 1), a storage shelf and optionally an additional storage shelf. The two independent physical servers are interconnected and direct attached to SAS and SSD storage.
ODA is basically a 2-node RAC cluster database system running Oracle Linux operating (OEL), Oracle Database, Oracle Grid Infrastructure (Clusterware and ASM). All these together provides the Oracle Database high availability running on ODA.
Advantages of Oracle Database Appliance
Oracle marketed ODA using the tagline “Simple, Reliable and Affordable”.- Simple: The ODA deployment made simple and easy to use by using the wizard based deployment.
- Reliable: The ODA platform provide complete high availability for Database and Application
- Affordable: With ODA you have the benefit of using Capacity-on-Demand Licensing. Pay for what you use.
Few other benefits includes
- Saves Time and Money
- Single Vendor Support
- High Performance and High Availability
- End to End Monitoring for all components
- Reduced Cost
- Easy management and Supporting
History of ODA Generation- V1 – Released in 2011 – First ODA model
- X3-2 – Released in 2013 – First Generation ODA model
- X4-2 – Released in 2013 – Second Generation ODA model
- X5-2 – Released in 2015 – Third Generation ODA model
- X6-2 – Released in 2016 – Fourth Generation ODA model
Below picture provides few details on the Oracle Database Appliance Hardware generation and enhancement.
In my next article I will touch base on Oracle Database Appliance X6-2 Small, Medium and Large.
Conclusion
In this article we have learned about Oracle Database Appliance and different hardware generations. The Oracle Database Appliance saves time and money by simplifying deployment, maintenance, and support of high availability Database solutions.
-
Oracle Database Appliance Kit Command Line Interface (oakcli)
Introduction
oakcli stands for Oracle Appliance Kit Command Line Interface. oakcli utility is used to manage Oracle Database Applaince. It used to carry out management tasks such as, Deploying, Patching, validating, monitoring, troubleshooting, Create Database, Create database homes, Configuring core key, manage Virtual machines and so on.
oakcli utility is located under the direcoty /opt/oracle/oak/bin/oakcli
oakcli logs oakcli commands output under the directory /opt/oracle/oak/log/<hostname>/client/oakcli.log
Few things that you can do with oakcli but not limited to are:- Deploy Oracle Database Appliance
- Configure network for Oracle Database Appliance deployment
- Patching Oracle Database Appliance
- Unpacking packages into oakcli repository
- Troubleshoot Oracle Database Appliance
- Monitor Oracle Database Appliance
- Validate Oracle Database Appliance
- Applying the Core Configuration key
- Copying the deployment configuration file
- Locate a disk on ODA
- Manage ODA Repository
- Manage ODA diagnostics collection
Execute the oakcli -h command to list the different options available with oakcli:
[root@odanode1 ~]# oakcli -h
Usage: oakcli show – Shows disk, diskgroup, expander, controller, server, processor, memory, power, cooling, network, enclosure, storage, version, fs, raidsyncstatus, dbhomes, dbstorage, databases, db_config_params, core_config_key, env_hw, ASR
oakcli configure – Configures the Network or ASR or additional Net
oakcli apply – Applies the core_config_key
oakcli locate – Locates a disk
oakcli deploy – Deploys the Database Appliance
oakcli update – Updates the Database Appliance
oakcli validate – Validates the Database Appliance
oakcli manage – Manages the OAK repository, diagcollect etc.,
oakcli unpack – Unpack the given package to OAK repository
oakcli copy – Copies the deployment config file
oakcli upgrade – Upgrades database
oakcli stordiag – Run storage diagnostic tool on both Nodes
oakcli test – Test ASR
oakcli orachk – Performs configuration settings check on ODA
oakcli create – Creates Database, DB storage, snapshotdb, dbhome, db_config_params file
oakcli delete – Deletes Database, DB storage, dbhome, db_config_params file
oakcli modify – Performs modify opeartions on Database
oakcli resize – Resizes DB storage
Commonly used Oracle Database Appliance Commands used on daily basis and their Output
- Execute the following command to list all the options that can be used with oakcli show
[root@odanode1 ~]# oakcli show -h
Usage:
oakcli show {disk|diskgroup|expander|fs|raidsyncstatus|controller|server|processor|memory|iraid|power|cooling|network|ib|enclosure|storage|core_config_key|version|dbhomes|dbstorage|databases|db_config_params|asr|env_hw} [<options>]
where:
disk – About the disk
diskgroup – ASM disk group
expander – Expander
fs – Filesystem
controller – Controller
storage – All storage components
version – Running software version
dbhomes – Installed oracle database homes
dbstorage – Details of ACFS storage setup for the databases
databases – Database names
db_config_params – db_config_params file
asr – ASR configuration
env_hw – Environment and Hardware information
server – Details of server sub-system
processor – Details of processor sub-system
memory – Details of memory sub-system
iraid – Details of internal RAIDs sub-system
power – Details of power supply sub-system
cooling – Details of cooling sub-system
network – Details of network sub-system
ib – Details of infiniband sub-system
enclosure – Details of enclosure sub-system
raidsyncstatus – RAID sync status information
core_config_key – Core configuration
For detailed help on each command and object and its options use:
oakcli <command> <object> -h
- To check if whether ODA deployment is Bare Metal or Virtualized
[root@odanode1 ~]# oakcli show env_hw
BM ODA X5-2
Public interface : COPPER
or
[root@odanode1 ~]# lsmod |grep net
( If no reply, It means the ODA is Bare Metal)
- To get the ODA software version
[root@odanode1 ~]# oakcli show version
Version
——-
12.1.2.9.0
- To get the ODA software and component version
[root@odanode1 ~]# /opt/oracle/oak/bin/oakcli show version -detail
Reading the metadata. It takes a while…
System Version Component Name Installed Version Supported Version
————– ————— —————— —————–
12.1.2.10.0
Controller_INT 11.05.03.00 Up-to-date
Controller_EXT 11.05.03.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED 944A Up-to-date
HDD_LOCAL A72A Up-to-date
HDD_SHARED A72A Up-to-date
ILOM 3.2.8.25 r114493 Up-to-date
BIOS 25040100 Up-to-date
IPMI 1.8.12.4 Up-to-date
HMP 2.3.5.2.8 Up-to-date
OAK 12.1.2.10.0 Up-to-date
OL 6.8 Up-to-date
GI_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
DB_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
- To list the shared disks on ODA
[root@odanode1 ~]# oakcli show disk
NAME PATH TYPE STATE STATE_DETAILS
e0_pd_00 /dev/sda HDD ONLINE Good
e0_pd_01 /dev/sdc HDD ONLINE Good
e0_pd_02 /dev/sde HDD ONLINE Good
e0_pd_03 /dev/sdg HDD ONLINE Good
e0_pd_04 /dev/sdi HDD ONLINE Good
e0_pd_05 /dev/sdk HDD ONLINE Good
e0_pd_06 /dev/sdm HDD ONLINE Good
e0_pd_07 /dev/sdo HDD ONLINE Good
e0_pd_08 /dev/sdq HDD ONLINE Good
e0_pd_09 /dev/sds HDD ONLINE Good
e0_pd_10 /dev/sdu HDD ONLINE Good
e0_pd_11 /dev/sdw HDD ONLINE Good
e0_pd_12 /dev/sdy HDD ONLINE Good
e0_pd_13 /dev/sdaa HDD ONLINE Good
e0_pd_14 /dev/sdac HDD ONLINE Good
e0_pd_15 /dev/sdae HDD ONLINE Good
e0_pd_16 /dev/sdag SSD ONLINE Good
e0_pd_17 /dev/sdah SSD ONLINE Good
e0_pd_18 /dev/sdaj SSD ONLINE Good
e0_pd_19 /dev/sdal SSD ONLINE Good
e0_pd_20 /dev/sdan SSD ONLINE Good
e0_pd_21 /dev/sdap SSD ONLINE Good
e0_pd_22 /dev/sdas SSD ONLINE Good
e0_pd_23 /dev/sdau SSD ONLINE Good
- To list ASM disk groups on ODA
[root@odanode1 ~]# oakcli show diskgroup
DiskGroups
———-
DATA
FLASH
RECO
REDO
- To list the Local file system and ACFS file system on ODA
[root@odanode1 ~]# oakcli show fs
Type Total Space Free Space Total DG Space Free DG Space Diskgroup Mount Point
ext3 29757M 12875M – – /
ext3 98M 61M – – /boot
ext3 59515M 21886M – – /opt
ext3 297580M 99815M – – /u01
acfs 51200M 51022M 52428736M 50878580M DATA /u02/app/oracle/oradata/EC00001
acfs 51200M 38661M 52428736M 50878580M DATA /u02/app/oracle/oradata/EC00002
acfs 51200M 51022M 52428736M 50878580M DATA /u02/app/oracle/oradata/EC00003
acfs 614400M 498139M 52428736M 50878580M DATA /u02/app/oracle/oradata/datastore
acfs 113920M 112668M 1526208M 1145088M FLASH /u02/app/oracle/oradata/flashdata
acfs 51200M 51022M 8618304M 4531524M RECO /cloudfs
acfs 5120M 5033M 8618304M 4531524M RECO /u01/app/oracle/fast_recovery_area/EC00001
acfs 5120M 3446M 8618304M 4531524M RECO /u01/app/oracle/fast_recovery_area/EC00002
acfs 5120M 5033M 8618304M 4531524M RECO /u01/app/oracle/fast_recovery_area/EC00003
acfs 1971200M 1923144M 8618304M 4531524M RECO /u01/app/oracle/fast_recovery_area/datastore
acfs 1536M 1456M 763120M 671776M REDO /u01/app/oracle/oradata/EC00001
acfs 1536M 1070M 763120M 671776M REDO /u01/app/oracle/oradata/EC00002
acfs 1536M 1456M 763120M 671776M REDO /u01/app/oracle/oradata/EC00003
acfs 25600M 13484M 763120M 671776M REDO /u01/app/oracle/oradata/datastore
- To list ODA Storage Shelve details
[root@odanode1 ~]# oakcli show storage
==== BEGIN STORAGE DUMP ========
Host Description: Oracle Corporation:ORACLE SERVER X5-2
Total number of controllers: 3
Id = 1
Serial Num = 500605b00a2f5c10
Vendor = LSI Logic
Model = ORCL-EXT-SAS3
FwVers = 09.00.00.00
strId = mpt3sas:03:00.0
Id = 2
Serial Num = 500605b00a2f5b00
Vendor = LSI Logic
Model = ORCL-EXT-SAS3
FwVers = 09.00.00.00
strId = mpt3sas:13:00.0
Id = 0
Serial Num = SV52603740
Vendor = LSI Logic
Model = LSI MegaRAID 9361-8i
FwVers = 4.230.40-3739
strId = mptmega:23:00.0
Total number of expanders: 2
Id = 1
Serial Num = 5080020001e65bea
Vendor = ORACLE
Model = DE2-24C
FwVers = 0018
strId = Secondary
WWN = 5080020001e677be
Id = 0
Serial Num = 5080020001e65bea
Vendor = ORACLE
Model = DE2-24C
FwVers = 0018
strId = Primary
WWN = 5080020001ea4ebe
Total number of PDs: 24
/dev/sda LSI Logic HDD 4000gb slot: 0 exp: 0
/dev/sdc LSI Logic HDD 4000gb slot: 1 exp: 0
/dev/sde LSI Logic HDD 4000gb slot: 2 exp: 0
/dev/sdg LSI Logic HDD 4000gb slot: 3 exp: 0
/dev/sdi LSI Logic HDD 4000gb slot: 4 exp: 0
/dev/sdk LSI Logic HDD 4000gb slot: 5 exp: 0
/dev/sdm LSI Logic HDD 4000gb slot: 6 exp: 0
/dev/sdo LSI Logic HDD 4000gb slot: 7 exp: 0
/dev/sdq LSI Logic HDD 4000gb slot: 8 exp: 0
/dev/sds LSI Logic HDD 4000gb slot: 9 exp: 0
/dev/sdu LSI Logic HDD 4000gb slot: 10 exp: 0
/dev/sdw LSI Logic HDD 4000gb slot: 11 exp: 0
/dev/sdy LSI Logic HDD 4000gb slot: 12 exp: 0
/dev/sdaa LSI Logic HDD 4000gb slot: 13 exp: 0
/dev/sdac LSI Logic HDD 4000gb slot: 14 exp: 0
/dev/sdae LSI Logic HDD 4000gb slot: 15 exp: 0
/dev/sdag LSI Logic SSD 400gb slot: 16 exp: 0
/dev/sdah LSI Logic SSD 400gb slot: 17 exp: 0
/dev/sdaj LSI Logic SSD 400gb slot: 18 exp: 0
/dev/sdal LSI Logic SSD 400gb slot: 19 exp: 0
/dev/sdan LSI Logic SSD 200gb slot: 20 exp: 0
/dev/sdap LSI Logic SSD 200gb slot: 21 exp: 0
/dev/sdas LSI Logic SSD 200gb slot: 22 exp: 0
/dev/sdau LSI Logic SSD 200gb slot: 23 exp: 0
==== END STORAGE DUMP =========
- To list Database homes on ODA
[root@odanode1 ~]# oakcli show dbhomes
Oracle Home Name Oracle Home version Home Location
—————- ——————- ————
OraDb12102_home1 2.1.0.2.170117(24732082,24828633) /u01/app/oracle/product/12.1.0.2/dbhome_1
- To list database storage on ODA
[root@odanode1 ~]# oakcli show dbstorage
All the DBs with DB TYPE as non-CDB share the same volumes
DB_NAMES DB_TYPE Filesystem Size Used Available AutoExtend Size DiskGroup
——- ——- ———— —— —– ——— —————- ——–
odatest CDB /u01/app/oracle/oradata/EC00001 1.5G 0.45G 1.05G 1G REDO
/u02/app/oracle/oradata/EC00001 50G 12.24G 37.76G 1G DATA
/u01/app/oracle/fast_recovery_area/EC00001 5G 1.63G 3.37G 1G RECO
odaprod non-CDB /u01/app/oracle/oradata/datastore 25G 11.83G 13.17G N/A REDO
/u02/app/oracle/oradata/datastore 600G 113.54G 486.46G N/A DATA
/u02/app/oracle/oradata/flashdata 111.25G 1.22G 110.03G 55G FLASH
/u01/app/oracle/fast_recovery_area/datastore 1925G 46.93G 1878.07G 194G RECO
odadev CDB /u01/app/oracle/oradata/EC00002 1.5G 0.08G 1.42G 1G REDO
/u02/app/oracle/oradata/EC00003 50G 0.17G 49.83G 1G DATA
/u01/app/oracle/fast_recovery_area/EC00003 5G 0.08G 4.92G 1G RECO
odaqa CDB /u01/app/oracle/oradata/EC00002 1.5G 0.08G 1.42G 1G REDO
/u02/app/oracle/oradata/EC00002 50G 0.17G 49.83G 1G DATA
/u01/app/oracle/fast_recovery_area/EC00002 5G 0.08G 4.92G 1G RECO
- To list databases on ODA
[root@odanode1 ~]# oakcli show databases
Name Type Storage HomeName HomeLocation Version
—– —— ——– ————– —————- ———-
odaprod RAC ACFS OraDb12102_home1 /u01/app/oracle/product/12.1.0.2/dbhome_1 12.1.0.2.170117(24732082,24828633)
- To list the database configuration parameter files on ODA
[root@odanode1 ~]# oakcli show db_config_params
The available DB configuration files are :
acfsoemrepo
default
orcl
- To list ASR status on ODA
[root@odanode1 ~]# oakcli show asr
The ASR is not configured
- To check the ODA servers details
[root@odanode1 ~]# oakcli show server
Power State : On
Open Problems : 0
Model : ODA X5-2
Type : Rack Mount
Part Number : 33772477+1+1
Serial Number : 1942NMF001
Primary OS : Not Available
ILOM Address : 14.68.20.101
ILOM MAC Address : 00:10:E0:8D:B3:FC
Description : Oracle Database Appliance X5-2 1535NMF00K
Locator Light : Off
Actual Power Consumption : 363 watts
Ambient Temperature : 27.750 degree C
Open Problems Report : System is healthy
- To list Processor on ODA
[root@odanode1 ~]# oakcli show processor
NAME HEALTH HEALTH_DETAILS PART_NO. LOCATION MODEL MAX_CLK_SPEED TOTAL_CORES
CPU_0 OK – 060F P0 (CPU 0) Intel(R) Xeon(R) CPU E5-2699 2.300 GHz 18
CPU_1 OK – 060F P1 (CPU 1) Intel(R) Xeon(R) CPU E5-2699 2.300 GHz 18
- To list Physical Memory on ODA
[root@odanode1 ~]# oakcli show memory
NAME HEALTH HEALTH_DETAILS PART_NO. SERIAL_NO. LOCATION MANUFACTURER MEMORY_SIZE CURR_CLK_SPEED ECC_Errors
DIMM_0 OK – 6A4G40DM0-CPB 00CE021525728FCD58 P0/D0 Samsung 32 GB 2133 MHz 0
DIMM_11 OK – 6A4G40DM0-CPB 00CE021525728FCD54 P0/D1 Samsung 32 GB 2133 MHz 0
DIMM_12 OK – 6A4G40DM0-CPB 00CE021525728FCD1C P1/D0 Samsung 32 GB 2133 MHz 0
DIMM_15 OK – 6A4G40DM0-CPB 00CE021525728FCD5F P1/D3 Samsung 32 GB 2133 MHz 0
DIMM_20 OK – 6A4G40DM0-CPB 00CE021525728FCD3C P1/D8 Samsung 32 GB 2133 MHz 0
DIMM_23 OK – 6A4G40DM0-CPB 00CE021525728FCD56 P1/D1 Samsung 32 GB 2133 MHz 0
DIMM_3 OK – 6A4G40DM0-CPB 00CE021525728FCD5B P0/D3 Samsung 32 GB 2133 MHz 0
DIMM_8 OK – 6A4G40DM0-CPB 00CE021525728FCD29 P0/D8 Samsung 32 GB 2133 MHz 0
- To list raid configuration on ODA
[root@odanode1 ~]# oakcli show iraid
NAME CTRL# PRODUCT SERIAL_NO BIOS_VER FW_VER VDISK_TYPE VDISK_STATE PDISK_MODEL EID:SLT PDISK_STATE SIZE
CV_MODEL CV_STATE CV_TEMP
IR_0_0_0 0 LSI MegaRAID 9361-8i SV52603740 6.17.04.2_4.16.08.00_0x06060A 4.230.40-3739 RAID1 Optl H109060SESUN600G 252:0 Onln 557.861 GB CVPM02 Optimal 29C
IR_0_0_1 0 LSI MegaRAID 9361-8i SV52603740 6.17.04.2_4.16.08.00_0x06060A 4.230.40-3739 RAID1 Optl H109060SESUN600G 252:1 Onln 557.861 GB CVPM02 Optimal 29C
- To check power on ODA
[root@odanode1 ~]# oakcli show power
NAME HEALTH HEALTH_DETAILS PART_NO. SERIAL_NO. LOCATION INPUT_POWER OUTPUT_POWER INLET_TEMP EXHAUST_TEMP
Power_Supply_0 OK – 7079395 476856Z+1524CE007B PS0 Present 167 watts 35.000 degree C 37.125 degree C
Power_Supply_1 OK – 7079395 476856Z+1524CE007V PS1 Present 163 watts 35.000 degree C 40.125 degree C
- To check FAN status on ODA
[root@odanode1 ~]# oakcli show cooling
NAME HEALTH HEALTH_DETAILS LOCATION FAN % FAN SPEED
Fan_0 OK – FM0 40 % 7800 RPM
Fan_1 OK – FM0 38 % 6600 RPM
Fan_10 OK – FM2 47 % 9200 RPM
Fan_11 OK – FM2 48 % 8300 RPM
Fan_12 OK – FM3 48 % 9300 RPM
Fan_13 OK – FM3 46 % 8000 RPM
Fan_14 OK – FM3 39 % 7600 RPM
Fan_15 OK – FM3 39 % 6800 RPM
Fan_2 OK – FM0 64 % 12300 RP
Fan_3 OK – FM0 60 % 10400 RP
Fan_4 OK – FM1 63 % 12200 RP
Fan_5 OK – FM1 59 % 10200 RP
Fan_6 OK – FM1 36 % 7000 RPM
Fan_7 OK – FM1 34 % 6000 RPM
Fan_8 OK – FM2 36 % 7000 RPM
Fan_9 OK – FM2 35 % 6100 RPM
- To check network status on ODA
[root@odanode1 ~]# oakcli show network
Gathering Statistics…
- To check IB interface on ODA
[root@odanode1 ~]# oakcli show ib
Infiniband is not present in the system
- To check ODA servers enclosure
[root@odanode1 ~]# oakcli show enclosure
NAME SUBSYSTEM STATUS METRIC
E0_FAN0 Cooling Not install 0 rpm
E0_FAN1 Cooling Not install 0 rpm
E0_FAN2 Cooling OK 3450 rpm
E0_FAN3 Cooling OK 3070 rpm
E0_FAN4 Cooling OK 3750 rpm
E0_FAN5 Cooling OK 3070 rpm
E0_FAN6 Cooling Not install 0 rpm
E0_FAN7 Cooling Not install 0 rpm
E0_IOM0 Encl_Electronics OK –
E0_IOM1 Encl_Electronics OK –
E0_PSU0 Power_Supply Not install –
E0_PSU1 Power_Supply OK –
E0_PSU2 Power_Supply OK –
E0_PSU3 Power_Supply Not install –
E0_TEMP0 Amb_Temp OK 30 C
E0_TEMP1 Midplane_Temp OK 35 C
E0_TEMP2 PCM0_Inlet_Temp OK 41 C
E0_TEMP3 PCM0_Hotspot_Temp OK 50 C
E0_TEMP4 PCM1_Inlet_Temp OK 35 C
E0_TEMP5 PCM1_Hotspot_Temp OK 45 C
E0_TEMP6 IOM0_Temp OK 52 C
E0_TEMP7 IOM1_Temp OK 43 C
- To check RAID sync status
[root@odanode1 ~]# oakcli show raidsyncstatus
Raid Type Raid Device Raid Status maintainPdFailHistory Rebuildrate
H/W Raid /dev/sdaw Optimal OFF 30%- To check CPU core configuration key file applied on ODA
[root@odanode1 ~]# oakcli show core_config_key
Optional core config key is not applied on the machine yet!
- To check OAK daemon is running on ODA server
[root@odanode1 ~]# ps -ef |grep oakd
root 21707 3996 0 Jan05 ? 1-20:47:15 /opt/oracle/oak/bin/oakd foreground
root 58895 83838 0 16:01 pts/0 00:00:00 grep oakd
- To check OAK location
[root@odanode1 ~]# env |grep ORA
ORA_OAK_HOME=/opt/oracle/oak
- To configure fistnet on ODA
[root@oak1 ~]# /opt/oracle/oak/bin/oakcli configure firstnet
- To deploy ODA
[root@oak1 ~]# oakcli deploy
- To unpack sofware on ODA
[root@odanode1 ~]#oakcli unpack -package p25499210_1212100_Linux_x86-64_1of2.zip
Unpacking will take some time , Please wait…
Successfully unpacked the files to repository.
- To create Database on ODA
[root@odanode1 ~]# oakcli create database -db odatest -oh OraDb12102_home1
- To validate cabling on ODA
[root@oak1 ~]# /opt/oracle/oak/bin/oakcli validate -c storagetopology
- To update/patch ODA server
[root@oak1 ~]# oakcli update -patch 12.1.2.10.0 –server -local
- To update/patch ODA storage
[root@oak1 ~]# oakcli update -patch 12.1.2.10.0 –storageConclusion
In this article we have learned about oackcli utility and few ODA commands used on daily basis. oakcli stands for Oracle Appliance Kit Command Line Interface. oakcli utility is used to manage Oracle Database Applaince. It used to carry out management tasks such as, Deploying, Patching, validating, monitoring, troubleshooting, Create Database, Create database homes, Configuring core key, manage Virtual machines and so on. -
Oracle Database Appliance – Resize ACFS File System
Introduction
Oracle Database Appliance uses the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) for database and virtual machine files storage. Oracle ACFS provides both servers with concurrent access to some or all of the shared storage on Oracle Database Appliance. It supports space-efficient storage snapshots, which provides fast provisioning databases and virtual machines within Oracle Database Appliance.
To check Storage used for database running on ODA, execute the following:
[root@dzuro614001nor ~]# oakcli show databases
Name Type Storage HomeName HomeLocation Version
—– —— ——– ————– —————- ———-
odatest RAC ACFS OraDb12102_home1 /u01/app/oracle/product/12.1.0.2/dbhome_1 2.1.0.2.170117(24732082,24828633)
In this article I will demonstrate how to check ACFS mounts on ODA and how to resize an Oracle ACFS file system.
[root@odanode1 ~]# su – grid
[grid@odanode1 ~]$ . oraenv
ORACLE_SID = [+ASM1] ? +ASM2
The Oracle base has been set to /u01/app/grid
[grid@odanode1 ~]$ mount | grep asm
/dev/asm/flashdata-5 on /u02/app/oracle/oradata/flashdata type acfs (rw)
/dev/asm/datdc00000-282 on /u02/app/oracle/oradata/DC00000 type acfs (rw)
/dev/asm/datastore-305 on /u01/app/oracle/fast_recovery_area/datastore type acfs (rw)
/dev/asm/rdodc00001-55 on /u01/app/oracle/oradata/DC00001 type acfs (rw)
/dev/asm/datdc00002-282 on /u02/app/oracle/oradata/DC00002 type acfs (rw)
/dev/asm/rcodc00002-305 on /u01/app/oracle/fast_recovery_area/DC00002 type acfs (rw)
/dev/asm/rdodc00000-55 on /u01/app/oracle/oradata/DC00000 type acfs (rw)
/dev/asm/datastore-282 on /u02/app/oracle/oradata/datastore type acfs (rw)
/dev/asm/rcodc00000-305 on /u01/app/oracle/fast_recovery_area/DC00000 type acfs (rw)
/dev/asm/datastore-55 on /u01/app/oracle/oradata/datastore type acfs (rw)
/dev/asm/datdc00001-282 on /u02/app/oracle/oradata/DC00001 type acfs (rw)
/dev/asm/rdodc00002-55 on /u01/app/oracle/oradata/DC00002 type acfs (rw)
/dev/asm/rcodc00001-305 on /u01/app/oracle/fast_recovery_area/DC00001 type acfs (rw)
/dev/asm/acfsvol-305 on /cloudfs type acfs (rw)
Here I would like to resize the ACFS /u02/app/oracle/oradata/DC00002 from 1.5TB to 2.5TB
Follow the steps below to resize the ACFS file system:
[grid@odanode1 ~]$ df -h /u02/app/oracle/oradata/DC00002
Filesystem Size Used Avail Use% Mounted on
/dev/asm/datdc00002-282
1.5T 233G 1.3T 15% /u02/app/oracle/oradata/DC00002
[grid@odanode1 ~]$ /sbin/advmutil volinfo /dev/asm/datdc00002-282
/dev/asm/datdc00002-282
Interface Version: 1
Size (MB): 1572864
Resize Increment (MB): 64
Redundancy: mirror
Stripe Columns: 8
Stripe Width (KB): 1024
Disk Group: DATA
Volume: DATDC00002
Compatible.advm: 12.1.0.2.0
[grid@odanode1 ~]$ asmcmd lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED NORMAL N 512 4096 4194304 103088128 93545932 6443008 43551462 0 Y DATA/
MOUNTED NORMAL N 512 4096 4194304 1526208 835840 381552 227144 0 N FLASH/
MOUNTED NORMAL N 512 4096 4194304 16930368 13944968 1058148 6443410 0 N RECO/
MOUNTED HIGH N 512 4096 4194304 763120 634480 381560 84306 0 N REDO/
[grid@odanode1 ~]$ /sbin/acfsutil size -h
Usage: acfsutil [-h] size [[-|+]nnn[K|M|G|T|P]] [-a nnn[K|M|G|T|P]] [-x nnn[K|M|G|T|P]] [-d <device>] <path>
– Resize file system and configure auto-resize
[-a] – Auto-resize increment
[-x] – Auto-resize maximum
[-d] – Resize only this device
[grid@odanode1 ~]$ /sbin/acfsutil size 2.5T /u02/app/oracle/oradata/DC00002
acfsutil size: new file system size: 2748779069440 (2621440MB)
[grid@odanode1 ~]$ df -h /u02/app/oracle/oradata/DC00002
Filesystem Size Used Avail Use% Mounted on
/dev/asm/datdc00024-282
2.5T 233G 2.2T 9% /u02/app/oracle/oradata/DC00002
[grid@odanode1 ~]$ /sbin/advmutil volinfo /dev/asm/datdc00002-282
Device: /dev/asm/datdc00002-282
Interface Version: 1
Size (MB): 2621440
Resize Increment (MB): 64
Redundancy: mirror
Stripe Columns: 8
Stripe Width (KB): 1024
Disk Group: DATA
Volume: DATDC00002
Compatible.advm: 12.1.0.2.0
Conclusion
In this article we have learned how to resize an Oracle ACFS file system. ODA uses Oracle Automatic Storage Management Cluster File System (Oracle ACFS) for database and virtual machine files storage, provides both servers with concurrent access and supports space-efficient storage snapshots.









