Solved

DTS and SSIS erros

Posted on 2009-07-06
5
994 Views
Last Modified: 2013-11-10
I have DTS package which runs every night in prod and last night it did not ran and when Iam trying to investigate I see the following error messages


Step Error Source: Microsoft OLE DB Provider for SQL Server
Step Error Description:Time-out occurred while waiting for buffer latch type 2 for page (3:90235), database ID 12.


The SQL Code in the package is it uses select from a linked server As400 .(DB2)


In test it runs the same through and SSIS Iam getting the below message


Failed to acquire connection "STop_AMLLIB".
Connection may not be configured correctly or you may not have the right permissions on this connection.



Below is the error message a few days ago

OnError,Set DWU,,,6/27/2009 12:48:37 AM,6/27/2009 12:48:37 AM,0,0x,
OLE DB provider "IBMDADB2" for linked server "STop_AAGPROD" returned message " SQL30081N  
A communication error has been detected.  Communication protocol being used: "TCP/IP".  
Communication API being used: "SOCKETS".  Location where the error was detected: "10.20.30.11".  
Communication function detecting the error: "connect".  Protocol specific error code(s): "10060", "*", "*".  SQLSTATE=08001
".
0
Comment
Question by:shadyc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 17

Accepted Solution

by:
dbaSQL earned 500 total points
ID: 24793264
I'm guessing this may be a network issue.  Either something was changed, or there's simply a problem developing.  See this, w/the common db2 tcp/ip errors:
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.doc/doc/c0005607.htm

also this one, down in the middle has notes re the 10060 error code that you received a couple days ago:   http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21164785

0
 
LVL 49

Expert Comment

by:Vitor Montalvão
ID: 24802231
Check if you can reach DB2 database. As dbaSQL told may be network problem. Maybe things are ok now, so you should check it again.

Good luck
0
 

Author Comment

by:shadyc
ID: 24808833
The job ran fine today but i'll check with that DB2 database too.Thanks for the info
0
 
LVL 17

Expert Comment

by:dbaSQL
ID: 24809263
Glad to hear it, but that somewhat substantiates the possibility of a network problem that caused that first hiccup.

It happens, I suppose....  Not a whole lot we can do for SQL if our network is burping.  ;-)
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
Viewers will learn how the fundamental information of how to create a table.
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question