Arbortext/Windchill Odd numbering behavior

[Aaronm87]

Version: Windchill 12.1

Use Case: Trying to get arbortext to work with Windchill

Description:

I'm having an unusual issue. We are starting to use arbortext with our Windchill system (version 8.3 and 12.1.10) and there some odd behaviors.

Initially, when I open the application and try to check an object into the server I get this error:

The autonumbering feature should be enabled for "WCTYPE|wt.epm.EPMDocument|com.acme.us.DynamicDocument" soft type

  It does that for any PRODUCT context or Library. However, if I connect to a PROJECT workspace and checkin the object it works. The weird thing is, it started at 000000032 and increments by -1 every time I create a new object and then it allows me to check in objects into product or library workspaces.

Hours later, I attempted again and this time it started at 000000042 and started going down.

Here is my OIR for the "Dynamic Document" type

 <AttributeValues objType="wt.epm.EPMDocument">

               <!-- set the folder -->
               <AttrValue id="folder.id" algorithm="com.ptc.core.foundation.folder.server.impl.FolderPathAttributeAlgorithm">
                  <Arg>/Default</Arg>
               </AttrValue>

               <!-- set the lifecycle -->
               <AttrValue id="lifeCycle.id" algorithm="com.ptc.core.foundation.lifecycle.server.impl.LifeCycleTemplateAttributeAlgorithm">
                  <Arg>
                     <!-- Translation of the word "Basic" must be the same as the translation done in commonLifeCycles.xml -->
                     <?loc-begin key="BASIC_LIFECYCLE_NAME" maxlen="30" match="commonLifeCycles.xml:BASIC_LIFECYCLE_NAME"?>acme Lifecycle<?loc-end?>
                  </Arg>
               </AttrValue>

               <!-- set the team template -->
               <AttrValue id="teamTemplate.id" algorithm="com.ptc.core.foundation.team.server.impl.TeamTemplateAttributeAlgorithm">
                  <Arg>Default</Arg>
               </AttrValue>

               <!-- set the number to a generated number -->
               <AttrValue id="number" algorithm="com.ptc.windchill.enterprise.revisionControlled.server.impl.NumberGenerator">
                  <Arg>{GEN:wt.enterprise.SequenceGenerator:EPM_seq:10:0}</Arg>
               </AttrValue>

               <!-- set the version info to a generated version info -->
               <AttrValue id="MBA|versionInfo" algorithm="com.ptc.core.foundation.vc.server.impl.VersionInfoGenerator">
                  <Arg>wt.series.HarvardSeries</Arg>
               </AttrValue>
               
               <!-- specify AttrConstraint tag -->
               <AttrConstraint id="lifeCycle.id" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">  	         
	       	   <Value algorithm="com.ptc.core.rule.server.impl.GetServerAssignedConstraint"/>
	       	   <Value algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint"/>
	       </AttrConstraint>
	       <AttrConstraint id="lifeCycle" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">
	       	   <Value algorithm="com.ptc.core.rule.server.impl.GetServerAssignedConstraint"/>      
	       	   <Value algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint"/>
	       </AttrConstraint>
	       <AttrConstraint id="folder.id" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">
	       	    <Value algorithm="com.ptc.core.rule.server.impl.GetServerPreGeneratedValue"/>	      
	       </AttrConstraint>
	       <AttrConstraint id="number" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">
	       	    <Value algorithm="com.ptc.core.rule.server.impl.GetServerAssignedConstraint"/>
	       	    <Value algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint"/>
	       </AttrConstraint>
	       <AttrConstraint id="teamTemplate.id" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">  	         
	       	    <Value algorithm="com.ptc.core.rule.server.impl.GetServerAssignedConstraint"/>                         
	       	    <Value algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint"/>
	       </AttrConstraint>
	       <AttrConstraint id="teamTemplate" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">
	       	    <Value algorithm="com.ptc.core.rule.server.impl.GetServerAssignedConstraint"/>      
	       	    <Value algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint"/>
	       </AttrConstraint>  
	       <AttrConstraint id="organization.id" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">
	       	    <Value algorithm="com.ptc.core.rule.server.impl.GetServerPreGeneratedValue"> 
	       	      <Value algorithm="com.ptc.windchill.enterprise.org.server.impl.OwningOrgDefaultAlgorithm"/> 
	       	    </Value> 
	       </AttrConstraint>
            </AttributeValues>

               

[BenLoosli]

I can maybe explain part of what you are seeing.

When pulling a sequence number from Oracle, it will always increment by 10 when you have a time delay between getting a new number from the database. This can be set by going into Oracle with SQLDeveloper and change a value from 1 to 0 for the sequencing. You can find this information in a web search for Oracle sequencing. There may also be some PTC articles on the issue.

As for the negative increment, I have not seen that but that may also be something set in the sequence generation values in Oracle.

[Aaronm87]

We are using SQL. Would that make a difference?

[vnamboodheri]

Hello @Aaronm87, 

It looks like you have some responses from some community experts. If it helped you solve your question please mark the appropriate reply as the Accepted Solution. 
Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

Thanks,
Vivek N.
Community Moderation Team.

[MikeLockwood]

This CS article seems to apply.

https://www.ptc.com/en/support/article/CS38963?source=search&as=0