We did an upgrade (mis-nomer) last year. After 3 months of trying to upgrade we ended up just creating new servers and export/importing objects. The biggest gotcha we ran into was when you import forms to the new database it changes the form ID (T236 became T450). Any sql statements included in workflow needed to be updated and external programs needed to be updated.
There were other things and if you take the time to search archives I described them pretty extensively. Good luck!! Susan On Tue, Apr 10, 2012 at 11:05 AM, David M. Clark <[email protected]>wrote: > ** > > Folks,**** > > ** ** > > I am finally in the process of upgrading our 6.03.00 patch 017 > implementation to the latest offered. By “upgrade” I mean a transfer > between old and new servers, not on the same server. The revs are > apparently too far apart to use Migrator to transfer code between, so I > will be using a 7.1 server as an intermediate transfer point. Migrator 7.1 > from the 6.3 box to the 7.1 box, then the latest Migrator from the 7.1 box > to the 7.6.04 box. I’ll also be using Export/Import tools as needed. Note > that no BMC Remedy applications are involved here, though I will be loading > ITSM later. My concern now is only with in-house developed code created > under or compatible with version 6.3. Solaris and Oracle on both sides.** > ** > > ** ** > > Anyone ever done this or have any suggestions as to problems that I may > encounter?**** > > ** ** > > Thanks,**** > > ** ** > > -David**** > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
