The Blog of Nenad

 Oracle is the leading business analytics software vendor by revenue, based on 2005 results, according to IDC's report Worldwide Business Analytics Software 2006-2010 Forecast and 2005 Vendor Shares. IDC's definition of business analytics software includes data warehousing platform, business intelligence tools, and packaged analytic applications.

Oracle leads the market in revenue, US$2.17 billion, and market share, 13.1%, with over $700 million more in revenue than the next closest vendor.

Hi everybody! I'll be back in two weeks, after a vacation with my family. Get ready for new batch of articles...

A) Pre-install:

NOTE: Do not use vnc connection to server to run Oracle installer

1. Check memory - at least 1GB for full install
$ grep MemTotal /proc/meminfo

2. Check disk space - at least 4.5GB
$ df -H

3. Check swap space - at least 1.5GB
$ grep SwapTotal /proc/meminfo

4. Check display capabilities - at least depths=8bits pp
$ /usr/X11R6/bin/xdpyinfo

5. Linux requirements

5a. software packages:
The minimum supported kernel and glibc versions are:
kernel 2.4.21-4-EL
glibc-2.3.2-95.3
Required versions of packages (same or newer required)
gcc-3.2.3-20
setarch-1.3-1
pdksh-5.2.14
openmotif21-2.1.30-8
gnome-libs-1.4.1.2.90-34.1
compat-glibc-7.x-2.2.4.32.5
compat-gcc-7.3-2.96.122
compat-libstdc++-7.3-2.96.122
compat-libstdc++-devel-7.3-2.96.122
compat-gcc-c++-7.3-2.96.122
sysstat-4.0.7

Execute this to determine if packages are present:
$ rpm -q setarch sysstat openmotif21 ORBit \
libpng10 gnome-libs compat-glibc compat-gcc compat-gcc-c++ \
compat-libstdc++ compat-libstdc++-devel

If packages are not installed then install them from:
* From RedHat AS3 Disk 2
$ cd /mnt/cdrom/RedHat/RPMS
$ rpm -Uvh setarch-1.3-1.i386.rpm
$ rpm -Uvh sysstat-4.0.7-4.i386.rpm

* From RedHat AS3 Disk 3
$ cd /mnt/cdrom/RedHat/RPMS
$ rpm -Uvh openmotif21-2.1.30-8.i386.rpm
$ rpm -Uvh ORBit-0.5.17-10.4.i386.rpm
$ rpm -Uvh libpng10-1.0.13-8.i386.rpm
$ rpm -Uvh gnome-libs-1.4.1.2.90-34.1.i386.rpm
$ rpm -Uvh compat-glibc-7.x-2.2.4.32.5.i386.rpm \
compat-gcc-7.3-2.96.122.i386.rpm \
compat-gcc-c++-7.3-2.96.122.i386.rpm \
compat-libstdc++-7.3-2.96.122.i386.rpm \
compat-libstdc++-devel-7.3-2.96.122.i386.rpm

Note: For Redhat 3.0, the equivalent version of openmotif 2.1.30-8 is
openmotif21-2.1.30-8. The openmotif21-2.1.30-8 package can be installed from disk number 3
of the Redhat 3.0 distribution by entering:
$ rpm -ivh openmotif21-2.1.30-8

5b. Check Linux release - should be "Red Hat Enterprise Linux AS release 3 (Taroon)"
$ cat /etc/issue

5c. Symbolic link for gc and g++:
Check:
$ cd /usr/bin
$ ls -l gcc g++
If these links do not exist, create them as follows:
1. Create a backup of the existing files:
$ mv /usr/bin/gcc /usr/bin/gcc.backup
$ mv /usr/bin/g++ /usr/bin/g++.backup
2. Create the symbolic links:
$ ln -s /usr/bin/gcc296 /usr/bin/gcc
$ ln -s /usr/bin/g++296 /usr/bin/g++

After this, "$ ls -l gcc g++" should give these links
... g++ -> /usr/bin/g++296
... gcc -> /usr/bin/gcc296

You can restore the original files if required, however you must recreate the links as
described in this procedure for Oracle Application Server to relink properly.

5d. If the hugemem kernel is used, set the architecture using following command:
$ setarch i386

6. Setup kernel parameters, limits and ports
6a. First check parameters and make a note of the current values and identify any values
that you must change:
$ /sbin/sysctl -a | grep sem
$ /sbin/sysctl -a | grep shm
$ /sbin/sysctl -a | grep msg
$ /sbin/sysctl -a | grep file-max
$ /sbin/sysctl -a | grep ip_local_port_range

6b. Then change them if necessary:
Add the following lines to the /etc/sysctl.conf file:
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 256 32000 100 142
fs.file-max = 131072
net.ipv4.ip_local_port_range = 20000 65000
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65535

Note: The semmns parameter should be set to the sum of the PROCESSES initialization
parameter for each Oracle database, adding the largest one twice, and then adding an
additional 10 for each database.
Note: If the current value for any parameter is higher than the value listed in this table,
do not change the value of that parameter

Run the following command to change the current kernel parameters:
$ /sbin/sysctl -p

Run the following command to check the current kernel parameters have been sucessfully changed:
$ /sbin/sysctl -a

6c. Set Shell Limits for the oracle User - Bourne or Bash Shell Limit:
Add the following lines to /etc/security/limits.conf file where -> represents the tab character:
* -> -> soft -> nproc -> -> 16384
* -> -> hard -> nproc -> -> 16384
* -> -> soft -> nofile -> -> 65536
* -> -> hard -> nofile -> -> 65536

Add the following line to the /etc/pam.d/login file, if it does not already exist:
session required /lib/security/pam_limits.so

Next, depending on the oracle user's default shell, make the following changes
to the default shell start-up file:
- For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file:
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 16384
else
ulimit -u 16384 -n 16384
fi
fi
-For the C or tcsh shell, add the following lines to the /etc/csh.login file:
if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 16384
endif

6d. Setup ports
In the default configuration of the operating system, the /etc/services file includes
ports 389 and 636 (for LDAP and LDAP/SSL). These happen to be the default ports for
Oracle Internet Directory. This means that if you want to use these port numbers for
Oracle Internet Directory, you must either delete or comment out these lines in
the /etc/services file. To comment out a line, add a # at the beginning of the line:

# ldap 389/tcp # Lightweight Directory Access Protocol
# ldap 389/udp # Lightweight Directory Access Protocol
# ldaps 636/tcp # LDAP protocol over TLS/SSL (was sldap)
# ldaps 636/udp # LDAP protocol over TLS/SSL (was sldap)

If you do not comment out or remove the lines from /etc/services, then the installer
will not assign ports 389 and 636. It assigns a number from the port number range for
Oracle Internet Directory.

7. Create oracle user, groups and Oracle directories:
7a. Check if Oracle inventory directory already exists on server:
check /etc/oraInst.loc file. This file lists the location of the inventory directory
and the group who owns it. If the file does not exist, the computer does not have
Oracle products installed on it.

7b. If necessary, create the new groups and users:
$ groupadd -g 500 oinstall
$ groupadd -g 501 dba
$ groupadd oper
$ useradd -u 502 -g oinstall -G dba oracle -s /bin/bash
$ passwd oracle

Check groups in which oracle user belongs:
$ groups oracle

7c. Create the directories in which the Oracle software will be installed:
$ mkdir -p /u01/app/oracle/product/10g_infra
$ mkdir -p /u01/app/oracle/product/10g_as
$ chown -R oracle.oinstall /u01

8. Apply patch no. 3006854: This patch creates the /etc/libcwait.so file and appends
the following line to the /etc/ld.so.preload file:
/etc/libcwait.so

$ su -
# cd /home/oracle/patch/oracle/3006854/
# chmod 777 rhel3_pre_install.sh
# ./rhel3_pre_install.sh

Note: Patch No.3006854 download from updates.oracle.com
$ wget ftp://metalink_user:password@updates.oracle/3006854/p3006854_9204_LINUX.zip

9. Setup of environment variables for installation:
9a. Check existing environment variables
$ env

9b. Check variables when su - check the environment variables when you are the new user
because the environment variables might not be passed to the new user:
$ /* root user */
$ su - oracle
$ env

9c. Setup variables if necessary:
ORACLE_HOME and ORACLE_SID - Does not matter (the installer unsets these two environment variables).

PATH, CLASSPATH, and Shared Library Path Environment Variables (LD_LIBRARY_PATH) - Must not contain
references to directories in any Oracle home directories

DISPLAY - Set it to the monitor where you want to the installer window to appear.
$ DISPLAY=test.mydomain.com:0.0; export DISPLAY
You can test the display by running the xclock program:
$ /usr/openwin/bin/xclock &

TMP and TMPDIR - Optional. If unset, defaults to /tmp.
$ TMP=/tmp2; export TMP
$ TMPDIR=/tmp2; export TMPDIR

TNS_ADMIN - Unset
$ unset TNS_ADMIN
Note: The /etc and the /var/opt/oracle directories must not contain a tnsnames.ora file.

ORA_NLS - Unset
$ unset ORA_NLS

LD_BIND_NOW (Linux Only) - Unset
$ unset LD_BIND_NOW

*** Example .bash_profile (only for installation, check out post-install section):
# Oracle Settings
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR

ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/904_infra; export ORACLE_HOME
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:$ORACLE_HOME/bin:$PATH; export PATH
PATH=$PATH:$ORACLE_HOME/dcm/bin:$ORACLE_HOME/opmn/bin; export PATH
PATH=$PATH:$ORACLE_HOME/Apache/Apache/bin; export PATH

export CLASSPATH
unset TNS_ADMIN
unset ORA_NLS
unset LD_BIND_NOW
...

You need to apply changes in .bash_profile (as oracle user in term window)
$ . .bash_profile

10. The /etc/hosts File:
The installer reads the /etc/hosts file to construct the location of the default
Identity Management realm. It displays this location in the "Specify Namespace in
Internet Directory" screen.

The /etc/hosts file should use the following format:
ip_address fully_qualified_hostname short_hostname
Example:
123.45.67.89 primaryHost.mydomain.com primaryHost
In the previous example, the location of the default Identity Management realm would look
like "dc=mydomain,dc=com".

If the file uses a different format, the installer displays an incorrect value in the
screen. For example, if the /etc/hosts contains:
123.45.67.89 primaryHost primaryHost.mydomain.com <--- incorrect format
the installer would display "dc=primaryHost,dc=com" as the default Identity Management realm.
This is probably not the value that you want for the default Identity Management realm.

11. Mount Oracle Application Server Installation CD:
CD should be auto-mounted, but just in case it doesn't:
$ mount -t iso9660 /dev/cdrom /mnt/cdrom

B) Installation:
1. Login as oracle user
2. Run the Oracle Universal Installer:
$ cd
$ mount_point/runInstaller

3a. If you plan to install both the OracleAS Metadata Repository and the Identity Management
components all on the same computer, select the "Identity Management and OracleAS Metadata
Repository" option.
3b. If you plan to install the infrastructure components on separate computers, you must
install them in this order:
1. Install the OracleAS Metadata Repository (You can have the installer create a new database
and populate it with the OracleAS Metadata Repository, or you can run the Oracle Application
Server Repository Creation Assistant ("OracleAS RepCA") to install the OracleAS Metadata
Repository in an existing database.
Note that you cannot register the OracleAS Metadata Repository with Oracle Internet Directory
at this point, because you do not have an Oracle Internet Directory yet. The registration is
done in the next step. )
2. Install the Identity Management components

Note: If you did not configure a component during installation (that is, you did not select
the component in the Select Configuration Options screen), you *can* configure some components
after installation. You *cannot* configure Oracle Internet Directory after installation.
You need to install and configure Oracle Internet Directory through the installer.

4. Installing OracleAS Infrastructure 10g:
4a. Start up the installer and complete the first few screens
4b. In the Select Installation Type screen, select Identity Management and OracleAS
Metadata Repository.
4c. Select Configuration Options:
Select Oracle Internet Directory.
Select OracleAS Single Sign-On.
Select Delegated Administration Services.
Select Oracle Directory Integration and Provisioning.
Select OracleAS Certificate Authority if you want to configure your own certificate
authority which can issue certificates for users and servers.
Do not select High Availability Addressing.
Click Next.
4d. Specify Namespace in Internet Directory:
Select the suggested namespace, or enter a custom namespace for the location of the
default Identity Management realm.
Note: The distinguished name (DN) that you specify on this screen will be designated as
the namespace in Oracle Internet Directory where users and groups are administered. Select
the suggested namespace if it meets your deployment requirements. If not, enter a DN that
you want in the custom namespace field. The installer determines the suggested namespace
from the /etc/hosts file.
4e. OracleAS Certificate Authority screens:
Note: Only if you select OracleAS Certificate Authority in the Select Configuration
Options screen, the installer displays screens where you need to enter OracleAS Certificate
Authority information.
Note: Note that you cannot install more than one OracleAS Certificate Authority against the same
OracleAS Metadata Repository.
4e1. Select OracleAS Metadata Repository:
This screen appears only if you are configuring OracleAS Certificate Authority and you
are using an existing Oracle Internet Directory and you are using an existing OracleAS
Metadata Repository. The Oracle Internet Directory must contain the registration for
the OracleAS Metadata Repository that you want to use.
Select the OracleAS Metadata Repository that you want OracleAS Certificate Authority to use.
Click Next.
4e2. Specify OCA Distinguished Name:
Typical DN: Use this section if your DN uses only the attributes listed in this section.
You do not have to fill in all the attributes specified in this section. Only
the o (organization) attribute is required. Note that the (single quote) character
is not a valid character in any of the attributes.
Common name (cn): Enter the name that you want on the certificate. This name must be
different from your hostname. Example: John Doe.
Organizational unit (ou): Enter the name of your division or department. Example: Sales.
Organization (o): Enter the name of your company or organization. Example: Oracle.
Country (c): Select your country from the drop-down list.
Custom DN: If your DN uses attributes not listed in the Typical DN section, specify
your DN in this section.
Click Next.
4e3. Select OCA Key Length:
Key Length (bits): Select the key length used in RSA algorithm to sign all certificates
issued by OracleAS Certificate Authority. Oracle recommends that you use at least
a 2048-bit key length. Longer key lengths provide greater security, but require
more time to issue each new certificate.
Click Next.
4e4. Specify OCA Administrators Password:
You need this password to manage OracleAS Certificate Authority. This password is
also used by the OracleAS Certificate Authority Configuration Assistant.
You can change the password after installation using the ocactl command. See the OracleAS Certificate Authority Online Help for details.
Click Next.
4f. Oracle9i Database screens:
Enter information for the OracleAS Metadata Repository database.
4f1. Specify Database Identification:
Global Database Name: Enter a name for the OracleAS Metadata Repository database.
Append the domain name of your computer to the database name.
Example: asdb.mydomain.com
SID: Enter the system identifier for the OracleAS Metadata Repository database. Typically
this is the same as the global database name, but without the domain name. The SID must
be unique across all databases. The SID cannot be longer than eight characters.
Example: asdb
Click Next.
4f2. Use default values from now on
4g. Specify OracleAS Instance Name and ias_admin Password

5. Post Infrastructure Installation
On completion of the infrastructure installation connect to the Enterprise Manager
Website (http://:1810) using the username "ias_admin" and
the password you assigned during the installation. If EM is not available start it with
the "emctl start iasconsole" command. Check that all the components are started before
proceeding to the portal installation.

6. Installing Portal and Wireless or Business Intelligence and Forms
6a. Install in different oracle home than infrastructure

# posted by Gospodar Finansija @ 10:39 AM 0 comments

If you do not have enough space in the /tmp directory, you can temporarily create a tmp directory in another filesystem. Here is how you can do this:

# su - root
# mkdir //tmp
# chown root.root //tmp
# chmod 1777 //tmp
# export TEMP=/ # used by Oracle
# export TMPDIR=/ # used by Linux programs like the linker "ld"

When you are done with your Oracle installation, shutdown Oracle and remove the temporary directory:

# su - root
# rmdir //tmp
# unset TEMP
# unset TMPDIR

This one is simple:

Log on to Oracle RMAN and type:
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;

That's it!

0. Requirements
To check the memory, recommended 512 MB
# grep MemTotal /proc/meminfo

To check the swap space, run:
# cat /proc/swaps

The Oracle Universal Installer requires up to 400 MB of free space in the /tmp directory. To check the space in /tmp, run:
# df /tmp

Disk Space: you will need about 2.5 GB for the database software. If you perform a typical database installation and not a customized database installation, then you will need about 3.5 GB of disk space.

1. Environment & system
- Required kernel parameters
SEMMNI 100 Defines the maximum number of semaphore sets in the entire system.
SEMMNS 256 Defines the maximum semaphores on the system. This setting is a minimum recommended value, for initial installation only. The SEMMNS parameter should be set to the sum of the PROCESSES parameter for each Oracle database, adding the largest one twice, and then adding an additional 10 for each database.
SEMOPM 100 Defines the maximum number of operations for each semop call.
SEMMSL 100 Defines the minimum recommended value, for initial installation only.
SHMMAX Set this parameter to half the size of physical RAM available on your system. This value cannot exceed 4294967295
SHMMNI 100 Defines the maximum number of shared memory segments in the entire system.
SHMALL 2097152 Defines the maximum total shared memory system wide.

- Modify your kernel settings in /etc/sysctl.conf (RedHat) as follows:
- Example settings, good for 10g also ---------------
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
kernel.hostname = rhl4.pkurs.com #<--- full qualified hostname !!
kernel.domainname = pkurs.com #<--- correct domain name !!
fs.file-max = 327679
-----------------------------------------------------

- Apply new kernel settings to current session with
# sysctl -p
- Run the following command to check the current kernel parameters have been sucessfully changed
# sysctl -a
- Hostname command should return the fully qualified hostname as shown below
# hostname
hostname.domainname
- If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.
- The oracle account used to install Oracle 9.2.0.1, should not have the Oracle install related variables set by default. For example setting ORACLE_HOME, PATH, LD_LIBRARY_PATH to include Oracle binaries in .profile, .login file and /etc/profile.d should be completely avoided.

2a. Packages
rpm -q make \
compat-db \
compat-gcc-32 \
compat-gcc-32-c++ \
compat-oracle-rhel4 \
compat-libcwait \
compat-libgcc-296 \
compat-libstdc++-296 \
compat-libstdc++-33 \
gcc \
gcc-c++ \
gnome-libs \
gnome-libs-devel \
libaio-devel \
libaio \
make \
openmotif21 \
xorg-x11-deprecated-libs-devel \
xorg-x11-deprecated-libs \
ORBit-devel \
gtk+-devel \
imlib-devel \
glib-devel

*** libaio-devel CD3
*** gnome-libs-devel CD4
*** ORBit-devel CD4
*** glib-devel CD4
*** gtk+-devel CD4
*** imlib-devel CD4

2b. The compat-oracle-rhel4-1.0-3 and compat-libcwait-2.0-1 packages are available from Oracle Metalink Patch 4198954. Install them now.
While installing the patch you might receive the warning. It is a normal behaviour.
- warning ---------
rpm -ivh compat-libcwait-2.0-2.i386.rpm
Preparing... ########################################### [100%]
cat: /etc/ld.so.preload: No such file or directory
1:compat-libcwait ########################################### [100%]
-------------------

3. Creating Oracle User Accounts
su - root
groupadd dba # group of users to be granted with SYSDBA system privilege
groupadd oinstall # group owner of Oracle files
useradd -c "Oracle software owner" -g oinstall -G dba oracle
passwd oracle

4. Creating Oracle Directories
su - root
mkdir -p /u01/app/oracle/product/9.2.0
chown -R oracle.oinstall /u01
mkdir /var/opt/oracle
chown oracle.dba /var/opt/oracle
chmod 755 /var/opt/oracle

5. Setting Oracle Environments
export LD_ASSUME_KERNEL=2.4.19
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/9.2.0
export ORACLE_SID=orcl
export ORACLE_TERM=xterm
export NLS_LANG=AMERICAN;
export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
export LD_LIBRARY_PATH
export PATH=$PATH:$ORACLE_HOME/bin

6. Start runInstaller
as root
# mount /mnt/cdrom
as oracle
$ /mnt/cdrom/runInstaller
- During the linking phase you might recieve the error if you have installed the agent. To overcome this problem. Please apply the Patch 3119415. (OPATCH utility needed)
- Also some "ins_ctx.k" file problem
- Also some "Apache/ports.ini" problem

7. Post Installation
7a. Before installing 9.2.0.5.0 Patchset, do the following:
7a1. Edit the /Disk1/install/oraparam.ini file supplied with the 9.2.0.5 patchset so that the line:
Linux=redhat-2.1,UnitedLinux-1.0,redhat-3,SuSE-7,SuSE-8
is changed to:
Linux=redhat-2.1,UnitedLinux-1.0,redhat-3,redhat-4,SuSE-7,SuSE-8
7a2. Now OUI 10.1.0.2 will start from /Disk1 (the 9.2.0.5 patchset staging area)
7a3. Install OUI 10.1.0.2 in main 9.2 ORACLE_HOME
7a. Install 9.2.0.5.0 Patchset, using installer from 9.2.0.5 Patchset shiphome
7b. Before installing the 9.2.0.6.0 patchset, you must download the Patch 4188455. To apply the patch:
7b0. Deinstall old OUI 2.2.0.10 from ORACLE_HOME (NOT NECESSARY)
7b1. Extract the patch 4188455 to a temp location, say, /tmp
7b2. Run the installer from the DB 9206 patchset shiphome with the argument -paramFile .
7b3. Install new OUI 10.1.0.3.0 in ORACLE_HOME using OUI from PatchSet 9.2.0.6.0 distribution. Newly installed OUI doesn't work from ORACLE_HOME.
7c. Install Patchset 9.2.0.6.0 using OUI from PatchSet 9.2.0.6.0 distribution.
*** Error linking ins_oemagent.mk
7d. After installing the 9.2.0.6.0 patchset, you should apply the Patch 4190568.
7e. Edit .bash_profile and add
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/9.2.0
export ORACLE_SID=orcl
export PATH=$ORACLE_HOME/bin:$PATH
8. Database creation with dbca utility: before using dbca, do the following (as root)
# touch /etc/rac_on
*** ORA-29807 encoutered while "Creating data dictionary views" - Ignored as advised on Metalink Note 237486.1

# posted by Gospodar Finansija @ 10:01 AM 0 comments

Let's assume that new hard drive is istalled as /dev/sdc. Following actions perform as root.

# fdisk /dev/sdc

Format as ext3 filesystem
# mkfs -t ext3 /dev/sdc

# cd /
# mkdir u02

Mount new drive on mount point /u02
# mount /dev/sdc /u02

Then add a line in /etc/fstab for example, where "3" is next available number:
#/dev/sdc /u02 ext3 defaults 1 3

Requirements
------------
The system must meet the following minimum hardware requirements:
* At least 1024 MB of physical RAM
* The following table shows the relationship between the available RAM and the required swap space.
Available RAM Swap Space Required
Between 1024 MB and 2048 MB 1.5 times the size of RAM
Between 2049 MB and 8192 MB Equal to the size of RAM
More than 8192 MB 0.75 times the size of RAM
* 400 MB of disk space in the /tmp directory
* Between 1.5 GB and 3.5 GB of disk space for the Oracle software, depending on the installation type
* 1.2 GB of disk space for a preconfigured database that uses file system storage (optional)


Pre-Install
-----------
NOTE: Tasks to perform as root user
- Check Hardware Requirements:
1. To determine the physical RAM size, enter the following command:
# grep MemTotal /proc/meminfo
2. To determine the size of the configured swap space, enter the following command:
# grep SwapTotal /proc/meminfo
3. To determine the amount of free disk space available in the /tmp directory, enter the following command:
# df -k /tmp
4. To determine the amount of free disk space available on the system, enter the following command:
# df -H
5. To determine whether the system architecture can run the software, enter the following command:
# grep "model name" /proc/cpuinfo
- Check Software Requirements
6. To determine which version of the operating system is installed, enter the following command:
# cat /etc/issue
7. To determine whether the required kernel is installed, enter the following command :
# uname -r
8. To determine whether the required packages are installed, enter commands similar to the following:
# rpm -q
The following packages (or later versions) must be installed:
make-3.79.1
gcc-3.2.3-34
glibc-2.3.2-95.20
compat-db-4.0.14-5 (*)
compat-gcc-7.3-2.96.128
compat-gcc-c++-7.3-2.96.128
compat-libstdc++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
openmotif21-2.1.30-8 (*)
setarch-1.3-1
If packages are not installed then install them from:
* From RedHat AS3 Disk 2
$ cd /mnt/cdrom/RedHat/RPMS
$ rpm -Uvh setarch-1.3-1.i386.rpm
* From RedHat AS3 Disk 3
$ cd /mnt/cdrom/RedHat/RPMS
$ rpm -Uvh openmotif21-2.1.30-8.i386.rpm
$ rpm -Uvh compat-glibc-7.x-2.2.4.32.5.i386.rpm \
compat-gcc-7.3-2.96.122.i386.rpm \
compat-gcc-c++-7.3-2.96.122.i386.rpm \
compat-libstdc++-7.3-2.96.122.i386.rpm \
compat-libstdc++-devel-7.3-2.96.122.i386.rpm \
compat-db-4.0.14-5.i386.rpm
NOTE: (RHEL 4.0) cdrom drive is acesible through mount point /media and NOT /mnt/cdrom
NOTE: (RHEL 4.0) Needed also is libaio-0.0.96.i386.rpm (From RedHat AS4 Disk 3)
9. Creating Required Operating System Groups and Users. If necessary, enter the following commands to create the oinstall and dba groups:
# groupadd oinstall
# groupadd dba
10. To determine whether the oracle user exists and belongs to the correct groups, enter the following command:
# id oracle
If necessary, complete one of the following actions:
- If the oracle user exists, but its primary group is not oinstall or it is not a member of the dba group, then enter the following command:
# /usr/sbin/usermod -g oinstall -G dba oracle
- If the oracle user does not exist, enter the following command to create it:
# /usr/sbin/useradd -g oinstall -G dba -u 501 oracle
This command creates the oracle user and specifies oinstall as the primary group and dba as the secondary group.
11. Enter the following command to set the password of the oracle user:
# passwd oracle
12. Configuring Kernel Parameters
12a. If the value of any kernel parameter is different from the recommended value, then complete the following steps: Using any text editor, create or edit the /etc/sysctl.conf file and add or edit lines similar to the following:
Note: Include lines only for the kernel parameter values that you want to change. For the semaphore parameters (kernel.sem), you must specify all four values. However, if any of the current values are larger than the recommended value, specify the larger value.
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144
12b. Apply new kernel settings to current session with :
# sysctl -p
12c. Run the following command to check the current kernel parameters have been sucessfully changed:
# sysctl -a
13. Set Shell Limits for the oracle User
13a. Set Shell Limits for the oracle User - Bourne or Bash Shell Limit:
Add the following lines to /etc/security/limits.conf file where -> represents the tab character:
* -> -> soft -> nproc -> -> 16384
* -> -> hard -> nproc -> -> 16384
* -> -> soft -> nofile -> -> 65536
* -> -> hard -> nofile -> -> 65536
13b. Add the following line to the /etc/pam.d/login file, if it does not already exist:
session required /lib/security/pam_limits.so
13c.Next, depending on the oracle user's default shell, make the following changes
to the default shell start-up file:
- For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file:
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 16384
else
ulimit -u 16384 -n 16384
fi
fi
- For the C or tcsh shell, add the following lines to the /etc/csh.login file:
if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 16384
endif
14. Create the directories in which the Oracle software will be installed:
# mkdir -p /u01/app/oracle/product/10gr2
# chown -R oracle.oinstall /u01
NOTE: Tasks to perform as oracle user
15. Unset variables
$ unset ORACLE_HOME
$ unset TNS_ADMIN

Installation
------------
Start Oracle Universal Installer and install only Oracle software.

Post-Install
------------
1. Edit .bash_profile and add
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/10.1.0/db_1
export ORACLE_SID=orcl
export PATH=$ORACLE_HOME/bin:$PATH
2. If when starting listener with
$ lsnrctl start
you get "Linux error 29: Illegal Seek" then edit listener.ora and add line
SUBSCRIBE_FOR_NODE_DOWN_EVENT_=OFF

It's quite simple, in fact.

# cd /
# ls -lR | sort +4n

Note that this is a lengthy operation!

To add a swap file:
1. Determine the size of the new swap file and multiple by 1024 to determine the block size. For example, the block size of a 64 MB swap file is 65536.
2. At a shell prompt as root, type the following command with count being equal to the desired block size:
# dd if=/dev/zero of=/swapfile bs=1024 count=65536
3. Setup the swap file with the command:
# mkswap /swapfile
4. To enable the swap file immediately but not automatically at boot time:
# swapon /swapfile
5. To enable it at boot time, edit /etc/fstab to include:
/swapfile swap swap defaults 0 0
The next time the system boots, it will enable the new swap file.
6. After adding the new swap file and enabling it, make sure it is enabled by viewing the output of the command cat /proc/swaps or free.

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

To disable the temporary swap space execute the following commands:

1.
# su - root
2.
# swapoff swapfile
3.
# rm swapfile

Here are two scripts that can be used for starting and stopping Oracle Collaboration Suite 10g Infrastructure and Applications.

Script ocsi starts/stops infrastructure, while ocsa starts/stops applications tier. Those scripts can be installed as RedHat services for automatic starting and stopping of OCS.

You need to set ORACLE_BASE and ORACLE_HOME variables to values required by your server.

ocsi
-------------------------------------------------------------------
#!/bin/bash
#
# chkconfig: 35 94 1
# description: init script to start/stop OCS 10g Infrastructure
#
#
# match these values to your environment:
export ORACLE_BASE=/u01/app
export ORACLE_HOME=$ORACLE_BASE/product/10.1.2/infra
export ORACLE_TERM=xterm
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/opmn/bin:$PATH
export ORACLE_SID=infra
export ORACLE_USER=oracle

# see how we are called:
case $1 in
start)
su - "$ORACLE_USER"<<EOO
lsnrctl start
sqlplus /nolog<<EOS
connect / as sysdba
startup
EOS
# emctl start dbconsole
opmnctl startall
sleep 20
EOO
;;

stop)
su - "$ORACLE_USER"<<EOO
lsnrctl stop
sqlplus /nolog<<EOS
connect / as sysdba
shutdown immediate
EOS
emctl stop dbconsole
opmnctl stopall
sleep 20
EOO
;;

*)
echo "Usage: $0 {start|stop}"
;;
esac
-------------------------------------------------------------------


ocsa
-------------------------------------------------------------------
#!/bin/bash
#
# chkconfig: 35 95 1
# description: init script to start/stop OCS 10g Applications
#
#
# match these values to your environment:
export ORACLE_BASE=/u01/app
export ORACLE_HOME=$ORACLE_BASE/product/10.1.2/apps
export ORACLE_TERM=xterm
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/opmn/bin:$ORACLE_HOME/ocas/bin:$PATH
export ORACLE_SID=infra
export ORACLE_USER=oracle

# see how we are called:
case $1 in
start)
tnslsnr listener_es -user 502 -group 500 &

su - "$ORACLE_USER"<<EOO
opmnctl startall
sleep 20
ocasctl -startall
sleep 20
EOO
;;

stop)
su - "$ORACLE_USER"<<EOO
lsnrctl stop listener_es
emctl stop dbconsole
sleep 20
opmnctl stopall
sleep 20
ocasctl -stopall
sleep 20
EOO
;;

*)
echo "Usage: $0 {start|stop}"
;;
esac

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

Oracle Collaboration Suite 10g (10.1.2.2.0) on RedHat Linux AS 3.0
==================================================================

NOTE: Oracle Collaboration Suite Infrastructure and Applications Installation on a Single Computer
NOTE: For Oracle Collaboration Suite Infrastructure and Applications installation on a single computer, 2 GB or more is recommended.

1. Disk Space: recommended total of 19GB, /tmp 250MB
Check disk space with
# df -kH

2. Swap Space: min 1.5GB
Check swap space with
# grep SwapTotal /proc/meminfo

3. Check that Red Hat Enterprise Linux AS/ES 3.0 is installed:
# cat /etc/issue
3a. The minimum supported kernel versions are: kernel-2.6.9-11.EL, kernel-smp-2.6.9-11.EL, kernel-hugemem-2.6.9-11.EL
Check for kernel version with
# rpm -qa | grep kernel

4. Check that the following software packages, or later versions, are installed:

glibc-2.3.2-95.30
glibc-common-2.3.2-95.30
binutils-2.14.90.0.4-35
compat-glibc-7.x-2.2.4.32.6
compat-libstdc++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
gcc-3.2.3-47
gcc-c++-3.2.3-47
libstdc++-3.2.3-47
libstdc++-devel-3.2.3-47
openmotif21-2.1.30-8
pdksh-5.2.14-21
setarch-1.3-1
make-3.79.1-17
gnome-libs-1.4.1.2.90-34.2
sysstat-5.0.5-5.rhel3 (*CD 3)
compat-db-4.0.14-5.1

Check packages with
# rpm -q glibc \
glibc-common \
binutils \
compat-glibc \
compat-libstdc++ \
compat-libstdc++-devel \
gcc \
gcc-c++ \
libstdc++ \
libstdc++-devel \
openmotif21 \
pdksh \
setarch \
make \
gnome-libs \
sysstat \
compat-db

5. Kernel
kernel.shmall = 3279547
kernel.shmmax = 2147483648
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 256 32000 100 142
fs.file-max = 327679
net.ipv4.ip_local_port_range = 10000 65000
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65535

By specifying the values in the /etc/sysctl.conf file, you ensure that they persist when you restart the system.

# /sbin/sysctl -p

6. Add the following lines to /etc/security/limits.conf file:

* soft nproc 4096
* hard nproc 16384
* soft nofile 4096
* hard nofile 65536

7. Add the following line to the /etc/pam.d/login file, if it does not already exist:

session required /lib/security/pam_limits.so

8. Depending on the default shell of the oracle user, make the following changes to the default shell startup file:

For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file:

if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi


For the C or tcsh shell, add the following lines to the /etc/csh.login file:

if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
endif

9. Check port 1521
# netstat -an | grep 1521

10. Hosts: The /etc/hosts file should use the following format:
ip_address fully_qualified_hostname short_hostname

Example:
123.456.789.99 ocs.mydomain.com ocs

10. Create directories
# mkdir -p /u01/app/product/10.1.2/apps
# mkdir -p /u01/app/product/10.1.2/infra
# chown -R oracle.oinstall /u01

11. Install OCS Infrastructure

12. Install OCS Applications

Patchset 10.1.2.2.0
-------------------

1. Patch 4892455 - Apps tier
Stop Calendar Server
# $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=CalendarServer
# . oraenv
# opatch apply
# $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=CalendarServer

2. Patch 4898766 - Apps Tier
# . oraenv
# $ORACLE_HOME/ocas/bin/ocasctl -stopall
# opatch apply
# $ORACLE_HOME/ocas/bin/ocasctl -startall

3. Patch 5007932 - Infra tier
Check infrastructure DB Version with 'select * from v$version;'
# . oraenv
# opatch apply

Stop App tier components
# $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=email
# $ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=OC4J_Mail
# $ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=OC4J_OCSClient

Load es_patch_10.1.2.2.sql package as the es_mail database user. (infra)
# cd $ORACLE_HOME/oes/install/sql
# sqlplus es_mail/manager1
# SQL> @es_patch_10.1.2.2.sql

Load esserver.jar and esmesg.jar into the es_mail schema:
# $ORACLE_HOME/bin/loadjava -f -v -r -user "es_mail/manager1" $ORACLE_HOME/jlib/esserver.jar
#$ORACLE_HOME/bin/loadjava -f -v -r -user "es_mail/manager1" $ORACLE_HOME/jlib/esmesg.jar

Recompile all invalid objects as the sys database user. Execute the following commands in the Oracle Collaboration Suite Database (Oracle Mail Database) Oracle_Home:

# cd $ORACLE_HOME/rdbms/admin
# $ORACLE_HOME/bin/sqlplus sys/@ as sysdba
# SQL> @utlrp.sql

Do not start Apps tier components

4. Patch 4949529 - Apps tier
# . oraenv
# opatch apply

Use the Mail Administration page to modify an IMAP property:
Log in to the Oracle Enterprise Manager Collaboration Suite Control console of the Oracle Mail Applications tier. For example: http://appstiername.com:1810
Log in as ias_admin
On the Farm page, click the Applications tier Oracle Application Server instance name. For example: inst1.appstiername.com
On the Oracle Collaboration Suite Control Home page, click Mail Application in the System Components table.
Click IMAP Server on the Service Targets table.
Click Default Settings.
Modify the Public Folder Cache Refresh Interval (min) value, setting it to 1440.
Click Apply. A confirming message appears.
Click Mail Application.
Select the IMAP Server radio button.
Click Stop.
Click Start.


When patching the FIRST Applications tier, upload oes10122patchsetupgrade.ldif into the Infrastructure Oracle Internet Directory. To do this, run the following command under $ORACLE_HOME:
$ORACLE_HOME/bin/ldapmodify -c -v -a -D"cn=orcladmin" -w -h -p -f $ORACLE_HOME/oes/bin/oes10122patchsetupgrade.ldif

Restart all protocol servers and OPMN instances:
# $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=email
# $ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OC4J_Mail
# $ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OC4J_OCSClient

Restart the Applications tier Oracle Enterprise Manager:
# $ORACLE_HOME/bin/emctl stop iasconsole
# $ORACLE_HOME/bin/emctl start iasconsole

5. Patch 4957487 - Apps tier
# . oraenv
# opatch apply

Stop OPMN using the following command:
# $ORACLE_HOME/opmn/bin/opmnctl stopall

Start OPMN using the following command:
# $ORACLE_HOME/opmn/bin/opmnctl startall

6. Patch 4924473 - Apps tier
# . oraenv
Oracle recommends that the OC4J_OCSClient instance be shut down before applying this patch. This can be done using OPMN; for example:
# $ORACLE_HOME/opmn/bin/opmnctl stopproc gid=OC4J_OCSClient
This patch also stops some other Application tier components during patching process (Portal, Web Cache, HTTP server). After patching is done, stopped components are started again.

Apply patch
# opatch apply -pre oid_su oid_pwd -opatch_pre_end -post oid_su oid_pwd -opatch_post_end
oid_su is the Oracle Internet Directory superuser (such as cn=orcladmin)

7. Patch 4924895 - Apps tier
# . oraenv
# opatch apply

8. Patch 4930030 - Apps tier
# . oraenv

Create an entry in your $MIDTIER_ORACLE_HOME/network/admin/tnsnames.ora that defines the connection details to the Oracle Collaboration Suite mailstore database for the internal Discussions administrator user owning Discussions folders (its username is discussions_ where is the Oracle Mailstore database SID). The mailstore is the database where the ES_MAIL schema used by Discussions stores data. A sample tnsnames.ora entry is shown below. Refer to Oracle Documentation Net Service Reference for more details on the tnsnames.ora syntax.

OCSMAILSTORE = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = myhost.mycompany.com) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dbsid.mycompany.com) ) )

Collect the following pieces of information prior to applying the patch. You will need this information to successfully apply the patch:
- The net service name (as defined in the tnsnames.ora file, "OCSMAILSTORE" in the preceding example) that defines the connection to the mailstore database. This is referred to as .
- The password for the "sys" user in the mailstore database. This password is referred to as .
- Oracle Internet Directory (OID) hostname, referred as , OID port referred as , OID administrator username referred as , and finally OID administrator password referred as .

Verify that the Oracle Collaboration Suite Infrastructure and Oracle Collaboration Suite mailstore database are running. Make sure that the OC4J process where the Discussions application is deployed (by default OC4J_OCSClient) is running on the Applications tier. You may leave other middle tier processes (such as OPMN, Webcache and Oracle Collaboration Suite Control (Enterprise Manager)) running.

Apply patch
# opatch apply -pre -dbconn -dbpwd -opatch_pre_end -post -oidhost -oidport -oidusr -oidpwd

9. Patch 4912230 - Apps tier
# . oraenv

Verify that the Oracle Collaboration Suite Infrastructure and Workspaces Database are up and running. Make sure that the OC4J process where the Workspaces application is deployed (by default OC4J_OCSClient) is running on the Applications tier. You may leave other middle tier processes (such as OPMN, Webcache and Oracle Collaboration Suite Control (Enterprise Manager)) running.

Apply patch (see previous patch notes for details)
# opatch apply -pre –dbconn -dbpwd -opatch_pre_end -post –oidhost -oidport -oidusr -oidpwd

10. Patch 4928124 - Apps tier
Stop the Oracle Content Services processes running on all Applications Tiers, as follows:
- Using a browser, access the following URL:
http://Applications_tier_host_name:port
For example, http://myserver.mycompany.com:1156.
- Enter the authentication information for the ias_admin user.
- Click your Applications Tier instance. The page refreshes to display all the Oracle Collaboration Suite components.
- Click the Content component or the component that corresponds to the Oracle Content Services instance.
- In the page corresponding to Oracle Content Services, click Stop Domain. (Node)
- Click OK on the confirmation page.

Ensure that the infrastructure and database instances are running

Type the following at the UNIX prompt to verify that these UNIX commands are available in the path and have no aliases attached to them. If there are aliases, the application of the patch may fail.
The expected response will indicate the path to the UNIX command. For example, /usr/bin/cp.
which cp
which rm
which sed
which find
which mkdir
which dirname
which zip
which unzip

# . oraenv
Apply the patch
# opatch apply
(You can track patch progress with # tail -f /u01/app/product/10.1.2/apps/content/log/Patch.log)

11. Patch 4947127
# . oraenv

Portal Schema Password
The portal schema password is required in the upgrade process. You can look up the Portal schema password using the following procedure:
- Start Oracle Directory Manager:
# $ORACLE_HOME/bin/oidadmin &
- Enter the name of the Infrastructure host running the Oracle Internet Directory instance used by Oracle Collaboration Suite Portlets.
- Log in using the orcladmin account.
- Navigate the following links:
Entry Management|cn=OracleContext|Products|IAS|IAS Infrastructure Databases|orclReferenceName=|OrclResourceName=PORTAL
The Portal schema password is the value of the orclpasswordattribute property. Make a note of the password, for use during the patch process.

Stop the OC4J Portal process
# $ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=OC4J_Portal

Apply patch
# opatch apply

Execute script
# $ORACLE_HOME/ocsprovs/bin/ocsprovs_installer.sh -mode packages -p portal -ps -c infra.dbhost.com:1521:sid -ouser -opass -ipass

for example
# $ORACLE_HOME/ocsprovs/bin/ocsprovs_installer.sh -mode packages -p portal -ps Xj0H00wr -c ocs.parallel.co.yu:1521:orcl -ouser cn=orcladmin -opass manager1 -ipass manager1

Start the OC4J Portal process
# $ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OC4J_Portal

==================================================================

Stop everything and backup software installation and database.
Installation:
# tar -cvf fullbck.tar /u01/app/oracle/*
System Files
# tar -cvf sys.tar /etc/ora* /usr/local/bin/*env /usr/local/bin/dbhome

==================================================================

SETUP OF WORKFLOW MAILER
------------------------

To configure the Oracle Workflow notification mailer:

1. Create an e-mail account for the notification mailer administrator (for example, wfadmin). The workflow account you create should only be used by the notification mailer system. Concurrent connections to this account are not allowed.
2. Create three folders for this e-mail account: one to use as an inbox, one to store processed messages, and one to store discarded messages. The default values for these folders in the notification mailer configuration wizard are INBOX, PROCESS, and DISCARD.
3. Ensure that all Oracle Workflow and e-mail server processes are running.
4. Access the Oracle Collaboration Suite Control on the computer where Oracle Workflow is running and go to the Collaboration Suite Home page.
5. In the System Components table, click Oracle Workflow.
6. On the Workflow Home page, click Service Components in the Related Links: Configuration section.
7. In the Service Components table, select Workflow Notification Mailer and click Edit.
8. Ensure that Automatic is selected for Startup Mode and click Next.
9. Click Next on the following page.
10. In the Inbound EMail Account section, provide the following information:
* Server Name: Enter the fully-qualified host name for the incoming e-mail server.
* Username: Enter the e-mail address you created for the workflow notification mailer administrator.
* Password: Enter the password for the workflow notification mailer administrator e-mail address.
* Inbox Folder: If the folder you created to use as an inbox has a name different from the default, provide the name of the inbox folder. The name for this folder is case-insensitive.
11. In the Outbound EMail Account section, in the Server Name field, provide the fully-qualified host name for the outgoing e-mail server.
12. In the EMail Processing section, provide the names of the Processed Folder and Discard Folder. The names for these folders are case-sensitive.
13. Click Next.
14. In the Send section, provide the following information:
* Reply-to Address: Enter the e-mail address you created for the workflow notification mailer administrator.
* HTML Agent: Enter the base URL that identifies the HTML Web agent that handles HTML notification responses, in the format: http://applications_tier_host:oracle_http_server_port/pls/wf
15. Click Next on all the remaining pages, then click Finish on the Review page.
16. Return to the Collaboration Suite Home page, select Service_Component_Container, and click Restart.

==================================================================

ENABLING CUSTOM WORKFLOW
------------------------
Enabling BPEL Workflow Creation in Oracle Content Services. To enable BPEL workflow creation in Oracle Content Services:

1. Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
2. In the Administration section, click Domain Properties.
3. Click IFS.DOMAIN.WORKFLOW.BPEL.CreationEnabled. You may need to move to the next page to find this property, or you can use the Search field.
4. Set the Value to true.
5. Click OK.
6. Return to the Content Services Home page and click Restart Domain.

==================================================================

BACKUP
------

1. Prepare the Oracle Collaboration Suite Database for backup
* enable ARCHIVELOG mode
- Set the ORACLE_HOME and ORACLE_SID environment variables
- Shutdown the database.

# sqlplus " / as sysdba"
SQL> shutdown immediate

- Start up the database in mount mode.
SQL> startup mount

- Enable ARCHIVELOG mode.
SQL> alter database archivelog;

* Enabling the flashback database feature for the Oracle Collaboration Suite Database
- Run the following query to check if the flashback_recovery_area is set up:
SQL> show parameters db_recovery

- Check that the database is only mounted.
SQL> select open_mode from v$database;

- Specify the destination directory for your archives by including the initialization parameter LOG_ARCHIVE_DEST_n in the initialization file. Set the log_archive_dest_1 parameter. The flash_recovery_area directory can be found under your $ORACLE_HOME location. Check that the location exists before entering the command.
SQL> alter system set log_archive_dest_1= "LOCATION=/u01/app/oracle/flash_recovery_area/ORCL/archivelog" scope=spfile;

- Turn on flashback database with the following SQL command:
SQL> alter database flashback on;

* Enabling block change tracking
- Run the following query to check if the db_create_file_dest parameter is set:
SQL> show parameters db_create_file

- Use the following command to enable block change tracking.
SQL> alter database enable block change tracking;

- Shutdown the database.
SQL> shutdown immediate;

- Start up the database and exit SQL*Plus.
SQL> startup
SQL> exit

2. Backup applications tier
- Execute the ocs_bkp_restore.sh script to configure the Oracle Collaboration Suite Recovery Manager to back up Oracle Collaboration Suite Applications.

# cd $ORACLE_HOME/backup_restore
# ./ocs_bkp_restore.sh -m configure

This script requires the following input:
Configure the backup environment file (yes/no) : yes >
Confirm that you want to configure the backup environment file. Click [Enter].

Enter ORACLE_HOME : /u01/app/oracle/product/10.1.2/ocs_1/apps >
Confirm the ORACLE_HOME path. Click [Enter].

Enter the config backup path :
Enter the path to your backup directory, where you want to store the configuration files (this example uses /u02/backup/apps/config).

Enter the database backup path :
Enter the path to your backup directory, where you want to store the database files (this example uses /u02/backup/apps/db).

Enter the log path :
Enter the path to your backup directory, where you want to store the log files (this example uses /u02/backup/apps/logs).

Enter the ORACLE_SID : orcl >
Confirm the ORACLE_SID setting. Click [Enter].

Enable Email notification (yes/no): yes >
Confirm that you want Email notification. Click [Enter] or type No, if you do not want Email notification.

Enter the SMTP host : >
Provide the name of the SMTP host. Enter the host name (this example uses a single-box installation).

Enter the SMTP port : 25 >
Confirm the SMTP port. Click [Enter].

Enter the from address : > @
Enter the to addresses(comma seperated) : > @

Enter the Email address from where you want to send notifications regarding backup and recovery and who should receive these notifications.

NOTE: You need to perform this step only once and not for each backup that you will take.

* After finished configuration
Back up the Applications instance using the backup_instance_cold mode. Press the [Enter] key when prompted by the question: Do you wish to continue?

./ocs_bkp_restore.sh -m backup_instance_cold

NOTE: repeat this in 'infra' tier

This is the perfect time to start a blog... It's summer and Soccer World Cup is in progress in Germany.

Of course, this has nothing to do with the topics I'll cover in my blog. It's just something to remember this new beginning by.

In this blog I will mostly post about various technologies that I'm interested in. Hopefully, it will be of use to some, and I'm looking forward for your feedback.