SQLSTATE=IM002,Code=0,Data source name not found

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
antojj
Participant
Posts: 30
Joined: Thu Dec 08, 2005 3:07 am

SQLSTATE=IM002,Code=0,Data source name not found

Post by antojj »

Hi,

Error obtained when a job is been ran in datastage designer.
steps:
1. I created database in sql server box (which is also hosting Datastage Server).
2. Designed the job to transfer data to another table using transformer.
3. Created DSN in the client box to connect to server box (For SQL Server).
4. Changed the properties in the Job Properties section with parameter values included to connect to SQL Server.
5. Ran the transformer and the following error is thrown.

dsr.metageta(get.dsninfo)(sqlconnect('#TargetConnection#','#T...
BCI Error:
SQLSTATE=IM002,Code=0,[datastage][sql client][odbc][Microsoft][..
Data source name not found and no default driver specified


Can anyone suggest me what might be the problem.
Antonio D'souza
dhiraj
Participant
Posts: 68
Joined: Sat Dec 06, 2003 7:03 am

Post by dhiraj »

Anto,
The DSN should be created on the server machine.
Create a system DSN on the server machine and the job should run fine.

Regards,
Dhiraj
balajisr
Charter Member
Charter Member
Posts: 785
Joined: Thu Jul 28, 2005 8:58 am

Post by balajisr »

Hi

Code: Select all

dsr.metageta(get.dsninfo)(sqlconnect('#TargetConnection#','#T... 
BCI Error: 
SQLSTATE=IM002,Code=0,[datastage][sql client][odbc][Microsoft][.. 
Data source name not found and no default driver specified 

This occurs when the dsn is not set properly.

Did you create dsn in the server where datastage server is present?

--Balaji S.R
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

If you see "#" characters in that style of error message it means that a job parameter of that name has not been found/resolved in the job. This probably means that it has been:
- omitted
- mis-spelled
- mis-cased

You must make sure that any job parameter reference in the job design - no matter where it occurs - exactly matches the job parameter name in the job properties.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply