cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading from 2009 SP2 to Integrity Lifecycle Manager 10.7 fails with NullPointerException During Database Schema Update.

SOLVED
Highlighted
Bedrock

Upgrading from 2009 SP2 to Integrity Lifecycle Manager 10.7 fails with NullPointerException During Database Schema Update.

We found this article which seems to match the problem we are facing: 

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS209167&lang=en_US

e run the SQL against our Integrity Lifecycle Manager Server's database:

SELECT ID, Name FROM Fields WHERE Content=null;

and we found 2 records with null content.

Suggested workaround is:

For each Field that is returned, set a Description on the Field in the Admin GUI.

Confirm that no fields remain affected by re-running the SQL statement above prior to upgrading to 10.7 in Production.

But that workaround is not feasible, as we can't longer use the ADMIN GUI. We have to solve in other way.

We need to know which fields we have to update and how , from the SQL database interface.

Thanks to Everyone!!

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Upgrading from 2009 SP2 to Integrity Lifecycle Manager 10.7 fails with NullPointerException During Database Schema Update.

Hi Martina,

It looks like you may have a Support case open for this already, so they will confirm for you too (if they haven't already), but you would need to roll back the migration and do the article workaround (updating the descriptions manually) first, then you can proceed with the migration again.  But a roll-back is required.

View solution in original post

1 REPLY 1
Highlighted

Re: Upgrading from 2009 SP2 to Integrity Lifecycle Manager 10.7 fails with NullPointerException During Database Schema Update.

Hi Martina,

It looks like you may have a Support case open for this already, so they will confirm for you too (if they haven't already), but you would need to roll back the migration and do the article workaround (updating the descriptions manually) first, then you can proceed with the migration again.  But a roll-back is required.

View solution in original post

Announcements