Driver error
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 101
- Joined: Mon Aug 13, 2007 2:32 am
Driver error
Hi,
I am getting this error:
[DataStage][SQL Client][ODBC][DataDirect][ODBC SQL Server Driver]The DataDirect ODBC driver you are attempting to access has been provided to you by IBM Corporation for exclusive use with IBM Information Server. You are not licensed to use this driver with any application other than IBM Information Server. If you would like to purchase a driver for some other use, please call 800-876-3101 or visit DataDirect at www.datadirect.com
Could any one suggest how to resolve this.
Regards,
Arnie
I am getting this error:
[DataStage][SQL Client][ODBC][DataDirect][ODBC SQL Server Driver]The DataDirect ODBC driver you are attempting to access has been provided to you by IBM Corporation for exclusive use with IBM Information Server. You are not licensed to use this driver with any application other than IBM Information Server. If you would like to purchase a driver for some other use, please call 800-876-3101 or visit DataDirect at www.datadirect.com
Could any one suggest how to resolve this.
Regards,
Arnie
-
- Participant
- Posts: 101
- Joined: Mon Aug 13, 2007 2:32 am
-
- Participant
- Posts: 101
- Joined: Mon Aug 13, 2007 2:32 am
I feel it is some connection problem.
When I try with ODBC(target) stage I can view data with condition: insert row without clearing.
but with condition:user-defined sql, the view data tab gets disabled.
And with DRS stage, when I do view data it says: DSP.Open GCI $DSP.Open error-100
Have u ever faced similar error before. Please help.
Regards,
Arnie.
When I try with ODBC(target) stage I can view data with condition: insert row without clearing.
but with condition:user-defined sql, the view data tab gets disabled.
And with DRS stage, when I do view data it says: DSP.Open GCI $DSP.Open error-100
Have u ever faced similar error before. Please help.
Regards,
Arnie.
-
- Participant
- Posts: 101
- Joined: Mon Aug 13, 2007 2:32 am
-
- Participant
- Posts: 101
- Joined: Mon Aug 13, 2007 2:32 am
well I almost went through whole dsxchange...got a similar kind of problem...in viewtopic.php?t=91340&highlight=
I have a longvarchar field len 2147483647. I changed this to longvarchar 2000 and then when I tried to view data it says:
[DataDirect][ODBC SQL Server Driver]COUNT field incorrect....
............................................................
............................................................
DSP.Open GCI $DSP.Open error -100
Please throw some light.
I have a longvarchar field len 2147483647. I changed this to longvarchar 2000 and then when I tried to view data it says:
[DataDirect][ODBC SQL Server Driver]COUNT field incorrect....
............................................................
............................................................
DSP.Open GCI $DSP.Open error -100
Please throw some light.
-
- Participant
- Posts: 101
- Joined: Mon Aug 13, 2007 2:32 am
-
- Participant
- Posts: 101
- Joined: Mon Aug 13, 2007 2:32 am
-
- Participant
- Posts: 101
- Joined: Mon Aug 13, 2007 2:32 am
ok here is the scenario that confuses me ....
In my job I am reading from a file and looking up with target table to get the max of sequence no and generation max+1 and then loading in the same target. That job was running well untill yesterday(now not running).
for testing purpose I broke the job in 2 parts. 1st part loads a flat file with new seqnuence numbers. and then 2nd job loads from thal file to the target.Even then it was not working and throwing driver,connection error etc as I have already mentions.Then I noticed that I am unable to even do view data in that target db.
I had a longvarchar column of len 2147483647 which I changed to len 20000 and then I was able to do view data....and job is also running fine. But now when I apply all this in that single job, it is again not working...the job just keeps on running for ever....when i abort the job,it says:[DataDirect][ODBC SQL Server Driver][libssclient22]ConnectionWrite (send()).
General network error. Check your network documentation.
Regards,
Arnie.
In my job I am reading from a file and looking up with target table to get the max of sequence no and generation max+1 and then loading in the same target. That job was running well untill yesterday(now not running).
for testing purpose I broke the job in 2 parts. 1st part loads a flat file with new seqnuence numbers. and then 2nd job loads from thal file to the target.Even then it was not working and throwing driver,connection error etc as I have already mentions.Then I noticed that I am unable to even do view data in that target db.
I had a longvarchar column of len 2147483647 which I changed to len 20000 and then I was able to do view data....and job is also running fine. But now when I apply all this in that single job, it is again not working...the job just keeps on running for ever....when i abort the job,it says:[DataDirect][ODBC SQL Server Driver][libssclient22]ConnectionWrite (send()).
General network error. Check your network documentation.
Regards,
Arnie.
In all honesty, Arnie, I'm a wee bit confused as well. We started off talking about using an IDENTITY column and now you are generating the sequence numbers yourself rather than letting the database do it for you? Is there any particular reason for that change?
I'm also unclear how you implemented the "max+1" logic. Did you do a single select to get the max value, say from outside your main job and then passed that into the job that needed it? That would work if you added @OUTROWNUM to the value for each row. However, it almost sounds like your lookup is in the main job and thus you are looking up the max value on each row, which means you'd need to use a transaction size of 1 so the lookup could 'keep up' in a manner of speaking.
When did the initial error come into the picture, before or after you "broke the job in 2 parts"? And why the Longvarchar? What actual data type in your target are you loading as a Longvarchar? What array size have you been using for that?
I'm also unclear how you implemented the "max+1" logic. Did you do a single select to get the max value, say from outside your main job and then passed that into the job that needed it? That would work if you added @OUTROWNUM to the value for each row. However, it almost sounds like your lookup is in the main job and thus you are looking up the max value on each row, which means you'd need to use a transaction size of 1 so the lookup could 'keep up' in a manner of speaking.
![Confused :?](./images/smilies/icon_confused.gif)
When did the initial error come into the picture, before or after you "broke the job in 2 parts"? And why the Longvarchar? What actual data type in your target are you loading as a Longvarchar? What array size have you been using for that?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers