Upgrade integrity server from 10.2 to 10.8 in one go?

[padams]

Hi,

We haven't upgraded our Integrity Server in a while and need to go from 10.2 to 10.8. Is it possible to upgrade directly to 10.8 or do we need to go from 10.2->10.3->10.4 etc.

I only ask because I remember doing one upgrade in the past where I skipped a release and it ended up missing a properties file (encryption.properties) due to a new feature that had been introduced in the previous release but was not created in the later release. Then I had to roll back and perform the intermediate upgrade before going to the next version.

Thanks in advance for any info.

Best regards,

Paul

[tmisner · Accepted solution]

Hello Paul,

Is there any specific reason you are looking to upgrade to Integrity 10.8 specifically? We have recently released Integrity 11.1 and recommend upgrading to the latest version.

First and foremost for an upgrade like this it is important to consider platform support. Please refer to the following documentation to confirm your current platforms are supported under the Integrity release you intend to upgrade to:

Integrity 11 Platform Support

https://support.ptc.com/WCMS/files/171619/en/Integrity_11_Supported_Platforms.pdf

Integrity 10 Platform Support

http://support.ptc.com/view?im_dbkey=142571

Upgrade Path

When upgrading from Integrity 10.2 to 10.8 you do not need to install every minor upgrade instance (i.e. 10.2 to 10.3 to 10.4). You will however need to install Integrity 10.7 before you can install any later versions of Integrity. The intermediary step to 10.7 is needed because a new table was introduced in this release. The aforementioned table provides a new model to store relationship data within the database. This new table was implemented because it scales much more efficiently than the previous table model it replaces. After the upgrade from 10.2 to 10.7 is complete data must be migrated from the old relationship table to the new relationship table. Please note the significant importance of this migration step. We highly recommend extensive testing of this data migration before it is implemented in production.

For more information on the relationship data migration after installing Integrity 10.7 please refer to Chapter 2 starting on page 57 of the following guide:

https://support.ptc.com/WCMS/files/164975/en/IntegrityUpgradingGuide_10_7.pdf

Please be sure to read through Chapter 1 of the above 10.7 Upgrade Guide as well for more information on best practices and recommendations prior to upgrading.

Similar Upgrade Guides are also available when upgrading to Integrity 10.8 or 11.1. They can be found here:

Integrity 10.8 Upgrade Guide

https://support.ptc.com/WCMS/files/168312/en/IntegrityUpgradingGuide_10_8.pdf

Integrity 11.1 Upgrade Guide

https://support.ptc.com/WCMS/files/172673/en/InstallUpgradingGuide_11_1.pdf

Please be sure to read through these guides for best practices and recommendations.

Hope that helps.

[padams]

Hi Tyler,

Our IT matches releases of its solutions with specific versions of Integrity, so I have to use 10.8 in this case.

Thanks for the info on the upgrade path, that is very useful. We will try it out on a test server first 🙂

Best regards,

Paul

[tmisner]

Glad I was able to assist. Good luck with your upgrade.

Have a good day,

Tyler Misner

Integrity Technical Support Engineer

[MichaelChatel]

In this particular upgrade path scenario (10.2 -> 10.8), the interim 10.7 install won't be needed, as the IIMAP relationship migration can still be done on 10.8.  For any Integrity version past that though (ex.  10.9 and higher, it's not available, so a 10.7 or 10.8 interim install would be needed in such an upgrade scenario.)

But in your case, you can go straight from 10.2 -> 10.8.

Tyler provided you good documentation links, and it's strongly recommended to go through the Upgrading guide one, before any attempt at upgrading, as it explains some of these upgrade path caveats, and some of the changes in functionality that come with 10.8.

[MichaelChatel]

Also, since Integrity 10.8 is what you're planning on upgrading to, you'll want to make sure you install Integrity 10.8 hotfix  HF-S140000001-026

(it replaces or supercedes the older mandatory hotfix HF-S140000001-022).  It's an important hotfix to avoid multi-edit issues on that version, if used.

[padams]

We tried to upgrade to 10.8 directly and had a huge amount of SQL errors in the log (unfortunately I do not have this log any more). Then we tried updating to 10.7 first and then 10.8 and then we ended up with only these few errors:

Integrity Upgrade 10.2 to 10.7

Running Offline Migration
./isutil –c migraterelationships 20

2017-04-26 09:11:08.109 SQL(5-main): SID15: SQLException: ORA-00904: "MCTAG": invalid identifier
: error code=904, state=42000
2017-04-26 09:11:08.109 SQL(5-main): SID15: ALTER TABLE Policies DROP COLUMN MCTag: 1811Ms
2017-04-26 09:11:08.111 SQL(5-main): SID15: SQLException: ORA-00904: "INTDEFAULT": invalid identifier
: error code=904, state=42000
2017-04-26 09:11:08.111 SQL(5-main): SID15: ALTER TABLE Policies DROP COLUMN IntDefault: 1659Ms
2017-04-26 09:11:08.113 SQL(5-main): SID15: SQLException: ORA-00904: "INTMIN": invalid identifier
: error code=904, state=42000
2017-04-26 09:11:08.113 SQL(5-main): SID15: ALTER TABLE Policies DROP COLUMN IntMin: 1396Ms
2017-04-26 09:11:08.114 SQL(5-main): SID15: SQLException: ORA-00904: "INTMAX": invalid identifier
: error code=904, state=42000
2017-04-26 09:11:08.114 SQL(5-main): SID15: ALTER TABLE Policies DROP COLUMN IntMax: 1226Ms
2017-04-26 09:11:08.116 SQL(5-main): SID15: SQLException: ORA-00904: "STRVALUEBOOT": invalid identifier
: error code=904, state=42000

Of course before we proceed on our production system, we would like to know why we are getting these errors and whether they are showstoppers. We are also wondering if it is because we have skipped some other update that is actually needed.

Thanks in advance for any input.

[tmisner]

Hello again Paul,

I am not familiar with this error when preforming this operation.

It is hard to say what could be causing this issue without further analysis. I would recommend opening a support case. One of the TSEs from the Integrity team will be happy to assist you further.

Thank you,

Tyler Misner

Integrity Technical Support Engineer