Article ID: 127003, created on Sep 25, 2015, last review on Nov 13, 2016

  • Applies to:
  • Operations Automation
  • Business Automation

Overview

For better performance experience we recommend to adjust PostgreSQL configuration using utility pgtune. The recommendation is applicable to OSA, BA and OACI (IM) databases.

How to use pgtune (general schema):

  1. Create a backup of current PostgreSQL configuration file:

    # cp <POSTGRESQL_CONF> <POSTGRESQL_CONF>.orig
    
  2. Generate optimized configuration file using pgtune:

    # /usr/bin/pgtune -i <POSTGRESQL_CONF> -c <MAX_CONNECTIONS> -S /usr/share/pgtune -o <POSTGRESQL_CONF>.new    
    
  3. Check new settings in the <POSTGRESQL_CONF>.new
  4. Replace current PostgreSQL configuration file with the optimized one:

    mv $<POSTGRESQL_CONF>.new <POSTGRESQL_CONF>
    

Values of <POSTGRESQL_CONF> and <MAX_CONNECTIONS> are different depending on the product. They are listed in corresponding section below.

OSA

OSA installer installs and invokes pgtune automatically and there is no need to reconfigure postgreSQL after OSA installation.

pgtune tunes number of connections (set to 256) and sets memory limits that depend on RAM size. You can see the settings applied by pgtune in file /var/lib/pgsql/9.1/data/postgresql.conf on OSA database server (section "CUSTOMIZED OPTIONS”)

However, if RAM size was changed (increased) on OSA database server it is required to re-configure postgreSQL using pgtune.

Launch pgtune using following values:

POSTGRESQL_CONF = /var/lib/pgsql/9.1/data/postgresql.conf
MAX_CONNECTIONS = 256

To apply the changes execute following:

  1. Stop OA. Execute on OSA Management node:

    # service pem stop
    

    or for OSA 6.0:

    # service pem stop
    # service pau stop
    
  2. Restart PostgreSQL. Execute on OSA database server:

    # service postgresql-9.1 restart
    
  3. Start OSA. Execute on OSA Management node:

    # service pem start
    

    or for OSA 6.0:

    # service pau start
    # service pem start
    

BA

Install pgtune. It might be available in OS repositories:

# yum install pgtune

Also you can find RPM-package on OA Management Node (OA 5.5) by running:

# find /usr/local/pem/install/ -name pgtune*

Launch pgtune using following values:

POSTGRESQL_CONF=/var/lib/pgsql/data/postgresql.conf
MAX_CONNECTIONS = 500

To apply the changes execute following:

  1. Stop BA. Execute on OA Management node:

    # service pba stop
    
  2. Restart PostgreSQL. Execute on BA database server:

    # service postgresql restart
    
  3. Start BA. Execute on OA Management node:

    # service pba start
    

OACI (IM database)

Install pgtune on IM database server. It is shipped in OA repository:

# yum install pgtune

Launch pgtune using following values:

POSTGRESQL_CONF = /var/lib/pgsql/9.1/data/postgresql.conf
MAX_CONNECTIONS = 100

Note: number of DB connections is configurable in IM configuration file and can be verified like below:

# awk '/database.*maxConnections/ {print $3}' /usr/local/share/PACI-im/IM-config.xml
maxConnections="10"

MAX_CONNECTIONS in PostgreSQL configuration must be not less than maximum number of database connections allowed in IM configuration.

To apply the changes execute following:

  1. Stop OACI services using the article #126873
  2. Restart PostgreSQL. Execute on IM database server:

    # service postgresql-9.1 restart
    
  3. Start OACI services using the article #126873

Search Words

integrity check oa database

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae

Email subscription for changes to this article
Save as PDF