Sorry if this seems overly simply...but a VERY simple procedure would be to not allow DB changes to the production DB in the middle of a production day. That's what maintenance windows are for. I would say a company policy preventing them from doing such a thing would stop them, and stop the issue you are experiencing.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of L G Robinson Sent: Tuesday, February 03, 2009 7:51 AM To: [email protected] Subject: Trapping SQL error in an active link Hi Folks, I have a problem with an active link set field action that utilizes an SQL statement. The problem stems from the fact that the SQL command is issued against a database table that is maintained by another group. Occasionally, they will update the table in the middle of the day, causing the table to briefly cease to exist or lose it's permissions. When this happens, the active link fails with one of the following error messages: ARERR [552] Failure during SQL operation to the database: E911..E911Remedy not found. Specify owner.objectname or use sp_help to check whether the object exists. ARERR [552] Failure during SQL operation to the database: SELECT permission denied on object E911Remedy, database E911, owner dbo (Sybase 10330) This data is not critical to the normal functioning of the application, so I am looking for a solution that allows me to "ignore" this error in the active link. As far as I can tell, I can control what happens if "no requests match" and if "multiple requests match", but there is no way to trap the SQL error condition and choose to ignore it. About the only thing I have been able to come up with so far is to run a cron job periodically that will check for the existence of the table and the correct permissions. The cron job could then set some external flag in the file system or call an API program to set some internal global within my application. Then I could check the global or the external flag in an active link before invoking the SQL call. Seems overly complicated and convoluted to me. Does anyone have a better approach? ARS: 5.01.02 patch 1313 on Solaris 2.8 Sybase: 12.5.2/EBF 11790 on Solaris 2.8 Thanks. Larry Larry Robinson [email protected] Office of Information Technology NC State University 919-515-5432 Voice Raleigh, NC 27695-7109 919-513-1893 FAX ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
