Hi,
It seems much easier to just install a 8.1 and export/import the def file
followed by a migration of the data using the API.
RRR have tools to assist you in many of these steps, as you may need to fix
some parts of your application to fully functional.
As for upgrading from HelpDesk to ITSM 8.1, I think you should start from
scratch on that one...
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Hello All,
> We are trying to perform an upgrade of our Remedy Instance on v5.01.01 to
> v8.1.
> So far we have upgraded ARS from v5.1.2 > v6.3 > v7.1 > v7.6.04.(Solaris)
> on Dev Environment as a proof of concept.
> We are targeting to Upgrade to v8.1 and also to move to Linux(VMware ESX).
> To accomplish this here's what we are trying to do:
> 1. Upgrade ARS to v7.6.04(Solaris), take DB(10g) copy
> 2. Install a fresh ARS of v7.6.04(Linux) + DB(10g)
> 3. Drop DB of Step 2 + Attach DB copy from Step 1(so we will have a ARS
> v7.6.04 with Linux on 10g DB)
> 4. Upgrade DB to 11g
> 4. Run upgrade install from ARS v7.6.04 to v8.1
>
> Based on the above approach/ steps I have few questions:
> 1. Is the above approach feasible?, as the aim for our upgrade is to bring
> our Remedy instance to a supported version.
> ARS upgrade from v5.1.2 to v8.1. Also, we would like to move away from
> Unix/Solaris platform to Linux VM platform.
> 2. We also have ITSM 5.6/Remedy HelpDesk v5.1.2 - How do we handle this? As
> for now, we are only thinking of upgrading ARS not ITSM.
> 3. Also, my understanding is v7.5 onwards, there has been drastic changes.
> Any caveats of losing our customizations(Customization on HPD as well as
> Custom applications we have in place)? How do we handle these?
> 4. Dev Server - As a proof of concept on our Dev Server, we upgraded ARS
> from v5.1.2 to v7.6.04 so far. Working on to upgrade to v8.1 now.
> 5. DB from non-unicode to unicode - Our Dev DB was already Unicode. Whereas
> our Prod DB is non -unicode, so at what point do we have to convert from
> non-unicode to Unicode(before running v6.3 Upgrade install)?
>
> Source - ARS v5.1.2 + ITSM v5.6(HelpDesk v5.1.2) + Custom/Home grown apps.
> Destination/Target - ARS v8.1 + ITSM v5.6(HelpDesk v5.1.2) if supported or
> ITSM v8,1(Service Desk) + Custom/Home grown apps.
>
> Environment Information:
> Current Production:
> Environment Info:
> AR Server Version : 5.01.02 Patch 1313
> Hardware : sun4u
> Operating System : SunOS 5.10
> DB : SQL -- Oracle
> DB Version : 10.2.0.5.0 - 64bi
>
> Current Development (where we are running ARS Upgrade Installs):
> Environment Info:
> AR Server Version : 7.6.04 SP4 201209051922
> Hardware : sun4u
> Operating System : SunOS 5.10
> DB : SQL -- Oracle
> DB Version : 10.2.0.5.0 - 64bi
>
> Does the above approach feasible? I would highly appreciate any
> help(practical lessons, gotchas, caveats, etc) you can provide.
>
> Regards,
> Raj
>
> _______________________________________________________________________________
> 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"