Monday, 28 July 2014

Problems with DBMS_LOCK on Oracle with IBM BPM Advanced 8.5.5.0

If you see this: -

[28/07/14 15:10:54:461 BST] 00000097 XmlBeanDefini I org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml]
[28/07/14 15:10:54:703 BST] 00000097 SQLErrorCodes I org.springframework.jdbc.support.SQLErrorCodesFactory <init> SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase]
[28/07/14 15:10:54:731 BST] 00000097 wle_perf_load I   Error locking system table: ConnectionCallback; bad SQL grammar []; nested exception is java.sql.SQLException: ORA-06550: line 1, column 13:
PLS-00201: identifier 'DBMS_LOCK' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

                                 org.springframework.jdbc.BadSqlGrammarException: ConnectionCallback; bad SQL grammar []; nested exception is java.sql.SQLException: ORA-06550: line 1, column 13:
PLS-00201: identifier 'DBMS_LOCK' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored


during the startup of an IBM BPM 8.5.5.0 environment, when using Oracle, then you'll need to add an additional DB grant

GRANT execute ON DBMS_LOCK TO pdwuser;

as per this IBM Technote: -


which was written for BPM 7.5 and 8.0, but still appears to be relevant.

<Caveat>
Of course, for all DB-related issues, check check check this with your DBA and, if needed, raise a PMR with IBM Support to validate that this is the RIGHT approach for your environment.
</Caveat>

No comments: