If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Importing table with long field names

Started by toddbutt, 09 Jul 2015 02:24:02 PM

Previous topic - Next topic

toddbutt

Trying to import a table from Teradata that has field names greater than 30 chars.  The names get cut off at 30 chars and fail when I validate because those fields can't be found.  Remove those fields and everything works.

Any suggestions?

MFGF

Quote from: toddbutt on 09 Jul 2015 02:24:02 PM
Trying to import a table from Teradata that has field names greater than 30 chars.  The names get cut off at 30 chars and fail when I validate because those fields can't be found.  Remove those fields and everything works.

Any suggestions?

Hi,

I don't believe this is a Cognos limitation - it's Teradata that imposes the 30-character length restriction. See the post below from a Teradata forum:

http://forums.teradata.com/forum/database/teradata-table-naming

Are you pointing at modern views that end with V (DBC.TablesV) or at legacy views that don't (DBC.Tables)? Are you connecting via the Teradata ODBC or via JDBC?

MF.
Meep!

toddbutt

The views do not have a trailing V.  They were recently created so I am not sure I would call them legacy either.  I'm not the DBA so I really don't know about the views.

Looks like I am using JDBC.

The Teradata DBA says they have Extended Object Names enabled.  He also says that since the other apps do not have this problem, it is probably a Cognos setting.


toddbutt

Converted the project to Compatible, updated the objects, and voila.
Now I see the true field names.

So Java drivers was the issue?