Skip to main content
B
BrianToussaint19-Tanzanite
19-Tanzanite
December 19, 2014
Solved

Revise after upgrade to 10.2

  • December 19, 2014
  • 7 replies
  • 2217 views

So I recently upgraded my test server from 10.1 m040 to 10.2 m020. I started testing stuff and came across something that is not a big deal from the big picture but a little disturbing that it would even happen, unless I've missed something that I need to do.

In 10.1 when I revised an object it would go from revision 2.2 to revision 3.0. In 10.2 when I just tried it, the revision went from 2.2 to 3.1. Is this normal with 10.2? What happened to iteration 0? Is there a preference for this?

Best answer by MikeLockwood

It's due to your first iteration, not the Revision Series.

This property has the value 1 OTB; need to change to 0.

wt.series.IntegerSeries.min

7 replies

T
TomU23-Emerald IV
23-Emerald IV
December 19, 2014

I think the series is referenced in your OIR. Let me see if I can find it...

T
TomU23-Emerald IV
23-Emerald IV
December 19, 2014

Yeah, whatever custom versioning scheme you were using on 9.1 needs to be loaded into 10.2.

A sample is shown in the knowlege base here:

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS23066

Another discussion here:

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS53009

Fully documented in the Specialized Administration Guide

20.PNG

T
TomU23-Emerald IV
23-Emerald IV
December 19, 2014

Brian, run this command from a Windchill shell to extract your current series: (change path as necessary)

java wt.series.LoadFileBasedSeries E:\PTC\Windchill_10.2\series.xml -read

Then on your 10.2 system, run this command to load it back in:

java wt.series.LoadFileBasedSeries E:\PTC\Windchill_10.2\series.xml -load

M
MikeLockwood22-Sapphire IAnswer
22-Sapphire I
December 19, 2014

It's due to your first iteration, not the Revision Series.

This property has the value 1 OTB; need to change to 0.

wt.series.IntegerSeries.min

T
TomU23-Emerald IV
23-Emerald IV
December 19, 2014

Thanks Mike! I wish there was a property migrator...

M
MikeLockwood22-Sapphire I
22-Sapphire I
December 19, 2014

There isn't a "property migrator" but one can fairly easily take all the properties in site.conf created / modified after install and dump them into site.conf on the target and then just xconfmanager -p. This needs to be a key part of the upgrade process, not explicitly addressed as a "how-to" in the guides.

Note: If you do in fact have a custom Revision (version) series, then all the above applies. Need to be super careful to not overwrite what you intend to upload. The -read execution has to be to a different filename.

    Terms & ConditionsAccessibility statement