Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 275630 - Last Review: March 10, 2004 - Revision: 2.1
INSERTS from DTS to DB2 Through OLE DB Provider for DB2 May Not Work Correctly
This article was previously published under Q275630
If a DTS package is built to export a SQL Server table to DB2/MVS (version 5.1) by using the Microsoft OLE DB Provider for DB2 (DB2OLEDB) and the
AUTOCOMMIT property of the provider is set to FALSE, the following error may be reported:
[OLE/DB provider returned message: A SQL error has occurred. Please consult the documentation for your specific DB2 version for a description of the associated Native Error and SQL State. SQLSTATE: 24501, SQLCODE: -501]
To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
215838Â
(http://kbalertz.com/Feedback.aspx?kbNumber=215838/EN-US/
)
How to Obtain the Latest SNA Server Version 4.0 Service Pack
Set the
AUTOCOMMIT property of the provider to TRUE.
Microsoft has confirmed that this is a problem in Microsoft SNA Server version 4.0.
This problem was first corrected in SNA Server 4.0 Service Pack 4.
You can apply the hotfix to resolve the error message that is shown in the "Symptoms" section, however, for the DTS export or import to work correctly, the
AUTOCOMMIT property of DB2OLEDB must be set to TRUE.
If you set the
AUTOCOMMIT property of the provider to FALSE, a COMMIT may never be issued, and therefore the inserts are rolled back. Users can still work around this behavior by writing their own transformation script for use with DTS, to issue a commit after every few inserts.
APPLIES TO
- Microsoft OLE DB Provider for DB2
- Microsoft OLE DB Provider for DB2
| kbbug kbfix kbsna400presp4fix kbqfe kbsna400sp4fix KB275630 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate