May 5, 2006 at 12:14 pm
I am connecting to a DB2 on a Unix and trying to update some data in one table. I have verified the connection as I can move data from DB2 to SS2k. The problem I am having is while updating the DB2 table, it gives me an error "Number of failing rows exceeded maximum".
Any one been able to connect successfully to DB2. I am using DB2 Connect and have tried the OLE DB and ODBC connections.
Any suggestions,
TIA
May 8, 2006 at 8:00 am
This was removed by the editor as SPAM
May 10, 2006 at 2:17 pm
I've come accross this error with a goodish number of different datasources. Specifically with a postgreSQL db that was setup so that it was case sensative. You could send a create table statement like
create table foo(
Id int4,
Column1 varchar(25)
)
But when you tried to refer to the table if you didn't specify the column name as Column1 and instead used column1 it would fail with that error.
Also, make sure none of your column names are reserved words in db2. A previous web developer thought it would be a good idea to name a column order. If you didn't use "order" or [order] to refer to it you would receive the same error.
hope this helps.
-Luke
Also check you permissions on the db2 datasource. being able to read from it doesn't nessecarily mean you can write, modify, delete, update etc.
May 11, 2006 at 9:26 am
Thanks for your response, but am not sure if case sensitivity is the problem. I did a test with a foo table and that didn't work either. However, this time the error is driver is incapable. Moreover, DTS auto selects the tables from the source and destination data connections.
I am more leaning towards a tablespace issue.
What do you think?
TIA
May 11, 2006 at 11:51 am
If you're getting a driver incapable error just for grins why don't you try running the odbcConf Tool it can be downloaded from microsoft here. I had a problem with Ms not supporting one of the drivers that I was using because the conformance level wasn't high enough.
As for my foo example from before, I meant more or less that you need to verify what permissions the Sql agent account and your account have on that datasource. while you're developing the package you're connecting with your rights when it runs as a scheduled task.
I'm not terribly familiar with db2, but I'm sure there is some quivalent to QA for it. Try connecting with that from your SQL box via the same odbc or ole drivers and such and see if you can connect that way.
May 12, 2006 at 12:50 pm
Ok, i tried the tool and it gave me a conformance level 1. The current odbc version is 3.52 and the driver version is 3.51.
I tried looking for some documentation on what that means but nada.
So what does this mean?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy