Question

RDB-List when processed with Wait shape not finding jdbc driver

Hello all,

We have a scenario where we queue the case to wait shape. So ideally when the wait time has reached, system is suppose to resume the flow and make Connect-SQL call.

The issue is, when wait shape is processing Connect-SQL, we are seeing the below error.

Problem encountered when getting connection for database externaldb: code: 0 SQLState: 08001 Message: No suitable driver found for jdbc:oracle:thin..........

However, when I resume the wait manually (user choose to continue process), I do not see this error and RDB-List executes just fine.

Note: this is only happening in one env. Moreover, we moved our external db from oracle to redshift. We did not see this when we are using the redshift. Apparently, we are seeing this only after we moved to oracle

***Edited by Moderator Marissa to update platform capability tags; update SR Details****

Group Tags

Correct Answer
October 2, 2019 - 1:00pm

here is why, in your web node, I can see this setting

com.amazon.redshift.jdbc42.Driver;oracle.jdbc.driver.OracleDriver

whereas in the util node (which runs agent processes) does not have oracle driver class, only redshit class.

Maybe util node did not restart to take effect.

 

Comments

Keep up to date on this post and subscribe to comments

Pega
September 30, 2019 - 1:58pm

Hi Abhinay,

As per the SR detail I think you are using PRPC 8.x version which supports the below drivers for oracle DB.

For Oracle 11gR2

11.1.0.6.0
11.1.0.7.0

Oracle 12c
12.1.0.1 or later

 

 

October 1, 2019 - 6:12pm
Response to ramau

Hello,

 

I had to import the ojdbc8.jar for this. The external DB is Oracle DB. Again, this is working fine for user. We are only seeing this error when user context is Service Level. In other upgraded env, we are seeing different error for the same process mentioned above 

 

java.lang.IllegalAccessError: oracle/jdbc/driver/OracleResultSetMetaData

 

Not sure if both the errors have a common root cause. Any help is much appreciated.

October 2, 2019 - 6:41am
Response to AbhinayC

You could have class conflict, what is your Pega platform db? I know your external DB is Oracle. It is likely that you have oracle driver classes in separate locations (e.g., one ojdbc jar on disk and one in pega database).

October 2, 2019 - 12:46pm
Response to KevinZheng_GCS

Could be. But if that's the case, I should see the error when I manually execute connect-sql (like searches from UI or executing stand alone activity) right. I believe ours is postgres (we are on pega cloud)

Would it be something with nodes? Like Service Level event runs on a different node (background) rather than WebUser node? (or may be remote node versus the one user logged into)

October 2, 2019 - 1:00pm
Response to AbhinayC

here is why, in your web node, I can see this setting

com.amazon.redshift.jdbc42.Driver;oracle.jdbc.driver.OracleDriver

whereas in the util node (which runs agent processes) does not have oracle driver class, only redshit class.

Maybe util node did not restart to take effect.