Wednesday, July 25, 2012

Oracle Applications Filesystem R12

Depending on the needs of a business and how the apps are installed the apps product directories may be located on a single machine or on multiple machines. OS environment settings locate different file locations on the database tier and application tier.


The top level applications directory structure is as below


  • the db-->apps_st-->data (DATA_TOP) directory is located on the database node machine, and contains the system tablespaces, redo log file, data tablespaces, index tablespaces, and database files
  • the db--->tech_st--->10.2.0 directory is located on the database node machine and contains the Oracle home for Oracle 10g database
  • the apps--->apps_st-->appl(APPL_TOP) contains product directories and files for Oracle Apps
  • the apps-->apps_st-->comn (COMMON_TOP) contains directories and files used across products
  • the apps-->tech_st-->10.1.2 directory contains the Oracle Home used for the Applications Technology stack tools components
  • the apps-->tech_st-->10.1.3 directory contains the Oracle Home used for the Applications technology stack Java components
Oracle APPS Env

Oracle apps uses env settings to find executable programs and other files required for apps operations. These settings are defined when you install Oracle APPS. Many of the setting are defined by the information you provide when running Rapid Install while others have the same values in all installations. 

Instance Home($INST_TOP)
Oracle R12 has introduced a top level directory called Instance Top. It provides the capability to share the application stack code and technology stack code across instances for instance test and development instance. It also provides the centralization of config log files making their management simpler.

The basic structure of Instance Home is -
<APPS_BASE>/inst/apps/<context>/<INST_TOP> where APPS_BASE is the top level of the Apps Installation and context is the highest level at which the application context exists
For instance
/d01/appmgr/inst/apps/dev1 where dev1 is the contextname


Instance Top is depicted as below



A key benefit of having an instance top is that Autoconfig no longer writes to the APPL_TOP or Oracle_Home directories so these can both be made read only file systems if required. In 11i the adpatch utility wrote to $APPL_TOP/admin on a patching/admin node. Under the new model $APPL_CONFIG_HOME/admin is used instead. $APPL_CONFIG_HOME will equate to a value such as /d01/applmgr/apps/apps_st/appl

Another advantage of instance home is that the log files can be stored centrally and therefore managed more easily. This is an important feature for security as log files could contain critical data. 

Log Files














Tuesday, July 24, 2012

Introducing OBIEE- Oracle Business Intelligence Enterprise Edition


Introducing OBIEE- Oracle Business Intelligence Enterprise Edition


OBIEE comes from Siebel Analytics which comes from an earlier acquisition of nQuire by Siebel in 2002.



By default, the Oracle Business Intelligence components are installed in a cluster configuration and are scalable.You cannot add Oracle Business Intelligence to an existing domain created by Oracle WebLogic Server or another Oracle Fusion Middleware product.

After running Oracle Business Intelligence 11g Installer, the installed products share the same Oracle Fusion Middleware infrastructure in a single WebLogic domain.
All Oracle Business Intelligence products intended for a WebLogic domain must be installed and configured at the same time. You cannot install some products now and then install others to the same WebLogic domain later.
For example, if you choose to install and configure Oracle Business Intelligence Enterprise Edition but not Oracle Real-Time Decisions, you cannot later add Oracle Real-Time Decisions to the WebLogic domain. Similarly, any WebLogic domains that contain Oracle Business Intelligence 11g products should not be extended later to include other Oracle Fusion Middleware products.


Installation

Type of installation

Type of installationPurposeDefinition
Simple InstallDemonstration and Evaluation
Single-User Development
Installation with the default settings on a single computer in the minimum number of steps
Enterprise InstallEnterprise Deployment
for Hosted Development
and Production
Enterprise Install type enables you to specify several more configuration settings than the simple
Software Only InstallEnterprise Deployment
for Highest Levels
of Availability and Security
Installation of the binary without configuration

To find the installers:
Downloads

For OBIEE Install Guide:
OBIEE INSTALL GUIDE



Installation on LINUX


Creation of the installer user
On Linux, running Oracle Business Intelligence 11g Installer as the root user is not supported.
[root@oel11g ~]# groupadd oinstall
  • Creation of the OBI User
[root@oel11g ~]# /usr/sbin/useradd obi -g oinstall
[root@oel11g ~]# passwd obi
Changing password for user obi.
New UNIX password:
BAD PASSWORD: it is WAY too short
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
Creation of the Middleware Home directory
mkdir -p /MiddlewareHome
chown -R obi:oinstall /MiddlewareHome
chmod -R 775 /MiddlewareHome
where
  • Linux - chown: Change owner to the user obi
  • chmod 775: Everything is allowed for the owner and read and execute access are allowed for everyone
Package
The prerequis verification of the installer will check all package. With an Oracle Database 11g installed, you need only to install onepackage (compat-db-4.1.25-9) that you can get from yum of from the installation DVD.
On yum, I found the package compat-db-4.2.52-5.1.i386.rpm that I have copied and installed from the tmp directory.
[root@oel11g tmp]# rpm -Uvh compat-db-4.2*
Preparing...                ########################################### [100%]
   1:compat-db              ########################################### [100%]
Set the File Handle Limit parameter
Set the hard and soft limit to the OBI user by modifying the file limits.conf such as for a database installation:
obi                 soft    nofile  4096
obi                 hard    nofile  65536
The maximum File-descriptor must be at least 4096
  • To discover the file-descriptor settings, run the command ulimit -a
  • Or set file-descriptor using the command ulimit -n 4096
[root@oel11g dev]# ulimit -a|grep open
open files                      (-n) 4096
Environment Variable
You can add them in the .bash_profile shell startup script of the obi user.
# File Descriptor Limit
ulimit -n 10240

# Database Parameters
ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export ORACLE_HOME
TNS_ADMIN=$ORACLE_HOME/network/admin
export TNS_ADMIN
PATH=$ORACLE_HOME/bin:/opt/bin:$PATH
export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH