Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Ishank Singh (IshankS8)
JP Morgan Chase

JP Morgan Chase
IN
IshankS8 Member since 2013 2 posts
JP Morgan Chase
Posted: May 27, 2020
Last activity: May 28, 2020
Posted: 27 May 2020 7:31 EDT
Last activity: 28 May 2020 5:51 EDT
Closed

Pega 8.2 Oracle can not be resolved as Variable

We are upgrading our application from 6.3 (which was previously upgraded from earlier) to 8.2

Post upgrade we are seeing below common error across many rules and even observed during rule re-validation.

cs.registerOutParameter(6, oracle.jdbc.OracleTypes.CURSOR)

"oracle cannot be resolved to a variable

Compile failed"

We have imported the  ojdbc8.jar and included them in compiler/defaultPaths as well.Using Oracle 11g

Can anyone advise as in what could the resolution.??

Thanks

 

***Edited by Moderator Marissa to update General to Product; update Platform Capability tags****

To see attachments, please log in.
Pega Platform 8.2
Updates

Posted: 4 years ago
Posted: 28 May 2020 5:51 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
Pegasystems Inc.
US

Normally you should never import jdbc jar into your database, especially Oracle is your main platform db. Also I wonder what rules are those? Are they OOTB or your own rules?

To see attachments, please log in.

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

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice