Skip Headers

Oracle® Collaboration Suite Certified Configuration Deployment and Cloning Guide
Release 9.0.4.1 for Linux x86
Part No. B12145-01
  Go To Table Of Contents
Contents		 Go To Index
Index
Previous Next  

7 Tuning

This chapter describes procedures for tuning Oracle Collaboration Suite Certified Configuration (Oracle Collaboration Suite CC).

This chapter contains the following sections:

Tuning Steps for Installations From Gold Image and Product CD-ROMs

Perform the following tuning steps for systems installed from the gold image and from Product CD-ROMs.

Tuning Systems

Perform the following tuning steps on your systems.

Enabling Bigpages on the Back-End System

Use the following to enable bigpages on the back-end system:

  1. Add the following line to the /etc/lilo.conf file: 

    append="bigpages=2300MB"

    For example, the /etc/lilo.conf file will look like the following: 

    image=/boot/vmlinuz-2.4.9-e.12enterprise
label=linux
initrd=/boot/initrd-2.4.9-e.12enterprise.img
read-only
root=/dev/sda6
append="bigpages=2300MB"

    where 2300 MB is the sum of all the back-end database SGAs.

  2. As the root user, run the /sbin/lilo command.

  3. Set file contents of /proc/sys/kernel/shm-use-bigpages to 1. Add the following line to the /etc/rc.d/rc.local file to ensure that this is done whenever the system restarts. 

    echo 1 > /proc/sys/kernel/shm-use-bigpages

Setting NFS Mount Options for File Systems

Set NFS mount options to the following values for all file systems: 

rw,bg,nointr,hard,wsize=32768,rsize=32768,nfsvers=3,tcp

Setting the ulimit of File Descriptors

Set the ulimit of file descriptors to 8192 (soft and hard) for both the back-end and middle-tier systems. Add the following lines to the /etc/security/limits.conf file on both the back-end and middle-tier systems: 

*     soft    nofile          8192
*     hard    nofile          8192

Setting the ulimit of Core Files

Set the ulimit of core files to 1000 file system blocks. Add the following lines to the /etc/security/limits.conf file on both the back-end and middle-tier systems: 

*     soft    core            1000
*     hard    core            1000

Enabling Hyper-Threading

Enable hyper-threading on both the back-end and middle-tier systems.

Tuning the Security Proxy

The startocs.sh and stopocs.sh scripts set up the ocsproxy.ini file during the installation of the Oracle Collaboration Suite CC middle-tier, and needs no further tuning. By default, after installation, 2 ports (5730 and 1621) on the middle-tier system are redirected to the corresponding ports on the back-end system.

If you need to redirect more ports, in addition to the default ports, from the middle-tier to the back-end system, then perform the following:

  • have available the list of port numbers that you want to redirect (including those on the middle-tier and those on the back-end system)

  • edit the $ORACLE_HOME/ocsproxy/bin/ocsproxy.ini configuration file. Add lines for each additional port you want redirected. The syntax for each entry is as follows: 

    group groupname <midtier-iface> <mt-port> <backend-iface> <be-port>

    where:

    • group is the keyword that identifies a port redirection specification

    • groupname is a name for port redirection specification. It can a maximum of 15 characters consisting of uppercase and lowercase letters (A-Z and a-z), numbers ( 0-9), and underscore (_).

    • midtier-iface is the network interface detail for the middle-tier system. It can be either a DNS qualified host name or IP address in a "number-and-dot" notation.

    • mt-port is the port number on the network interface to be redirected.

    • backend-iface is the network interface detail for back-end host. If can be either a DNS qualified host name or IP address in a "number-and-dot" notation.

    • be-port is the back-end port number on the network interface.

    For example, to redirect port 5432 from the middle-tier system network interface (with an IP address of 192.168.130.17) to a target port of 2345 on the back-end system network interface (with an IP address of 192.168.130.18), use the following entry in the ocsproxy.ini file: 

    group sample_entry 192.168.130.17 5432 192.168.130.18 2345

Note:

There is a one-to-one correspondence between ports on the middle-tier system to ports on the back-end system. Ensure that the network interface specification (for the middle-tier and the back-end systems) use valid host names or IP addresses. Also ensure that the groupnames are unique.

Performance Tuning for Files

You must run the following script periodically to prevent Oracle Files performance degradation from outdated files statistics. Add the following entry into the crontab of the ia<SID>u user.

As the ia<SID>u user, run crontab -e. 

0 0 * * * /<SID>u/collab/product/ocsmt_904/ifs/files/admin/scripts/ifs_analyze.sh > /tmp/ifs_analyze.log 2>&1

Content of the shell script ifs_analyze.sh (the script should have permission 700 set, and owned by the owner of the mid tier ORACLE_HOME):
#!/bin/sh 
# Name: ifs_analyze.sh 
# 
# Ensure restrictive permissions as this file contains passwords 
# Permission 700 recommended 
# 
ORACLE_HOME=/<SID>u/collab/product/ocsmt_904 
export ORACLE_HOME
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
 
$ORACLE_HOME/bin/sqlplus ifssys/<password>@<SID>  << EOF
@$ORACLE_HOME/ifs/files/admin/sql/analyze.sql ifssys
exit;
EOF

Tuning Steps for Installations From Product CD-ROMs Only

Perform the following tuning steps for systems installed from Product CD-ROMs only. You do not need to tune systems installed from the gold image because the gold image is pre-tuned.

Tuning the Email Infostore Database

Perform the following tuning steps for the Email Infostore database.


Note:

You will modify various database parameters in this section. You must shut down and restart the database for the modifications to take effect. Before you shut down the database, use the stopocs.sh script located in the /admin/mwcc/ocs/904/etc/rc.oracle/directory to shut down the client processes: 
$ stopocs.sh $ORACLE_HOME

Disabling Dispatchers

Use the following to disable dispatchers:

  1. Comment the dispatchers line in the init file: 

    #dispatchers="(PROTOCOL=TCP)"

  2. Create spfile from pfile.

Setting Parameters

Set the following parameters:

  1. Set the processes parameter to 750: 

    alter system set processes=750 scope=spfile;

  2. Set db_cache_size to 1G: 

    alter system set db_cache_size=1G scope=spfile;

  3. Set undo_retention to 1800: 

    alter system set undo_retention=1800 scope=spfile;

  4. Set db_writer_processes to 4: 

    alter system set db_writer_processes=4 scope=spfile;

  5. Increase the size of redo log files to 300M: 

    startup open restrict
alter database add logfile group 5 '/<SID>/oradata/data03/redo05.dbf' size 300M;
alter database add logfile group 6 '/<SID>/oradata/data03/redo06.dbf' size 300M;
alter database add logfile group 7 '/<SID>/oradata/data03/redo07.dbf' size 300M;
alter database add logfile group 8 '/<SID>/oradata/data03/redo08.dbf' size 300M;
select group#, bytes, status from v$log /* to find the status of redo logfile groups */;
         alter system switch logfile 
         /* perform this step till group 1, 2, 3 and 4  become inactive */;
         alter database drop logfile group 1;
         alter database drop logfile group 2;
         alter database drop logfile group 3;
         alter database drop logfile group 4;

Tuning the Infrastructure Database

Perform the following tuning steps for the Infrastructure database.


Note:

You will modify various database parameters in this section. You must shut down and restart the database for the modifications to take effect. Before you shut down the database, use the stopocs.sh script located in the /admin/mwcc/ocs/904/etc/rc.oracle/directory to shut down the client processes: 
$ stopocs.sh $ORACLE_HOME

Disabling Dispatchers

Use the following to disable dispatchers:

  1. Comment the dispatchers line in the init file: 

    #dispatchers="(PROTOCOL=TCP)"

  2. Create spfile from pfile.

Setting Parameters

Set the following parameters:

  1. Set the processes parameter to 750: 

    alter system set processes=750 scope=spfile;

  2. Set undo_retention to 1800: 

    alter system set undo_retention=1800 scope=spfile;

Tuning the Files Infostore

Perform the following tuning steps for the Files Infostore.


Note:

You will modify various database parameters in this section. You must shut down and restart the database for the modifications to take effect. Before you shut down the database, use the stopocs.sh script located in the /admin/mwcc/ocs/904/etc/rc.oracle/directory to shut down the client processes: 
$ stopocs.sh $ORACLE_HOME

The file server is started as the root user and must be shut down as the root user. Use the following command to shut down the file server: 

$ $ORACLE_HOME/ifs/files/bin/ifsctl stop

Disabling Dispatchers

Use the following to disable dispatchers:

  1. Comment the dispatchers line in the init file: 

    #dispatchers="(PROTOCOL=TCP)"

  2. Create spfile from pfile.

Setting Parameters

Set the following parameters:

  1. Set the processes parameter to 750: 

    alter system set processes=750 scope=spfile;

  2. Set db_cache_size to 500M: 

    alter system set db_cache_size=500M scope=spfile;

  3. Set undo_retention to 1800: 

    alter system set undo_retention=1800 scope=spfile;

Note:

After you have tuned all the databases, restart the databases for the changes to take effect.

Tuning the Protocol Servers

Perform the following tuning steps for the protocol servers:

  1. Create a total of four instances each for imap, smtp_in, smtp_out, and pop protocol servers by repeating the following commands three times: 

    oesctl create instance <system name>:um_system:imap
oesctl create instance <system name>:um_system:smtp_in
oesctl create instance <system name>:um_system:smtp_out
oesctl create instance <system name>:um_system:smtp_pop

  2. Modify the listener.ora file for the middle-tier listener_es to have QUEUESIZE=20 for each of the protocol server. For example, 

    LISTENER_ES = (DESCRIPTION_LIST =
  (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(KEY = UMREG)))
  (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 25)) (PRESENTATION = ESSMI)(QUEUESIZE=20))
  (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 143)) (PRESENTATION = IMAP)(QUEUESIZE=20))
  (DESCRIPTION = (ADDRESS = (PROTOCOL = TCPS)(HOST = <hostname>)(PORT = 993)) 
(PRESENTATION = IMAPSSL)(QUEUESIZE=20))
  (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 110)) (PRESENTATION = POP)(QUEUESIZE=20))
  (DESCRIPTION = (ADDRESS = (PROTOCOL = TCPS)(HOST = <hostname>)(PORT = 995)) 
(PRESENTATION = POPSSL)(QUEUESIZE=20))

  3. Set the "Password Expiry time" to value 0 (0 means user passwords never expire) by connecting to the OID server using oidadmin: 

    + - Password Policy Management
                    - cn=PwdPolicyEntry
    Password Expiry Time --> Change from 518400 to 0

  4. Set the connection pool parameters for imap, smtp_in and smtp_out: 

    Entry management
     cn=OracleContext
       cn=Products
         cn=EMailServerContainer
           cn=UM_SYSTEM
             cn=mailstores
               cn=<backend system name>
                 cn=<mid-tier system>:UM_SYSTEM:imap:<instance number>
                 cn=<mid-tier system>:UM_SYSTEM:smtp_in:<instance number>
                 cn=<mid-tier system>:UM_SYSTEM:smtp_out:<instance number>
                 cn=<mid-tier system>:UM_SYSTEM:pop:<instance number>
 
                              imap   smtp_in   smtp_out   pop
   orclmailprocessdbmaxconn   30     30        30         30
   orclmailprocessdbminconn   5      5         5          5
   orclmailprocessdbincrconn  5      5         5          5

  5. Set orclmailprocflags to "-l -cp=3" for smtp_in, smtp_out, and list server: 

    Entry Management
     cn=OracleContext
       cn=Computers
         cn=<mid-tier system name>
           cn=<base name of oracle home>
             cn=eMailServer
               cn=mailProcessConfig
                 cn=<mid-tier system name>:um_system:smtp_in
                 cn=<mid-tier system name>:um_system:smtp_out
                 cn=<mid-tier system name>:um_system:list
                   orclmailprocflags: -l -cp=3

  6. Set orclmailsmtpsubmitonly to true: 

    Entry Management
     cn=OracleContext
       cn=Computers
         cn=<mid-tier system name>
           cn=<base name of oracle home>
             cn=eMailServer
               cn=mailProcessConfig
                 cn=<mid-tier system name>:um_system:smtp_in
                   orclmailsmtpsubmitonly: true

  7. Set orclmailadmincollectioninterval to 600: 

     Entry Management
     cn=OracleContext
       cn=Computers
         cn=<mid-tier system name>
           cn=<base name of oracle home>
             cn=EMailServer
               cn=mailProcessConfig
                 orclmailadmincollectioninterval: 600

  8. Set the Email application connection pooling parameters for the imap, smtp_in, smtp_out, and pop servers: 

     Entry Management
     cn=OracleContext
       cn=Computers
         cn=<mid-tier system name>
           cn=<base name of oracle home>
             cn=EMailServer
               cn=mailProcessConfig
                 orclmailreconecttimeout: 1
                 orclmailappminconnpool: 10
                 orclmailappmaxconnpool: 50
                 orclmailappconnpoolincr: 5

  9. Set orclmailsmtpminqueueage = 10 for smtp_in and smtp_out: 

     Entry Management
     cn=OracleContext
       cn=Computers
         cn=<mid-tier system name>
           cn=<base name of oracle home>
             cn=eMailServer
               cn=mailProcessConfig
                 cn=<mid-tier system>:UM_SYSTEM:smtp_in
                 cn=<mid-tier system>:UM_SYSTEM:smtp_out
                   orclmailsmtpminqueueage: 10

  10. Set orclmailsmtpauthentication = false and orclmailsmtpconnectionnumber = 10 for smtp_in: 

    Entry Management
      cn=OracleContext
        cn=Computers
          cn=<mid-tier system name>
            cn=<base name of oracle home>
              cn=eMailServer
                cn=mailProcessConfig
                  cn=<mid-tier system>:UM_SYSTEM:smtp_in
                    orclmailsmtpauthentication: false
                    orclmailsmtpconnectionnumber: 0

  11. Set orclmailsmtpmsgtimeout = 15 for smtp_out: 

    Entry Management
      cn=OracleContext
        cn=Computers
          cn=<mid-tier system name>
            cn=<base name of oracle home>
              cn=eMailServer
                cn=mailProcessConfig
                  cn=<mid-tier system>:UM_SYSTEM:smtp_out
                    orclmailsmtpmsgtimeout: 15

  12. Enable higher log level of any one of the smtp_in and smtp_out protocol servers: 

     Entry Management
      cn=OracleContext
        cn=Computers
          cn=<mid-tier system name>
            cn=<base name of oracle home>
              cn=eMailServer
                cn=mailProcessConfig
                  cn=<mid-tier system>:UM_SYSTEM:<PROTOCL>
                    cn=<mid-tier system>:UM_SYSTEM:<PROTOCL>:<instance number>
                      orclmailprocloglevel: 16

    where PROTOCL is either smtp_in or smtp_out.


    Note:

    By default, orclmailprocloglevel is not set and it is not shown in oidadmin. This entry can be modified using the configuration checker.

    A configuration checker script is installed in the /admin/mwcc/ocs/904/utils/cchecker directory. You can use the script after installation and configuration to validate the configuration parameters of the installed Oracle Collaboration Suite CC components and the operating system settings.

    You can also use the script to set Oracle Collaboration Suite CC configuration parameters to the values recommended in this chapter.For more information on usage, type cc.sh.


  Previous Next
Oracle Logo
Copyright © 1999, 2003 Oracle Corporation
All rights reserved
  Go To Table Of Contents
Contents		 Go To Index
Index