Hi Forum,
I was testing a job in my pc and appear this message when try to view data in the ODBC stage:
Error executing View Data command:
##F TDOD 000004 11:28:11(034) <main_program> Fatal Error: Could not connect to datasource[DataDirect][ODBC lib] Data source name not found and no default driver specified.
This job was working ok, but, that is not the problem, i open the job from other pc and i can view data !!!!
Anybody has an answer for this case????
Could not connect to datasource ODBC
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 133
- Joined: Wed Mar 05, 2003 4:19 pm
- Location: Lima - Peru. Sudamerica
- Contact:
Could not connect to datasource ODBC
Saludos,
Miguel Seclén
Lima - Peru
Miguel Seclén
Lima - Peru
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 5
- Joined: Tue Sep 23, 2008 2:30 pm
- Location: Michigan
Possible causes
[Hi,
This might be due to two reasons
1. The ODBC DSN is not setup on your system from where you are trying to access the JOB (System DSN). Make sure that you have admin access to setup the DSN on your PC.
2. Your profile with which you are connecting is not having access to the .odbc.ini file in the UNIX box.
This might be due to two reasons
1. The ODBC DSN is not setup on your system from where you are trying to access the JOB (System DSN). Make sure that you have admin access to setup the DSN on your PC.
2. Your profile with which you are connecting is not having access to the .odbc.ini file in the UNIX box.
Thanks & Regards,
Raj
Raj
-
- Participant
- Posts: 5
- Joined: Tue Sep 23, 2008 2:30 pm
- Location: Michigan
Possible causes
[Hi,
This might be due to two reasons
1. The ODBC DSN is not setup on your system from where you are trying to access the JOB (System DSN). Make sure that you have admin access to setup the DSN on your PC.
2. Your profile with which you are connecting is not having access to the .odbc.ini file in the UNIX box.
This might be due to two reasons
1. The ODBC DSN is not setup on your system from where you are trying to access the JOB (System DSN). Make sure that you have admin access to setup the DSN on your PC.
2. Your profile with which you are connecting is not having access to the .odbc.ini file in the UNIX box.
Thanks & Regards,
Raj
Raj
-
- Participant
- Posts: 5
- Joined: Wed Sep 17, 2008 12:24 am
- Location: Think BIG ,Start small and Skills fast
-
- Participant
- Posts: 133
- Joined: Wed Mar 05, 2003 4:19 pm
- Location: Lima - Peru. Sudamerica
- Contact:
Re: Possible causes
Hi Raj, thanks for your comments.
The conection was seted in the .odbc.ini, in the pc nothing. I dont need to set an ODBC dns in the pc because the server is running on the unix box.
and the user is the same when connect in the differentes pcs.
The conection was seted in the .odbc.ini, in the pc nothing. I dont need to set an ODBC dns in the pc because the server is running on the unix box.
and the user is the same when connect in the differentes pcs.
Saludos,
Miguel Seclén
Lima - Peru
Miguel Seclén
Lima - Peru
-
- Participant
- Posts: 5
- Joined: Tue Sep 23, 2008 2:30 pm
- Location: Michigan
Re: Possible causes
Hi,
Make sure that the other PC doesn't have any client tools for connecting to the Database - Since this is DataDirect Driver - it might be using some client library files from the local system. Refer to the following link also from DataDirect KB.
http://cp-datadirect.talismaonline.com/ ... e=3352&p=4
Make sure that the other PC doesn't have any client tools for connecting to the Database - Since this is DataDirect Driver - it might be using some client library files from the local system. Refer to the following link also from DataDirect KB.
http://cp-datadirect.talismaonline.com/ ... e=3352&p=4
Thanks & Regards,
Raj
Raj