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

Connector wizard not working against Teradata database



User is using Teradata as an external DB.

They see an exception while using SQL connector wizard, and it doesn't generate any rules.

Error Messages

2015-02-19 18:57:51,853 [http-/] [TABTHREAD1] [ ] [ ECS:01.01.01] ( internal.mgmt.Executable) ERROR  - Exception
java.lang.ArrayIndexOutOfBoundsException: 7
at com.pegarules.generated.activity.ra_action_getcolumninfo_2b172b51c366e98218a535d3bbf619a4.step2_circum0(
at com.pegarules.generated.activity.ra_action_getcolumninfo_2b172b51c366e98218a535d3bbf619a4.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pegarules.generated.flow.ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.RunTaskActivity(
at com.pegarules.generated.flow.ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.Task_UTILITY153_circum0(
at com.pegarules.generated.flow.ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pegarules.generated.StartFlow_071001_pHqeTXSalkhabVGTYNWp6A.StartFlow07_10_01(
at com.pegarules.generated.StartFlow_071001_pHqeTXSalkhabVGTYNWp6A.invoke(
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(
at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflection(

Steps to Reproduce

1) Run Connector and Metadata wizard.
2) Select Database Name as Teradata
3) Include a table which has Date data type as one of its column.

Root Cause

The root cause of this problem is defect/misconfiguration in the PRPC operating environment. The issue is because of the unsupported Date column Type by PRPC.


This issue is resolved through the following local change: 

1) User can use Varchar type instead of Date.
2) This can also be done by creating a view on the table and cast DATE column to VARCHAR in the view (CAST(CAST(DATE_Column AS FORMAT ‘YYYYMMDD’) AS CHAR(8)) AS Varchar_column).
3) User manually created classes, properties & database mappings. They were able to use Date/Time properties against the DATE columns and they can be used in filter conditions, although there is a local time zone to GMT conversion that can throw out the filter by one day.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% 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