Good Contents Are Everywhere, But Here, We Deliver The Best of The Best.Please Hold on!
Database Management Services, Oracle Database Appliance - ODA, Oracle Database Management Solution, Oracle Databases, Remote Database Management, Technology Consulting Services

September 2019 Oracle announced Oracle Database Appliance X8-2 (Small, Medium and HA). ODA X8-2 comes with more computing resources compared with X7-2 Models.

Let’s take a quick look at few benefits of ODA followed by the technical specification on ODA X8-2 Small/Medium and HA.

Oracle Database Appliance is an Engineered System. Software, server, storage, and networking, all co-engineered and optimized to run Oracle Database and applications.


Benefits of Oracle Database Appliance (ODA):

  1. Software, server, storage, and networking engineered and optimized to run Oracle Database and applications.

  2. Supports Oracle Database Standard Edition, Standard Edition One, Standard Edition 2, and Enterprise Edition. Optimized for Cloud.

  3. Capacity on Demand Licensing – Reduced Cost.

  4. Ease of deployment, patching, management, and support.

  5. Increased performance and reliability with NVMe flash storage.

  6. Reliable hardware architecture with redundant power, cooling, networking, and storage.

  7. Browser User Interface (BUI)


In this article we will compare the technical specifications of ODA X8-2 model family (Small, Medium and HA). This comparison table comes handy when you want to quickly take a look at the resources available for a given model.

 

For more information on the technical specification loot at the ODA X8-2 HA and Small/Medium Data Sheet at:

https://www.oracle.com/technetwork/database/database-appliance/oda-x8-2-ha-datasheet-5730739.pdf

https://www.oracle.com/technetwork/database/database-appliance/oda-x8-2sm-datasheet-5730738.pdf



Component

ODA X8-2 Small

ODA X8-2 Medium

ODA X8-2 HA


Database Server

1

1

2

Storage Shelf

NA

NA

1 4U DE3-24C Storage Shelf per System

Optional Second Storage Shelf for Expansion

Rack Size

1 2RU Server

1 2RU Server

2 2RU Servers & 1 4U Storage Shelf

Processor

One 16-core Intel Xeon Gold 5218

Two 16-core Intel Xeon Gold 5218

Two 16-core Intel Xeon Gold 5218 Per Server

Physical Memory

192 GB

Expandable to 384 GB

384 GB

Expandable to 768 GB

384 GB

Expandable to 768 GB per server

Storage

Two 6.4 TB NVMe SSDs

12.8 TB (raw)

Base: Two 6.4 TB NVMe SSDs

12.8 TB (raw)

Base: Six 7.68 TB SSDs

46 TB (raw)

Storage Expansion

Not expandable

Expandable up to 76.8 TB (raw)

Expandable up to 369 TB SSD or up to 92 TB SSD / 504 TB HDD (Raw)

Network

4 x 10GBase-T ports (RJ45) expandable up to 12 x 10GBase-T ports or

2 x 10/25 GbE ports (SFP28) expandable up to 6 x 10/25 GbE ports

4 x 10GBase-T ports (RJ45) expandable up to 12 x 10GBase-T ports or

2 x 10/25 GbE ports (SFP28) expandable up to 6 x 10/25 GbE ports

4 x 10GBase-T ports (RJ45) expandable up to 12 x 10GBase-T ports or

2 x 10/25 GbE ports (SFP28) expandable up to 6 x 10/25 GbE ports

Oracle Database

Oracle Database 18c/19c EE & SE 2

Oracle Database 12c R1/R2 EE & SE 2

Oracle Database 11g R2 EE, SE & SE 1

Oracle Database 18c/19c EE & SE 2

Oracle Database 12c R1/R2 EE & SE 2

Oracle Database 11g R2 EE, SE & SE 1

Oracle Database 18c/19c EE & SE 2

Oracle Database 12c R1/R2 EE & SE 2

Oracle Database 11g R2 EE, SE & SE 1

Database Deployment

Single Instance

Single Instance

Single Instance, RAC & RAC One node

Virtualization

Oracle Linux KVM

Oracle Linux KVM

Oracle VM & Oracle Linux KVM

Operating System

Oracle Linux

Oracle Linux

Oracle Linux





Are you and your team considering setting up Oracle Database Appliance? Let Netsoftmate help you choose the right product keeping under consideration your budget, requirement and usage forecasting. Click on the image below to sign-up NOW!



0

Database Management Services, Oracle Database Appliance - ODA, Oracle Database Management Solution, Oracle Databases, Remote Database Management, Technology Consulting Services
In September 2019, Oracle announced Oracle Database Appliance X8-2 (Small, Medium and HA). ODA X8-2 comes with more computing resources compared with X7-2 Models.


Let’s take a quick look at few benefits of ODA followed by the technical specification on ODA X8-2 Small/Medium and HA.


Oracle Database Appliance is an Engineered System. Software, server, storage, and networking, all co-engineered and optimized to run Oracle Database and applications.


Benefits of Oracle Database Appliance (ODA):

  1. Software, server, storage, and networking engineered and optimized to run Oracle Database and applications.
  2. Supports Oracle Database Standard Edition, Standard Edition One, Standard Edition 2, and Enterprise Edition.
  3. Optimized for Cloud
  4. Capacity on Demand Licensing – Reduced Cost
  5. Ease of deployment, patching, management, and support
  6. Increased performance and reliability with NVMe flash storage
  7. Reliable hardware architecture with redundant power, cooling, networking, and storage
  8. Browser User Interface (BUI)


Oracle Database Appliance X8-2 HA Benefits & Technical specification


  1. Support mission-critical applications and consolidation of many databases
  2. Built for high availability
  3. Choice of high-performance flash or high-capacity drives
  4. 32 cores per server (64 cores in total for 2 servers)
  5. 384 GB physical memory per server expandable upto 768 (1.5 TB memory in total for 2 servers)
  6. Storage Shelf
  7. High Capacity: 46 TB SSD and 252 TB SDD raw capacity per shelf
  8. High Performance: 184 TB SSD raw capacity per shelf
  9. Choice of 10GBase-T or 10/25 GbE SFP28 public networking
  10. 25GbE interconnect for cluster communication


For more information on the technical specification loot at the ODA X8-2 HA Data Sheet at:
https://www.oracle.com/technetwork/database/database-appliance/oda-x8-2-ha-datasheet-5730739.pdf


 
 


 
  • Oracle Database Appliance X8-2 Small Technical specification

  1. One server
  2. 1 Intel Xeon processor, 16 Cores
  3. 192GB Physical memory expandable upto 384GB
  4. Choice of 10GBase-T or 10/25 GbE SFP28 public networking
  5. 12.8TB NVMe raw storage



Oracle Database Appliance X8-2 Medium Technical specification

  1. One server
  2. 2 Intel Xeon processor, 32 Cores
  3. 384 GB Physical memory expandable upto 768GB
  4. Choice of 10GBase-T or 10/25 GbE SFP28 public networking
  5. 12.8 TB NVMe raw storage capacity with optional expansion to 76.8 TB NVMe raw storage


For more information on the technical specification loot at the ODA X8-2 S/M Data Sheet at:
https://www.oracle.com/technetwork/database/database-appliance/oda-x8-2sm-datasheet-5730738.pdf



Conclusion


In this article we seen the benefits and the technical specification of latest Oracle Database Appliance X8 model family. ODA is the right choice for all type of Businesses as an on-premises solution and cloud ready option.



Are you and your team considering setting up Oracle Database Appliance? Let Netsoftmate help you choose the right product keeping under consideration your budget, requirement and usage forecasting. Click on the image below to sign-up NOW!



0

Database Management Services, Oracle Database Appliance - ODA, Oracle Database Management Solution, Oracle Databases, Remote Database Management, Uncategorized

ODA is basically a 2-node RAC cluster database system running Oracle Linux operating (OEL), Oracle Database Enterprise Edition or Standard 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.

 
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
  •  
With ODA X7-2, the ODA Large configuration is discontinued.
 
 
With the different model families there is always a confusion that which command line tool to be used for managing, monitoring and administrating Oracle Database Appliance.
 
 
 
 
In this article we will explain different command line tools that can be used to manage and administer an Oracle Database Appliance Small, Medium, Large and HA models for both Bare Metal and Virtualized Platform environment.
 
 
Let’s look at the different command line tools available:
 
OAKCLI: oakcli stands for Oracle Appliance Kit Command Line Interface. oakcli utility is used to manage Oracle Database Appliance. 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.

 
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.

The following table provides a quick reference on when to use oakcli Vs. odacli/odaadmcli
 
  • For Oracle Database Appliance software version 12.2.1.4 or older use the tools as shown in the following table
  •  
  •  
Oakcli
odacli/odaadmcli
ODA V1
ODA X6-2 S, M, L
ODA X3-2
ODA X7-2 S, M
ODA X4-2
ODA X7-2 HA (Bare Metal only) 
ODA X5-2
 
ODA X6-2 HA
 
ODA X7-2 HA (VM Only)
 
 


  • For Oracle Database Appliance software version 18.3.0.0 and later user the tools as shown in the following table


  •  
oakcli
odacli/odaadmcli
All hardware versions running Virtualized platform
All hardware versions running Bare Metal (physical)
 


Examples using oakcli, odacli and odaadmcli:
 
[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
 
 
[root@odanode1 ~]# odaadmcli show disk
        NAME            PATH            TYPE            STATE           STATE_DETAILS
 
        pd_00           /dev/nvme0n1    NVD             ONLINE          Good
        pd_01           /dev/nvme1n1    NVD             ONLINE          Good
 
 
[root@odanode1 ~]# odaadmcli show diskgroup
DiskGroups
———-
DATA
RECO
 
 
[root@odanode1 ~]# odaadmcli show env_hw
BM ODA X6-2 Small
 
 
[root@odanode1 ~]# odaadmcli show storage
==== BEGIN STORAGE DUMP ========
Host Description: Oracle Corporation:ORACLE SERVER X6-2
Total number of controllers: 2
        Id          = 0
        Pci Slot    = 10
        Serial Num  = xxxxxxxxxx
        Vendor      = Samsung
        Model       = MS1PC2DD3ORA3.2T
        FwVers      = KPYABR3Q
        strId       = nvme:19:00.00
        Pci Address = 19:00.0
 
        Id          = 1
        Pci Slot    = 11
        Serial Num  = xxxxxxxxxxx
        Vendor      = Samsung
        Model       = MS1PC2DD3ORA3.2T
        FwVers      = KPYABR3Q
        strId       = nvme:1b:00.00
        Pci 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 =========
 
 
[root@odanode1 ~]# oakcli show env_hw
BM ODA X5-2
Public interface : COPPER
 
 
[root@odanode1 ~]# oakcli show oda_base
ODA base domain
ODA base CPU cores :36
ODA base domain memory :362
ODA base template :/OVS/template.tar.gz
ODA base vlans :[‘priv1’, ‘net1’]
ODA base current status :Running
 
 
[root@odanode1 ~]# oakcli show env_hw
VM-oda_base ODA X7-2 HA
 
 
 
Conclusion

In this article we have learned about Oracle Database Appliance X6-2 and X7-2 model family. Also, we have learned when to use different ODA command lines tools such as oakcli, odacli and odaadmcli to manage and administer an Oracle Database Appliance.


eBook - Oracle Exadata X8M Patching Recipes | Netsoftmate
 
 
 
0

During the Oracle Database Appliance Deployment you can optionally configure CloudFS file system. The default mount point is /cloudfs and set to default size of 50GB. Oracle Database Appliance uses the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) for database and virtual machine files storage. ACFS can only be used to configure shared storage file system on ODA. Oracle ACFS provides both servers with concurrent access to /cloudfs shared file system. The default size of 50GB may not sufficient and must be increased to store big files for business requirement.


In this article we will demonstrate how to resize the /cloudfs file system using ASMCA GUI interface


Steps to resize the /cloudfs file system using asmca GUI Interface

Step 1: Get the current /cloudfs file system size

Step 2: Start VNC on node 1. Here I am starting VNC as root user. You can choose to start it as Grid or Oracle user.

[root@odanode1 ~]# rpm -qa *vnc*
tigervnc-1.1.0-18.el6.x86_64
tigervnc-server-1.1.0-18.el6.x86_64
[root@odanode1 ~]# ps -ef|grep vnc
root     23281 20754  0 13:32 pts/1    00:00:00 grep vnc

[root@odanode1 ~]# vncserver :1

You will require a password to access your desktops.

Password:
Verify:

New ‘odanode1:1 (root)’ desktop is odanode1:1

Creating default startup script /root/.vnc/xstartup
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/odanode1:1.log

[root@odanode1 ~]# ps -ef|grep vnc
root     23399     1  1 13:32 pts/1    00:00:00 /usr/bin/Xvnc :1 -desktop odanode1:1 (root) -auth /root/.Xauthority -geometry 1024×768 -rfbwait 30000 -rfbauth /root/.vnc/passwd -rfbport 5901 -fp catalogue:/etc/X11/fontpath.d -pn
root     23481 23480  0 13:33 pts/1    00:00:00 vncconfig -iconic
root     23636 20754  0 13:33 pts/1    00:00:00 grep vnc

Step 3: Start VNC viewer on desktop and enter the hostname/IP address on node 1. Enter the root password as we have started the VNC server using root user.



Step 4: Switch to grid user and verify the Grid Home

Step 5: Set Oracle Home to Grid home and start asmca

Step 6: Click on ASM Cluster File System Tab

Step 7: Right Click on /cloudfs and select Resize option

Step 8: Enter the desired new size. Here I am resizing the /cloudfs to 200GB

Step 9: Resize in progress

Step 10: Resize completed

Step 11: Verify the /cloudfs size



Conclusion

In this article we have learned how to resize/increase the size of /cloudfs ACFS file system on ODA using ASMCA GUI utility. The cloudfs file system is configured during the ODA deployment and it is set to 50GB which is not sufficient for storing the big files. The cloudfs is build using ACFS and it can be resized easily using ASMCA graphical interface.

0

Oracle Database Appliance (ODA) is an entry level Engineered System. 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.

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.

ODA consists of several hardware components such as Mother Board, Processor, Memory, Power Supply, FAN, Network cards and so on. You can monitor the hardware status of these components using OAKCLI command for both Bare Metal and Virtualized platform.

Note: ODACLI is used for Hardware monitoring and administrative tasks on the Oracle Database Appliance on X6-2 S/M/L & X7-2 S/M.


In this article we will demonstrate how to monitor different hardware component status on ODA nodes.

Using OAKCLI command to Get Hardware Status


  • Execute the following command to display ODA server details

[root@odanoden1 ~]# oakcli show server

        Power State              : On
        Open Problems            : 0
        Model                    : ODA X4-2
        Type                     : Rack Mount
        Part Number              : 33060862+1+1
        Serial Number            : 1440XXXXXX
        Primary OS               : Not Available
        ILOM Address             : 10.10.20.1
        ILOM MAC Address         : 00:10:E0:62:3F:F6
        Description              : Oracle Database Appliance X4-2 1440XXXXX
        Locator Light            : Off
        Actual Power Consumption : 261 watts
        Ambient Temperature      : 18.500 degree C
        Open Problems Report     : System is healthy

[root@odanoden2 ~]# oakcli show server

        Power State              : On
        Open Problems            : 0
        Model                    : ODA X4-2
        Type                     : Rack Mount
        Part Number              : 33060862+1+1
        Serial Number            : 1440XXXXXX
        Primary OS               : Not Available
        ILOM Address             : 10.10.20.2
        ILOM MAC Address         : 00:10:E0:62:41:D6
        Description              : Oracle Database Appliance X4-2 1440XXXXX
        Locator Light            : Off
        Actual Power Consumption : 269 watts
        Ambient Temperature      : 17.750 degree C
        Open Problems Report     : System is healthy


  • Execute the following command to display ODA model

[root@odanoden1 ~]# oakcli show env_hw
BM ODA X4-2
Public interface : COPPER


  • Execute the following command to display ODA software version details

[root@odanoden1 ~]# 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)


  • Execute the following command to display ‘oakcli show’ help

[root@odanoden1 ~]# oakcli show -h
Usage:
oakcli show {disk|diskgroup|expander|fs|raidsycstatus|controller|server|processor|memory|power|cooling|network|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
        power                    – Details of power supply sub-system
        cooling                  – Details of cooling sub-system
        network                  – Details of network 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


  • Execute the following command to monitor the Processor Status

[root@odanoden1 ~]# oakcli show processor

        NAME  HEALTH HEALTH_DETAILS PART_NO. LOCATION   MODEL                         MAX_CLK_SPEED TOTAL_CORES ENABLED_CORES

        CPU_0 OK     –              060E     P0 (CPU 0) Intel(R) Xeon(R) CPU E5-2697  2.700 GHz       12        NA
        CPU_1 OK     –              060E     P1 (CPU 1) Intel(R) Xeon(R) CPU E5-2697  2.700 GHz       12        NA


  • Execute the following command to monitor the Memory Status

[root@odanoden1 ~]# oakcli show memory

        NAME    HEALTH HEALTH_DETAILS PART_NO.         SERIAL_NO.         LOCATION MANUFACTURER MEMORY_SIZE CURR_CLK_SPEED ECC_Errors

        DIMM_0  OK     –              M393B2G70DB0-YK0 00CE03143317593248 P0/D0    Samsung      16 GB       1600 MHz       0
        DIMM_1  OK     –              M393B2G70DB0-YK0 00CE0314331759238B P0/D1    Samsung      16 GB       1600 MHz       0
        DIMM_10 OK     –              M393B2G70DB0-YK0 00CE031433175926CD P1/D2    Samsung      16 GB       1600 MHz       0
        DIMM_11 OK     –              M393B2G70DB0-YK0 00CE031433175927AD P1/D3    Samsung      16 GB       1600 MHz       0
        DIMM_12 OK     –              M393B2G70DB0-YK0 00CE031433175922C3 P1/D4    Samsung      16 GB       1600 MHz       0
        DIMM_13 OK     –              M393B2G70DB0-YK0 00CE03143317593250 P1/D5    Samsung      16 GB       1600 MHz       0
        DIMM_14 OK     –              M393B2G70DB0-YK0 00CE0314331759367A P1/D6    Samsung      16 GB       1600 MHz       0
        DIMM_15 OK     –              M393B2G70DB0-YK0 00CE03143317593319 P1/D7    Samsung      16 GB       1600 MHz       0
        DIMM_2  OK     –              M393B2G70DB0-YK0 00CE031433175927A8 P0/D2    Samsung      16 GB       1600 MHz       0
        DIMM_3  OK     –              M393B2G70DB0-YK0 00CE03143317592B31 P0/D3    Samsung      16 GB       1600 MHz       0
        DIMM_4  OK     –              M393B2G70DB0-YK0 00CE03143317592B35 P0/D4    Samsung      16 GB       1600 MHz       0
        DIMM_5  OK     –              M393B2G70DB0-YK0 00CE03143317591C3C P0/D5    Samsung      16 GB       1600 MHz       0
        DIMM_6  OK     –              M393B2G70DB0-YK0 00CE031433175922C7 P0/D6    Samsung      16 GB       1600 MHz       0
        DIMM_7  OK     –              M393B2G70DB0-YK0 00CE0314331759324E P0/D7    Samsung      16 GB       1600 MHz       0
        DIMM_8  OK     –              M393B2G70DB0-YK0 00CE0314331759324B P1/D0    Samsung      16 GB       1600 MHz       0
        DIMM_9  OK     –              M393B2G70DB0-YK0 00CE0314331759331A P1/D1    Samsung      16 GB       1600 MHz       0


  • Execute the following command to monitor Power Status

[root@odanoden1 ~]# 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+1435CE00EU PS0      Present     119 watts    32.250 degree C 36.562 degree C
        Power_Supply_1  OK     –              7079395  476856Z+1435CE00F6 PS1      Present     112 watts    37.000 degree C 40.375 degree C


  • Execute the following command to monitor Network Status

[root@odanoden1 ~]# oakcli 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:62:3F:F2  yes (eth2)    46.250 degree C
        Ethernet_NIC_1 OK     –              NET1     X540    INTEL        00:10:E0:62:3F:F3  no (eth3)     46.250 degree C
        Ethernet_NIC_2 OK     –              NET2     X540    INTEL        00:10:E0:62:3F:F4  no (eth4)     51.000 degree C
        Ethernet_NIC_3 OK     –              NET3     X540    INTEL        00:10:E0:62:3F:F5  no (eth5)     51.500 degree C
        Ethernet_NIC_4 –      –              NET4     X540    INTEL        90:E2:BA:81:2B:B4  yes (eth0)    –
        Ethernet_NIC_5 –      –              NET5     X540    INTEL        90:E2:BA:81:2B:B5  yes (eth1)    –


  • Execute the following command to monitor Storage Status

[root@odanoden1 ~]# oakcli show storage
==== BEGIN STORAGE DUMP ========
Host Description: Oracle Corporation:SUN SERVER X4-2
Total number of controllers: 3
        Id         = 1
        Serial Num = 500605b008030030
        Vendor     = LSI Logic
        Model      = SGX-SAS6-EXT-Z
        FwVers     = 11.05.03.00
        strId      = mpt2sas:30:00.0

        Id         = 2
        Serial Num = 500605b00802fbc0
        Vendor     = LSI Logic
        Model      = SGX-SAS6-EXT-Z
        FwVers     = 11.05.03.00
        strId      = mpt2sas:40:00.0

        Id         = 0
        Serial Num = 500605b008071240
        Vendor     = LSI Logic
        Model      = SGX-SAS6-INT-Z
        FwVers     = 11.05.03.00
        strId      = mpt2sas:50:00.0

Total number of expanders: 2
        Id         = 1
        Serial Num = 50800200019f0002
        Vendor     = ORACLE
        Model      = DE2-24P
        FwVers     = 0018
        strId      = Primary
        WWN        = 5080020001a6b97e

        Id         = 0
        Serial Num = 50800200019f0002
        Vendor     = ORACLE
        Model      = DE2-24P
        FwVers     = 0018
        strId      = Secondary
        WWN        = 5080020001a6babe

Total number of PDs: 24
        /dev/sdl        LSI Logic         HDD  900gb slot:  0  exp:  0
        /dev/sdn        LSI Logic         HDD  900gb slot:  1  exp:  0
        /dev/sdah       LSI Logic         HDD  900gb slot:  2  exp:  0
        /dev/sdai       LSI Logic         HDD  900gb slot:  3  exp:  0
        /dev/sdaj       LSI Logic         HDD  900gb slot:  4  exp:  0
        /dev/sdak       LSI Logic         HDD  900gb slot:  5  exp:  0
        /dev/sdal       LSI Logic         HDD  900gb slot:  6  exp:  0
        /dev/sdam       LSI Logic         HDD  900gb slot:  7  exp:  0
        /dev/sdan       LSI Logic         HDD  900gb slot:  8  exp:  0
        /dev/sdao       LSI Logic         HDD  900gb slot:  9  exp:  0
        /dev/sdap       LSI Logic         HDD  900gb slot: 10  exp:  0
        /dev/sdaq       LSI Logic         HDD  900gb slot: 11  exp:  0
        /dev/sdar       LSI Logic         HDD  900gb slot: 12  exp:  0
        /dev/sdaa       LSI Logic         HDD  900gb slot: 13  exp:  0
        /dev/sdab       LSI Logic         HDD  900gb slot: 14  exp:  0
        /dev/sdac       LSI Logic         HDD  900gb slot: 15  exp:  0
        /dev/sdad       LSI Logic         HDD  900gb slot: 16  exp:  0
        /dev/sdae       LSI Logic         HDD  900gb slot: 17  exp:  0
        /dev/sdaf       LSI Logic         HDD  900gb slot: 18  exp:  0
        /dev/sdag       LSI Logic         HDD  900gb slot: 19  exp:  0
        /dev/sda        LSI Logic         SSD  200gb slot: 20  exp:  0
        /dev/sdb        LSI Logic         SSD  200gb slot: 21  exp:  0
        /dev/sdc        LSI Logic         SSD  200gb slot: 22  exp:  0
        /dev/sdd        LSI Logic         SSD  200gb slot: 23  exp:  0
==== END STORAGE DUMP =========


  • Execute the following command to monitor Shared Disk Status

[root@odanoden1 ~]# oakcli show disk
        NAME            PATH            TYPE            STATE           STATE_DETAILS

        e0_pd_00        /dev/sdl        HDD             ONLINE          Good
        e0_pd_01        /dev/sdn        HDD             ONLINE          Good
        e0_pd_02        /dev/sdah       HDD             ONLINE          Good
        e0_pd_03        /dev/sdai       HDD             ONLINE          Good
        e0_pd_04        /dev/sdaj       HDD             ONLINE          Good
        e0_pd_05        /dev/sdak       HDD             ONLINE          Good
        e0_pd_06        /dev/sdal       HDD             ONLINE          Good
        e0_pd_07        /dev/sdam       HDD             ONLINE          Good
        e0_pd_08        /dev/sdan       HDD             ONLINE          Good
        e0_pd_09        /dev/sdao       HDD             ONLINE          Good
        e0_pd_10        /dev/sdap       HDD             ONLINE          Good
        e0_pd_11        /dev/sdaq       HDD             ONLINE          Good
        e0_pd_12        /dev/sdar       HDD             ONLINE          Good
        e0_pd_13        /dev/sdaa       HDD             ONLINE          Good
        e0_pd_14        /dev/sdab       HDD             ONLINE          Good
        e0_pd_15        /dev/sdac       HDD             ONLINE          Good
        e0_pd_16        /dev/sdad       HDD             ONLINE          Good
        e0_pd_17        /dev/sdae       HDD             ONLINE          Good
        e0_pd_18        /dev/sdaf       HDD             ONLINE          Good
        e0_pd_19        /dev/sdag       HDD             ONLINE          Good
        e0_pd_20        /dev/sda        SSD             ONLINE          Good
        e0_pd_21        /dev/sdb        SSD             ONLINE          Good
        e0_pd_22        /dev/sdc        SSD             ONLINE          Good
        e0_pd_23        /dev/sdd        SSD             ONLINE          Good


  • Execute the following command to monitor ODA server enclosure

[root@odanoden1 ~]# oakcli show enclosure

        NAME        SUBSYSTEM         STATUS      METRIC

        E0_FAN0     Cooling           OK          3450 rpm
        E0_FAN1     Cooling           OK          3070 rpm
        E0_FAN2     Cooling           OK          3070 rpm
        E0_FAN3     Cooling           OK          3070 rpm
        E0_IOM0     Encl_Electronics  OK          –
        E0_IOM1     Encl_Electronics  OK          –
        E0_PSU0     Power_Supply      OK          –
        E0_PSU1     Power_Supply      OK          –
        E0_TEMP0    Amb_Temp          OK          19 C
        E0_TEMP1    Midplane_Temp     OK          27 C
        E0_TEMP2    PCM0_Inlet_Temp   OK          32 C
        E0_TEMP3    PCM0_Hotspot_Temp OK          38 C
        E0_TEMP4    PCM1_Inlet_Temp   OK          27 C
        E0_TEMP5    PCM1_Hotspot_Temp OK          36 C
        E0_TEMP6    IOM0_Temp         OK          38 C
        E0_TEMP7    IOM1_Temp         OK          45 C


Using ILOM CLI to Get the Hardware Status


  • Execute the following command to connect to ILOM and monitor Hardware Status

[root@odanoden2 ~]# ssh odanoden2-ilom
Password:

Oracle(R) Integrated Lights Out Manager

Version 3.2.8.25 r114493

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

Warning: password is set to factory default.

Warning: HTTPS certificate is set to factory default.

Hostname: odanoden2-ilom

-> show -level all -output table /SP/faultmgmt
Target                          | Property                             | Value
——————————–+————————————–+———————————————————

-> show -l all /SYS type==’Hard Disk’

 /SYS/DBP0/HDD0
    Targets:
        OK2RM
        PRSNT
        SERVICE
        STATE

    Properties:
        type = Hard Disk
        ipmi_name = HDD0

    Commands:
        cd
        show

 /SYS/DBP0/HDD1
    Targets:
        OK2RM
        PRSNT
        SERVICE
        STATE

    Properties:
        type = Hard Disk
        ipmi_name = HDD1

    Commands:
        cd
        show


Using ILOM GUI to Get the Hardware Status




Conclusion

In this article we have learned how to monitor various hardware components status on ODA nodes using oakcli and ILOM. ODA server comes with different hardware components and monitoring them is key for ODA availability.

2

During Oracle Database Appliance Deployment you can optionally configure CloudFS file system. The default mount point is /cloudfs and set to default size of 50GB. Oracle Database Appliance uses the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) for database and virtual machine files storage. ACFS can only be used to configure shared storage file system on ODA. Oracle ACFS provides both servers with concurrent access to /cloudfs shared file system. The default size of 50GB may not sufficient and must be increased to store big files for business requirement.





In this article we will demonstrate how to resize the /cloudfs file system manually using ACFS commands.


Steps to resize the /cloudfs file system


Step 1: Login to node 1 as grid user the owner of Grid Infrastructure software

[grid@odanoden1 ~]$ id
uid=1000(grid) gid=1001(oinstall) groups=1001(oinstall),1003(racoper),1004(asmdba),1005(asmoper),1006(asmadmin)

Step 2: Verify the existing size of /cloudfs. Here is my case the /cloufs is 200GB and it was resized in the past from 50GB to 200GB

[grid@odanoden1 ~]$ df -h /cloudfs
Filesystem           Size  Used Avail Use% Mounted on
/dev/asm/acfsvol-23  200G  483M  200G   1% /cloudfs

Step 3: Set the ORACLE SID to +ASM1

[grid@odanoden1 ~]$ echo $ORACLE_SID

[grid@odanoden1 ~]$ . oraenv

ORACLE_SID = [grid] ? +ASM1
The Oracle base has been set to /u01/app/grid

[grid@odanoden1 ~]$ echo $ORACLE_SID

+ASM1

Step 4: List the ACFS Mounts. Here we can see that /cloudfs volume is /dev/asm/acfsvol-23

[grid@odanoden1 ~]$ mount |grep asm
/dev/asm/acfsvol-23 on /cloudfs type acfs (rw)
/dev/asm/datastore-272 on /u01/app/oracle/oradata/datastore type acfs (rw)
/dev/asm/datastore-97 on /u02/app/oracle/oradata/datastore type acfs (rw)
/dev/asm/datastore-23 on /u01/app/oracle/fast_recovery_area/datastore type acfs (rw)

Step 5: Get the size of the volume /dev/asm/acfsvol-23

[grid@odanoden1 ~]$ /sbin/advmutil volinfo /dev/asm/acfsvol-23
Device: /dev/asm/acfsvol-23
Interface Version: 1
Size (MB): 204800
Resize Increment (MB): 64
Redundancy: high
Stripe Columns: 8
Stripe Width (KB): 1024
Disk Group: RECO
Volume: ACFSVOL
Compatible.advm: 12.1.0.2.0

Step 6: Resize the /cloudfs as follows. Here we are increasing /cloudfs by 50GB

[grid@odanoden1 ~]$ /sbin/acfsutil size +50g /cloudfs
acfsutil size: new file system size: 268435456000 (256000MB)

Step 7: Verify the new size of the volume /dev/asm/acfsvol-23

[grid@odanoden1 ~]$ /sbin/advmutil volinfo /dev/asm/acfsvol-23
Device: /dev/asm/acfsvol-23
Interface Version: 1
Size (MB): 256000
Resize Increment (MB): 64
Redundancy: high
Stripe Columns: 8
Stripe Width (KB): 1024
Disk Group: RECO
Volume: ACFSVOL
Compatible.advm: 12.1.0.2.0

Step 8: Verify the new size of /cloudfs file system

[grid@odanoden1 ~]$ df -h /cloudfs
Filesystem           Size  Used Avail Use% Mounted on
/dev/asm/acfsvol-23  250G  585M  250G   1% /cloudfs


Conclusion

In this article we have learned how to resize/increase the size of /cloudfs shared file system on ODA. The cloudfs file system is configured during the ODA deployment and it is set to 50GB which is not sufficient for storing the big files. The cloudfs is build using ACFS and it can be resized easily using ACFS commands.

0

About ODA Snapshot Database

  • ODA Snapshot Database is created using oakcli command line utility
  • ODA automates the entire snapshot database creation process
  • Snapshot Database is created by taking a snapshot of the Oracle ASM Cluster File System (ACFS) where the source data files reside
  • The Source Database can be:
    • Non-RAC
    • RAC
    • RAC One Node
  • Snapshot Database requires less time and Storage
  • No downtime for source database for creating snapshot database
  • You can create an Oracle RAC database from an Oracle RAC One Node database
  • Create snapshot database feature is not available in ODA X6 – S / M / L
  • Create snapshot database feature is planned for 12.2 ODA X6 – S / M / L  RDBMS


Prerequisites

The Source Database must meet the following requirement to create Snapshot Database

  • It shouldn’t be a Standby database
  • It shouldn’t be a Container database
  • It shouldn’t be in READ-ONLY, RESTRICTED or ONLINE BACKUP Mode
  • It must be in ARCHIVE LOG Mode
  • All datafiles should be ONLINE
  • It shouldn’t use centralized wallet with TDE
  • It should be 11.2.0.4 and above


Important Note


  • Both the Compute Nodes in ODA cluster must have system clock synchronized. The create snapshot database command may fail if the clocks are not synchronized.
  • You can’t create a RAC snapshot database from Non-RAC source database and vice versa
  • You can create Non-RAC snapshot Database from a Non-RAC Snapshot database



Courtesy Oracle

Steps to Create Snapshot Database Using oakcli utility


  • List existing databases

[root@odanode1 ~]# oakcli show databases
Name     Type       Storage   HomeName             HomeLocation                               Version
—–    ——     ——–  ————–       —————-                           ———-
orcldb   RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)
odatest  RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)


  • Make source database is ARCHIVE LOG Mode

SQL> select name, open_mode, database_role, log_mode from gv$database;

NAME      OPEN_MODE            DATABASE_ROLE    LOG_MODE
——— ——————– —————- ————
ODATEST   READ WRITE           PRIMARY          ARCHIVELOG
ODATEST   READ WRITE           PRIMARY          ARCHIVELOG

SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Disabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     53
Current log sequence           54


  • List the database files

SQL> set lines 400 pages 200
SQL> col name for a120
SQL> select name, status from v$datafile;

NAME                                                                                                                     STATUS
———————————————————————————————————————— ——-
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_system_doqhbjop_.dbf                        SYSTEM
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_sysaux_doqhbnkx_.dbf                        ONLINE
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_undotbs1_doqhbq7b_.dbf                      ONLINE
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_undotbs2_doqhbzyd_.dbf                      ONLINE
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_users_doqhc0tz_.dbf                         ONLINE
/u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_test_ffsnh1x9_.dbf                          ONLINE

6 rows selected.


  • Syntax for oakcli create command

[root@odanode1 ~]# oakcli create -h
Usage:
oakcli create {database | dbstorage | snapshotdb| dbhome | db_config_params } [<options>]
Where:
         database            – Creates the Database
         snapshotdb          – Creates the Snapshot Database
         dbhome              – Creates the Database Home
         dbstorage           – Creates Storage for a given Database
         db_config_params    – Creates the Database configuration parameter file
[root@odanode1 ~]# oakcli create snapshotdb -h
Usage:
      oakcli create snapshotdb  -db <db_name> -from <db_name>

      where:
         db_name      – Name of the database to be created.
         from         – Source database for creating  the snapshot database.


  • Execute the following command to create snapshot database

Here we are creating a snapshot database newdb from source database odatest

[root@odanode1 ~]# oakcli create snapshotdb -db newdb -from odatest
INFO: 2018-04-22 14:51:11: Please check the logfile  ‘/opt/oracle/oak/log/odanode1/tools/12.1.2.10.0/createdb_newdb_56401.log’ for more details

Please enter the ‘root’  password :
Please re-enter the ‘root’ password:

Please enter the ‘SYS’  password for the Database odatest:
Please re-enter the ‘SYS’ password:
Please select one of the following for Database Deployment  [1 .. 2] :
1    => RACONE
2    => RAC
2
The selected value is : RAC

Specify the  Database Class (1. odb-01 ‘1 core, 8 GB memory’   2. Others) [1] :
The selected value is : odb-01 ‘1 core, 8 GB memory’
……….Completed

SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
……
SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
INFO: 2018-04-22 14:54:03: Creating the SNAP Database ‘newdb’ from the source Database ‘odatest’
INFO: 2018-04-22 14:54:11: Do not perform any Structural change to Database ‘odatest’ till SNAP Database ‘newdb’ is created
INFO: 2018-04-22 14:54:31: Taking SNAP of the Database ‘odatest’
INFO: 2018-04-22 14:54:32: Successfully took  the SNAP of database: odatest
INFO: 2018-04-22 14:55:24: Creating controlfile for database: newdb
INFO: 2018-04-22 14:56:05: Successfully created the control file for the database : newdb
INFO: 2018-04-22 14:56:05: Adding log files for the second thread for the database : newdb
INFO: 2018-04-22 14:56:11: Successfully added the log files for second thread
INFO: 2018-04-22 14:56:15: Recovering the database: newdb,  snapshot time : ‘2018-04-22:14:54:32’ , until time : ‘2018-04-22:14:54:49’
INFO: 2018-04-22 14:56:17: Successfully recovered the database
INFO: 2018-04-22 14:56:17: Opening the database with resetlogs
INFO: 2018-04-22 14:56:27: Successfully opened the database after recovery
INFO: 2018-04-22 14:56:31: Setting the temporary tablespace for database : newdb
INFO: 2018-04-22 14:56:33: Successfully set the temporary tablespace for the database : newdb
INFO: 2018-04-22 14:57:35: Successfully changed the Database ID
INFO: 2018-04-22 14:58:51: Adding the Database resource to the clusterware
INFO: 2018-04-22 14:59:48: Successfully started the database
INFO: 2018-04-22 14:59:48: Updating the TNS entries for the database newdb
INFO: 2018-04-22 15:00:24: Successfully set the RMAN SNAPSHOT control file
INFO: 2018-04-22 15:00:34: Disabling the external references in the database ‘newdb’ inherited from ‘odatest’
INFO: 2018-04-22 15:00:35: Successfully disabled the external references
INFO: 2018-04-22 15:00:59: Run the SQL script ‘/u01/app/oracle/product/12.1.0.2/dbhome_1/enable_external_refs_newdb_oMj0.sql’ on the 
database ‘newdb’ to enable these external references
 Also need to restart the database after running the SQL script
SUCCESS: 2018-04-22 15:01:57: Successfully created the Database ‘newdb’ from ‘odatest’


  • List the databases

We can now see the newdb database created and it using ACFS file system

[root@odanode1 ~]# oakcli show databases
Name     Type       Storage   HomeName             HomeLocation                               Version                     
—–    ——     ——–  ————–       —————-                           ———-                  
orcldb   RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)
newdb    RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)
odatest  RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)


  • Verify the newly create snapshot database

SQL> select name, open_mode, database_role, log_mode from gv$database;

NAME      OPEN_MODE            DATABASE_ROLE    LOG_MODE
——— ——————– —————- ————
NEWDB     READ WRITE           PRIMARY          ARCHIVELOG
NEWDB     READ WRITE           PRIMARY          ARCHIVELOG

SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     2
Next log sequence to archive   3
Current log sequence           3
SQL> set lines 400 pages 200
SQL> col name for a100
SQL> select name, status from v$datafile;

NAME                                                                                                 STATUS
—————————————————————————————————- ——-
/u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_system_doqhbjop_.dbf        SYSTEM
/u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_sysaux_doqhbnkx_.dbf        ONLINE
/u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_undotbs1_doqhbq7b_.dbf      ONLINE
/u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_undotbs2_doqhbzyd_.dbf      ONLINE
/u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_users_doqhc0tz_.dbf         ONLINE
/u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_test_ffsnh1x9_.dbf          ONLINE

6 rows selected.

[root@odanode1 ~]# cd /u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile
[root@odanode1 datafile]# ls -ltr
total 3676440
-rw-r—– 1 oracle asmadmin   23076864 Apr 21 06:00 o1_mf_temp_doqhbr2n_.tmp
-rw-r—– 1 oracle asmadmin  387981312 Apr 22 14:54 o1_mf_undotbs2_doqhbzyd_.dbf
-rw-r—– 1 oracle asmadmin    5251072 Apr 22 14:54 o1_mf_users_doqhc0tz_.dbf
-rw-r—– 1 oracle asmadmin 1073750016 Apr 22 14:54 o1_mf_test_ffsnh1x9_.dbf
-rw-rw—- 1 oracle asmadmin   23076864 Apr 22 15:01 o1_mf_temp_ffspq06s_.tmp
-rw-r—– 1 oracle asmadmin  734011392 Apr 22 15:21 o1_mf_system_doqhbjop_.dbf
-rw-r—– 1 oracle asmadmin  319823872 Apr 22 15:21 o1_mf_undotbs1_doqhbq7b_.dbf
-rw-r—– 1 oracle asmadmin 1216356352 Apr 22 15:21 o1_mf_sysaux_doqhbnkx_.dbf


Conclusion

In this article we have demonstrated how to create snapshot database using oakcli. Using oakcli automates the entire snapshot database creating process. Snapshot Database is created by taking a snapshot of the Oracle ASM Cluster File System (ACFS) where the source data files reside.

0

Introduction

In my previous articles, we have learned how to Create Oracle Database Appliance Database Configuration Parameter file. 

If you want to create a database with different database configuration parameter then you must create a database configuration file with your desired parameters. You can use the ‘oakcli create db_config_params’ command to create a database configuration file. The configuration files are created under the locatoin ‘/opt/oracle/oak/install/dbconf’ with a default extension of ‘.dbconf’.

Refer to the blog post at on how to create a databsae configuration file
http://netsoftmate.blogspot.com/2018/05/oracle-database-appliance-database-configuration-file.html

In this article we will demonstrate how to create a database using custom configuration parameter file.

One can use OAKCLI or DBCA utility to create the database on ODA. But it is recommended to use OAKCLI on ODA to create the database. With OAKCLI, creating database is very easy and it is just one command.



Courtesy Oracle

Steps to Create a Database Using Configuration File


  • Login to Compute node 1 as root user and execute the following command:

[root@odanode1]# oakcli create database -db testdb -oh OraDb12102_home1 -params ayx.conf
INFO: 2018-04-23 16:13:42: Please check the logfile  ‘/opt/oracle/oak/log/odanode1/tools/12.1.2.10.0/createdb_testdb_94038.log’ for more details

Please enter the ‘root’  password :
Please re-enter the ‘root’ password:

Please enter the ‘SYSASM’  password : (During deployment we set the SYSASM password to ‘welcome1’):
Please re-enter the ‘SYSASM’ password:

Please select one of the following for Database type  [1 .. 3] :
1    => OLTP
2    => DSS
3    => In-Memory
1 –> Enter 1 for OLTP and hit return
The selected value is : OLTP
Please select one of the following for Database Deployment  [1 .. 3] :
1    => EE : Enterprise Edition
2    => RACONE
3    => RAC
3 –> Enter 3 for RAC and hit return
The selected value is : RAC

Specify the  Database Class (1. odb-01 ‘1 core, 8 GB memory’   2. Others) [1] : 2 –> Enter 2 for Others and hit return

Please select one of the following for Database Class [1 .. 9] :
1    => odb-01s  (   1 cores ,     4 GB memory)
2    =>  odb-01  (   1 cores ,     8 GB memory)
3    =>  odb-02  (   2 cores ,    16 GB memory)
4    =>  odb-04  (   4 cores ,    32 GB memory)
5    =>  odb-06  (   6 cores ,    48 GB memory)
6    =>  odb-12  (  12 cores ,    96 GB memory)
7    =>  odb-16  (  16 cores ,   128 GB memory)
8    =>  odb-20  (  20 cores ,   160 GB memory)
9    =>  odb-24  (  24 cores ,   192 GB memory)
3 –> Enter 3 for odb-02
The selected value is : odb-02  (   2 cores ,    16 GB memory)
INFO   : Logging all actions in the file /opt/oracle/oak/onecmd/tmp/odanode1-20180423161500.log and traces in the file /opt/oracle/oak/onecmd/tmp/odanode1-20180423161500.trc
INFO   : Loading the configuration file /opt/oracle/oak/onecmd/create_database.params…
INFO   : Creating the node list files…
INFO   : Setting up ssh for root…
INFO   : Setting up SSH across the Private Network…

…………Completed
INFO   : Running as root: /usr/bin/ssh -l root 192.168.16.24 /root/DoAllcmds.sh
INFO   : Background process 99086 (node: 192.168.16.24) gets done with the exit code 0
INFO   : Running as root: /usr/bin/ssh -l root 192.168.16.25 /root/DoAllcmds.sh
INFO   : Background process 99132 (node: 192.168.16.25) gets done with the exit code 0
INFO   : Setting up SSH completed successfully
INFO   : Running the command /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd –exclude=*zip –exclude=*gz –exclude=*log –exclude=*trc –exclude=*rpm to sync directory</opt/oracle/oak/onecmd> on node <192.168.16.25>
SUCCESS: Ran /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd –exclude=*zip –exclude=*gz —exclude=*log –exclude=*trc –exclude=*rpm and it returned: RC=0

……….Completed
INFO   : Did not do scp for node : odanode1
INFO   : Running as root: /usr/bin/ssh -l root odanode1 /root/DoAllcmds.sh
INFO   : Background process 99840 (node: odanode1) gets done with the exit code 0
INFO   : Running as root: /usr/bin/ssh -l root odanode2 /root/DoAllcmds.sh
INFO   : Background process 99887 (node: odanode2) gets done with the exit code 0
INFO   : Did not do scp for node : odanode1
INFO   : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161544.sh
INFO   : Background process 99960 (node: odanode1) gets done with the exit code 0
INFO   : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161544.sh
INFO   : Background process 307 (node: odanode2) gets done with the exit code 0
INFO   : Setting up SSH for user oracle…
…INFO   : checking nodes in /opt/oracle/oak/onecmd/tmp/db_nodes…

SUCCESS: All nodes in /opt/oracle/oak/onecmd/tmp/db_nodes are pingable and alive.
INFO   : Checking SSH setup for user (oracle) on nodes in /opt/oracle/oak/onecmd/tmp/db_nodes…
INFO   : Did not do scp for node : odanode1
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161609.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161609.sh
INFO   : Background process 1220 (node: odanode1) gets done with the exit code 0
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161609.sh
INFO   : Background process 1266 (node: odanode2) gets done with the exit code 0
INFO   : Setting up ACFS storage
INFO   : Did not do scp for node : odanode1
INFO   : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/acfsm_94038.sh
INFO   : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/acfsm_94038.sh
INFO   : Background process 1669 (node: odanode1) gets done with the exit code 0
INFO   : Background process 1715 (node: odanode2) gets done with the exit code 0
INFO: 2018-04-23 16:16:27: Successfully setup the storage structure for the database ‘testdb’
SUCCESS: Successfully setup ACFS storage for the database testdb
INFO   : Creating Database using DBCA…
INFO   : Did not do scp for node : odanode1
INFO   : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161627.sh
INFO   : Background process 4974 (node: odanode1) gets done with the exit code 0
INFO   : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161627.sh
INFO   : Background process 5026 (node: odanode2) gets done with the exit code 0
INFO   : Running DBCA using /opt/oracle/oak/onecmd/tmp/dbca-testdb.sh on odanode1 as oracle…
INFO   : Check output in /opt/oracle/oak/onecmd/tmp/dbca-testdb-20180423161500.log on odanode1
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/dbca-testdb.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbca-testdb.sh
         Instance testdb1 is running on node odanode1
         Instance testdb2 is running on node odanode2
INFO   : One or more Instances running on the cluster nodes.
INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl setenv database -d testdb -t ‘TZ=America/New_York’ to set DB timezone
INFO   : Running the command /u01/app/12.1.0.2/grid/bin/crsctl stat resource ora.testdb.db -p
.INFO   : Did not do scp for node : odanode1
..
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/dbupdates-testdb.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbupdates-testdb.sh
INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl stop database -d testdb
INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl start database -d testdb
INFO: 2018-04-23 16:31:42: Successfully set the RMAN SNAPSHOT control file
.INFO   : Did not do scp for node : odanode1
..
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/runDatapatch.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/runDatapatch.sh
SUCCESS: 2018-04-23 16:32:13: Successfully created the Database : testdb
INFO   : Resecuring the environment… odanode1 odanode2
INFO   : Removing the SSH setup for root…
INFO   : Running as root: /usr/bin/ssh -l root odanode1 chmod 751 /opt/oracle/oak/onecmd/tmp
INFO   : Running as root: /usr/bin/ssh -l root odanode2 chmod 751 /opt/oracle/oak/onecmd/tmp
INFO   : Running as root: /usr/bin/ssh -l root odanode2 /bin/rm -rf /root/.ssh
INFO   : Running as root: /usr/bin/ssh -l root odanode1 /bin/rm -rf /root/.ssh


Conclusion
In this article we have learned how to create a database on Oracle Database Appliance using Database Configuration parameter file. If you want to create a database with different database configuration parameter then you must create a database configuration file first with your desired parameters. Creating an Oracle Database on ODA is just one step process. OAKCLI utility takes care of everything for you to create the database.

0

When you create a database on Oracle Database Appliance (ODA) it uses a ‘default’ database configuration file which consists of a default parameters. 



The default database configuration file uses the following parameters:

[root@odanode1 ~]# oakcli show db_config_params
The available DB configuration files are :
default

[root@odanode1 ~]# oakcli show db_config_params -conf default -detail
DATABASE_BLOCK_SIZE       =>    8192
DATABASE_LANGUAGE         =>    AMERICAN
DATABASE_CHARACTERSET     =>    AL32UTF8
DATABASE_TERRITORY        =>    AMERICA
COMPONENT_LANGUAGES       =>    en
NLS_NCHAR_CHARACTERSET    =>    AL16UTF16

If you want to create a database with different database configuration parameter then you must create a database configuration file with your desired parameters. You can use the ‘oakcli create db_config_params’ command to create a database configuration file. The configuration files are created under the locatoin ‘/opt/oracle/oak/install/dbconf’ with a default extension of ‘.dbconf’.

In this article we will demonstrate how to create a database configuration file.

Steps to generate/create a database configuration file

Step 1: List the Database Configuration files

[root@odanode1 ~]# oakcli show db_config_params
The available DB configuration files are :
default

Step 2: Create Database Configuration file

[root@odanode1 dumpfiles]# oakcli create db_config_params -conf newdbconf
Please select one of the following for Database Block Size  [1 .. 4] :
1    => 4096
2    => 8192
3    => 16384
4    => 32768
2    –> Enter the value. Here I entered 2 for 8k block size
The selected value is : 8192

Specify the  Database Language (1. AMERICAN 2. Others) [1] : 1 –> Here I entered 1 for AMERICAN database language
The selected value is : AMERICAN

Specify the  Database Characterset (1. AL32UTF8 2. Others) [1] : 2 –> Enter 2 for Other Characterset

Please select one of the following for Database Characterset [0 .. 10] :
0    => Others
1    => AL32UTF8
2    => AR8ADOS710
3    => AR8ADOS720
4    => AR8APTEC715
5    => AR8APTEC715T
6    => AR8ARABICMACS
7    => AR8ASMO8X
8    => AR8HPARABIC8T
9    => AR8ISO8859P6
10    => AR8MSWIN1256

<<Hit enter to display more characterset>>

Please select one of the following for Database Characterset  [0 .. 21] :
11    => AR8MUSSAD768
12    => AR8MUSSAD768T
13    => AR8NAFITHA711
14    => AR8NAFITHA711T
15    => AR8NAFITHA721
16    => AR8NAFITHA721T
17    => AR8SAKHR706
18    => AR8SAKHR707
19    => AR8SAKHR707T
20    => AZ8ISO8859P9E
21    => BG8MSWIN

<<Hit enter to display more characterset>>

Please select one of the following for Database Characterset  [0 .. 32] :
22    => BG8PC437S
23    => BLT8CP921
24    => BLT8ISO8859P13
25    => BLT8MSWIN1257
26    => BLT8PC775
27    => BN8BSCII
28    => CDN8PC863
29    => CEL8ISO8859P14
30    => CL8ISO8859P5
31    => CL8ISOIR111
32    => CL8KOI8R

<<Hit enter to display more characterset>>

Please select one of the following for Database Characterset  [0 .. 43] :
33    => CL8KOI8U
34    => CL8MACCYRILLICS
35    => CL8MSWIN1251
36    => EE8ISO8859P2
37    => EE8MACCES
38    => EE8MACCROATIANS
39    => EE8MSWIN1250
40    => EE8PC852
41    => EL8DEC
42    => EL8ISO8859P7
43    => EL8MACGREEKS

<<Hit enter to display more characterset>>

Please select one of the following for Database Characterset  [0 .. 54] :
44    => EL8MSWIN1253
45    => EL8PC437S
46    => EL8PC851
47    => EL8PC869
48    => ET8MSWIN923
49    => HU8ABMOD
50    => HU8CWI2
51    => IN8ISCII
52    => IS8PC861
53    => IW8ISO8859P8
54    => IW8MACHEBREWS

<<Hit enter to display more characterset>>

Please select one of the following for Database Characterset  [0 .. 65] :
55    => IW8MSWIN1255
56    => IW8PC1507
57    => JA16EUC
58    => JA16EUCTILDE
59    => JA16SJIS
60    => JA16SJISTILDE
61    => JA16VMS
62    => KO16KSC5601
63    => KO16KSCCS
64    => KO16MSWIN949
65    => LA8ISO6937

<<Hit enter to display more characterset>>

Please select one of the following for Database Characterset  [0 .. 76] :
66    => LA8PASSPORT
67    => LT8MSWIN921
68    => LT8PC772
69    => LT8PC774
70    => LV8PC1117
71    => LV8PC8LR
72    => LV8RST104090
73    => N8PC865
74    => NE8ISO8859P10
75    => NEE8ISO8859P4
76    => RU8BESTA

<<Hit enter to display more characterset>>

Please select one of the following for Database Characterset  [0 .. 87] :
77    => RU8PC855
78    => RU8PC866
79    => SE8ISO8859P3
80    => TH8MACTHAIS
81    => TH8TISASCII
82    => TR8DEC
83    => TR8MACTURKISHS
84    => TR8MSWIN1254
85    => TR8PC857
86    => US8PC437
87    => UTF8

<<Hit enter to display more characterset>>

Please select one of the following for Database Characterset  [0 .. 98] :
88    => VN8MSWIN1258
89    => VN8VN3
90    => WE8DEC
91    => WE8DG
92    => WE8ISO8859P1
93    => WE8ISO8859P15
94    => WE8ISO8859P9
95    => WE8MACROMAN8S
96    => WE8MSWIN1252
97    => WE8NCR4970
98    => WE8NEXTSTEP
96 –> Enter 96 to select WE8MSWIN1252 as characterset
The selected value is : WE8MSWIN1252

Specify the  Database Territory (1. AMERICA 2. Others) [1] : –> Here I entered 1 for AMERICA database Territory
The selected value is : AMERICA

Specify the  Component Language (1. en 2. Others) [1] : –> Here I entered 1 for en Component Language
The selected value is : en

Please select one of the following for NLS Characterset  [1 .. 2] :
1    => AL16UTF16
2    => UTF8
1    –> Here I entered 1 for AL16UTF16 NLS Characterset
The selected value is : AL16UTF16

Successfully generated the Database parameter file ‘newdbconf’

Step 3: Verify the configuration file is created

[root@odanode1 ~]# oakcli show db_config_params
The available DB configuration files are :
newdbconf
default

Step 4: List the parameters for newly created configuration file

[root@odanode1 ~]# oakcli show db_config_params -conf newdbconf -detail
DATABASE_BLOCK_SIZE       =>    8192
DATABASE_LANGUAGE         =>    AMERICAN
DATABASE_CHARACTERSET     =>    WE8MSWIN1252
DATABASE_TERRITORY        =>    AMERICA
COMPONENT_LANGUAGES       =>    en
NLS_NCHAR_CHARACTERSET    =>    AL16UTF16


Conclusion

In this article we have learned how to create a database configuration file with the desired parameters. The Default database configuration file parameters may not be applicable for all the databases. You can use the ‘oakcli create db_config_params’ command to create a database configuration file.

0

You want to drop a database on Oracle Database Appliance (ODA) that is no more required or used. Use the “oakcli delete database” command to delete a database from ODA.



In this article we will demonstrate how to delete a database on Oracle Database Appliance.

Steps to Delete Database on ODA

Step 1: List the database currently running on ODA

[root@odanode01 ~]# oakcli show databases
Name     Type       Storage   HomeName             HomeLocation                               Version                     
—–    ——     ——–  ————–       —————-                           ———-                  
newdb    RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)
odatest  RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)

Step 2: Get the syntax to delete the database

[root@odanode01 ~]# oakcli delete database -h
Usage:
        oakcli delete database  -db  <db_name>

     where:
      db_name      –    name of the database  to be deleted

Step 3: Execute the “oakcli delete database” command to delete the database

[root@odanode01 ~]# oakcli delete database -db newdb
INFO: 2018-04-22 15:28:56: Look at the log file ‘/opt/oracle/oak/log/odanode01/tools/12.1.2.10.0/deletedatabase_newdb_39297.log’ for 

more details

Please enter the ‘root’  password :
Please re-enter the ‘root’ password:

Please enter the ‘SYS’  password :
Please re-enter the ‘SYS’ password:
INFO: 2018-04-22 15:29:30: Setting up SSH
…………Completed
SUCCESS: Ran /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd –exclude=*zip –exclude=*gz —

exclude=*log –exclude=*trc –exclude=*rpm and it returned: RC=0

……….Completed
……
SUCCESS: All nodes in /opt/oracle/oak/onecmd/tmp/db_nodes are pingable and alive.
INFO: 2018-04-22 15:31:06: SSH has been successfully established
INFO: 2018-04-22 15:33:04: Successfully deleted the database ‘newdb’
INFO: 2018-04-22 15:33:09: Attempting to cleanup the SNAP entries for the database: newdb
INFO: 2018-04-22 15:33:09: Successfully deleted the SNAP entries

Step 4: Verify that the database is dropped

[root@odanode01 ~]# oakcli show databases
Name     Type       Storage   HomeName             HomeLocation                                Version                     
—–    ——     ——–  ————–       —————-                            ———-                  
odatest  RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1   12.1.0.2.170117(24732082,24828633)

Conclusion

In this article we have learned how to Delete database on Oracle Database Appliance (ODA). Using oakcli delete database database is extremely simple and easy to drop a database which otherwise required to use database utilities like DBCA or SQL command to drop the database.

0

PREVIOUS POSTSPage 1 of 3NO NEW POSTS

[contact-form-7 id=”4973″ title=”Lead”]