EBS - E-Business Suite 12.1.1 Standard Installation on Linux OEL 5.3

Installation of EBS with Rapid Install

With Rapid Install, you can perform the following tasks:

  • Install a new, fully configured Oracle E-Business Suite system, including the latest certified Oracle E-Business Suite technology stack and all patches, product family release update packs, release update packs, and other updates available at the time of this Oracle E-Business Suite release.
  • Lay down the file system and configure server processes for an upgraded system.
  • Install a new database node or Applications node technology stack.

Rapid Install employs a wizard that guides you through the screens used to carry out the selected task. On the wizard screens, you enter configuration values for your system; these will typically be saved in the Oracle E-Business Suite database for later use.

Depending of your installation architecture, the installation may change. This document is based on a single node with all components installed.


Config file

Previous releases of Oracle E-Business Suite only used a text file, config.txt, to store the supplied configuration values. In Release 12, the name of this configuration file changed, and it now includes the database SID, to give a file name of conf_<SID>.txt (for example, conf_PROD.txt). This file stores the information collected by Rapid Install for all database and Applications nodes. Rapid Install stores copies of the conf_<SID>.txt file in three separate locations:

  • Database 11gR1 <ORACLE_HOME>/appsutil: This copy is used on database nodes, on Applications nodes in multi-node installs, and in upgrades. It is permanently stored and not deleted.
  • $INST_TOP: This copy is used on Applications nodes in multi-node installs, and in upgrades. It is permanently stored and not deleted.
  • /tmp/<time stamp>: This copy is used by Rapid Install during the installation run. It is deleted when the installation is completed.

Release 12.1.1 utilizes the conf_<SID>.txt file in certain situations, for example where the database has not yet been created. The configuration file is also employed in multi-node (distributed) installs, where you only need to enter the install information once, on one machine, and can then copy the configuration file to other machines as required.


The main configuration engine used by Rapid Install is called AutoConfig. Rapid Install supplies the configuration information to AutoConfig, which stores the configuration for each node in a node-specific configuration file called a context file.

AutoConfig simplifies and standardizes the management of your system configuration; at any time after the initial installation, you can use the Configuration Editor in Oracle Applications Manager to update various system settings, and then run an AutoConfig script to populate the system configuration files with new values.

Type of installation


In a new Standard installation, you define many aspects of the configuration. You will need to choose where to install the required nodes (database node and primary Applications node).


In an Express installation, you set up a fully configured, single-user/single-machine system using a few basic configuration parameters, such as database type and name, top-level installation directory, and port pool choice. The remaining directory specifications and mount points are supplied by Rapid Install using default values. An Express installation includes a set of core products and uses the US7ASCII character set.


Operating System Supported Version

A fully installed linux Operating System: Linux - Installation

To determine your version, see Linux - How to know the version of the distribution (Operating system)

Operating System Name Supported Version Minimum Kernel
Oracle Enterprise Linux 4 - Update 4 or higher (32-bit) 2.6.9-
Oracle Enterprise Linux 5 - Update 1 or higher (32-bit) 2.6.18-8.el5PAE
Red Hat Enterprise Linux 4 - Update 4 or higher (32-bit) 2.6.9-42.EL
Red Hat Enterprise Linux 5 - Update 1 or hgiher (32-bit) 2.6.18-8.el5PAE
SUSE Linux Enterprise Server 10 - GA, SP1 or higher (32-bit)

Minimal Hardware requirement

  • Memory: At least 2GB of 3GB would be better and 4GB will the top
  • File System Space Requirements for Standard Installation: At least 300GB. 350GB will be better
Node Space Required
Applications node file system (includes OracleAS 10.1.2 Oracle Home,
OracleAS 10.1.3 Oracle Home, COMMON_TOP, APPL_TOP, and INST_TOP)
35 GB (50 GB on HP-UX Itanium)
Database node file system (Fresh install) 55 GB
Database node file system (Vision Demo database) 208 GB (210 GB on HP-UX Itanium)

Reference: CPU, Memory, Disk Space Requirement (Page 23)

  • Temporary directories and files

For install time temporary disk space, Rapid Install uses the directory defined by the TMPDIR variable (on UNIX) or TEMP and TMP variables (on Windows). You should ensure there is at least 1 GB of free temporary space before starting an installation.

Preparation of the host


From oss.oracle.com

The following i386 packages are not part of the OS distribution media and must be downloaded separately from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux for both OEL 5 and RHEL 5 and installed manually:

This article can help you to determine your update version.

From the OEL 5 or RHEL 5 distribution media

The following i386 packages must be installed from the OEL 5 or RHEL 5 distribution media.

Some rpm are distributed as part of the 'default' installation of Enterprise Linux.

# From Enterprise Linux 5 DVD
cd /media/cdrom/Server
rpm -Uvh compat-glibc-2.3.4-2.26*
rpm -Uvh gcc-4.1.2-14.el5*
rpm -Uvh gcc-c++-4.1.2-14.el5*
rpm -Uvh glibc-2.5-12*
rpm -Uvh glibc-common-2.5-12*
rpm -Uvh glibc-devel-2.5-12*
rpm -Uvh libgcc-4.1.2-14.el5*
rpm -Uvh libstdc++-devel-4.1.2-14.el5*
rpm -Uvh libstdc++-4.1.2-14.el5*
rpm -Uvh make-3.81-1.1*
rpm -Uvh gdbm-1.8.0-26.2.1*
rpm -Uvh libXp-1.0.0-8.1.el5*
rpm -Uvh libaio-0.3.106-3.2*
rpm -Uvh libgomp-4.1.2-14.el5*
rpm -Uvh sysstat-7.0.0-3.el5*
rpm -Uvh compat-libstdc++-296-2.96-138*
rpm -Uvh compat-libstdc++-33-3.2.3-61*
cd /

Reference: Operating System Requirement

Additionally, the following RPMs are required for an 11gR1 Database (which is bundled with the 12.1.1 release) on the database tier:

  • elfutils-libelf-devel-0.125
  • elfutils-libelf-devel-static-0.125
  • libaio-devel-0.3.106
  • unixODBC-2.2.11
  • unixODBC-devel-2.2.11
  • kernel-headers-2.6

Just to remember, below the rpm installation that I have performed.

rpm -Uvh  kernel-headers-2.6.18-128.el5.i386.rpm
rpm -Uvh compat-glibc-*
rpm -Uvh glibc-headers*
rpm -Uvh glibc-devel*
rpm -Uvh libgomp*
rpm -Uvh gcc-4.1.2*
rpm -Uvh libstdc++-devel*
rpm -Uvh gcc-c++*
rpm -Uvh libXau-devel*
rpm -Uvh libXp-1.0.0-8.1.el5.i386.rpm
rpm -Uvh sysstat-7.0.2-3.el5.i386.rpm
rpm -Uvh elfutils-libelf-devel*
rpm -Uvh libaio-devel-0.3.106-3.2.i386.rpm
rpm -Uvh unixODBC*
After installing these patches


ldconfig -v

Networking - Hosts Name settings


The /etc/hosts file must contain a fully qualified name for the server:

 <IP-address>  <fully-qualified-machine-name>  <machine-name>

Loopback adapter when installing on a DHCP Host on UNIX systems
You must configure the host to resolve hostnames to the loopback IP address by modifying the /etc/hosts file to contain the following entries: hostname.domainname hostname localhost.localdomain localhost

Example with hostname = ebs121 and domainname = gerardnico.com

[[email protected] etc]# cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.       ebs121.gerardnico.com    ebs121       localhost.localdomain localhost
::1             localhost6.localdomain6 localhost6

The configuration line must be in first place !

After doing so, check that the hostname resolves to the loopback IP address by entering the following command:

/bin/ping hostname.domainname

You must get something like this:

[[email protected] ~]# ping -c 1 ebs121.gerardnico.com
PING ebs121.gerardnico.com ( 56(84) bytes of data.
64 bytes from localhost.localdomain ( icmp_seq=1 ttl=64 time=0.134 ms

--- ebs121.gerardnico.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.134/0.134/0.134/0.000 ms


Verify that the /etc/sysconfig/network file is formatted as follows:


Example with the node_name = ebs121 and domain_name = gerardnico.com

[[email protected] tmp]# cat /etc/sysconfig/network


If the /etc/sysconfig/networking/profiles/default/network file exists, remove it.

[[email protected] tmp]# cat /etc/sysconfig/networking/profiles/default/network
[[email protected] tmp]# rm /etc/sysconfig/networking/profiles/default/network
rm: remove regular file `/etc/sysconfig/networking/profiles/default/network'? y
[[email protected] tmp]# cat /etc/sysconfig/networking/profiles/default/network
cat: /etc/sysconfig/networking/profiles/default/network: No such file or directory

Restart of the system

If you changed any files in the next steps, restart the system.

[[email protected] tmp]# reboot

Broadcast message from root (pts/2) (Sun Mar  7 22:25:38 2010):

The system is going down for reboot NOW!

Kernel Setting

The current values of the kernel parameters can be tested using the following command:

/sbin/sysctl -a | grep <param-name>

Add or amend the following lines in the “/etc/sysctl.conf” file.

Specifying the parameters in the sysctl.conf file causes the parameters to be set upon reboot.

# Kernel sysctl configuration file for Oracle Enterprise Linux
# For binary values, 0 is disabled, 1 is enabled.  See sysctl(8) and
# sysctl.conf(5) for more details.

# Append this one
kernel.sem = 256 32000 100 142
fs.file-max = 131072
net.ipv4.ip_local_port_range = 10000 65000
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144

# Modify this one
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.msgmax = 8192
kernel.msgmnb = 65535
kernel.msgmni = 2878

kernel.shmmax must have the half size of the physical memory (in bytes), and at least 2147483648

Run the following command to change the current kernel parameters:

/sbin/sysctl -p

The resolver - DNS parameters

The file /etc/resolv.conf is used by the resolver a library that determines the IP address from an host name. It defines the DNS.

Two Domain Name System (DNS) resolver parameters (timeout and attempts) are set by default to low values when the operating system is installed.

These low values may cause attempted network connections to an Oracle database to fail. If this happens, add or update the following entries to these minimum settings in the /etc/resolv.conf file on each server node:

[[email protected] ~]# cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search cornac.net
options attemps:5
options timeout:15

Limiting user processes

To limit the user processes, open the /etc/security/limits.conf file and change the existing values for “hard” and “soft” parameters as follows. Restart the system after making changes.

If the current value for any parameter is higher than the value listed in this document, then do not change the value of that parameter.

*               hard    nofile          65535
*               soft    nofile          4096
*               hard    nproc           16384
*               soft    nproc           2047

Create Operating System Accounts

Before running Rapid Install, you must create the operating system accounts that will be used:

  • in the installation of the database node: the oracle account

The operating system user that owns the database node file system and starts the database node services is called the oracle user.

  • and Applications node file systems: the applmgr account

The operating system user that owns the Applications node file system and starts the Applications node services is called the applmgr user. The applmgr user is the account that owns the Applications node technology stack (APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home, and OracleAS 10.1.3 1-14 Oracle E-Business Suite Installation Guide: Using Rapid Install Oracle Home).

The names of these accounts must be the same on all nodes in an Oracle E-Business Suite system.

You can perform (Reference - Page 27 - For unix user):

  • a single-user installation: one user for the two account
  • a Multi-user installations: one user by account.

The default name for the oracle user is ora<SID>. For example, for a production (PROD) environment, the default Oracle OS username might be oraprod.

For the applmgr user, the default name is appl<SID>. For example, for a Vision Demo (VIS) environment, the default Apps OS username might be applvis.

Two common groups that are defined in installations are:

  • the oinstall group (which owns the Oracle Inventory information)
  • and the dba group whose members have SYSDBA privileges of the database.
groupadd dba

useradd -m -g dba oravis
passwd oravis
useradd -m -g dba applvis
passwd applvis

where :

  • the –m flag indicates that a new home directory should be created,
  • -g specified the primary group
  • and –G specifies the secondary group.

Once the user is created, the password is immediately reset using the passwd command.

Path and Maintenance tools

The following maintenance tools must be installed on all machines, and their locations specified both in the PATH of the account that runs the wizard, and in the PATH of the accounts that will own the database tier and Applications tier file systems.

Operating System Required Maintenance Tools
Linux x86, X86-64 ar, gcc, g++, ld, ksh, make, X Display Server
Microsoft Windows Server (32-bit) Microsoft C++, MKS Toolkit *, GNU make

Reference: Platform-Specific Software Requirements (page 22)

To verify that they are installed, just run the version command and see if you have a answer.

Required Maintenance Tools Description Version command
ar create, modify, and extract from archives ar V
gcc GNU project C and C++ compiler gcc –version
g++ gcc - GNU project C and C++ compiler g++ –version
ld The GNU linker ld –version
ksh KornShell, a standard/restricted command and pro-gramming language ksh –version
make GNU make utility to maintain groups of programs make –version
X Display Server X Windows System (commonly X or X11) X -version


Inventory Directory - oraInst.loc

As per note 405293.1, on all platforms except Windows, oraInst.loc must exist and point to a valid inventory directory. Specifically:

  • oraInst.loc must be located in /etc (for Linux and IBM AIX) or /var/opt/oracle (for Solaris, HP-UX PA RISC, and HP-UX Itanium)
  • oraInst.loc must point to a valid central inventory location
  • the central inventory location must be writable by the owner of the oracle files and the application files

If oraInst.loc does not exist, create it in the proper directory. The contents should look like this:


where: /d01/oracle/oraInventory points to the directory where the central inventory is to be located and must be writable by the owner of the oracle files and the application files.

Installation directories

mkdir -p /d01/oracle/VIS 
mkdir -p /d01/oracle/VIS/inst
chown -R oravis:dba /d01 
chmod -R 775 /d01


Software preparation


You can download EBS from edelivery.oracle.com.

Once you click on the link “Oracle E-Business Suite Release 12.1.1 Media Pack for Linux x86”, you have a lot of file to download. Not all of them are necessary for the installation of EBS.

Don't be afraid to use the firefox plugin DownThemAll to simplify the task.

The syntax of each file is:


Example: B53824-01_1of4 has:

  • B53824-01 as part file (which represent a CD)
  • and is the first file on a series of four

The different part files can be aggregate in 5 groups:

Parts Complete Description Part Number
Start Here Oracle E-Business Suite Release 12.1.1 Rapid Install Start Here B53824-01
APPL_TOP Oracle E-Business Suite Release 12.1.1 for Linux x86 Rapid Install APPL_TOP Disk1 - V15573-01
Disk2 - V15574-01
RDBMS Oracle E-Business Suite Release 12.1.1 for Linux x86 Rapid Install RDBMS V15576-01
Tools Oracle E-Business Suite Release 12.1.1 for Linux x86 Rapid Install Tools V15575-01
Databases Oracle E-Business Suite Release 12.1.1 for Linux x86 Rapid Install Databases Disk1 - V15564-01
Disk2 - V15565-01
Disk3 - V15566-01
Disk4 - V15567-01
Disk5 - V15568-01
Disk6 - V15569-01
Disk7 - V15570-01
Disk8 - V15571-01
Disk9 - V15572-01


The most current version of the Rapid Install wizard is You can obtain this version by applying «Patch 8639046», available at My Oracle Support (Formerly Oracle MetaLink). To verify your current version, use the RapidWizVersion executable, located in the rapidwiz directory on the Start Here DVD.

Your system path may vary.

$ cd /stageR12/startCD/Disk1/rapidwiz
$ ./RapidWizVersion
Oracle Applications Rapid Install Wizard
(c) Copyright 2000-2006 Oracle Corporation.  All rights reserved.

The patch file is: p8639046_R12_GENERIC.zip

Setting Up the Stage Area

The stage area is just a local repository on the computer where all the files needed for an installation are present.

The setting of the stage area depend then if you are in possession of CD or files.

  • with the CD, you must run a Perl script that creates the install directory and copies the contents of the Release 12.1.1 software bundle to the appropriate location in the file system, known as the stage area (or staging area). You must have perl 5.0053 or higher installed, and it must be in your PATH. Use the following commands to identify the perl version and its location:
[[email protected] /]# perl -v
This is perl, v5.8.8 built for i386-linux-thread-multi
  • with the files. If you have downloaded the file, just unzip the content of the files in a staging directory.

You will then end up with this structure onder the staging area (for instance /stageR12/) :

Parts Directory Structure
Start Here startCD/Disk1
APPL_TOP oraApps/Disk1 to Disk12
RDBMS oraDB/Disk1 to Disk7
Tools oraAS/Disk1 to Disk3
Databases oraAppDB/Disk1 to Disk65

Starting the installation

User who start the installation

On machines containing multiple nodes, you can assign one user account to be the owner of the database node file system, and another to be the owner of the Applications node file system. For this type of install, Rapid Install can install both nodes in one run if the install is started by the root user. If you are installing on a machine with only one node to install, or with all nodes sharing the same user, you can run the install as either the root user or the specific user for those nodes.

Unset the ENV environment variable

Unset the ENV environment variable prior to installing installation, as it can alter variables that are set by the Oracle installation scripts. The command unset ENV can be used to unset the variable if necessary.

unset ENV

Starting the installation

[[email protected] rapidwiz]# unset ENV
[[email protected] rapidwiz]# ./rapidwiz
Rapid Install Wizard is validating your file system......
4 dvd labels found
Rapid Install Wizard will now launch the Java Interface.....
  • Welcome screen. Next
  • Wizard operation. Choose Install Oracle Application Release 12.1.1. Next
  • Oracle Configuration Manager Details. Next
  • Configuration Choice. Create a new configuration. Next
  • Global System Settings. Next
  • Database Node:

Path Variable Value Example
INSTALL_BASE /d01/oracle/VIS/
INST_TOP $INSTALL_BASE/inst/apps/$CONTEXT_NAME /d01/oracle/VIS/inst/apps/VIS_ebs121/

Edit Path:

RDBMS Oracle Home /d01/oracle/VIS/db/tech_st/11.1.0
Data Top (SYS) /d01/oracle/VIS/db/apps_st/data
Data Top (LOG) /d01/oracle/VIS/db/apps_st/data
Data Top (TXN) /d01/oracle/VIS/db/apps_st/data
Data Top (ARCHIVE) /d01/oracle/VIS/db/apps_st/data

The database usernames and their respective default passwords are:

  • APPS Username (APPS), APPS password (APPS),
  • GWYUID username (APPLSYSPUB), GWYUID Password (PUB),
  • Guest username (GUEST), and Guest password (ORACLE).
  • Primary application node:

Edit path:

APPL_TOP Mount pointy /d01/oracle/VIS/apps/apps_st/appl
APPL_TOP (aux1) /d01/oracle/VIS/apps/apps_st/appl
APPL_TOP (aux2) /d01/oracle/VIS/apps/apps_st/appl
APPL_TOP (aux3) /d01/oracle/VIS/apps/apps_st/appl
COMMON_TOP /d01/oracle/VIS/apps/apps_st/comn
Tools Oracle Home /d01/oracle/VIS/apps/tech_st/10.1.2
Web Oracle Home /d01/oracle/VIS/apps/tech_st/10.1.3
Temp directory /d01/oracle/VIS/inst/apps/VIS_ebs121/temp
  • Node information. Next
  • System check. Next
  • Component Installation Review. Next
  • Install in progress

  • post install check failed on the HTTP server.

  • Oracle HTTP Server Patch (on OEL 5 and RHEL 5 only)

Download and apply the patch 6078836 from OracleMetaLink to fix an issue with the Oracle HTTP Server bundled with the E-Business Suite technology stack. Perform the following command as root:

[[email protected] scripts]# cd /stageR12
[[email protected] stageR12]# unzip p6078836_101330_LINUX.zip
Archive:  p6078836_101330_LINUX.zip
   creating: 6078836/
  inflating: 6078836/libdb.so.2
  inflating: 6078836/README.txt
[[email protected] stageR12]# mv /usr/lib/libdb.so.2 /usr/lib/libdb.so.2.6078836
mv: cannot stat '/usr/lib/libdb.so.2': No such file or directory
[[email protected] stageR12]# cd 6078836
[[email protected] 6078836]# cp libdb.so.2 /usr/lib

All startup shutdown scripts in Oracle Applications 11i(11.5.10) are in $COMMON_TOP/admin/script/$CONTEXT_NAME where COMMON_TOP is also called as OAD_TOP and CONTEXT_NAME is your SID_hostname. For an instance Name of VISION and its on machine with name machine1 so your CONTEXT_NAME will be VISION_machine1.

Script to start/stop Web Server is adapcctl.sh where ad (application dba), apc(apache), ctl(control) and sh stands for shell script. Syntax:

    adapcctl.sh {start|stop|status}
[[email protected] bin]# cd /d01/oracle/VIS/inst/apps/VIS_ebs121/admin/scripts
[[email protected] scripts]# ./adapcctl.sh status

You are running adapcctl.sh version 120.7.12010000.2

Checking status of OPMN managed Oracle HTTP Server (OHS) instance ...

Processes in Instance: VIS_ebs121.ebs121.gerardnico.com
ias-component                    | process-type       |     pid | status
OC4JGroup:default_group          | OC4J:oafm          |   18880 | Alive
OC4JGroup:default_group          | OC4J:forms         |   18814 | Alive
OC4JGroup:default_group          | OC4J:oacore        |   18722 | Alive
HTTP_Server                      | HTTP_Server        |     N/A | Down
[[email protected] scripts]# ./adapcctl.sh start

You are running adapcctl.sh version 120.7.12010000.2

Starting OPMN managed Oracle HTTP Server (OHS) instance ...

adapcctl.sh: exiting with status 0

adapcctl.sh: check the logfile /d01/oracle/VIS/inst/apps/VIS_ebs121/logs/appl/admin/log/adapcctl.txt for more information ...

[[email protected] scripts]# ./adapcctl.sh status

You are running adapcctl.sh version 120.7.12010000.2

Checking status of OPMN managed Oracle HTTP Server (OHS) instance ...

Processes in Instance: VIS_ebs121.ebs121.gerardnico.com
ias-component                    | process-type       |     pid | status
OC4JGroup:default_group          | OC4J:oafm          |   18880 | Alive
OC4JGroup:default_group          | OC4J:forms         |   18814 | Alive
OC4JGroup:default_group          | OC4J:oacore        |   18722 | Alive
HTTP_Server                      | HTTP_Server        |   24735 | Alive
  • System check status show that the HTTP server (OHS - Oracle HTTP Server) is up and running

  • post install checks succeed and you can click on the next button to see the finish screen

Post-installation tasks

Perform the following command (as root on your system) to update a required link to a Motif library prior to relinking or patching the 10.1.2 Application Server Oracle Home:

# unlink /usr/lib/libXtst.so.6
# ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6

Without this updated link, you may see the following errors during a relink of the 10.1.2 Oracle Home:

/usr/lib/libXtst.so.6: undefined reference to  `[email protected]_2.4'
/usr/lib/libXtst.so.6: undefined reference to  `[email protected]_2.3.4'
/usr/lib/libXtst.so.6: undefined reference to  `[email protected]_2.3.4' 

Since the ldconfig command overrides this link, the above link command (ln) will have to be re-issued after running the ldconfig command.

Relink Advanced Supply Chain Planning executables (for SLES 10 and OEL/RHEL 5.4 or higher only)

During the relink phase of the installation of EBS Release 12 (12.1.1) on SLES 10 or OEL/RHEL 5.4 (Update 4 or higher), failures will result while relinking the Advanced Supply Chain Planning (ASCP) executables. To fix this problem, users are required to replace the following line under the Linux section of the $AD_TOP/bin/adrelinknew.sh:

CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'


CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec'

After making this change, users are then required to run the adadmin utility and relink application executables.


The syntax for the login page is

  http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLogin

For example:

The Oracle E-Business Suite Login page appears and you can login with SYSADMIN. It's a privileged account that has System Administrator responsibility. The default password for this account is also SYSADMIN.

Then tape sysadmin/sysadmin and click Login.

Et voila !

Post-Installation Tasks

Change Default Passwords

The default password are:

Vision Demo manager manager
Default Database manager change_on_install

To maintain database security and restrict access to these accounts, you should change these passwords.


A lot of posts installation tasks exist and you can found them in the installation book “Chapter Finishing Tasks”

Applications DBA utilities

The following Applications DBA (AD) utilities can be found in Oracle Applications Maintenance Procedures, Managing Server Processes, how to start and stop Application and Database Tier Services

Database tier scripts

  • addbctl.sh to start the database (p40}
 ./addbctl.sh start
  • addlnctl.sh to start the listener
./addlnctl.sh start VIS

They can be found under $ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME> directory.


To get the correct environment variable, you can call the following env environment configuration file

source /d01/oracle/VIS/db/tech_st/11.1.0/VIS_ebs121.env

Application tier scripts

  • adstrtal.sh - start all application tiers
  • adstpall.sh - stop all application tiers

They can be found under $INST_TOP/admin/scripts directory.



Restarting the Installation

If the installation process terminates before completion, you can use the -restart parameter to run Rapid Install again. Example:

$ rapidwiz -restart

Log files

Log files can be located under the following directories:

  • $ORACLE_HOME/appsutil/log/<CONTEXT_NAME>
  • $INST_TOP/logs


You must be sure to have follow the steps in the network section and that the line in /etc/hosts where you define your hostname and domain name is present in the first line.

Internal Server Error on Login Page

To check status of OPMN managed process

cd $LOG_HOME/ora/10.1.3/opmn
vi opmn.log

Startup shutdown scripts

All startup shutdown scripts in Oracle Applications 11i(11.5.10) are in $COMMON_TOP/admin/script/$CONTEXT_NAME where COMMON_TOP is also called as OAD_TOP and CONTEXT_NAME is your SID_hostname. For an instance Name of VISION and its on machine with name machine1 so your CONTEXT_NAME will be VISION_machine1.

Script to start/stop Web Server is adapcctl.sh where ad (application dba), apc(apache), ctl(control) and sh stands for shell script. Syntax:

adapcctl.sh {start|stop|status}

Documentation / Reference

Associated Document: Platform Installation and Upgrade Note

See Oracle Company - My Oracle Support (MOS):

Plateform Platform Installation and Upgrade Note
Linux x86 (32 bit) 761564.1
Linux x86-64 761566.1
HP-UX PA-RISC (64-bit) 762894.1
HP-UX Itanium 762891.1
IBM AIX on Power Systems (64-bit) 761569.1
Microsoft Windows Server (32-bit) 761567.1
Sun Solaris SPARC (64-bit) 761568.1

In addition, you should refer to My Oracle Support Knowledge Document 405565.1, Oracle E-Business Suite Release 12 Installation Guidelines, for supplementary information on Rapid Install that may have become available since this book (page 26) was published.

Powered by ComboStrap