390600 is the Admin thread. That makes me think it is something happening during the loading of objects into the server's memory cache. With the SQL logging on and restarting the server you should be able to cross-reference the time of the error in the arerror.log file with what is being loaded in the arsql.log file.
Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, September 22, 2010 2:46 PM To: [email protected] Subject: Re: Reposting because we really our running out of options, and need help: UPGRADE from 7.0.01 to 7.5 issues - Data types are not appropriate for relational operation (ARERR 313) ** There was a few filters that were firing. We verified all of them, couldn't find anything wrong with them, so we did a backup and deleted them. Still have the error showing up at startup. Thank you, -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, September 22, 2010 2:40 PM To: [email protected] Subject: Reposting because we really our running out of options, and need help: UPGRADE from 7.0.01 to 7.5 issues - Data types are not appropriate for relational operation (ARERR 313) ** I am reposting this since I did not get any replies and we are running out of options. I am still hoping that someone has an idea or a suggestion on what we can try. We have this issue escalated with BMC and been looking for a reason/solution/fix for 2 weeks now. *********************************************** We have a total of 9 servers (3 dev, 3 test and 3 prod). Each of them have different applications running (1 has old ITSM 4 and 5 mixed, 1 has home-grown apps with some web apps and the last one is 100% web home-grown apps). They all are in the process of being upgraded from 7.0.01 patch 008 to ARS 7.5 patch 006. All 3 dev have been upgraded and 1 test server was also upgraded. On 2 of the 3 dev server and on the test server we get the same error at start-up: 390600 : Data types are not appropriate for relational operation (ARERR 313) only at start-up of the server. The third dev server has no error. None of the servers had that error before the upgrade. The applications on all 3 dev servers were tested and we cannot get reproduce the error at all. Only shows up at startup Since we were not able to get any information from the Logs beside the error showing in the arerror.log, we decided to take a more drastic approach: After doing a backup: Deleted all the filters , restarted the server ==> error still shows up Deleted all the escalation, restarted the server ==> error still shows up Opened all the forms that have table fields, checked the Table field Properties and deleted the forms that had errors on those table fields ==> error still shows up We are about to do the same with View forms. We are running out of things to delete. And we do not feel confident in upgrading our production servers with this error in our logs. I am running out of ideas. Anyone? Really need suggestions, ideas, help. both are ARS 7.5 patch 6 [ Home grown apps on one server and old ITSM (mix of 4 and 5) with no longer working ITSM workflow just the forms ] SQL 2005 (remote database) Win 2003 sp2 servers Thank you, Pascale Boyer Remedy Technical Lead & Developer Daimler Trucks North America LLC Montgomery Park, 9th floor Portland, OR 97210 U.S.A Phone:503-745-6569 Email:[email protected] http://www.daimler-trucksnorthamerica.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
