JR57819: DBUPGRADE AND BPMUPDATESYSTEMAPP COMMANDS FAIL WHILE UPGRADING WITH JAVA 7 AND A CUSTOMIZED ORACLE JDBC DRIVER PATH

bpm.8570.cf2017.06.delta.repository

APAR status

• Closed as program error.

Error description

• The following issues occur while upgrading to IBM Business
  Process Manager (BPM) cumulative fix 2017.03 with Java 7 and a
  customized Oracle JDBC driver path:
  
  -The DBUpgrade command fails with an error similar to the
  following error:
  
  [Apr 7, 2017 11:08:20 AM] 00000001 FINE:
  com.lombardisoftware.tools.dbupgrade.UpgradeDatabase.main -
  Could not connect to your Process Server database.
  java.lang.RuntimeException: Could not connect to your Process
  Server database.
  at
  com.lombardisoftware.tools.dbupgrade.steps.TestDatabases.execute
  (TestDatabases.java:35)
  at
  com.lombardisoftware.tools.dbupgrade.UpgradeDatabase.main(Upgrad
  eDatabase.java:124)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  :
  Caused by: java.lang.ClassNotFoundException:
  oracle.jdbc.driver.OracleDriver
  at java.lang.Class.forName(Class.java:301)
  at
  org.springframework.jdbc.datasource.DriverManagerDataSource.setD
  riverClassName(DriverManagerDataSource.java:146)
  
  -While the deployment manager starts, the BPMUpdateSystemApp
  command fails with an error similar to the following error:
  
  org.springframework.jdbc.support.MetaDataAccessException: Error
  while
  extracting DatabaseMetaData; nested exception is
  org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC
  driver
  class 'oracle.jdbc.driver.OracleDriver', cause:
  oracle.jdbc.driver.OracleDriver
  at
  org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaDa
  ta(JdbcUtils.java:296)
  at
  org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaDa
  ta(JdbcUtils.java:320)
  
  
  PRODUCTS AFFECTED
  IBM Business Process Manager (BPM) Advanced
  IBM BPM Standard
  IBM BPM Express
  

Local fix

• To use a customized Oracle JDBC driver path with Java 7, make
  sure the ojdbc6.jar file is available in the customized JDBC
  driver path alongside ojdbc7.jar.
  
  To make sure the database upgrade related commands can correctly
  resolve the JDBC driver path, ensure all referenced WebSphere
  variables are defined at the deployment manager's node level.
  

Problem summary

• The DBUpgrade command uses a Java 6 runtime environment and,
  therefore, requires the ojdbc6.jar JDBC driver when using
  Oracle. If a customized Oracle JDBC driver path does not contain
   the ojdbc6.jar file, the DBUpgrade fails to load an Oracle JDBC
   driver.
  
  Database upgrade commands like DBUpgrade and BPMUpdateSystemApp
  use the actual data source configuration to access the database.
  For this reason, any WebSphere variables in the JDBC driver path
  must be resolved. If a WebSphere variable like
  ORACLE_JDBC_DRIVER_PATH is moved from node level to cell level
  after initial IBM BPM is configured, the JDBC driver path lookup
  might fail, depending on whether the cell-level variables.xml
  file is available in the session workspace of the command in
  question.
  

Problem conclusion

• A fix will be available in IBM BPM V8.5.7 cumulative fix 2017.06
   that correctly recognizes a customized Oracle JDBC driver path
  when Java 7 is used.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R857 PSY

     UP