You don't mention the nature of the processing you're doing...so here's some 'potential' scenarios... :) But in reality it could be lots of things...
1) Lost connection to UV Is it possible you connection is timing out? That is, your UV ODBC connection is timing out - possibly? Check the timeout in your unirpcservices file for ODBC connections and check what your application is doing - perhaps it is opening the connection first, doing a MS SQL query and in the mean time the connection is lost? 2) UV SQL Query failure due Check the log files on the UV side in the account where you queries are connecting to for any log files (uvodbc.log or uverror.log, etc) applicable for your UV release. Is the files/tables you're querying dynamic hashed files (are they OK? Not need of repair/fixing) and have you checked by "manually" doing the "same" SQL query from UV itself using the CONNECT verb or at the TCL prompt in the account you're connecting to? Are there any SQL Updates going on? If so I'd be thinking that there is locking contention issues may be happening (such things you can't reproduce on demand)... I also wonder if your process is running out of memory or the like (any core files?)...perhaps consider explicitly setting up the buffers in the uci.config. But that seems unlikely and perhaps should be a last resort type change! Yet, again speculation unless we really know what you're query is doing... It may be worth while to turn on some UVODBC logging if you still have problems - beware of log file sizes though! :) Regards, David -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Ken Ford Sent: Wednesday, 24 November 2010 12:44 PM To: u2-users@listserver.u2ug.org Subject: [U2] Connectivity issue with ODBC - SQL. From: Ken Ford Sent: Wednesday, 24 November 2010 11:37 AM To: 'u2-users@listserver.u2ug.org' Cc: Angel Frost Subject: Connectivity issue with ODBC - SQL. Could anyone shed light on the following problem we are having? We have a Windows 2003 R2, running SQL Server 2008R2 connecting to Universe 10.3 on AIX 5.3, via UniVerse ODBC driver 3.7 And are getting the error below intermittently (sensitive details represented with '*'s): Message: Executed as user: *******. The OLE DB provider "MSDASQL" for linked server "**" reported an error. The provider reported an unexpected catastrophic failure. [SQLSTATE 42000] (Error 7399) Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "**". [SQLSTATE 42000] (Error 7303). The step failed. We have checked the user group list archives, and couldn't find anything matching this completely. Thanks for any help you can provide, Ken Ford Senior Software Engineer - Universe "Today, the Universe - tomorrow, the world!" ************** IMPORTANT MESSAGE ***************************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ************************************************************** _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
