Monday 28 August 2017

Oracle Database Appliance: Create Database

Introduction

In my previous articles, we have learned how to Deploy an Oracle Database Appliance. 
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.
Let's see how to quickly create a database on ODA.

Steps to create Database on ODA


  • List the existing RDBMS Oracle Homes. With OAKCLI it is very easy to get the Oracle Homes Printed.

[root@odanode1 ~]# oakcli show dbhomes
Oracle Home Name Oracle Home version Home Location
---------------- ------------------- ------------
OraDb12102_home1 /u01/app/oracle/product/12.1.0.2/dbhome_1

You can also use the following option to get the Oracle HOME Name.

[root@odanode1 ~]# cd /u01/app/oraInventory/ContentsXML
[root@odanode1 ContentsXML]# grep -i "HOME NAME" inventory.xml
<HOME NAME="OraGrid12102" LOC="/u01/app/12.1.0.2/grid" TYPE="O" IDX="1" CRS="true">
<HOME NAME="OraDb12102_home1" LOC="/u01/app/oracle/product/12.1.0.2/dbhome_1" TYPE="O" IDX="2">

Here we have only Oracle HOME name OraDb12102_home1. We will be using this name to create the database.


  • Using OAKCLI to create database. Let's see the options available.

Display options that can be used with OAKCLI

[root@odanode1 ~]# oakcli -h
Usage:  oakcli show       - Shows disk, diskgroup, expander, controller, server, processor, memory, power, cooling, network, enclosure, storage, version, fs, raidsyncstatus, dbhomes, 

dbstorage, databases, db_config_params, core_config_key, env_hw, ASR
        oakcli configure  - Configures the Network or ASR or additional Net
        oakcli apply      - Applies the core_config_key
        oakcli locate     - Locates a disk
        oakcli deploy     - Deploys the Database Appliance
        oakcli update     - Updates the Database Appliance
        oakcli validate   - Validates the Database Appliance
        oakcli manage     - Manages the OAK repository, diagcollect etc.,
        oakcli unpack     - Unpack the given package to OAK repository
        oakcli copy       - Copies the deployment config file
        oakcli upgrade    - Upgrades database
        oakcli stordiag   - Run storage diagnostic tool on both Nodes
        oakcli test       - Test ASR
        oakcli orachk     - Performs configuration settings check on ODA
        oakcli create     - Creates Database, DB storage, snapshotdb, dbhome, db_config_params file
        oakcli delete     - Deletes Database, DB storage, dbhome, db_config_params file
        oakcli modify     - Performs modify opeartions on Database
        oakcli resize     - Resizes DB storage

Display options that can be used with OAKCLI CREATE

[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

Display options that can be used with OAKCLI CREATE DATABASE 

[root@odanode1 ~]# oakcli create database -h
Usage:
      oakcli create database  -db <db_name> [[[-oh <home>] | [-version <version>]]  [-params <params_file>] [-cdb]]

      where:
         db_name      - Name of the database to be created.
         home         - Existing oracle home for creating the database. By default we create a new database home.
         version      - Database Version information for creating the database home. [ex. 11.2.0.2.7] If not provided create the database home from latest available bits.
         params_file  - Name of the db_config_parameter file [This file can be created using using 'oakcli create db_config_params'].
                        If not provided, create the database using  default configuration file
         cdb          - Creates this database as a container database


  • Create Database as follows

When you execute the create database command, it will prompt you the following details:

    • root password
    • SYSASM password
    • Databsae Type (OLTP, DSS or In-Memory)
    • Database Deployment (EE, RACONE or RAC)
    • Database Class

[root@odanode1 ~]# oakcli create database -db odatest -oh OraDb12102_home1
INFO: 2017-07-04 12:02:24: Please check the logfile  '/opt/oracle/oak/log/odanode1/tools/12.1.2.10.0/createdb_odatest_71669.log' for more details
INFO: 2017-07-04 12:02:26: Database parameter file is not provided. Will be using default parameters for DB creation

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
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
The selected value is : RAC

Specify the  Database Class (1. odb-01 '1 core, 8 GB memory'   2. Others) [1] : 2

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
The selected value is : odb-02  (   2 cores ,    16 GB memory)
INFO   : Logging all actions in the file /opt/oracle/oak/onecmd/tmp/odanode1-20170704120410.log and traces in the file /opt/oracle/oak/onecmd/tmp/odanode1-20170704120410.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   : Running as root: /usr/bin/ssh -l root 192.168.16.25 /root/DoAllcmds.sh
INFO   : Background process 77365 (node: 192.168.16.24) gets done with the exit code 0
INFO   : Background process 77412 (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   : Running as root: /usr/bin/ssh -l root odanode2 /root/DoAllcmds.sh
INFO   : Background process 78082 (node: odanode1) gets done with the exit code 0
INFO   : Background process 78130 (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-20170704120453.sh
INFO   : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120453.sh
INFO   : Background process 78210 (node: odanode1) gets done with the exit code 0
INFO   : Background process 78256 (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-20170704120518.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/DoAllcmds-20170704120518.sh
INFO   : Background process 79851 (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-20170704120518.sh
INFO   : Background process 79897 (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_71669.sh
INFO   : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/acfsm_71669.sh
INFO   : Background process 80312 (node: odanode1) gets done with the exit code 0
INFO   : Background process 80360 (node: odanode2) gets done with the exit code 0
INFO: 2017-07-04 12:05:36: Successfully setup the storage structure for the database 'odatest'
SUCCESS: Successfully setup ACFS storage for the database odatest
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-20170704120536.sh
INFO   : Background process 83721 (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-20170704120536.sh
INFO   : Background process 83768 (node: odanode2) gets done with the exit code 0
INFO   : Running DBCA using /opt/oracle/oak/onecmd/tmp/dbca-odatest.sh on odanode1 as oracle...
INFO   : Check output in /opt/oracle/oak/onecmd/tmp/dbca-odatest-20170704120410.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-odatest.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbca-odatest.sh
         Instance odatest1 is running on node odanode1
         Instance odatest2 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  odatest -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.odatest.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-odatesth
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbupdates-odatest.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 -ddatest
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 -odatest
INFO: 2017-07-04 12:24:56: 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: 2017-07-04 12:25:27: Successfully created the Database : odatest
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

********THIS COMPLETES THE DATABASE CREATION PROCESS***********


  • Validate Database


SQL> select * from v$version;

BANNER                                                                               CON_ID
-------------------------------------------------------------------------------- ----------
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production              0
PL/SQL Release 12.1.0.2.0 - Production                                                    0
CORE    12.1.0.2.0      Production                                                                0
TNS for Linux: Version 12.1.0.2.0 - Production                                            0
NLSRTL Version 12.1.0.2.0 - Production                                                    0

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

NAME      OPEN_MODE            DATABASE_ROLE    LOG_MODE     FLASHBACK_ON
--------- -------------------- ---------------- ------------ ------------------
ODATEST   READ WRITE           PRIMARY          ARCHIVELOG   NO


[oracle@odanode1 ~]$ srvctl status database -d odatest
Instance odatest1 is running on node odanode1
Instance odatest2 is running on node odanode2

[oracle@odanode1 ~]$ srvctl config database -d odatest
Database unique name: odatest
Database name: odatest
Oracle home: /u01/app/oracle/product/12.1.0.2/dbhome_1
Oracle user: oracle
Spfile: /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/odatest/spfileodatest.ora
Password file: /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/odatest/orapwodatest
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups:
Mount point paths: /u01/app/oracle/oradata/datastore,/u02/app/oracle/oradata/datastore,/u01/app/oracle/fast_recovery_area/datastore
Services:
Type: RAC
Start concurrency:
Stop concurrency:
OSDBA group: dba
OSOPER group: racoper
Database instances: odatest1,odatest2
Configured nodes: odanode1,odanode2
Database is administrator managed

SQL> set lines 150
SQL> select name from v$datafile;

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

SQL> select name from v$controlfile;

NAME
----------------------------------------------------------------------------------------------------------------
/u01/app/oracle/oradata/datastore/odatest/ODATEST/controlfile/o1_mf_doqhbb49_.ctl

SQL> select member from v$logfile;

MEMBER
----------------------------------------------------------------------------------------------------------------
/u01/app/oracle/oradata/datastore/odatest/ODATEST/onlinelog/o1_mf_1_doqhbb7f_.log
/u01/app/oracle/oradata/datastore/odatest/ODATEST/onlinelog/o1_mf_2_doqhbf18_.log
/u01/app/oracle/oradata/datastore/odatest/ODATEST/onlinelog/o1_mf_3_doqhxbg9_.log
/u01/app/oracle/oradata/datastore/odatest/ODATEST/onlinelog/o1_mf_4_doqhxg9m_.log


Conclusion
In this article we have learned how to create a database on Oracle Database Appliance. Creating an Oracle Database on ODA is just one step process. OAKCLI utility takes care of everything for you to create the database. You can also use the DBCA utility to create the database but it is recommended to use OAKCLI utility to create database.

Oracle Database Appliance Bare Metal Setup In A Nutshell

Introduction


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 ODA deployment.



Pre-Deployment Steps


  • 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 administartor 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 patches

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


Here I am downloading the patches for ODA Bundle patch version 12.1.0.11


    • OS ISO image (2.1.2.11) - If you want to reimage ODA to latest ODA software version.

12999313 Oracle Database Appliance 12.1.2.11.0 Bare Metal ISO Image.
Choose the correct version when downloading the patch.

  • ODA Bundle Patch (26080564) - These patches are required to update the firmware post reimaging ODA


File name: p26080564_1212110_Linux-x86-64_1of2.zip & p26080564_1212110_Linux-x86-64_2of2.zip

  • End-User Bundle


12978712 - Oracle Database Appliance 12.1.2.11.0 End User Bundle (GI+RDBMS)
Choose the correct version when downloading the patch.



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 OS ISO image perform the complete reimage of both the nodes - Optional
  • 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
- Repeat the step on ODA node 1

  • Copy and unpack the ODA Bundle Patch (node 0 and 1) and End-user Bundle GI/RDBMS (node 0) patches to ODA under /tmp

- Copy to /tmp or file system where there is more stapce
- cd /tmp
- /opt/oracle/oak/bin/oakcli unpack -package /tmp/filename.zip

  • VNC Configuration and Connection - Optional

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

  • Complete the ODA bare metal deployment

/opt/oracle/oak/bin/oakcli deploy

  • Update the firmware (ILOM, BIOS and so on)

oakcli update –patch 12.1.2.10.0 --verify
oakcli update -patch 12.1.2.10.0 --server -local (on both nodes)
oakcli update -patch 12.1.2.10.0 --storage

  • Update RDBMS homes

oakcli update -patch  12.1.2.11.0  --database or
oakcli update -patch  12.1.2.11.0  --database --local



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 Bare Metal Deployment. It is very important to consider the deployment steps carefully to avoid issues. ODA deployment is simple and very easy to perform.

Saturday 12 August 2017

Oracle Database Appliance (ODA) Bare Metal Deployment

Introduction


ODA Congigurator can be run in offline or online mode.



Offline: Use the standalone ODA configurator to create an offline deployment plan and validate your network settings before the actual deployment. You can download the ODA configurator for offline deployment at:



http://www.oracle.com/technetwork/database/database-appliance/overview/oda-configurator-1928685.html



Online: You can configure your system at the time of deployment. In that case, you can use the online ODA Configurator which is part of the base Oracle Database Appliance software.



In this article I will demonstrate how to perform a Bare Metal Deployment online.




Before starting the Deployment, make sure the following tasks were completed:


  • ODA cabling is completed
  • ODA is Powered up
  • Gather the Network Information
  • Assign IP address to ILOM
  • Reimage ODA nodes - Optional
  • Configure initial network
  • Copy ODA software and unpack
  • Update firmware


Steps to perform a Bare Metal ODA Deployment


  • Connect to first node of ODA using VNC (or you can also use Web ILOM)


  • Start ODA Deployment using the "oakcli deploy" command.

oakcli command is located under /opt/oracle/oak/bin/oakcli

  • On the welcome screen click next


  • On Configuration Type screen, you have options to choose from:

Typical
Custom
SAP Application


Here I am selecting "Custom" as it will give more flexibility to provide more information.

Click Next


Note: If you have create a configuration file already in offline mode. Use the Browse button to select it now.



  • On System Information screen, enter the following details:

"System Name"
This will be your prefix for Hostname, Interface, SCAN name and ILOM


"Region" and "Timezone"

Select appropriate


"Database Backup Location" 

You have "Internal" and "External" option. If you choose "Internal" the space will be used from DATA and RECO disk groups. Oracle will internally size DATA and RECO ASM disk group to 40% and 60% respectively.


"Root password"

Enter root password and confirm root password.


"Disk Group Redundancy"

Select HIGH or Normal


"Accelerator Disk Group"

select REDO or FLASH


Click Next



  • On Generic Network screen, enter:

Enter "Domain name" to be used
Check the box if no DNS Server available.
If you are using DNS and NTP server enter thier IPs.


Click Next



  • On Public Network Screen:

Enter the Node0 and Node1 IP, VIPs, SCAN IPs, Netmask and Gateway IP.
Select bond0 for interface. This is the only choice.
Enter ILOM IPs for ILOM0 and ILOM1, Netmask and Gateway IP


Click Next



  • On Other Network Screen, enter:

Enter the IPs for for Node0 and Node1 for net1, else click next to continue.


Click Next



  • On Database Information screen, enter:

If you don't want to create an intial database uncheck the box and click next


If you wish to create an initial database, check the box and fill the required information.

"Database name"
Name for the database to be created


"Is Container Database"

Choose true if you want to create a container database else false to create a regular (non-container database)


"Database Type"

Choose from OLTP, DSS or In-Memory.


"Database Class"

Choose from the 10 different database template that comes with ODA


"Database Deployment"

Choose from RAC, RAC One Node or Enter Edition (Standalone)


"Database Files on Flash Storage"

If you wish to store database in Flash disk select true


Click Next



  • On Database Information Screen, Select:

Database Language, Block Size, Characterset, Territory and National Character set.


Click Next



  • On ASR Configuration Screen, Select:

"Configure Internal Oracle ASR"
If you wish to configure ASR on ODA Server and enert the Proxy server name, port number and MOS credentails


"Configure External Oracle AS"

If you wish to configure ASR on a separate server. Enter the ASR Manager Hostname or IP and port number.


Select SNMP 2 for configuring ASR



Note: If you don't select to configure ASR now you can configure ASR post ODA deployment using oakcli commands



Click Next



  • On CloudFS Information Screen:

You can choose to configure ACFS file system called /cloudfs.


Click Next



  • On the summary page:

Click Save button to save to store the configuration in a text file.




  • Click Install to begin the Deployment




  • Click Show Details button to check the Deployment Log.






  • Click Next


  • Click Close to complete the Deployment




Conclusion



In this article we have learned how to Deploy an Oracle Database Appliance Bare Metal setup in online mode. ODA Configurator can be run in offline or online mode. You can use the online ODA Configurator which is part of the base Oracle Database Appliance software. In online mode, You configure the system at the time of deployment. The ODA setup deployment process is very simple and it takes roughly around 1 hour to 1 hour 30 minutes.


ODA : Update Firmware On ODA Post Reimage


Introduction

In my previous article we have learned how to Reimage an Oracle Database Appliance to 12.1.2.10. It is important to note that the Reimage process doesn't update the firmware (BIOS, ILOM, Local and Shared HDD) on ODA nodes. The below screen shot show the output post Re-imaging an ODA X4-2. There is nothing wrong with reimage process and it is completely expected as the reimage process doesn't update the firmware.


We can see that the ILOM, BIOS, HDD _Local and HDD_Shared are not up-to-date.




In this article I will demonstrate how to update the firmware post ODA re-imaging.

Prerequisites

  1. Root user access to ODA ILOM
  2. Download the ODA Bundle Patch using patch 25499210

The following steps should be followed to update the firmware on ODA post reimaging.
  1. Configure initial network
  2. Copy ODA software
  3. Update firmware

Configure initial network


The "oakcli configure firstnet" command is used to configure an initial network on Oracle Database Appliance (ODA) that enables you to copy ODA End User Bundle software to ODA server. oakcli configure firstnet allows you to establish the network interfaces for the Oracle Database Appliance upon first usage. Once you have completed the reimaging of ODA servers, you should log onto the one of the node ILOM console and do the initial configuration of the Oracle Database Appliance network using the command firstnet. The bond0 interface is configured when execute the firstnet utility. Before running firstnet, ensure that you allocated IP addresses and verify that their entries in the DNS have been completed. 

Steps to Execute firstnet utility

Connect to the ILOM console using browser or putty to configure the initial IP address for the node you are connected to.

Once you execute the firstnet utility it will ask you for the IP address, Netmask and Gateway IPs.



Once the network interfaces have been configured, you need to test them by using the ping command on the node.  Additionally, you can test the network by pinging the configured node from your remote client.

[root@oak1 ~]# ping 10.10.17.11
PING 172.16.202.71 (10.10.17.11) 56(84) bytes of data.
64 bytes from 10.10.17.11: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 10.10.17.11: icmp_seq=2 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=3 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=4 ttl=64 time=0.006 ms
64 bytes from 10.10.17.11: icmp_seq=5 ttl=64 time=0.005 ms

--- 172.16.202.71 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4544ms
rtt min/avg/max/mdev = 0.005/0.010/0.027/0.009 ms

[root@oak1 ~]# ifconfig
bond0     Link encap:Ethernet  HWaddr 00:10:E0:62:3F:F2
          inet addr:10.10.17.11  Bcast:10.10.17.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:762 (762.0 b)  TX bytes:546 (546.0 b)

bond1     Link encap:Ethernet  HWaddr 00:10:E0:62:3F:F4
          UP BROADCAST MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth0      Link encap:Ethernet  HWaddr 90:E2:BA:81:2B:B4
          inet addr:192.168.16.24  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:138257 errors:0 dropped:0 overruns:0 frame:0
          TX packets:138436 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11200490 (10.6 MiB)  TX bytes:11134648 (10.6 MiB)

eth1      Link encap:Ethernet  HWaddr 90:E2:BA:81:2B:B5
          inet addr:192.168.17.24  Bcast:192.168.17.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:138217 errors:0 dropped:0 overruns:0 frame:0
          TX packets:138434 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11197894 (10.6 MiB)  TX bytes:11134800 (10.6 MiB)

eth2      Link encap:Ethernet  HWaddr 00:10:E0:62:3F:F2
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:762 (762.0 b)  TX bytes:546 (546.0 b)

eth3      Link encap:Ethernet  HWaddr 00:10:E0:62:3F:F2
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth4      Link encap:Ethernet  HWaddr 00:10:E0:62:3F:F4
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth5      Link encap:Ethernet  HWaddr 00:10:E0:62:3F:F4
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:512371 errors:0 dropped:0 overruns:0 frame:0
          TX packets:512371 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:38908072 (37.1 MiB)  TX bytes:38908072 (37.1 MiB)

Repeat the steps on ODA node 2.

Copy Patches to ODA
Once the initial network is configured you can now copy the ODA patch to ODA node 1 under /tmp.







Update firmware

The Reimage process doesn't update the firmware (BIOS, ILOM, Local and Shared HDD). The below screen shows that the firware is not updated on both the nodes.




Let's update the firmware on ODA nodes.
  • Copy the patches from node 1 to node 2.
  • Unpack the patches using oakcli command as shown on both the nodes
  • Update the firmware on node 1. At the end of the firmware update the node is rebooted.

  • Once the node 1 comes back, verify the firmware is updated.
  • Update the firmware on node 2. At the end of the firmware update the node is rebooted.

  •  Once the node 2 comes back, verify the firmware is updated.
  • Update the firmware on Shared Storage. Both the ODA nodes rebooted at the end of storage update.

  • Now verify the firmware on both the nodes.


We can now see that the firware is update on both the nodes.

Conclusion
 

Reimaging an Oracle Database Appliance doesn't update the firmware (BIOS, ILOM, Local and Shared HDD). So we have to download the ODA patches and update the firmware post reimage manually. You must run the update command on both the ODA nodes and once for storage from node 1. It is fairly straight forward to update the firmware.

Comparing Oracle Database Appliance X8-2 Model Family

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