Support Article
Connector wizard not working against Teradata database
SA-6775
Summary
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-/0.0.0.0:8080-4] [TABTHREAD1] [ ] [ ECS:01.01.01] ( internal.mgmt.Executable) ERROR - Exception
java.lang.ArrayIndexOutOfBoundsException: 7
at com.pega.pegarules.data.internal.access.DatabaseImpl.isColumnTypeSupported(DatabaseImpl.java:12090)
at com.pegarules.generated.activity.ra_action_getcolumninfo_2b172b51c366e98218a535d3bbf619a4.step2_circum0(ra_action_getcolumninfo_2b172b51c366e98218a535d3bbf619a4.java:375)
at com.pegarules.generated.activity.ra_action_getcolumninfo_2b172b51c366e98218a535d3bbf619a4.perform(ra_action_getcolumninfo_2b172b51c366e98218a535d3bbf619a4.java:86)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pegarules.generated.flow.ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.RunTaskActivity(ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.java:6326)
at com.pegarules.generated.flow.ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.Task_UTILITY153_circum0(ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.java:1260)
at com.pegarules.generated.flow.ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.perform(ra_action_processmetadata_aa7906d1a950356726aa8aaa932a7693.java:615)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pegarules.generated.StartFlow_071001_pHqeTXSalkhabVGTYNWp6A.StartFlow07_10_01(StartFlow_071001_pHqeTXSalkhabVGTYNWp6A.java:167)
at com.pegarules.generated.StartFlow_071001_pHqeTXSalkhabVGTYNWp6A.invoke(StartFlow_071001_pHqeTXSalkhabVGTYNWp6A.java:76)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:133)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:110)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:8786)
at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflection(LibrarySupport.java:181)
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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.