Skip to main content
A
AT_1223370810-Marble
10-Marble
September 23, 2025
Solved

Data Model Error While UpgradeManager

  • September 23, 2025
  • 1 reply
  • 521 views
I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.2.13

While upgrading from version 9.1 to 10.2 (first phase of a 9.1 to 12.1 upgrade project) we get inheritance exceptions.
We have Modelled class DesignChangeTask which is subtype of WTChangeActivity2, but Windchill is trying to treat DesignChangeTask as a Changeable2 during the Execute Server Migrators / Update the Pending Change Indicator and we are getting below error
Caused by: wt.util.WTException: (wt.query.queryResource/38) wt.query.QueryException: Class Attribute class "interface wt.change2.Changeable2" is not a super class of or equal to any of the table classes "class ext.ec.epp.change.DesignChangeTask"

Here are the errors that I faced
Nested exception is: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.ptc.windchill.upgrade.updates.directives.MigratorMethod.invoke(MigratorMethod.java:131)
at com.ptc.windchill.upgrade.updates.directives.LightWeightServiceDirective$Server.invokeLightWeightServiceApi(LightWeightServiceDirective.java:635)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at wt.method.MethodResultWriter.writeExternal(MethodResultWriter.java:152)
at wt.method.MethodResult.writeExternal(MethodResult.java:226)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1455)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1429)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347)
at sun.rmi.server.UnicastRef.marshalValue(UnicastRef.java:293)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:332)
at sun.rmi.transport.Transport$1.run(Transport.java:177)
at sun.rmi.transport.Transport$1.run(Transport.java:174)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:556)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: wt.util.WTException: (wt.query.queryResource/38) wt.query.QueryException: Class Attribute class "interface wt.change2.Changeable2" is not a super class of or equal to any of the table classes "class ext.ec.epp.change.DesignChangeTask"
Nested exception is: (wt.query.queryResource/38) wt.query.QueryException: Class Attribute class "interface wt.change2.Changeable2" is not a super class of or equal to any of the table classes "class ext.ec.epp.change.DesignChangeTask"
at wt.change2.ChangeStatusCalculator.updatePendingChangeIndicator(ChangeStatusCalculator.java:334)
at wt.change2.ChangeStatusCalculator.updatePendingChangeIndicator(ChangeStatusCalculator.java:295)
at wt.change2.ChangeStatusCalculator.updatePendingChangeIndicator(ChangeStatusCalculator.java:277)
at wt.change2.MigrateChangeStatusIndicators.runMigration(MigrateChangeStatusIndicators.java:38)
... 28 more
Caused by: (wt.query.queryResource/38) wt.query.QueryException: Class Attribute class "interface wt.change2.Changeable2" is not a super class of or equal to any of the table classes "class ext.ec.epp.change.DesignChangeTask"
at wt.query.ClassAttribute.validate(ClassAttribute.java:700)
at wt.query.SearchCondition.validate(SearchCondition.java:828)
at wt.query.ConditionsClause.append(ConditionsClause.java:365)
at wt.query.ConditionsClause.append(ConditionsClause.java:234)
at wt.query.QuerySpec.appendWhere(QuerySpec.java:1126)
at wt.change2.listeners.ResultingChangeEventHandler.appendResultingChangeCondition(ResultingChangeEventHandler.java:275)
at wt.change2.listeners.DefaultResultingChangeEventHandler.getChangeablesToSetIndicator(DefaultResultingChangeEventHandler.java:334)
at wt.change2.ChangeStatusCalculator.executeUpdatePendingChange(ChangeStatusCalculator.java:463)
at wt.change2.ChangeStatusCalculator.executeUpdatePendingChange(ChangeStatusCalculator.java:403)
at wt.change2.ChangeStatusCalculator.executeUpdatePendingChange(ChangeStatusCalculator.java:368)
at wt.change2.ChangeStatusCalculator.executeUpdatePendingChange(ChangeStatusCalculator.java:364)
at wt.change2.ChangeStatusCalculator.updatePendingChangeIndicator(ChangeStatusCalculator.java:317)
... 31 more
    Best answer by AT_12233708

    Hi, @avillanueva and @jbraga 
    The problem was caused by (evidently, no real proof) a rollback of the "Updates the associations of change objects and objects that can be changed" that didn't invert the column links as described in the article https://www.ptc.com/en/support/article/CS261042 .
    Veeeery weird, but the proof is that a re-execution with same db, same application installation, same customization build worked.

    Why first one didn't work? Do not know sincerely but first time we had a lot of interruptions caused by connections, generic bad performance issues over the net and the systems etc.
    A more fluid and continuous  re-execution of UpgradeManager with same set-up worked! This means that completion controls after UpgradeManager tasks are not bullet-proof and sometimes some weird roll-back may happen.

    Thank you for your help in any case, you have been both precius!

    1 reply

    avillanueva
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    September 23, 2025

    Strange since that interface is used for things that are on change tasks like affected and resulting items, not the task itself.  I suggest openning ticket with PTC. You do not have an errant inclusion of this interface in your modelled class do you?

    A
    AT_1223370810-MarbleAuthor
    10-Marble
    September 25, 2025

    Hello and Thank you for your support:
    we are investigating furter:
    The problem happens during the Upgrade the Pending Change indicator of the Servers Migrator from 9.1 to 10.2

    The issue seems caused by the unsuccesful execution of  the task    "Updates the associations of change objects and objects that can be changed" 
    (that seems apparently completed sucecsfully).
    As described in the article     https://www.ptc.com/en/support/article/CS261042 the role  links seem not being inverted and the Upgrade the Pending Change indicator of the Servers Migrator picks up objects from the wrong list (and those objects don't have the required interface).

    jbraga
    jbraga21-Topaz I
    21-Topaz I
    September 25, 2025

    @AT_12233708 ,

     

    I agree with @avillanueva assessment above. Are you able to share the source code for your modelled class or at least the class declaration with annotations?

      Terms & ConditionsCookie settingsAccessibility statement