when trying to connect to Terradata from Pega 8.1.5, we are getting below error message.
ERROR - Section 'TestConnectionResults' execution error on page 'ClassConnectionStatus' of class 'Code-Pega-ConnectionReport'.
com.pega.pegarules.pub.database.DatabaseException: Database-General Problem retrieving schema information for database XXXXX , table AAAAA.BBBBB 3523 42000 [Teradata Database] [TeraJDBC 15.10.00.14] [Error 3523] [SQLState 42000] The user does not have SELECT access to DBC.UDTInfo.
DatabaseException caused by prior exception: java.sql.SQLException: [Teradata Database] [TeraJDBC 15.10.00.14] [Error 3523] [SQLState 42000] The user does not have SELECT access to DBC.UDTInfo.
| SQL Code: 3523 | SQL State: 42000
***Edited by Moderator Marissa to update Content Type from Discussion to Question***
@softsree As Paul indicted, Teradata is not a list of supported Connectors, hence look for alternatives, we have had Teradat Connection at some point in one of our Pega based app and the Performance was un accepatble.
To help with the situation, we enabled SQL Jobs to read the data from Teradata and loads a table/view inside our Reporting Schema.
As far as the error shown above, indicates the Permission issue rather than connection issue due to a driver/jar missing. Please make sure you are able to connect to Teradata system using Tera Client or other teradata clients to amke sure your connection details are correct.
We were able to estalish a JDBC connection from Pega to Terradata DB and when we created a database table instance to connect to a table, it gave above error (on test connectivity). We checked with Terradata DBA, they confirmed that the system view that pega is trying to access (not sure why it has to access system view) is an outdated view and it should not access. They have new views for them but Pega is trying to access the old one. That's when, we thought the drivers that is used for the connectivity may be out dated, still trying to access the old views instead of new one's.
Regarding alternative approach, the data base is huge and it is a SOR. we don't want to replicate that. Will check if permission can be given. Also, noted your point on performance. Will weigh in on that one too. API would have been the best bet, unfortunately we don;t have one.