Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: Oracle JDBC Driver 10.1.2.0 Database.Impl Error, problem opening database instance

Suggest edit Updated on September 25, 2019

Symptom

You are using Process Commander V 5.5 SP1 configured with Oracle Database 10.2.0.1.0 using JDBC Driver 10.1.0.2.0. When you attempt to log in to Process Commander, you encounter errors similar to the following example:

[ server_name] [ STANDARD] [ PegaRULES:05.05] ( engine.database.DatabaseImpl) ERROR server|server_IP_address Administrator@pega.com - There was a problem opening a database instance (class: Rule-Obj-Model): Problem getting candidates for Rule Resolution (class: Rule-Obj-Model, object class: Data-Admin-Operator-ID, family name: DATA-ADMIN-OPERATOR-ID!PYDEFAULT): code: 17412 SQLState: <none> Message: Bigger type length than Maximum

com.pega.pegarules.pub.database.ConnectionException: Problem getting candidates for Rule Resolution (class: Rule-Obj-Model, object class: Data-Admin-Operator-ID, family name: DATA-ADMIN-OPERATOR-ID!PYDEFAULT): code: 17412 SQLState: <none> Message: Bigger type length than Maximum

Caused by SQL Problems.

Problem #1, SQLState null, Error code 17412: java.sql.SQLException: Bigger type length than Maximum

These messages are triggered by a known issue with the Oracle JDBC Driver 10.1.2.0.

 

Solution

Upgrade to JDBC Driver 10.2.0.2.

  • Previous topic Troubleshooting: ORA-01460 and ORA-01461 errors for database operations with Oracle 10.2.0.3
  • Next topic Troubleshooting: Activity saves a DateTime value in a Date property (Oracle schema issue)
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us