March 19, 2008 at 6:28 am
Greetings.
Some background: I have a SQL 2000 database that is currently handling reporting and data warehouse functions. It pulls data from all our production dB servers, including 3 Sybase ASE 12.5.2 servers, using DTS packages. All data pulls in just fine. I use Sybase ODBC drivers on this box.
I'm trying to get the datawarehouse converted to SQL 2005 SP2, using DTSX / SSIS. I wrote the extract packages using SSIS, and, for the most part, they run fine. I'm using the Sybase OLEDB drivers, version 12.5.2 for connectivity.
All the database structures are identical on my 3 ASE servers. One of the ASE servers is located on the same LAN segment as my MS-SQL servers. I have two WAN Segments; the lower-speed WAN segment contains 1 ASE server, and a higher speed WAN segment contains 1 ASE server.
The extract packages are identical for all three ASE servers, differing only in which server they connect to.
ASE LAN Server 1 - all DTSX packages run fine.
ASE WAN Server 2 - all DTSX packages run fine.
ASE WAN Server 3 - the longest running DTSX package fails intermittently. All packages are typically executed during off-hours; however, if I manually execute a failed package during peak business hours, it might run just fine.
The failure is always logged as: "Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "ASE OLE DB Provider" Hresult: 0x80004005 Description: "Socket closed.".
Now, the given package might run fine for a week, then suddenly it will fail with the above error.
I've checked everything I can think of (ASE configuration, load) and am coming up empty.
Now, to make matters even more interesting: I can successfully extract the same data, every night, with no problems to my SQL 2000 server, using DTS packages.
I also have a problem with creating an ASE Linked Server in SQL 2005: I can set up the Linked Server, and I can successfully view all databases on the server. I can also, for all databases except 1, view all tables in those databases. However, when I attempt to view tables in this one database, I get an error displayed in SQL Management Studio: "Value cannot be null. Parameter name: context (ObjectExplorer)." I can display views in this same database, however.
This linked server problem happens with all 3 of my ASE servers, and the behavior is identical. I also have this same problem in the November CTP of SQL 2008.
Coincidentally (?), the database which refuses to display in a linked server is also the database from which I'm having trouble extracting data on 1 server.
Thanks for any thoughts on this.
May 15, 2008 at 8:26 pm
hi,
i tried the document below pertaining to linking sybase 12.5 to sqlserver 2000 and sqlserver 2005
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=311875&SiteID=17
http://www.sybase.com/content/1029118/1029118.doc
but when our company upgrade the sybase to 15.x i can't find the oledb configuration stated on the document. so i can't linked the sybase 15.x now to sqlserver 2005. can somebody help me.!!!please...
where i can find the oledb configuration in sybase 15.xx..
tnx..
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply