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.

Support Article

Encountered a result set that has column of an unrecognized type

SA-27810

Summary



After migrating from DB2 to Oracle and changing Oracle DATE columns to TIMESTAMP columns for greater accuracy (to store millisecond information), reports are failing due to an unrecognized column-type error. Obj-Browse and RDB-List are working fine with timestamp type.

Error Messages



Encountered a result set that has a column of an unrecognized type

Steps to Reproduce

  1. Expose the DateTime property to timestamp column in Oracle.
  2. Create report definition to display Pega DateTime property.
  3. Run the report definition.

Root Cause



A defect in Pegasystems’ code or rules.

Resolution



Perform the following local-change:
Set the following Java Virtual Machine (JVM) option in the application server to enable Oracle JDBC driver support for timestamp columns: Doracle.jdbc.J2EE13Compliant=true
Set this as a server runtime-custom property in Websphere.

Published September 13, 2016 - Updated October 8, 2020

Was this useful?

33% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us