Necessary corrections for Oracle and DB2 databases when used with the Portfolio Manager v6.1.1.2 migration package

Resolving The Problem

This solution is broken down into two parts. The first part applies only to Oracle databases. The second part applies to both Oracle and DB2 databases.

Part 1:
When you are migrating to Portfolio Manager v6.1.1.2 and using an Oracle database, make the following alteration to the ConnectionPool.ini file, which is the main configuration file of the web application.

1. Navigate to the …\war\WEB-INF\classes directory
2. Open to edit the ConnectionPool.ini file, and locate the section labeled Oracle
   

   ############################
   
   # ORACLE #
   
   ############################

   
   Note: In this section you will find 7 “ALTER SESSION SET” statements
3. Locate and remove the following statement, which is deprecated and might impact performance on the database.:
   “ALTER SESSION SET CLOSE_CACHED_OPEN_CURSORS = TRUE”
4. Set the “Statements=7” property to 6, “Statements=6”
5. Re-sequence the “Statement#=” to 1 through 6 as shown in the example:
   Statements=6
   Statement1=ALTER SESSION SET NLS_TERRITORY = AMERICA
   Statement2=ALTER SESSION SET NLS_DATE_FORMAT = 'YYYY-MM-DD'
   Statement3=ALTER SESSION SET NLS_TIMESTAMP_FORMAT = 'YYYY-MM-DD hh24:mi:ss.ff6'
   Statement4=ALTER SESSION SET NLS_TIMESTAMP_TZ_FORMAT = 'YYYY-MM-DD hh24:mi:ss.ff6'
   Statement5=ALTER SESSION SET NLS_NUMERIC_CHARACTERS = '.,'
   Statement6=ALTER SESSION SET NLS_SORT = BINARY

• db2java.jar if you are using DB2 as your database vendor
• classes12.jar if you are using Oracle as your database vendor