Catalog Error

Connectivity

Catalog Error

I am getting the following error when trying to connect to Teradata from UNIX (Sun OS). This connection was working couple of weeks back and stopped working after the server crashed due to user libraries were deleted (do not know how).
I am trying to connect using ODBC entry and below is how my ODBC is setup.
---------------------------
[tdp1_ip]
Driver=/usr/odbc/drivers/tdata.so
Description=Dev Teradata
DBCName=10.206.68.19
DateFormat=AAA
SessionMode=ANSI
DefaultDatabase=
UserName=
Password=
---------------------------
I am using to test my odbc connection. Below is the error message:
-----------------------------------
./demoodbc DataDirect Technologies, Inc. ODBC Sample Application.
./demoodbc: will connect to data source 'tdp1_ip' as user 'user1/passwd1'.
SQLConnect: Failed...
SQLSTATE = S1000
NATIVE ERROR = 0
MSG = [NCR][ODBC Teradata Driver] Unable to get catalog string.

SQLSTATE = 28000
NATIVE ERROR = 0
MSG = [NCR][ODBC Teradata Driver] Unable to get catalog string.

SQLConnect: Retrying Connect.
SQLConnect: Failed...
SQLSTATE = S1000
NATIVE ERROR = 0
MSG = [NCR][ODBC Teradata Driver] Unable to get catalog string.

SQLSTATE = 28000
NATIVE ERROR = 0
MSG = [NCR][ODBC Teradata Driver] Unable to get catalog string.

SQLConnect: Retrying Connect.
SQLConnect: Failed...
SQLSTATE = S1000
NATIVE ERROR = 0
MSG = [NCR][ODBC Teradata Driver] Unable to get catalog string.

SQLSTATE = 28000
NATIVE ERROR = 0
MSG = [NCR][ODBC Teradata Driver] Unable to get catalog string.

SQLConnect: Retrying Connect.
No connection could be established.
----------------------------------------
Any help on this is greatly appreciated.

Thanks,
6 REPLIES
Teradata Employee

Re: Catalog Error

Be sure you have installed proper TDICU and TeraGSS libraries also.
Enthusiast

Re: Catalog Error

hi Fred,

one of my team members is facing the same situation right now. Our team uses Teradata ODBC driver in Business Objects reports. The situation came up when she was trying to pull a Business Objects report.

The "Catalog error" prompt shows up only when Business Objects alone is being used.
If she just logs in to Teradata and then opens the report in Business Objects, then, there is no catalog error.

I understand that the issue is with the ODBC driver. Can you help me in fixing this? Whom should I consult or what should I do now?

Any suggestion is greatly appreciated.

Thank you
Teradata Employee

Re: Catalog Error


"[ODBC Teradata Driver] Unable to get catalog string."

This error indicates that Teradata ODBC driver trying to post an error, but it cannot find it's error message catalog file.

Search for "tdodbc.cat" file and set NLSPATH variable. For example if you find tdodbc.cat in

/opt/teradata/client/lib/odbc/tdodbc.cat

then set

NLSPATH=/opt/teradata/client/lib/odbc/%N.cat

---

It would let you see the actual error message.

Re: Catalog Error

Status Code: 8140 Connecting to ODBC. Unable to populate section table sect1.error IM002 Microsoft ODBC DRiver Manager Data Source name not found and no default drive specified

Re: Catalog Error

I have similar issues but with Informatica. Below is the error message.

RR_4036 Error connecting to database [

[Teradata][Unix system error] 238 Unable to get catalog string.

Database driver error...

Function Name : Connect

Database driver error...

Function Name : Connect

Database Error: Failed to connect to database using user [MMDMETL] and connection string [TDPRD_BTET].].

Restarting the job from autosys typically resolves this issue. Is there a way to determine what the underlying issue would be and how to prevent it from happening again?

appreciate any guidances.....

Enthusiast

Re: Catalog Error

Hi Jayce, 

Di you get any clue to the above error posted and seen at Informatica?