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) Stack
Step 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
In 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 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:
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 Oracle
The 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.
Note: 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 ApplianceSmall, 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 -h
odacli <command> <options>
Commands list (use –help option for help on any command):
appliance:
create-appliance
describe-appliance
asr:
configure-asr
delete-asr
describe-asr
test-asr
update-asr
component:
describe-component
cpucore:
describe-cpucore
list-cpucores
update-cpucore
credential:
set-credential
database:
create-database
delete-database
describe-database
list-databases
register-database
dbhome:
create-dbhome
delete-dbhome
describe-dbhome
list-dbhomes
update-dbhome
dbstorage:
create-dbstorage
delete-dbstorage
describe-dbstorage
list-dbstorages
dcsagent:
update-dcsagent
job:
describe-job
list-jobs
latestpatch:
describe-latestpatch
network:
create-network
delete-network
describe-network
list-networks
update-network
networkinterface:
describe-networkinterface
list-networkinterfaces
repository:
update-repository
server:
update-server
To describe ODA execute the following command
[root@odanode1 ~]# odacli describe-appliance
Appliance Information
—————————————————————-
ID: 9aef262c-xxxx-xxxx-xxxx-0d877c03d762
Platform: ODA
Data Disk Count: 2
CPU Core Count: 10
Created: May 23, 2017 3:08:03 AM CST
System Information
—————————————————————-
Name: odanode
Domain Name: netsoftmate.com
Time Zone: Asia/Pacific
DB Edition: EE
DNS Servers: 10.1.1.1
NTP Servers: ntp1.netsoftmate.com
Disk Group Information
—————————————————————-
DG Name Redundancy Percentage
————————- ————————- ————
Data Normal 80
Reco Normal 20
Options:
–details, -d
Detail Info
To describe ODA in details execute the following command
65b60824-cb18-4fec-bdec-baf7e440efc9 Provisioning service creation May 23, 2017 3:08:03 AM CST Success
74d38c8e-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 Success
26de75bb-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-latestpatch
componentType availableVersion
————— ——————–
gi 12.1.0.2.170117
db 11.2.0.4.161018
db 12.1.0.2.170117
oak 12.1.2.10.0
ilom 3.2.8.24.r114611
os 6.8
bios 38070000
Options :
–json, -j
json output
To list all the network details execute the following command
To check power status execute the following command
[root@odanode1 ~]# odaadmcli 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+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 network
NAME 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 C
Ethernet_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.
In 2011, Oracle Introduced an entry level Engineered system known as Oracle Database Appliance (ODA). 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 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:
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. The 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.
Note: With ODA X7-2, looks like the ODA X7-2 Large configuration is discontinued. 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
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
The following picture shows the Oracle Database Appliance X6 and X7 Model Family Details
Conclusion In this blog we have learned about Oracle Database Appliance X6 and X7 Model Family. With the new ODA model Small, Medium and Large, the Oracle Database Appliance X6-2 and X7-2 model family brings Oracle Engineered Systems to within reach of every organization.
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 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:
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.
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 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
[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!
[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.
Conclusion 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.
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 RACACFS 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.