Oracle Database Appliance (ODA) Installation, Configuration and Deployment Steps

The Oracle Database Appliance saves time and money by simplifying deployment, maintenance, and support of database solutions for organizations of every size. Optimized for the world’s most popular database–Oracle Database–it integrates software, compute, storage, and network resources to deliver database services for a wide range of custom and packaged online transaction processing (OLTP), in-memory database, and data warehousing applications. All hardware and software components are engineered and supported by Oracle, offering customers a reliable and secure system with built-in automation and best practices. In addition to accelerating the time to value when deploying database solutions, the Oracle Database Appliance offers flexible Oracle Database licensing options and reduces operational expenses associated with maintenance and support.

All Oracle Database Appliance Models are optimized to run Oracle Database Standard Edition and Enterprise Edition. The Oracle Database Appliance X7-2S and Oracle Database Appliance X7-2M are ideal for customers who require single instance databases on an engineered platform. The Oracle Database Appliance X7-2-HA is ideal for customers who are looking to consolidate multiple databases onto a highly available and scalable-engineered platform.

In this blog post, I want to write step by step documentation for Oracle Database Appliance (ODA) Installation, Configuration and Deployment. The installation of Oracle Database Appliance (ODA) is very easy and done by the ODA configuration manager. After filled out all the necessary information in the ODA configuration manager screens, you will click the “install” button, and the installation progress will start. It is 33 steps and each of them executes some commands/scripts in the background.  You can see all the detailed status of each steps in the ODA configuration manager screen.

ODA is x86 based engineered system. The minimum SW release for ODA X6-2 is version The Oracle Database Appliance X6-2 can only be deployed as a Non-Virtualized (Bare Metal) Configuration. The Bare Metal image will be installed by the factory. For the latest ISO images, check My Oracle Support, Patches & Updates tab. The ODA X6-2 images are listed under patches for Oracle Database Appliance Software, and clearly marked for ODA X6-2. Since you will not know which version is installed on the ODA before proceeding with the installation it is recommended to download all the patches that might be needed to save a lot of download time whilst at the customer site. It is strongly recommended that you access MOS Document ID 888888.1 which contains links to the above patches. The downloaded files can be copied onto a USB stick for access by the system.


Download the following files (where xxxxxx represents the current version
number e.g. 121280 for ODA SW
• – ODA ISO Bare Metal Restore
file – only be necessary if a complete re-image is required.
• – (two parts 1of 2 and 2of 2) GI
Clone files. This file is required for deployment.
• – ODA Patch Bundle
Depending on the version of the database that the customer would like to
provision, you can download both of them, or either one of the following two
• – (two parts 1of 2 and 2of 2)
These clone files are for creating a new database home running DBBP. (DBBP – Database Bundle Patch).
These clone files are for creating a new database home running DBBP. (DBBP – Database Bundle Patch).

If you are using a KVM or directly attached monitor and keyboard, the ILOM may be configured using the web configurator. This will save the task of connecting to the serial port to configure the ILOM net management port manually. When the SP initially boots it will attempt to obtain an IP address from a DHCP server. You must have a cable connected to the SP Network Management port (NET MGT). If DHCP server is available you can connect to the SP via network (ssh or https), otherwise you have to connect to the SP via a serial line (see below) and specify a static Ethernet configuration.

Obtain the Service Processor IP address from one of the following locations. Record the IP address for future reference:
• The system BIOS setup screen.
• Command-line interface – connect to serial port via terminal device (such as a laptop). Log into the SP via CLI and display the IP address.

This will be the address assigned by the DHCP server.

Advanced → BMC Network Configuration →Current Ipv4 address in BMC


Power on the server. There are several ways to do this:
• Press the power-on button on the front panel (with clock symbol).
• From the CLI on the SP issue: start /SYS

-> start /SYS

• On the ILOM GUI expand the Host Management link in the left column then select Power Control. In the Main panel you will see Host is currently off Select Power On and then save.

If using CLI: gain host console access. To stop the host console press ESC followed by ( i.e. opening round bracket. To leave the secure shell: exit

From server’s SP:

-> start /HOST/console

At the OS login prompt:User root with welcome1 as password.


To set a static IP address for the SP using the CLI and a serial line connection perform the steps below.

Log in to the ILOM SP.

User = root
Pwd = changeme

login as: root
Using keyboard-interactive authentication.
Oracle(R) Integrated Lights Out Manager
Version r112010
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: oda-x6-m-ilom

-> ls




-> cd SP

-> ls


check_physical_presence = true
current_hostname = oda-x6-m-ilom
hostname = oda-x6-m-ilom
reset_to_defaults = none
system_contact = (none)
system_description = ORACLE SERVER X6-2, ILOM v3.2.7.26, r112010
system_identifier = Oracle Database Appliance X6-2 Medium 1639NM10PK
system_location = (none)


-> cd network

-> ls


commitpending = (Cannot show property)
dhcp_clientid = none
dhcp_server_ip = none
ipaddress =
ipdiscovery = static
ipgateway =
ipnetmask =
macaddress = 00:10:E0:BD:C8:20
managementport = MGMT
outofbandmacaddress = 00:10:E0:BD:C8:20
pendingipaddress =
pendingipdiscovery = static
pendingipgateway =
pendingipnetmask =
pendingmanagementport = MGMT
pendingvlan_id = (none)
sidebandmacaddress = 00:10:E0:BD:C8:21
state = ipv4-only
vlan_id = (none)


-> set pendingipdiscovery = static
-> set pendingipaddress =
-> set pendingipgateway =
-> set pendingipnetmask =
-> set commitpending = true
-> set state = enabled
-> ls

start /SYS
Press the power-on button on the front pane

Note that the commitpending command requires several seconds to complete. It is also possible to configure ILOM network settings via the system BIOS in the Advanced Menu tab under BMC Network.

Verify the changes.

-> show /SP/network


To set a static IP address for the SP using the GUI perform the steps below.

1- Determine the current IP address of the SP using one of the methods described at the top of this page. For this to work IP assignment by DHCP must have succeeded!

2- Connect to the SP via a web browser running on a remote system (Firefox or Internet Explorer).

3- Log into the web GUI using the default user name & password.
User = root
Pwd = changeme

4- Select ILOM Administration and then Connectivity to display information about the current network configuration of your ILOM. The network configuration can be modified then press the Save button.


Run the command configure-firstnet. Respond to the prompts to configure the public network interface. Also provide the netmask and gateway IP address.

[root@oak ~]# configure-firstnet
Select the Interface to configure the network on (btbond1 btbond2
sfpbond1) [btbond1]:
Configure DHCP on btbond1 (yes/no) [no]:
INFO: You have chosen Static configuration
Enter the IP address to configure :
Enter the Netmask address to configure :
Enter the Gateway address to configure[] :
INFO: Plumbing the IPs now
INFO: Restarting the network
Shutting down interface btbond1: [ OK ]
Shutting down interface btbond2: [ OK ]
Shutting down interface p3p1: [ OK ]
Shutting down interface p3p2: [ OK ]
Shutting down interface sfpbond1: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface btbond1: Determining if ip address is already in use for device btbond1…
[ OK ]
Bringing up interface btbond2: [ OK ]
Bringing up interface sfpbond1: [ OK ]

To verify the current ODA system version, run the following command:

[root@oak ~]# cat /opt/oracle/oak/pkgrepos/System/VERSION

To re-image with a newer version, you will require the Bare Metal ISO image. The file can be unzipped on a Linux.
# unzip


Now that you have an active network interface, you can use scp/ftp/filezilla to transfer the following files to the server node. –> RDBMS –> RDBMS –> grid –> grid
p23530609_121280_Linux-x86-64 –> OS image


[root@oak ~]# unzip
[root@oak ~]# unzip
[root@oak A]# ls
oda-sm- README.html
[root@oak A]# cat oda-sm- oda-sm- >

Apply the update:

[root@oak A]# update-image –image-files
Unpacking will take some time, Please wait…


There are 2 database versions that can be provisioned:
• DBBP (database bundle patch)
• DBPSU (database PSU)
Depending on the version of the database that you would like to provision, you can install both, or either one of them. The below example is for, which only has one file and did not need to be concatenated like the GI patch. If the patch comes with two files, they must first need to be concatenated before installing with the image-update command:

[root@oak ~]# unzip
[root@oak ~]# update-image –image-files
Unpacking will take some time, Please wait…


You are now ready to deploy the Oracle Database Appliance. Using the Chrome or IE browser, enter the following URL:

Username: oda-admin
Password (default):welcome1

2- On the first screen, click on Create Appliance

3- Mandatory fields have  star sign *. The hostname can contain alphanumeric characters and dashes (-). The hostname cannot exceed 63 characters. The password must begin with an alpha character and cannot contain quotation marks. The password cannot exceed 30 characters.

4- Write Client Access Network inf.

5- Database information details

6- If Yes, ASR User Name and Password is required. If Yes to HTTP Proxy, the Proxy Server Name and Proxy Port is required. If Yes to HTTP Proxy Requires Authentication, Proxy User Name and Proxy Password is required. Click NO and Submit button.

7- Select Yes

8- Provisioning job will submitted. Click the link to display job details.

9-  Provisioning service creation steps. To monitor deployment progress, you can monitor the dcs-agent.log file:

# tail -f /opt/oracle/dcs/log/dcs-agent.log

If there is an error during deployment, we will see it in the dcs-agent.log file

It is ready to use.

[root@veridata ~]# su – oracle
oracle@ veridata /home/oracle>
oracle@ veridata /home/oracle>
oracle@ veridata /home/oracle> sqlplus / as sysdba

SQL*Plus: Release Production on Tue Feb 20 22:22:08 2018

Copyright (c) 1982, 2014, Oracle. All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release – 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics
and Real Application Testing options

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

——— ———— ——————–

SQL> select name from v$datafile;


[root@veridata ~]# su – grid
grid@ veridata /home/grid>
grid@ veridata /home/grid> asmcmd lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED NORMAL N 512 4096 4194304 4894016 4879956 0 2434880 0 Y DATA/
MOUNTED NORMAL N 512 4096 4194304 1231176 1218588 0 604180 0 N RECO/
grid@ veridata /home/grid>

[root@veridata ~]# /opt/oracle/dcs/bin/odacli list-databases

ID DB Name DB Version CDB Class Shape Storage Status
—————————————- ———- ——————– ———- ——– ——– ———- ———-
e2292352-b538-4d79-8a70-e1cc9a0c18b7 VERIDATA false OLTP odb6 ASM Configured

[root@veridata ~]# /opt/oracle/dcs/bin/odacli describe-appliance

Appliance Information
ID: 71358f0e-d684-44f0-9e74-d8436e0a6778
Platform: OdaliteM
Data Disk Count: 2
CPU Core Count: 20
Created: February 20, 2018 9:39:24 PM EET

System Information
Name: veridata
Domain Name:
Time Zone: Europe/Istanbul
DB Edition: EE
DNS Servers:
NTP Servers:

Disk Group Information
DG Name Redundancy Percentage
————————- ————————- ————
Data Normal 80
Reco Normal 20

[root@veridata ~]#


How to Move From the Standard Edition to the Enterprise Edition?

If you are using the Standard Edition of the Oracle Database and want to move to the Enterprise Edition, then complete the following steps:

Ensure that the release number of your Standard Edition server software is the same release as the Enterprise Edition server software.

For example, if your Standard Edition server software is release, then you should upgrade to release of the Enterprise Edition.

  • Shut down your database.

If your operating system is Windows, then stop all Oracle services, including the OracleServiceSID Oracle service, where SID is the instance name.

  • Deinstall the Standard Edition server software.
  • Install the Enterprise Edition server software using the Oracle Universal Installer.
  • Select the same Oracle home that was used for the de-installed Standard Edition. During the installation, be sure to select the Enterprise Edition.
  • When prompted, choose Software Only from the Database Configuration screen.
  • Start up your database.

Your database is now upgraded to the Enterprise Edition.
You can verify it from the banner:

SQL> select banner from v$version;

Oracle Database 12c Enterprise Edition Release – 64bit Production
PL/SQL Release – Production
CORE Production
TNS for Linux: Version – Production
NLSRTL Version – Production

RMAN Restore from ASM to Non ASM in 12c Take a long time

Any RMAN command at the mount state which involves Non ASM location can take more time.

RMAN-03090: Starting restore at 2015-11-09 15:01:53
RMAN-08030: allocated channel: ORA_AUX_DISK_1
RMAN-08500: channel ORA_AUX_DISK_1: SID=1 device type=DISK

RMAN-08021: channel ORA_AUX_DISK_1: restoring control file
RMAN-08180: channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
RMAN-08505: output file name=/oradata/C12102/controlfile/control01.ctl

RMAN-03091: Finished restore at 2015-11-09 15:01:55

Actual Restore starts after 20 min

RMAN-03090: Starting restore at 2015-11-09 15:21:59
RMAN-12016: using channel ORA_AUX_DISK_1
RMAN-12016: using channel ORA_AUX_DISK_2
RMAN-12016: using channel ORA_AUX_DISK_3
RMAN-12016: using channel ORA_AUX_DISK_4

Alert log shows the below messages during the above time when there seems to be No Activity by RMAN after restoring the Controlfile

WARNING: failed to start ASMB (ASM instance not found)

Errors in file /opt/oracle/diag/rdbms/c12102/C12102/trace/C12102_asmb_24847.trc:
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Synchronization Service
WARNING: ASMB exiting with error

This problem due to unpublished BUG 19503821

You must apply patch number 19503821 to solve this problem.

ORA-01180 and ORA-01110 during RMAN Restore

The below error occured while doing a full database restore to the test system. I also checked that I restored most recent control file and the backup sets are cataloged.I tried the process two times but still the same error.

Starting restore at 10-OCT-17
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
using channel ORA_DISK_6
using channel ORA_DISK_7
using channel ORA_DISK_8

creating datafile file number=1 name=/DATA/alfa/datafile/system01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/10/2017 01:08:29
ORA-01180: can not create datafile 1
ORA-01110: data file 1: ‘+DATAC1/ALFA/DATAFILE/system.319.922730217’

When I searched Oracle Metalink, found below documents.

RMAN restore fails with ORA-01180: can not create datafile 1 (Doc ID 1265151.1)
RMAN restore of database fails with ORA-01180: Cannot create datafile 1 (Doc ID 1573040.1)

I reset the database to the previous incarnation and run the restore & recovery again.

SQL> select INCARNATION#, RESETLOGS_TIME from v$database_incarnation order by RESETLOGS_TIME desc;

———— ———
2 22-MAY-17
1 16-SEP-16

rman target /

RMAN> reset database to incarnation 1;

RMAN> restore database;

When a BACKUP controlfile is used with a Flash Recovery Area defined, an  implicit crosscheck of the FRA is done and any files found belonging to the database are catalog’d to the controlfile.

Archivelogs created after a resetlogs operation will cause a new incarnation to be registered in the controlfile.

The new incarnations meant the database backup needed for restore  no longer belonged to the current incarnation.

After reseting the database to the previous incarnation, restore operation completed successfully.

You can also remove the Flash Recovery Area  parameters from the spfile/pfile  and use instead log_archive_dest_1.

How To Manually Install Oracle OEM 13c Agent?

1- We need to download the agent software from OMS Server for the platform which we will install. Login with sysman.

[oracle@isu13c bin]$ ./emcli login -username=sysman
Enter password :

Login successful

[oracle@isu13c bin]$ ./emcli sync
Synchronized successfully

2- Get the supported platform list

[oracle@isu13c bin]$ ./emcli get_supported_platforms
Version =
Platform = Linux x86-64
Platforms list displayed successfully.

3- Download the agent software

[oracle@isu13c bin]$ ./emcli get_agentimage -destination=/tmp/agentinstaller -platform=”Linux x86-64″
=== Partition Detail ===
Space free : 53 GB
Space required : 1 GB
Check the logs at /u01/app/oracle/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2018-04-25_12-12-30-PM.log
Downloading /tmp/agentinstaller/
File saved as /tmp/agentinstaller/
Downloading /tmp/agentinstaller/
File saved as /tmp/agentinstaller/
Downloading /tmp/agentinstaller/unzip
File saved as /tmp/agentinstaller/unzip
Executing command: /tmp/agentinstaller/unzip /tmp/agentinstaller/ -d /tmp/agentinstaller
Exit status is:0
Agent Image Download completed successfully.

4- let me copy the software to target server and unzip.

scp oracle@


5- Let me install the agent

mkdir /u01/app/oracle/agent
./ AGENT_BASE_DIR=/u01/app/oracle/agent \
-force \
-ignorePrereqs \
-invPtrLoc /etc/oraInst.loc \
OMS_HOST=isu13c \
AGENT_INSTANCE_HOME=/u01/app/oracle/agent/agent_inst \

After installation, don’t forget to execute script as root user.

Our agent is running and ready.

/u01/app/oracle/agent/agent_13. status agent
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
Agent Version :
OMS Version :
Protocol Version :
Agent Home : /u01/app/oracle/agent/agent_inst
Agent Log Directory : /u01/app/oracle/agent/agent_inst/sysman/log
Agent Binaries : /u01/app/oracle/agent/agent_13.
Core JAR Location : /u01/app/oracle/agent/agent_13.
Agent Process ID : 64876
Parent Process ID : 64751
Agent URL : https://oracledrs:3872/emd/main/
Local Agent URL in NAT : https://oracledrs:3872/emd/main/
Repository URL : https://isu13c.localdomain:4903/empbs/upload
Started at : 2017-11-21 09:51:57
Started by user : oracle
Operating System : Linux version 4.1.12-37.4.1.el6uek.x86_64 (amd64)
Number of Targets : 7
Last Reload : (none)
Last successful upload : 2018-04-25 13:22:43
Last attempted upload : 2018-04-25 13:22:43
Total Megabytes of XML files uploaded so far : 172.1
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 59.73%
Collection Status : Collections enabled
Heartbeat Status : Ok
Last attempted heartbeat to OMS : 2018-04-25 13:23:53
Last successful heartbeat to OMS : 2018-04-25 13:23:53
Next scheduled heartbeat to OMS : 2018-04-25 13:24:53

Agent is Running and Ready