Oracle EBS R12.2.6 on Virtual Box Pt2

If you followed my previous post Oracle E-Business Suite R12.2.6 on Virtual Box you will have already downloaded the 19 required zip files, and be ready to go.

Ok, change directory to the location of the downloaded files, unzip and concatenate them into a single OVA file using the following:

$ unzip ‘V*.zip’

$ cat Oracle-E-Business-Suite-12.2.6_VISION_INSTALL.ova.* > Oracle-E-Business-Suite-12.2.6_VISION_INSTALL.ova

Getting started – Virtual Box

Start Virtual Box and navigate to File -> Import Appliance

Click on ‘Expert Mode’ and edit the ‘Virtual Disk Image’ path to a location with adequate space (~500GB), in this example I am using my Samsung Portable SSD T1 1TB dive mounted at ‘/Volumes/Samsung_T1’


Click ‘Import’, go to lunch or grab a coffee and watch the progress bar if you prefer, the remaining time will re-calulate periodically.


Once complete, start up your new Oracle EBS R12.2.6 VM from within Oracle VirtualBox

Oracle E-Business Suite R12.2.6


The initial boot will prompt you to change the ‘root’, ‘oracle’ and ‘applmgr’ passwords, the process will continue to start and configure an Oracle database called ‘EBSDB’.


Use ifconfig -a’ to determine your VM’s IP address from you VirtualBox console before using SSH from your host to connect using your preferred client.

Add the IP address to your local ‘/etc/host’ file so your browser can resolve your Oracle EBS VISION sandbox environment. e.g.

# apps

Change directory to ‘/u01/install/APPS/scripts’ to access the database and application stop / start scripts and run ‘’ and ‘’



[oracle@apps scripts]$ ./
Logfile: /u01/install/APPS/12.1.0/appsutil/log/EBSDB_apps/addlnctl.txt

You are running version 120.4

Starting listener process EBSDB …

LSNRCTL for Linux: Version – Production on 15-AUG-2017 07:42:19

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

Starting /u01/install/APPS/12.1.0/bin/tnslsnr: please wait…

TNSLSNR for Linux: Version – Production
System parameter file is /u01/install/APPS/12.1.0/network/admin/EBSDB_apps/listener.ora
Log messages written to /u01/install/APPS/12.1.0/admin/EBSDB_apps/diag/tnslsnr/apps/ebsdb/alert/log.xml

Version TNSLSNR for Linux: Version – Production
Start Date 15-AUG-2017 07:42:19
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
Listener Parameter File /u01/install/APPS/12.1.0/network/admin/EBSDB_apps/listener.ora
Listener Log File /u01/install/APPS/12.1.0/admin/EBSDB_apps/diag/tnslsnr/apps/ebsdb/alert/log.xml
Listening Endpoints Summary…
Services Summary…
Service “EBSDB” has 1 instance(s).
Instance “EBSDB”, status UNKNOWN, has 1 handler(s) for this service…
The command completed successfully exiting with status 0 check the logfile /u01/install/APPS/12.1.0/appsutil/log/EBSDB_apps/addlnctl.txt for more information …

You are running version 120.1

Starting the database EBSDB …

SQL*Plus: Release Production on Tue Aug 15 07:42:19 2017

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

Connected to an idle instance.
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.

Total System Global Area 2147483648 bytes
Fixed Size 2926472 bytes
Variable Size 1308625016 bytes
Database Buffers 822083584 bytes
Redo Buffers 13848576 bytes
Database mounted.
Database opened.
Disconnected from Oracle Database 12c Enterprise Edition Release – 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options exiting with status 0

[oracle@apps scripts]$ ./ 
Starting the Oracle E-Business Suite Application Tier Services
You are running version 120.24.12020000.11

All enabled services for this node are started. Exiting with status 0 check the logfile /u01/install/APPS/fs1/inst/apps/EBSDB_apps/logs/appl/admin/log/adstrtal.log for more information …

Before you can logon you will need to enable SYSADMIN and the Demo accounts, Oracle have provided scripts to do this  e.g.

[oracle@apps scripts]$ ./

This script will let you set a new password for the SYSADMIN EBS Applications User, the default password most likely was “sysadmin”, so pick a different one now.

Enter new password for SYSADMIN:
Re-enter password for SYSADMIN:
Changing password for SYSADMIN
Log filename : L7583909.log
Report filename : O7583909.out
[oracle@apps scripts]$

[oracle@apps scripts]$ ./

Enter a new password for the EBS Applications Users, the default password
most likely was “welcome”, so pick a different one now…

Enter new password for DEMO users:
Re-enter password for DEMO users:
Setting password for DEMO users…
Log filename : L7583911.log

[oracle@apps scripts]$

Oracle EBS R12 Dashboard

You should now be able to logon as ‘SYSADMIN’ or explore your Oracle EBS R12.2.6 VISION sandbox environment using the Demo users (see below) and the password defined above at:


Sales Dashboard – LJONES

Oracle E-Business Suite R12.2.5 Fresh Install – Part III

Oracle EBS R12.2.5 Upgrade

In Part I of my Oracle R12.2.5 Fresh Install walkthrough I described the prepatory steps for the install.

In Part II we shared details on how to install Oracle EBS using the latest R12.2.5 media including Oracle 12cR1.

In this Blog post I walk provide details of how to upgrade your EBS environment from R12.2.0 to R12.2.5.

Current Configuration

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

SQL> select release_name from apps.fnd_product_groups;

R12.2.5 Upgrade Process

If you have access to refer to Oracle E-Business Suite Releases 12.2.5 Readme (Doc ID 1983050.1)

Apply Consolidated Seed Table Patch

Stop all Application services other than the WebLogic AdminServer on the run file system.

$ ./ apps/apps

$ ./ start

Apply the patch using the new adop tool, adpatch no longer required.

$ cd ../VIS/fs_ne/EBSapps/patch
$ unzip
$ unzip p21900871
$ adop phase=apply patches=17204589,21900871 merge=yes hotpatch=yes

Start all AppsTier services

$ ./ apps/apps

Enter Weblogic password when prompted.

Apply R12.2.5 Release Update Pack

Source the run edition environment variables

$. <INSTALL_BASE>EBSapps.env. run

Stop the Weblogic AdminServer and Node Manager services

$ ./ stop
$ ./ stop

Set the 12c database parameter optimizer_adaptive_features to false


Apply previously downloaded patch 19676458

$ cd ../VIS/fs_ne/EBSapps/patch
$ unzip
$ adop phase=apply apply_mode=downtime patches=19676458

Reset the 12c database parameter optimizer_adaptive_features back to true


Re-Start all AppsTier services

$ ./ apps/apps

Perform adop clean-up
$ adop phase=cleanup

Synchronise the file systems using atop as below, this will copy the new run edition code and configuration to the other file system.
$ adop phase=fs_clone

Updated Configuration

As you can see from below we have now a running Oracle EBS R12.2.5 environment on a 12c database.

R12.2.5 OAM


Oracle E-Business Suite Clone Log Parser utility

Oracle EBS Log Parser

As anyone who has ever performed an Oracle E-Business suite clone knows it can be a complex time consuming task,  any error during the cloning process may result in a considerable amount of time been spent reviewing multiple clone log files in various directories on the Apps & Database tiers. To assist with this challenge the Oracle Proactive Support Team developed the ‘Log Parser’, this utility is able to consolidates error information from the 12 seperate clone log files into a easy to read HTML report. The ‘Log Parser’ also perform some basic configuration checks and reports this along with useful recommendations and the Oracle support pages links.

The Log parser analyses the following logs:

  • StageDBTier.log
  • StageAppsTier_.log
  • ApplyDBTier.log
  • ApplyDatabase.log
  • ApplyDBTechStack.log
  • ApplyAppsTechStack.log
  • ApplyAppsTier.log
  • CloneContext.log
  • make_.log, make.log
  • adconfig.log
  • ohclone.log
  • adcrdb_.txt
  • NetServiceHandler.log
  • setup_stubs.log
  • Central/Global oraInventory/logs directory and all sub-directories, for any files with a .err, .log or .txt extension


The installation couldn’t be much simpler – download, extract, run

You can download the ‘Log Parser’ directly from ‘My Oracle Support’  – E-Business Suite Clone Log Parser Utility (Rapid Clone 11i,12.0, 12.1) (Doc ID 1447553.1)


Database Tier

Download the ‘Log Parser’ zip file into /tmp and unzip the file into $ORACLE_HOME/appsutil/clone

Screen Shot 2015-01-07 at 10.49.10

Once you have unzipped the Log Parser your a ready to navigate to the LogParser directory and run the LogParser perl script.

Screen Shot 2015-01-07 at 11.27.34

On completion you will have a new HTML report available for your review

Screen Shot 2015-01-07 at 11.30.59

Transfer this back to your desktop an open in your preferred browser, click on the ‘Show Details’ links in the various sections to expand the report.

Screen Shot 2015-01-07 at 11.35.28

Applications Tier

Download the ‘Log Parser’ zip file into /tmp and unzip the file into <COMMON_TOP>/clone

Screen Shot 2015-01-07 at 18.55.48

Once you have unzipped the Log Parser your a ready to navigate to the LogParser directory and run the LogParser perl script.

Screen Shot 2015-01-07 at 19.01.48

On completion you will have a new HTML report available for your review, as before click on the ‘Show Details’ to expand the report.

Screen Shot 2015-01-07 at 18.56.22

Transfer this back to your desktop an open in your preferred browser.

Screen Shot 2015-01-07 at 19.06.07

In a future post I will walk through the Log Parser report and review the output.

Oracle EBS and Delphix

The Delphix EBS solution provides AppsDBA’s, functional consultants, test teams and business users the ability to perform Self Service on-demand EBS environment (Database, Database Tier & AppsTier) clones. This dramatically reduced the end-to-end provision time coming down from multiple weeks to a mater of minutes.

In a couple of previous posts I have provided a walkthrough of how to Virtualise your EBS environment and also how to create a new Virtual EBS environment.




How Many Databases is Enough?

Database usage throughout the Extended Project Life Cycle

How many Databases do I need?

A question that often comes up when talking to Solution Architects is how many databases do I need to plan for in my technical architecture?

Now, on the surface this seems a simple question and sometimes results in a simple response, however before you jump in with a stock answer of 3 or 4 (Production, Test and Development or Production, Pre-Production, Test and Development) you should apply the 6 W’s – Who, What, Where, When, Why & hoW to the full Extended Life Cycle

Your thought process needs to cover:

Application Life Cycle Management (ALM)


Type of Project e.g.

  • Change – New Implementation, Upgrade
  • Business As Usual (BAU) – Operations / ‘RUN’

Project Life Cycle
Major planned Project activities e.g.


  • POC (Proof of Concept)
  • CRP (Conference Room Pilots)
  • SVT (System Validation Test)
  • UAT (User Acceptance Test)
  • Cutover / Go-Live

Development Methodology e.g.

  • Waterfall
  • Agile / SCRUM etc..

Business Testing Requirements

  • Manual
  • Automated

Production ‘Run’ Support

  • DBA Patching
  • Daily / Ad-hoc Refresh

Training and Education requirements

Databases are not just used by developers

It’s also easy to forget databases are used by more than Developers, DBA’s and Business End Users, throughout the application life cycle different teams will also have competing demands and these all need to be satisfied. This can be further complicated when a project has a phased Go-Lives which result with Project and ‘RUN’ development, test and user acceptance testing activities occurring concurrently.

Large Enterprise ERP upgrade and implementation projects suffer from complex inter-team dependencies for example Data Migration teams can not load financial data until Functional teams have configured accounting structures, technical teams can’t configure enterprise scheduling solutions until business processes are defined.

An inadequate number of databases leads to project delays as the database becomes a bottleneck with teams having to wait for other teams to complete activities before they can start their tasks. e.g. Functional consultants unable to test business processes whilst data loads are being undertaken by Data Migration team members.

Other teams and activities to consider include:

Application Functional Specialists

  • Development of System Set-up
  • Business Process Configuration
  • Business Process Testing

Data Migration Teams

  • Development of ETL (Extraction, Transformation and Load) routines
  • Data Mapping
  • Data Cleansing

Technical Teams

  • Performance testing
  • System Integration
  • Automation
  • Enterprise Scheduling

Business Process Owners

  • Application Process Validation


Database demands change throughout the life cycle of a project and application, a flexible approach is required which can provide databases on-demand with minimal hardware and operational overheads.

The number of databases required should therefore be calculated to satisfy the peak demand and should not be limited by storage infrastructure. Virtual Databases remove the storage constraints and operational barriers providing project teams the required agility without requiring additional storage infrastructure.