I absolutely agree with Claire! With a non-ITSM system building a new environment and migrating your definitions/data (via the API) is likely *way* easier than going through an upgrade(s). Not only will this very likely save you time, frustration and hair on your head but you will end up with a cleaned up environment because you will find things that are no longer relevant and leave those out of the new system.
For example in 2009 we moved our custom system from AR 7.0.01 to AR 7.5 by building a new 7.5 system and importing defs/data. Since then we have upgraded that same database to 7.6.04 and now 8.1.02.001. Along the way we have changed to new app/db servers and have upgraded SQL as well. My team recently started the discussion of building a new AR DB from a fresh install the next time we upgrade a major AR version, just like we did in 2009. In our case we are currently using Help Desk 6 and everything else custom (ok so it isn't a completely custom system however HD had been so customized and so far out of support we consider it ours now. We even converted the HD objects to Custom.). This year we are starting the process of building a custom app to replace HD6. With HD6 we have a *ton* of CMDB objects that have never been used. Also at one point we had SLA installed. Instead of surgically removing the CMDB/SLA objects from our DB we'll likely build a new DB from a fresh install and just leave all the stuff we no longer want behind. We'll use the API for *everything* that we "move" to make sure all definitions and data are check against the current version as they are brought in. HTH, Jason On Mon, Jan 5, 2015 at 8:39 AM, Sanford, Claire < claire.sanf...@memorialhermann.org> wrote: > Your last line is the answer!! If you can do that, you will save yourself > quite a bit of pain!! > > "...do a "new install" and import my custom forms and data with migrator." > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Carina Burns > Sent: 3 January 2015 05:53 > To: arslist@ARSLIST.ORG > Subject: Re: Help with upgrade path > > I did have to apply the fix on the Schema_Archive table not because we had > data but because it was the wrong field type (Varchar2 instead of Number) > and was throwing errors. Interestingly, yours is the second post I've > found about deleting the Flashboard forms (if you don't use them) in order > to upgrade to 7.64. > > I'm trying to upgrade to 8.1.2 from 7.1, and it's throwing an error about > not being able to update the FB:User Privilege form. It says the form > doesn't exist (and sure enough, it isn't there when looking with Developer > Studio). I am starting to think that with the ARS Server upgrade option, > it expects certain forms to be there from earlier upgrades and hence > doesn't import them. I will try deleting the flash board forms and running > the upgrade again to see if it loads them all. > > Another point is that I get unique index errors in the upgrade logs about > the ADF_ServerApps and ADF_GroupUser forms...Neither of those forms show up > when looking with Developer Studio either. I find it amusing that it > gives index violation errors since I don't have these forms on my 7.1 > install meaning clearly I can't have duplicate records! > > It's really looking like I may have to stair step my upgrade from 7.1 to > 7.5 to 7.64 and then to 8.1.2. Although support at BMC is convinced that > I should be able to go from 7.1 to 8.1.2 because I have only custom forms > and no mods to the stock ARS forms. > > I have a crazy idea that I may try. Before I went down the thorny upgrade > path, I did a "new install" of the 8.1.2 server to get all the binaries > onto the new machine. Before truncating everything and importing my 7.1 > ARADMIN schema, I did a database export of the pristine ARADMIN schema. I'm > really tempted to export off my upgraded 7.1 ARADMIN schema then reload > that pristine ARADMIN schema. I would then export the definitions for the > forms the upgrade installer thinks I am missing and then bring the upgraded > 7.1 ARADMIN schema back in, import the definitions for those forms, and > then run the upgrade installer for ARS 8.1.2 again. > > Yup, crazy. But my other alternatives if I can't straight upgrade is to > SLOWLY go thru each upgrade or do a "new install" and import my custom > forms and data with migrator. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the > Answers Are, and have been for 20 years" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
