Error: Failing rows exceeds max specified

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Data Warehousing » Data Transformation Services (DTS) » Error: Failing rows exceeds max specified

16 posts, Page 1 of 2

1 2 »»

Error: Failing rows exceeds max specified

Rate Topic

Display Mode

Topic Options

Author

Message

SA-1

Posted Thursday, March 23, 2006 3:29 PM

Ten Centuries

Group: General Forum Members
Last Login: Tuesday, June 11, 2013 8:04 AM
Points: 1,140, Visits: 936

Source: SQL Server 2K (Win2k)

Tool: DTS

Destination: DB2 (Linux)

Error Source: Data Pump

Error Message: The failing rows exceeds the maximum specified

Error Code: 80040E53

The thing I find strange is that the destination tab field type show as Graphic in the package. In DB2 they are VARCHAR.

I tried CStr in the transformation. I tried both IBM ODBC and IBM OLE DB Provider.

Any suggestions.

TIA

Post #268083

Site Owners

Posted Monday, March 27, 2006 8:00 AM

SSChampion

Group: General Forum Members
Last Login: Friday, May 18, 2007 3:36 PM
Points: 10,040, Visits: 1

No one has responded to this topic yet. Even if you don't have a complete answer, the original poster will appreciate any thoughts you have!

Post #268645

Andrei-176105

Posted Tuesday, October 09, 2007 4:44 AM

Grasshopper

Group: General Forum Members
Last Login: Thursday, June 21, 2012 8:56 AM
Points: 12, Visits: 63

Hello, our DB2 was converted to Linux and I am facing exactly the same problem. I replaced Data Pump with ActiveX for now. Did you figure it out? Thanks.

Post #408373

Luis Alfredo Lozada Portal

Posted Monday, December 31, 2007 1:00 PM

Valued Member

Group: General Forum Members
Last Login: Thursday, October 14, 2010 10:51 AM
Points: 73, Visits: 28

Some found the solution?

I have the same problem when inserted directly using the OLEDB Connection from an ExecutionTask runs smoothly, but when I have a load from a text file, fails with the same error you.

Plaease, Help me.

Post #437653

Andrei-176105

Posted Friday, January 04, 2008 10:12 AM

Grasshopper

Group: General Forum Members
Last Login: Thursday, June 21, 2012 8:56 AM
Points: 12, Visits: 63

If you are using DB2 Connect to connect to Linux DB2 from DTS package running DTS Data pump it happens because by default StaticCursor is selected and DB2 does not allow StaticCursor for Update\Inser\Delete.
You need to
1. Go to DB2 Connect Configuration Assistant
2. Right click on Alias
3. Select CLI Settings
4. Select SETTINGS tab
5. If you do not have CursorTypes property already click Add and select it from the list uncheking
STATIC checkbox
6. If you have it already click on current value and then uncheck STATIC box on pop up screen.
7. Exit saving everything

There is another way to do it thru DB2CMD utility commands. Change value to 6 or 7. Search for this command syntax on Google...

Note: On my workstation change was in effect imidiately, but on the server it required reboot. I do not know why...

Post #439034

Luis Alfredo Lozada Portal

Posted Friday, January 04, 2008 7:56 PM

Valued Member

Group: General Forum Members
Last Login: Thursday, October 14, 2010 10:51 AM
Points: 73, Visits: 28

No, I use DTS SQL Server 2000.

Help meeeeee

Post #439178

Luis Alfredo Lozada Portal

Posted Friday, January 04, 2008 7:59 PM

Valued Member

Group: General Forum Members
Last Login: Thursday, October 14, 2010 10:51 AM
Points: 73, Visits: 28

You can share your solution?

Post #439181

Andrei-176105

Posted Sunday, January 06, 2008 4:30 PM

Grasshopper

Group: General Forum Members
Last Login: Thursday, June 21, 2012 8:56 AM
Points: 12, Visits: 63

That is exactly what I am talking about: Data Pump task of DTS SQL server 2000.
It is used to load data between different sources\destination and it is the one that produces this error.
This thread is dedicated to this issue (see the initial post).
You sounded like you have the same problem - in this case solution is listed above, if not - you are on the wrong thread.

Post #439377