May 13, 2006 at 6:18 am
I have a job that runs an SSIS package that brings data from an iSeries box and loads staging tables in SQL Server, It is scheduled to run at 3:00AM. It was working fine until last week, now it loads several of the tables then dies giving the following error.
The jobs runs fine if you start it manually. I am using the SQL Server destination.
Event Name: OnError
Message: An OLE DB error has occurred. Error code: 0x80040E14.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Time-out occurred while waiting for buffer latch type 4 for page (1:546008), database ID 6.".
May 16, 2006 at 8:00 am
This was removed by the editor as SPAM
May 16, 2006 at 3:03 pm
Does it fail on the same table/import load each time? Since it did work without issue, the problem is probably not within SQL Server, it is probably within the data being imported. If it does fail on the same import stage, I would focus on the data within that load.
If it is possible to process the inputs manually, then I'd try that to see where it is failing at.
I once had an import of text files that worked fine, then suddenly failed because the text delimination was double quotes and some yahoo entered a name in the database as O"Brian instead of O'Brian.
Not sure this will help you at all, but it may be a place to start.
May 17, 2006 at 6:06 am
I wasn't failing on the same table each time, but the really strange part is that I deleted and recreated the schedule, not the job or the package, and now it's running fine again.
May 18, 2006 at 11:35 am
Contact your network administrator or check the event log - this could point to data corruption due to a hardware error.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply