Hi, Listers!

 

Has anyone successfully upgraded from ITSM 7.0.03 to ITSM 7.6.03?  Can
anyone shed some light on it?  I also like to know if anyone encounters
any issue in their post-upgraded ITSM 7.6.03 production environment. Is
ITSM 7.6.03 stable?

 

We have looked at 7.6.04 upgrade but decided to go with 7.6.03 since
User Tool 7.6.04 doesn't support ITSM 7.6.04 and we are not ready to
replace the user tool with the web browser client. Our mid-tier server
is primarily for requesters at this point. 

 

We currently have:

 

OS: Solaris 10

Database: Oracle 10gR2 (remote)

ARS: 7.1 patch 7

CMDB: 2.1 patch 5 (no CI in production so far)

ITSM - Incident, Problem, Change, and Asset (not used): 7.0.03 patch 9

SRM: 2.2 patch 4

SLM: 7.1 patch 2

 

The upgrade plan is:

 

Phase 1:

 

Upgrade ARS 7.1 to 7.6.03

Upgrade CMDB 2.1 to 7.6.03

Upgrade Mid-tier 7.1 to 7.6.03

Upgrade User Tool 7.1 to 7.6.03 (or 7.6.04)

 

 

Phase 2:

 

Upgrade ITSM 7.0.03 to 7.6.03

Upgrade SRM 2.2 to 7.6.03

 

Phase 3:

 

Upgrade SLM 7.1 to 7.6.03

Install KM 7.6.03 (new)

 

I am starting to become frustrated about the whole upgrade after a few
ITSM 7.6.03 upgrade attempts in my dev environment. The ARS and CMDB
upgrades seem to be fine so far, but ITSM is a challenge. My biggest
concern so far is the time it takes to run ITSM 7.6.03 upgrade
installer. I have lost count of trying ITSM upgrade. The last attempt
was eventually completed after more than 90 hours. It took that long
even after I had turned on Dev Cache Mode and had basically commented
out in armonitor.conf all non-used processes including dispatcher,
arplugin, email engine, assignment engine, approver, slm, arcmdbd,
arrecond, normeng, and atriumplugin. I still got many warning messages
that indicate multiple def/arx file import failures.

 

 

Thanks,

Eric


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to