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

Introduction:


Oracle Database Console that existed in Oracle Database 10g and 11g is now dead in Oracle Database 12c. Oracle Database 12cR1 gave birth to a completely new GUI interface known as Oracle Enterprise Manager Database Express or simply EM Express. EM Express replaces the Database Console that existed in Oracle 10g and 11g.


Enterprise Manager Database Express is a lightweight browser-based tool for managing Oracle Database 12c is well suitable for common DBA tasks such as Tablespace Management, User Management and comprehensive performance diagnostics and tuning. You can’t perform a lot of DBA activities using EM Express as you were able do it using Database Console.


EM Express is built inside the Oracle Database and uses internal infrastructure components, such as XDB and SQL*Net. The database must be open in order to use EM Express as EM Express is built inside the database. 


If you selected the option “Configure Enterprise Manager (EM) database express”, the EM Express will be configured as part of the database creation process. Once the database is created, DBCA displays a success message with the EM Express URL. The default EM Export https port number is 5500.


Database Express is used to manage a single database and it is automatically installed when you create a database using DBCA.


The URL to connect to EM Express has the following format “https://<hostname>:5500/em” for Example, “https://dm01db01.netsoftmate.com:5500/em”



Important Note: 
  • EM Express cannot create a CDB 
  • EM Express can be configured at both root and PDB level, with each container using a different HTTP/HTTPS port
  • EM Express can view any PDB as if it were a standalone database (non-CDB)
  • EM Express cannot stop and start the database and listener
  • EM Express is RAC aware 
  • You can grant users read-only access so that they can view the UI but not make any changes
SQL> grant EM_EXPRESS_BASIC to <user>;
  • EM is supported on Enterprise Edition, Standard Edition and Express Edition
  • Diagnostic Pack and Tuning Pack features are not available in Standard Edition and Express Edition
  • Basic EM Express features are available free of cost
  • You need Diagnostic Pack and Tuning Pack license to use performance diagnostics and tuning features


In this article I will demonstrate how to connect to EM Express and use different EM Express features.


  • Connecting to EM Express

Enter the EM Express URL into the web browser and confirm the security warning. Here I am using Chrome for accessing EM Express.



https://dm01db01.netsoftmate.com:5500/em



Enter the credentials to login to the EM Express console.




This is the EM Express home page. We can see there are 4 different tabs that can be used for different purposes.


  • EM Express Tab

Let’s look at the each Tab and the options available in each table.



Configuration Tab list the different parameters, database properties,  feature usage and Memory configuration




Storage Tab can be used for Tablespace Management, Undo, Redo Log & Archive Log Management and Control File Management


Under Security Tab you manage Users, Roles & Profiles


Performance Tab is the important tab that is used to Manage the Database Performance


To check base feature usage, navigate to Configuration Tab and click on Database Feature Usage. The below page shows all the database feature usage.


This is the Memory Management page



  • How to create a new tablespace using EM Express
Navigate to Configuration tab and click Tablespaces. Select Create Tablespace and follow the instructions below to create a new tablespace



Enter Name, select tablespace type, bigfile and status. Click Next



Check if you want to use OMF, Enter number of Datafiles, Size, Auto Extend, Increment and Max Size. Click Next


Select Block Size and Extent Allocation. Click Next


Choose the logging option. Click Next


Select space management and Compress type.


Click on on Show SQL if you want to capture the SQL statement so you can use it to create tablespaces manually. Click Ok to create tablespace


The confirmation screen show that he tablespace is create successfully


Verify the tablespace creation


Check all tablespace in the database


Performance Hub Page


Click on the activity tab to check the current database acitivty


Click on ADDM tab to check the ADDM recommendation


Click on SQL Tuning Advisor under Performance tab


Enable Automatic SQL Tuning Advisor


Request being processed


Click ok to complete


User page displaying all the database users. You can also create a new user using the Create User button on the page.




Conclusion


In this article we have learned about Oracle Enterprise Manager Database Express 12c or simply EM Express. EM Express replaced the Database console that was existed in Oracle database 10g and 11g. It is a lightweight browser-based tool for managing Oracle Database 12c is well suitable for common DBA tasks.



0

Introduction


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:

  • 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.

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.

  • Oracle Database Appliance X7-2S (single-instance database)
  • Oracle Database Appliance X7-2M (single-instance database)
  • Oracle Database Appliance X7-2 HA 


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.
3



Introduction



Exadata Database Machine or simply known as Exadata is:


  • An Engineered System
  • A pre-configured combination of balanced Hardware and unique software
  • A unique platform for running Oracle Databases
  • Consists of Compute Grid, Storage Grid and Network Grid
  • A fully integrated platform for Oracle Database
  • Ideal for Database Consolidation platform
  • It provides High Availability and High Performance for all types of Workloads



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



Exadata Hardware Components



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


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



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



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



Different Exadata Hardware components failures



  • Battery Failure on Exadata X4-2



  • Flash Card Failure on Exadata V2



  • Flash Card Failure on Exadata X5-2



  • Flash Card Failure on Exadata V6-2



  • Hard Disk Failure on Exadata V2



  • Hard Disk Failure on Exadata X2-2



  • Hard Disk Failure on Exadata X4-2



  • Hard Disk Failure on Exadata X5-2



  • IB Port Failure on Exadata X2-2



  • IB Port Failure on Exadata X4-2



  • IB Port Failure on Exadata X5-2



  • Physical Memory (DIMM) Failure on Exadata X5-2



  • Physical Memory (DIMM) Failure on Exadata X6-2



  • Processor Failure on Exadata X4-2



  • Processor Failure on Exadata X5-2



  • Power Supply Failure on Exadata V2



  • Power Supply Failure on Exadata X4-2



  • Power Supply Failure on Exadata X5-2


  • Power Supply Failure on Exadata X6-2





Conclusion



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



0

In this article, I would like to demonstrate how to create a shell script to perform an RMAN SCN based backup and execute in background. 


Tip: Scripting is a powerful tool to automate and execute jobs in background.

Below example shows how to perform an SCN based RMAN Incremental backup using 4 Channels when we perform Roll-forward of Physical Standby.

Step 1. Make a RMAN command file with RMAN Commands.



Create a cmd script and include RMAN backup command.


Get current SCN of Physical Standby and select a location to store RMAN backup files.

SQL> column BYTES current_scn 99999999999999
SQL> select current_scn from v$database;
CURRENT_SCN
———–
7707430599033

$ cd /orac01/orclprd_standby
$ vi SCN_based_backup.cmd
run
{
allocate channel t1 type disk ;
allocate channel t2 type disk ;
allocate channel t3 type disk ;
allocate channel t4 type disk ;
backup incremental from scn 7707430599033 database format ‘/ora01/orclprd_standby/stnd_backp_%U.bak’;
release channel t1;
release channel t2;
release channel t3;
release channel t4;
}

Step 2. Prepare shell script and include above .cmd RMAN


$ vi rman_scn_based_incremental_bkup_for_standby.ksh
#!/bin/ksh
export ORACLE_SID=orclprd
export ORACLE_HOME=/u01/app/oracle/product/11.2.0.4/db
export PATH=$PATH1:$ORACLE_HOME/bin
rman target /   msglog /ora01/orclprd_standby/rman_SCN_backup.log cmdfile=/ora01/orclprd/RMAN_SCN_backup_from_primary/SCN_ based_backup.cmd

Step 3. Change permissions of above shell scripts


$ chmod 755 rman_scn_based_incremental_bkup_for_standby

Step 4. Start RMAN using nohup to run in background


$ nohup ./rman_scn_based_incremental_bkup_for_standby &


Monitor RMAN log

$ tail -300f /ora01/orclprd_standby/rman_SCN_backup.log


Conclusion:  In this article we have learned how to perform RMAN SCN based backup using Unix shell script. Incremental backup are very useful such as rolling forward an standby database.



Author : Hameed
0

Uncategorized
Background:
 
Cyber-crimes and the annual costs incurred by business are on the rise year over year. In 2017, the average cost of a data breach alone in North America is $1.3 million for enterprises and $117,000 for small and medium-sized businesses (SMBs), according to a report from Kaspersky Lab.
 
So what can an organization do to reduce their risk? The most common response is to recommend technology overkill, and mostly that is address with a balance of intelligent security tools, governance practices and focused training of team members.
 
In this article, I will explain about most important and vital plan to keep in-place that will help organizations and security incident response teams (SIRT) to be well prepared and organized for handling security incidents in an effective way.
 
Security Incident Response Plan:
 
Mostly referred as SIRP is a plan developed, reviewed and implemented by Security In-charge to handle security incidents.
 
SIRP plan on high-level should include:
1.       Security Incident Response Plan Policy
2.       Security Incident Response Plan Testing Procedure
 
It is commonly known that a well-defined, published and acknowledged policy will be hard for employee to deny wrong doing when you have signed papers showing review of existing policies.
 
So let’s take a start from Policy.
 
Security Incident Response Plan
 
 
Following section is not uniform and may differ organization to organization based on their own format of Policy drafting.
 
  • Executive Statement
  • Purpose
  • Scope
  • Cancellation or Expiration
  • Roles & Responsibilities

 
 
 
 
 
SIRP policy should include but not limited to:
 
  • Service or Product description
  • Contact Information (contact information for dedicated team members to be available during business / non-business hours should an incident occur and escalation be required)
  • Triage
  • Identified Mitigations & Testing
  • Mitigation & Remediation Timelines

 
 
 
 
 
SIRP Policy must also provide reference to below documents;
 
  • Security Incident Response Plan & Testing Procedure
  • Security Incident Identification & Severity

 
 
 
Conclusion:
 
In this article we understood importance of security incident handling and how to start with policy document. I will soon publish part 2 in series of SIRP articles that will give insight about preparing SIRP Testing Procedure which will be the actual plan for preparing security teams and carrying out SIRP test.
 
 
0

Oracle Released Exadata Storage Software version 18.1.0.0.0 on October 2nd 2017.
Patch (25342756) for Storage server software and Infiniband Switch software For more details review the MOS note 2288392.1 ESS version 18.1.0.0.0 supports the following Oracle Database software releases:
  • 12.2.0.1.0
  • 12.1.0.2.0
  • 12.1.0.1.0
  • 11.2.0.4.0
  • 11.2.0.3.0
Exadata 18.1.0.0.0 Software and Image files for upgrade are:
  • Patch 25342756 – Storage server software (18.1.0.0.0.170915.1) and InfiniBand switch software (2.2.7-1)
  • Patch 26829586 – Database server bare metal / domU ULN ISO image (18.1.0.0.0.170915.1)
  • Patch 26829591 – Database server dom0 ULN OVM channel ISO image (18.1.0.0.0.170915.1)

0

Another Exadata Storage Software 18c update released!! Oracle Released Exadata Storage Software version 18.1.1.0.0 on October 26th 2017. Earlier release was ESS version 18.1.0.0.0 on October 2nd 2017. – Patch (26875767) for Storage server software and Infiniband Switch software For more details review the MOS “Exadata 18.1.1.0.0 release and patch (26875767) (Doc ID 2311786.1)” ESS version 18.1.1.0.0 supports the following Oracle Database software releases: – 12.2.0.1.0 – 12.1.0.2.0 – 12.1.0.1.0 – 11.2.0.4.0 – 11.2.0.3.0 Exadata 18.1.1.0.0 Software and Image files for upgrade are: – Patch 26875767 – Storage server software (18.1.1.0.0.171018) and InfiniBand switch software (2.2.7-1) – Patch 26923500 – Database server bare metal / domU ULN exadata_dbserver_18.1.1.0.0_x86_64_base OL6 channel ISO image (18.1.1.0.0.171018) – Patch 26923501 – Database server dom0 ULN exadata_dbserver_dom0_18.1.1.0.0_x86_64_base OVM channel ISO image (18.1.1.0.0.171018)
0

Introduction

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

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


  • To identify faulty hardware, execute the ILOM following command:

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


-> Session closed
Disconnected

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

You can also check for hardware failures using Web ILOM

Steps to Clear a hardware fault post hardware replacement:


  • Identify the hardware fault

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


-> Session closed
Disconnected


  • Connect to problematic Compute node ILOM

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

Oracle(R) Integrated Lights Out Manager

Version 3.2.8.24 r114580

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

Warning: HTTPS certificate is set to factory default.

Hostname: dm01db01-ilom

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


  • Execute the following command to clear the fault

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


  • Verify the fault is cleared

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

No Faulty hardware found.

Verify from Web ILOM


  • Exit from ILOM

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

Conclusion

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

0

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.

0

Introduction

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.

You can deploy ODA in one of the following model:

  • Bare Metal Deployment
  • Virtualized Platform Deployment

By default, ODA ships with the latest version of Bare Metal Operating System. To deploy Oracle Database Appliance Virtualized platform, you must re-image ODA using Virtualized OS ISO image.

To identify ODA deployment type, execute the following command:

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

The output shows that it is a Bare Metal deployment. If you see the string VM-Dom0, it means that is a Virtualized platform.

Deploying an Oracle Database Appliance consists of several basic steps. It is very important to plan the ODA deployment properly before performing the actual steps, this helps you to avoid issues during deployment and save time.

In this article I will layout the high level steps required to perform a successful Oracle Database Appliance Virtualized Platform deployment.




Pre-Deployment Steps

  • Decide the type of Deployment
    • Bare Metal (BM) or Virtualized Platform (VM)

  • Gather Network details.
    • Fill the ODA Pre-Install Checklist form with details like, Cluster name, Hostname, IP Address etc.
    • Allocate IPs and Submit DNS and firewall requests
    • Other network details required are, Domain name, DNS, NTP.
    • Work with your Network administrator to gather all these details.

  • Oracle Appliance Manager Configurator
Build the deployment configuration files using the Oracle Appliance Manager Configurator utility in offline mode.This is an optional step which will save time to complete the deployment and perform network validation before deployment.

Read more on ODA configuration at: http://netsoftmate.blogspot.in/2017/06/oracle-database-appliance-oda.html

  • Download ODA Virtualized Platform patches

Download the below patches from MOS note 888888.1
Read the MOS note 888888.1 carefully before downloading the patches.

As of writing the latest Virtualized OS ISO image and latest ODA_BASE is 12.1.2.12.0

    • ODA Virtualized Platform Patches – Choose the correct release from the drop down  menu.

Patch 16186163 – Oracle Database Appliance VM ISO Image. (DOM0)  
Patch 16186172 – Oracle Database Appliance VM Template (ODA_BASE)

Note: Oracle Grid Infrastructure and Oracle Database software are installed by deploying ODA_BASE

Deployment Steps

  • Receive Oracle Database Appliance delivery at Data Center
  • Unpack Oracle Database Appliance box
  • Read the Manually carefully that comes with ODA box
  • Mount ODA components as per guidelines
  • Connect the Power and Network Cables. Read the ODA Setup poster for your model, for example: Setup Poster X6-2 HA
  • Power On the PSU
  • Power On the Systems. Turn on the power to  Storage shelf first and the power on the ODA Node 0 and Node 1.
  • Configure and Setup Oracle ILOM Configuration.

ILOM configuration via Serial port (Doc ID 1395445.1)
How to Setup ILOM (Doc ID 1393191.1)

  • Using Virtualized OS ISO image perform the complete reimage of both the nodes – MUST

  • Validate the cable connections to the Storage shelf

# oakcli validate -c storageTopology

Note: If you see any errors or warning, connect the cables correctly. DO NOT ignore the error or the warning.

  • Network Configuration –  Configure firstnet
    • Connect to ODA node 0 using ILOM and run firstnet

# /opt/oracle/oak/bin/oakcli configure firstnet

    • Verify you can ping node 0 and node 1
    • Respond to the prompts (Domain Name, DNS Server, Hostname, Network, IP address and Gateway

  • Copy the downloaded ODA_BASE zip files to DOM0 under /OVS
    • Copy to /OVS or file system where there is more stapce

  • Unzip the zip files copied under /OVS
# cd /OVS
# unzip unzip p16186172_1212120_Linux-x86-64_1of3.zip
# unzip unzip p16186172_1212120_Linux-x86-64_2of3.zip
# unzip unzip p16186172_1212120_Linux-x86-64_3of3.zip


unzipping the zip files will create two files, oda_base_12.1.2.12.gz01, oda_base_12.1.2.12.gz02 and oda_base_12.1.2.12.gz03

  • Merge or concatenate the above 2 files as below:
# cat oda_base_12.1.2.12.gz01 oda_base_12.1.2.12.gz02 oda_base_12.1.2.12.gz03 > oda_base_12.1.2.12.tar.gz

This file name will be used in next step.

  • Deploy ODA_BASE
    • From Node0 (oak1-dom0), deploy oda_base by executing the following command as root user

# /opt/oracle/oak/bin/oakcli deploy oda_base

Enter the file name with full path /OVS/oda_base_12.1.2.12.tar.gz when prompted

    • Select the number of cores for ODA_BASE and network for ODA_BASE

  • Verify the ODA_BASE domain

# xm list
# /opt/oracle/oak/bin/oakcli show oda_base

  • VNC Configuration and Connection

To Deploy ODA you need GUI interface, to do this you make use of VNC server to connect with ODA and open GUI interface.
You can also connect to Web ILOM and execute xstart to start VNC

Connect to oda_base using vncviewer with <oak1-dom0>:5900

  • Complete the ODA Virtualized Platform deployment
    • Connect to ILOM as root user and start the X window.
    • Execute the following command to complete ODA Deployment

# /opt/oracle/oak/bin/oakcli deploy



  • Verify the ODA Deployment

# oakcli show env_hw
# oakcli show version -detail

Post Deployment and Cleanup

  • Validate ODA Deployment

# /opt/oracle/oak/bin/oakcli show version -detail
# crsctl status res -t
# /opt/oracle/oak/bin/oakcli validate -c storagetopology
# oakcli show dbhomes -detail
# oakcli validate -d
# oakcli validate -c OSDiskStorage
# oakcli validate -c SharedStorage
# oakcli validate -c SystemComponents
# oakcli validate -c NetworkComponents
# oakcli validate -c DiskCalibration

  • ODA Redeploy or Cleanup – Optional

To perform a redeploy for the Oracle Database Appliance is a very simple task and is executed with the cleanupDeploy.pl script

# /opt/oracle/oak/onecmd/cleanupDeploy.pl

Once this cleanupDeploy.pl script completes, you can rerun the deployment process using the Oracle Appliance Manager utility discussed earlier.


Conclusion

In this article we have learned the steps required to perform an Oracle Database Appliance Virtualized Platform Deployment. It is very important to consider the deployment steps carefully to avoid issues. By default, ODA ships with the latest version of Bare Metal Operating System. To deploy Oracle Database Appliance Virtualized platform, you must re-image ODA using Virtualized OS ISO image.

0

PREVIOUS POSTSPage 9 of 18NEXT POSTS

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