That did the trick - thanks. I have no idea how it could have happened, but at least our web app can log in again.

So I guess there is nothing to be done and I have to start deleting backup jobs until I figure out which one this is.

SELECT distinct project_name, project_descrip, budget_version

FROM nontouch.projects_600

UNION

SELECT distinct project_name, project_descrip, budget_version

FROM nontouch.projects_500 p5

WHERE NOT EXISTS

(SELECT project_name, project_descrip, budget_version

FROM nontouch.projects_600 p6

WHERE p6.project_name = p5.project_name) ...

SELECT project_name, project_descrip, budget_version

FROM nontouch.projects_600

GROUP BY project_name, project_descrip, budget_version

UNION SELECT project_name, project_descrip, budget_version

FROM nontouch.projects_500 p5...

Turns out my pass through query in SQL Server to DB2 requires an = 2 syntax instead of LIKE '2'

Response from Microsoft:

280106 HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in SQL Server

http://support.microsoft.com/?id=280106

Your Registry settings should be:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]

"OracleXaLib"="oraclient8.dll"

"OracleSqlLib"="orasql8.dll"

"OracleOciLib"="oci.dll"

MS SQL Server HKLM\SOFTWARE\Microsoft\MSDTC\MTxOCI settings default to...

Added SET XACT_ABORT ON/SET XACT_ABORT OFF to the stored proc and no change. Still the same error message.