Unable to test connectivity on Data-Admin-DB-Table

We noted that at stat up Pega platform is having trouble finding database definition with this error message: "ERROR - Definition mismatch detected for database ubi; the entry in the preferences will be preferred."

That is unexpected because there is a DB-Name entry with the ID "UBI". Yes the definition is in capital letters. This was working fine in 6.3. Should it be in lower case ? we tried changing it to lower case but we still had the error.

Then when we try to "test connectivity" on a table that is using this database definition, Pega crashes with the error : Database-BadDBDef-Missing	ubi

at ~[prprivate.jar:?] (complete stack trace attached)

We think, we started to have this issue moving to Java 8 and the new JDBC8. I've heard in the past that the new jndi/xxx under JDBC8 is not managing "auto-commit" the same way.

Does anyone know if Pega is expecting the connection from the pool to be in "auto-commit" mode or not ?


Keep up to date on this post and subscribe to comments

October 3, 2019 - 6:42pm

Not sure how auto commit can play a role of the problem here.  Is ubi configured properly as a data source in WAS?  Did we see a problem of testing the connection from WAS?

October 3, 2019 - 6:49pm
Response to WaikeiKwok_GCS

No problem on the WAS side. I'm referring to the auto-commit part because I saw something about "autocommit" in the stack trace and I remember having some issues with the configuration of the connection pool when we upgraded to JDBC8 in the past for other app servers.

October 3, 2019 - 6:57pm

I forgot to add that if we do the folowing steps we can restore the situation:

  1. open the instance of the DB-Name
  2. save it
  3. use the button "test connection"
  4. open the table entry (in DB-Table)
  5. save it 
  6. use the "test connectivity" button

We need to do that after each restart of the JVM

October 4, 2019 - 3:41am

Which version of Pega are you working with here?

Also what type of database is UBI? (Oracle/MSSQL/Postgres/etc...)


October 7, 2019 - 9:38am
Response to LaurenceB_GCS

We are now running Pega 7.3.1. and the Oracle DB is Oracle 11g.

from the PegaRules log:

PRPC-7.3.1-184: 2017-10-14 00.41 EDT
Database version: Oracle Database 11g Enterprise Edition
Driver: Oracle JDBC driver
Driver version:
Vendor: IBM Corporation, JVM version: 1.8.0_161
VM Name: IBM J9 VM(build -