Wow, we never tried this. It makes sense, just never thought about it. We see this with ARS/Migrator 7.5 (various patches). Usually we were migrating to production and didn't schedule an outage to make a handful of changes, so we don't restart the arserver (right away anyways). It sure would have been easier than ripping out the new db columns and metadata.
After this happened a few times we started manually creating any new fields in Dev Studio or importing just the def of forms that have new fields and then using Migrator for the rest of the changes. Our best guess was that the form definition was not being update properly but the db and metadata work was being done. I guess we were partially right, the form def wasn't being updated in the server cache. Thanks! Jason On Tue, Apr 27, 2010 at 12:16 PM, Grooms, Frederick W < [email protected]> wrote: > It appears that Migrator does not always force the arserver to reload its > internal cache. I have found that a stop and start of arserver is usually > the safest route after a migration. > > Glad I could help > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Pruitt, Christopher (Bank of America > Account) > Sent: Tuesday, April 27, 2010 1:59 PM > To: [email protected] > Subject: Re: Remedy Migrator 7.1 patch 009 Issue > > OUTSTANDING Fred, > > That did the trick. You, as always, a valuable member of the ARSList who > always has the answers we need, you are our lifesaver. > > Christopher Pruitt > Business Consulting III > HP Enterprises Services > [email protected] > www.hp.com > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Grooms, Frederick W > Sent: Tuesday, April 27, 2010 1:41 PM > To: [email protected] > Subject: Re: Remedy Migrator 7.1 patch 009 Issue > > Chris, > > Have you stopped and restarted the arserver app? > > We have seen this problem where Migrator does not update the field count in > arschema correctly (and we find out when we restart the arserver app). If > you get errors (Field count incorrect and form not loaded) when starting > then stop the arserver again and update arschema with the correct # of > fields from aradmin.field. > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Pruitt, Christopher (Bank of America > Account) > Sent: Tuesday, April 27, 2010 1:23 PM > To: [email protected] > Subject: Remedy Migrator 7.1 patch 009 Issue > > Have anyone of you noticed this behavior from the Remedy Migrator 7.1 patch > 009? > > Issue: > We extract forms from one server and create a def file. There were 131 > forms in the def file. > 6 Regular > 5 Joins and > 120 Display Only > > We open the def with Migrator and convert it to a Migrator file. Ok so far. > This works great. Now the issue. > When we migrated the file to the new server the Migrator gave no errors. It > report all imported 100%, however, when we look some or the forms they are > missing fields. We query the aradmin.field table and it reports that all > the fields are present. > > We look at the forms via the admin tool and they are not there. We even > checked the Form, Select View, Fields In View and these fields are not > listed. But the field table shows them in the database. > > We try and re-import the forms that has the missing data and we get the > error message ARERR 382 violates index and it will not let us import it. > > We even tried to blowing away the record in the aradmin.field table, > blowing away the C column in the t-table and tried changing the field count > in arschema. Then import the form from another server that is a copy of the > original form without the fields and did a "Delete excess fields" and then > tried to re-import the form and we still get the ARERR 382 error. > > > Environment: > Remedy version: 7.1.00 Build 200708221849 > OS: SunOS 5.9 > Database: Oracle 10.2.0.4.0 - 64bi > > Two questions, > > Has anyone ever experiences this before? > How can we fix this without blowing away the forms and re-importing them, > because some has a HUGH amount of data that would take a very long time to > export and re-import. > > Christopher Pruitt > Business Consulting III > HP Enterprises Services > [email protected]<mailto:[email protected]> > www.hp.com<http://www.hp.com/> > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
