Oracle Fusion Applications: Installing Fusion Applications Transactional Database

INSTALLING FUSION APPLICATIONS DATABASE WITH RCU IN LINUX 84x64 [Part1]

We need to install oracle 11gR2 [11.2.0.3] database .. to install the Fusion applications Release 5[rup4].. oracle fusion applications can be architecture with four database
[1] fusion applications transaction database,[FADB]
[2]OID database[OIDDB]
[3] OAM database[OAMDB]
[4] data warehouse database for fusion BI [the 4 data ware house database is optional need to installed if we are using the BI] ..

Here we have explained the steps to install the fusion applications transitional database...which holds the all the transitional data of the fusion applications ..
[1] preparing the Linux box to install the database
[2] installing the database binaries
[3] configuring the database for fusion applications with necessary patches
[4] Running Rcu to create the fusion schema's

[1] Preparing Linux 86x64 box for installing fusion applications transitional database

Step 1

Install the Necessary Rpm's

1] binutils-2.17.50*
2] compat-libstdc++-33-3.2.3-61*
3] elfutils-libelf-*
4] glibc-2.5-81.el5_8.2.
5] glibc-common-2.5-81.el5_8.2.
6] ksh-20100621-5.el5_8.1
7] libaio-0.3.106-5.x86_64
8] libgcc-4.1.2-52.el5_8.1
9] libstdc++-4.1.2-52.el5_8.1
10]libstdc++44-devel.x86_64

11]glibc-headers-2.5-81.el5_8.2.x86_64

12] sysstat-7.0.2-11.el5.x86_64

13] unixODBC-devel-2.2.11-10.el5

14]unixODBC-2.2.11-10.el5

15]unixODBC-libs-2.2.11-10.el5

16]gcc-c++-4.1.2-52.el5_8.1.x86_64

17]kernel-headers.x86_64

18]glibc-devel-2.5-81.el5_8.2.

19]libgomp-4.4.6-3.el5.1

20]make-3.81-3.el5.x86_64

21]openmotif22-2.2.3-20
22]openmotif-2.3.1-6.1.el5_8
23]xorg-x11-utils

Step 2

Create the username and group in O/S

[root@fah ~]# groupadd orafusion

[root@fah ~]# groupadd oper

[root@fah ~]#useradd orafadb -g orafusion -G oper

-g is the primary group's name

-G is the secondary group's name

[root@fah ~]# id orafadb

uid=54326(orafadb) gid=54324(orafusion) groups=54324(orafusion),54323(oper)

Step 3

Create directory and give necessary permissions to the directory

we have created the mount point and mounted in the /u03/app and navigate to /u03/app/ and create the directory

[root@fah app] #mkdir oracle

[root@fah app] #chown orafadb:orafusion oracle

[root@fah app]#chmod -R g+w oracle

Step 4

LIMITS.CONF VALUES FOR THE FUSION TRANSACTION DATABASE O/S USER

Navigate to limit's.conf which is located in /etc/security

orafadb soft nofile 327679

orafadb hard nofile 327679

orafadb soft nproc 131072

orafadb hard nproc 131072

orafadb soft stack 131072

orafadb soft core unlimited

orafadb hard core unlimited

orafadb soft memlock 50000000

orafadb hard memlock 50000000

Legends for <type> in limits.conf file

hard

Hard is used for enforcing hard resource limits. These limits are set by the superuser and enforced by the Kernel. The user cannot raise his requirement of system resources above such values

Soft

Soft is used for enforcing soft resource limits. These limits are ones that the user can move up or down within the permitted range by any pre-existing hard limits.

Legends for <item> in limits.conf file

core

limits the core file size

memlock maximum locked-in-memory address space

nproc maximum number of processes

nofile maximum number of open files

stack maximum stack size

Step 5

Create the environmental variables in the .bash_profile for the database

Edit the .bash_profile which is located under the ~ [home directory ] of the user and add the Environmental variables listed below

Change the database_sid and basepath according to the environment

export PATH

ORACLE_SID=<database_sid>; export ORACLE_SID

ORACLE_BASE=<base path of the oracle binaries>; export ORACLE_BASE

ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1; export ORACLE_HOME

ORACLE_TERM=xterm; export ORACLE_TERM

TNS_ADMIN=$ORACLE_HOME/network/admin; export TNS_ADMIN

PATH=.:${JAVA_HOME}/bin:${PATH}:$HOME/bin:$ORACLE_HOME/bin

PATH=${PATH}:/usr/bin:/bin:/usr/bin/X11:/usr/local/bin

export PATH=$PATH:$ORACLE_HOME/OPatch

export PATH

LD_LIBRARY_PATH=$ORACLE_HOME/lib

LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$ORACLE_HOME/oracm/lib

LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/lib:/usr/lib:/usr/local/lib

export LD_LIBRARY_PATH

CLASSPATH=$ORACLE_HOME/JRE

CLASSPATH=${CLASSPATH}:$ORACLE_HOME/jlib

CLASSPATH=${CLASSPATH}:$ORACLE_HOME/rdbms/jlib

CLASSPATH=${CLASSPATH}:$ORACLE_HOME/network/jlib

export CLASSPATH

export TEMP=/tmp

Legends

database_ sid = Database Name [ ORCL]

base path = The path where we are going to install the oracle binary's and it will be before the products directory for ex [/u03/app/oracle]

Step 6

KERNAL PARAMETER VALUES FOR THE FUSION APPLICATIONS DATABASE

Edit the /etc/syscctl.conf file for modifying the Kernel Parameter's

net.ipv4.ip_forward = 0

net.ipv4.conf.default.rp_filter = 1

net.ipv4.conf.default.accept_source_route = 0

kernel.core_uses_pid = 1

net.ipv4.tcp_syncookies = 1

fs.file-max = 6815744

kernel.msgmni = 2878

kernel.msgmax = 8192

kernel.msgmnb = 65536

kernel.sem = 250 32000 100 142

kernel.shmmni = 4096

kernel.shmall = 4294967296

kernel.shmmax = 88046829568

kernel.sysrq = 1

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 1048576

fs.aio-max-nr = 3145728

net.ipv4.ip_local_port_range = 9000 65500

vm.min_free_kbytes = 51200

net.ipv4.tcp_wmem = 262144 262144 262144

net.ipv4.tcp_rmem = 4194304 4194304 4194304

Once the file is saved check the configuration by using sysctl -p

To check the semaphore configuration

[root@fah ~]# ipcs -ls

------ Semaphore Limits --------

max number of arrays = 142

max semaphores per array = 250

max semaphores system wide = 32000

max ops per semop call = 100

semaphore max value = 32767

To check the shared memory configuration

[root@fahtestdb ~]# ipcs -lm

------ Shared Memory Limits --------

max number of segments = 4096

max seg size (kbytes) = 85983232

max total shared memory (kbytes) = 17179869184

min seg size (bytes) = 1

Legends

kernel.core_uses_pid If the parameter's the value 0, then a core dump file is simply named as core. If it is nonzero value, then the core dump file includes the process ID while naming the core file like core.PID

kernel.msgmni :This Parameter is used for system-wide limit on the number of message queue identifiers

kernel.msgmax :This parameter defines a system-wide limit specifying the maximum number of bytes in a single message written on a System V message queue

kernel.msgmnb :This parameter defines a system-wide parameter used to initialize the msg_qbytes setting for subsequently created message queues. The msg_qbytes setting specifies the maximum number of bytes that may be written to the message queue.

kernel.sem : This parameter contains 4 numbers defining limits for System IPC semaphores

[1]SEMMSL The maximum semaphores per semaphore set

[2]SEMMNS A system-wide limit on the number of semaphores in all semaphore sets

[3]SEMOPM The maximum number of operations that may be specified in a call.

[4]SEMMNI A system-wide limit on the maximum number of semaphore identifiers

kernel.shmmni This parameter defines the number of shared memory segment identifiers in the system

kernel.shmall This parameter specifies the total amount of shared memory[pages] that the system can use at one time

kernel.shmmax we need to specify the value of 1/2 of physical RAM

kernel.sysrq This parameter controls the functions allowed to be invoked by the SysRq Ke if the value is 1 meaning that every possible with SysRq

INSTALLING ORACLE DATABASE BINARY'S FOR FUSION APPLICATION'S DB

Download the Fusion applications binaries from the edelivery.oracle.com and unzip in to the directory

[root@fah ~]# cd /unziped_directory/installers/database/Disk1

Step 1

Run the install to start the gui of the database installer

Step 2

Provide the details MOS or Skip this step

Step 3

Select to install the database software only later we will create the database and configure

Step 5

In this process we had used the single instance so select the single instance to proceed the installation

Step 6

Select the necessary language

Step 7
Click the select options and Select the five components [mandatory] [this five components selection is mandatory if you are missing nay of this components then you will get error's in fusion applications provsioning

Step 8

Specify the ORACLE_BASE location and the ORACLE_HOME location

Step 9

Specify the user group according to o/s user which had been create earlier

Step 10

start the installation of binay's

Step 11

Run the root.sh script for the root user

Step 12

CREATING DATABASE FOR FUSION APPLICATIONS

Step 1

INIT PARAMETER'S FOR THE FUSION APPLICATIONS TRANSITIONAL DATABASE

[1]AQ_TM_PROCESSES
Purpose: enables time monitoring of queue messages. The times can be used in messages that specify delay and expiration properties. Values from 1 to 10 specify the number of queue monitor processes created to monitor the messages. If AQ_TM_PROCESSES is not specified or is set to 0, then the queue monitor is not created.
Recommended value [aq_tm_processes=10]

[2]AUDIT_TRAIL
Purpose enables or disables database auditing. [we need to disable the audit in the fadb]
Recommended Value audit_trail='NONE'

[3]PGA_AGGREGATE_TARGET
Purpose specifies the target aggregate PGA memory available to all server processes attached to the instance Default value will be 10 MB or 20% of the size of the SGA, whichever is greater
Recommend value pga_aggregate_target=8589934592 [9GB] it can be from [4 GB] to [9 GB] according to your environment

[4]SGA_TARGET
Purpose specifies the total size of all SGA components. If SGA_TARGET is specified, then the components of the SGA is automatically resized :
Recommended Value sga_target=19327352832 [it can be from 9 GB to 18 GB according to the environment ]

[5]DB_FILES
Purpose specifies the maximum number of database files that can be opened for this database
Recommended Value db_files=1024

[6]DB_RECOVERY_FILE_DEST_SIZE
Purpose specifies (in bytes) the hard limit on the total space to be used by target database recovery files created in the flash recovery area
Recommended Value db_recovery_file_dest_size=44040192000 [here we have used 40GB we can specify according to you env ]

[7]DISK_ASYNCH_IO
Purpose controls whether I/O to datafiles, control files, and logfiles is asynchronous (that is, whether parallel server processes can overlap I/O requests with CPU processing during table scans)
Recommended Value disk_asynch_io = FALSE

[8]FAST_START_MTTR_TARGET
Purpose enables you to specify the number of seconds the database takes to perform crash recovery of a single instance
Recommended Value fast_start_mttr_target=3600

[9] FILESYSTEMIO_OPTIONS
Purpose used for the purpose of enable or disable asynchronous I/O or direct I/O on file system files. This parameter is platform-specific and has a default value that is best for a particular platform. It can be dynamically changed to update the default setting.
FILESYTEMIO_OPTIONS can be set to one of the following values:
ASYNCH: enable asynchronous I/O on file system files, which has no timing requirement for transmission.
DIRECTIO: enable direct I/O on file system files, which bypasses the buffer cache.
SETALL: enable both asynchronous and direct I/O on file system files.
NONE: disable both asynchronous and direct I/O on file system files
Recommended Value filesystemio_options='Setall'

[10]JOB_QUEUE_PROCESSES
Purpose specifies the maximum number of processes that can be created for the execution of jobs
Recommended value job_queue_processes=100 [min 10 to max according to your env]

[11]LOG_CHECKPOINTS_TO_ALERT
Purpose writes the checkpoint accordance in the alert log file . Doing so is useful for determining whether checkpoints are occurring at the desired frequency
Recommended value log_checkpoints_to_alert=TRUE

[12]NLS_SORT
Purpose we we are setting the NLS_SORT rather than BINARY causes a sort to use a full table scan, regardless of the path chosen by the optimizer. BINARY is the exception because indexes are built according to a binary order of keys. Thus the optimizer can use an index to satisfy the ORDER BY clause when NLS_SORT is set to BINARY. If NLS_SORT is set to any linguistic sort, the optimizer must include a full table scan and a full sort in the execution plan Nls_sort is set to Binary for the improved performance of the ORDER BY quires
Recommended Value nls_sort='BINARY'

[13]OPEN_CURSORS
Purpose specifies the maximum number of open cursors (handles to private SQL areas) a session can have at once. You can use this parameter to prevent a session from opening an excessive number of cursors ..no of Cursors open is set to be 500 to 1000 according to you environment
Recommended Value open_cursors=1000

[14]PLSQL_CODE_TYPE
Purpose specifies the compilation mode for PL/SQL library units. .we need to set the value to the NATIVE PL/SQL library units (with the possible exception of top-level anonymous PL/SQL blocks) will be compiled to native (machine) code. Such modules will be executed natively without incurring any interpreter overhead
Recommended Value plsql_code_type='NATIVE'

[15]PROCESSES
Purpose Sets the maximum number of operating system processes that can be connected to Oracle concurrently. The value of this parameter must account for Oracle background processes. SESSIONS parameter is deduced from this value
Recommended Value processes=5000

[16]SESSION_CACHED_CURSORS
Purpose specifies the number of session cursors to cache. Repeated parse calls of the same SQL statement cause the session cursor for that statement to be moved into the session cursor cache. Subsequent parse calls will find the cursor in the cache and do not need to reopen the cursor. Oracle uses a least recently used algorithm to remove entries in the session cursor cache to make room for new entries when needed
Recommended Value session_cached_cursors=1000

[17]TRACE_ENABLED
Purpose it is used to controls tracing of the execution history, or code path, of Oracle
Recommended Value trace_enabled=FALSE

[18]TWO HIDDEN PARAMETERS SHOULD BE SPECIFIED FOR THE RELEASE 5 INSTILLATION

[I] Recommended Value b_tree_bitmap_plans=FALSE
[II] Recommended Value fix_control='5483301:OFF','6708183:ON'
Set the Dispatches to the null
[iii] Recommended Value dispatchers=''

[iv] shared_servers=0

This are the recommended parameter values for the transitional database for the large database setting and you can go through the installation guide for the more details on this parameter's http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e16600/provdbinstall.htm#CIHIAACB

Step 2

Configuring the database using the DBCA

start the from the terminal ./dbca

Step 1Select the Create Database for creating the new database

Step 2
Select the Custom database to Proceed Further

Step 3
Specify the database specify the global database name with the fully qualified value databasename.domainname

Step 4
Create the Listener if you want to configure the EM or proceed with the next step

Step 5
Use the common Password or specif for all the username which is mentioned [SYS,SYSTEM]

Step 6
provide the fast recover area size here we have provided above 40 GB

Step 7

Step 8

Specify the memory management sizes and the necessary initialization parameter values in this step

we need to select the AL32UTF8 and UTF8 character sets while specifying the character set

Step 9

Add another member to the redo log group and increase the size of of the redo log file to 2 GB and create 3 group's

Step 10

Increase the tablespace size for the below tablespace's

SYSTEM 10GB

SYSAUX 6GB

TEMP 10GB

UNDO 12GB with auto extend on

Step 11

Once the database is installed Successfully apply all the necessary patches for the fusion applications installation

Step 3

Parch the database with the necessary patches according to the release nodes of your version of fusion applications here we have specified the patches for the release 5 of fusion applications

Navigate to the staging directory of the fusion applications and navigate to installers--->database---->patches and you can identify all the related patches ..apply all the patches and do the post installation steps successfully

Totally there will be a 29 patches applied to the database verify the release notes for the additional patches

10263668 12772404 12985184 13365700 13503598 13787482 14029429 14574590

12312133 12880299 13014128 13382280 13508115 13790109 14058884

12358083 12889054 13073340 13404129 13714926 13983131 14110275

12672969 12977501 13257247 13454210 13775960 14019600 14143796

[orafadb@fah patch]$ /u03/app/oracle/product/11.2.0/dbhome_1/OPatch/opatch lsinv -patch_id

Invoking OPatch 11.2.0.1.7

Oracle Interim Patch Installer version 11.2.0.1.7

Oracle Home : /u03/app/oracle/product/11.2.0/dbhome_1

Central Inventory : /u03/app/oraInventory

from : /etc/oraInst.loc

OPatch version : 11.2.0.1.7

OUI version : 11.2.0.3.0

Log file location : /u03/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2013-01-22_14-15-43PM.log

Lsinventory Output file location : /u03/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/lsinv/lsinventory2013-01-22_14-15-43PM.txt

--------------------------------------------------------------------------------

Installed Top-level Products (1):

Oracle Database 11g 11.2.0.3.0

There are 1 products installed in this Oracle Home.

Interim patches (29) :

;;;;/

check all the 29 patches are applied

Step 4

Navigate to the staging directory and the find the apps_rcu

/<staging dir>/installers/apps_rcu/linux

Find the rcuHome_fusionapps_linux.zip and unzip the file in the apps_rcu directory

Navigate to the

/staging_dir/installers/apps_rcu/rcu/integration/fusionapps/export_fusionapps_dbinstall.zip

mkdir /tmp/rcu

cp export_fusionapps_dbinstall.zip /tmp/rcu

Navigate to the

</Staging_dir>/installers/apps_rcu/rcu/integration/biapps/schema/

cp otbi.dmp /tmp/rcu

Step 1
Navigate to the apps_rcu/bin

Step 2
select the create to create the RCU

Step 3
Specify the Hostname : <host name of the database server>
Port : <port used for the database>
Service Name : <fully qualified host name>
username : <sys>
Password : <password for the sys>
Role : SYSDBA