Question 1 Replies 41 Views × Close popover Ishank Singh (IshankS8) JP Morgan Chase JP Morgan Chase IN View Profile Send Message 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 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**** Pega Platform 8.2 System Administration Upgrades Share × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Posted: 11 months ago Posted: 28 May 2020 5:51 EDT × Close popover Kevin Zheng (KevinZheng_GCS) PEGA Director, Software Solutions Engineering Pegasystems Inc. US View Profile Send Message KevinZheng_GCS PEGA replied to IshankS8 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?