Support Article
Error code 5315 trying to access view in Teradata database
SA-10553
Summary
The Pega user is unable to access a Teradata Database from within Pega.
Error Messages
2015-05-04 16:34:37,238 [ WebContainer : 37] [TABTHREAD9] [ ] [ ] (taModel_DBClassMappings.Action) ERROR - Caught exception looking up external database column names
com.pega.pegarules.pub.database.DatabaseException: Database-General Problem retrieving schema information for database DataTest, table MySchema.MyTable 5315 HY000 [Teradata Database] [TeraJDBC ] [Error 5315] [SQLState HY000] The user does not have SELECT access to DBC.UDTInfo.TypeName.
From: (unknown)
Caused by SQL Problems.
Problem #1, SQLState HY000, Error code 5315: java.sql.SQLException: [Teradata Database] [TeraJDBC ] [Error 5315] [SQLState HY000] The user does not have SELECT access to DBC.UDTInfo.TypeName.
at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:257)
at com.pega.pegarules.data.internal.access.TableInformationMapImpl.lookupTableInfo(TableInformationMapImpl.java:564)
at com.pega.pegarules.data.internal.access.DatabaseImpl.getColumnsForUndefinedTable(DatabaseImpl.java:12054)
at com.pegarules.generated.activity.ra_action_pzlprefreshcolumnmappingslist_83b2020481d64eee81d24db0ff07b887.step4_circum0(ra_action_pzlprefreshcolumnmappingslist_83b2020481d64eee81d24db0ff07b887.java:399)
Steps to Reproduce
1. From Pega user, access Database Table Class Mapping.
2. Attempt to reference the table name.
Root Cause
The root cause of this problem is defect or misconfiguration in the operating environment. In order to get the structure of a table/view the DatabaseMetaData APIs is used from the JDBC driver.
The database user that you are using needs to have whatever privileges that are needed by the JDBC driver. For this Teradata DB it looks like this is the privilege that needs to be granted.
One must be granted SELECT access to DBC.UDTInfo in order to call some of the DatabaseMetaData methods that can return UDT information.
Resolution
This issue is resolved by making the following change to the operating environment:
Grant database user that is connecting to the external Teradata database SELECT access to DBC.UDTInfo.
Published February 29, 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.