DTS and SSIS erros

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
".
shadycAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dbaSQLCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vitor MontalvãoMSSQL Senior EngineerCommented:
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
shadycAuthor Commented:
The job ran fine today but i'll check with that DB2 database too.Thanks for the info
0
dbaSQLCommented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.