title: Installing Oracle OIM_OIF 10g R3 link: https://onemoretech.wordpress.com/2007/03/10/installing-oracle-oim_oif-10g-r3/ author: lembobro description: post_id: 740 created: 2007/03/10 05:45:00 created_gmt: 2007/03/10 05:45:00 comment_status: open post_name: installing-oracle-oim_oif-10g-r3 status: publish post_type: post

Installing Oracle OIM_OIF 10g R3

… otherwise known as Oracle Identity Management 10g, Release 3 (10.1.4.0.1), which is a mouthful, even for an Oracle product.

Note: This article will be updated from time to time as I learn more about how these Oracle products fit together.

Previous versions of 10g Application Server included the Identity Management Infrastructure. With Release 3, it gets split off into it’s own distribution on 2 separate CD’s.

There are lots of little improvements that go into the new release, not the least of which is the update to database 10.1.0.5 and Application Server 10.1.2.0.2 that relieves you of the time-consuming task of patching up to these versions.

Before installing, it’s become my practice to add a special system user for the infrastructure, usually named “oracle”, whose primary group is dba (useradd -c "Oracle Apps User" -g dba oracle). This is the user I’ll do the install as. Make sure that this user has filesystem permissions to write to oraInventory and the infra application subdirectory.

Installing is pretty straightforward. If you use CentOS 4 as I do, you’ll need to either execute runInstaller with the “-ignoreSysPrereqs” switch or modify the /etc/redhat-release file by deleting the line referring to CentOS and substituting “Red Hat Enterprise Linux AS release 4” so that the installer will not abort because your system isn’t certified.

Assuming my install will be called “infra1”, this is how I would lay out the filesystem:

Oracle Base /u01/app/oracle
Oracle Inventory /u01/app/oracle/oraInventory
Oracle Home /u01/app/oracle/product/infra
Database files /u02/oradata/infra1

(the db instance was named “infra1”, which is also the SID)

Make sure to have root privileges on the server. There are a couple of scripts that need to be run as root during the install.

There may be kernel parameter changes that need to be done. These can be done dynamically using the sysctl utility, without rebooting the system. The Quick Install Guide has a nice section on how to do this under “Kernel Parameter Settings for OracleAS Metadata Repository”.

Thanks to the Energy Policy Act of 2005, every system on the planet needs to be patched to account for DST coming early this year, March 11 to be exact.

Oracle is no exception, and even though it was only release a little while ago, Identity Manager R3 also requires patching.

There are two basic patches that are needed, both only available to customers with support contracts, via MetaLink:

• 5865568, updates the Oracle JVM used by the App Server with the new timezone data.
• 5632264, replaces the old timezone data for the database and database clients.

Ah, let the games begin!

ADDENDUM: Linux Kernel Parameters, an example

These go in /etc/sysctl.conf and get bootstrapped with the /sbin/sysctl -p command. The values indicated below are valid for a Red Hat Enterprise (or CentOS) Linux 4 system:

`

# Params for Oracle Identity Infrastructure
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.msgmnb = 65535
kernel.msgmni = 2878
kernel.sem = 256 32000 100 142
fs.file-max = 131072
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 1048576
net.core.rmem_max = 1048576
net.core.wmem_default = 262144
net.core.wmem_max = 262144

`

Copyright 2004-2019 Phil Lembo