Service Desk Practitioners Forum
cancel

migration issues of migrating HPSD 4.5 sp 11 to sp 22

Highlighted
Fepelof_1
Respected Contributor.

migration issues of migrating HPSD 4.5 sp 11 to sp 22

Hi there,

has anyone faced this ? Which issues must be considered, pay attention ?

thanks
Fep
9 REPLIES
Ruth Porter
Acclaimed Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

Hi Fep,

Main thing is the alteration to the structure of attachments - make sure you check the readme and upgrade instructions and you should be OK.

Regards

Ruth
http://www.teamultra.net
De Naeyer Robby
Trusted Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

Indeed attachments, but also the JAVA version needs to be upgraded to 1.4.
Mark O'Loughlin
Acclaimed Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

Hi,

1) attachments structure changes
2) Java to be upgraded
3) There are options to upgrade the 4k information fields to CLOB. You can do this at the tiem of upgrade or at a later date. it does take time if you have a lot of records ad it test it out if you have reporting tools that expect a certain type of field (i.e. not CLOB)
Craig R Taylor
Honored Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

Hi Mark,

What do you mean by CLOB? (Brain no worky this morning)

Thanks

Craig
You can observe a lot just by watching. - YOGI BERRA
Mark O'Loughlin
Acclaimed Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

The 4k info text fields are set to varchar32 (or similar) and can cuase jdbc errors when using certain characters as the DB field is of limited size and cannot hold the data (for multi byte characters) so the records could not be closed and caused great annoyance among staff and admins.

Converting these fields to CLOB means that they have more than enough room to store the data on the DB.

However some reporting tools may expect the old vahchar type DB field and updating the DB to CLOB can be time comsuming if you have a lot of records in the DB - which meand DB downtime.

Craig R Taylor
Honored Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

I guess the 4k field conversion to CLOB is covered under ITSM008420. It also allows the 64K field to be conveted to CLOB. However, you can only do the conversion for Oracle not MS-SQL.
You can observe a lot just by watching. - YOGI BERRA
Mark O'Loughlin
Acclaimed Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

True - tks for adding that.
Craig R Taylor
Honored Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

Another thing that may need to be considered is if you have anything written with the web-api. Your JAR files will need to be recompiled and redeployed.
You can observe a lot just by watching. - YOGI BERRA
Ken Briscoe
Acclaimed Contributor.

Re: migration issues of migrating HPSD 4.5 sp 11 to sp 22

There is one more tricky one.
In the past DB rules could update custom fields regardless of whether they were active for a given category or not. Not so any more. If you have a field which is not active for the current category of say, a change, then you'll get an error in the log like this..
"Thu, 14/06/2007 15:54:36 Program error: the attribute 'call duration.' of this service call cannot be modified, because the service call item was opened in view mode or because the attribute is read-only."

We had this for several custom fields used behind the scenes for info or workflow control, and it caused quite a problem.
You need to check your log carefully.
The solution is to activate the custom field for all categories - but that may not be what you want of course.
I logged it with HP - they insist this is an enhancement and refused to acknowledge it as a bug, and said they won't change it back.

Also there is a bug that prevents Service and SLA DB rules updating any custom fields...HP have a hot fix for that one.
Otherwise, our SP7 to SP22 went OK.
Good luck......Ken.
My email is kenilian@bigpond.com.au