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

Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X

idA2A2 generation logic

Srikanth1
12-Amethyst

idA2A2 generation logic

I am using Windchill PDMLink Release 12.0 and Datecode with CPS 12.0.2.3

How is idA2A2 generated in the object DB tables like WTDocMaster, WTDoc?
Is the value generated in sequence regardless of the table/object type?
I verified the DB sequence, ID_Sequence but this does not seem to be generating the number in sync with the object creation.
Please advise.

1 ACCEPTED SOLUTION

Accepted Solutions
bhushandd
17-Peridot
(To:Cassie)

Hi @Srikanth1,

This is Bhushan from PTC Technical Support.

 

The IDA2A2 field uses a sequence that generated a new sequence number every time.

However, the same sequence is used by all tables having the IDA2A2 field.

 

Hence you can see inconsistencies in the IDA2A2 field of the WTDocument and the IDA2A2 is supposed to be used internally.

For customer use, we have a Number field that can be the next sequence number for a specific object type.

 

Also, when the database application is restarted, all cached sequence numbers get skipped hence PTC does not guarantee order and continuous sequence.

Only the uniqueness of the sequence number is guaranteed.

Check the article: CS113612 - Auto-numbering of objects not incrementing correctly in Windchill PDMLink 

 

For Oracle, the cached number is 20 whereas for SQL Server it is 1000.

There are ways to block the caching however it may result in a performance impact on the database level.

 

If my response helps, please mark it as the solution to help other members. Thanks for using the Community! 

View solution in original post

4 REPLIES 4
avillanueva
22-Sapphire I
(To:Srikanth1)

Cassie
14-Alexandrite
(To:Srikanth1)

  • PTC does not guarantee the order and continuous for sequence numbers, only uniqueness
  • Oracle caches for a sequence 20 numbers by default
  • It is recommended to keep cache sequencing for a best performance

  • Turning off sequence caching will not eliminate gaps or skipping of sequence
  • https://www.ptc.com/en/support/article/cs113612
bhushandd
17-Peridot
(To:Cassie)

Hi @Srikanth1,

This is Bhushan from PTC Technical Support.

 

The IDA2A2 field uses a sequence that generated a new sequence number every time.

However, the same sequence is used by all tables having the IDA2A2 field.

 

Hence you can see inconsistencies in the IDA2A2 field of the WTDocument and the IDA2A2 is supposed to be used internally.

For customer use, we have a Number field that can be the next sequence number for a specific object type.

 

Also, when the database application is restarted, all cached sequence numbers get skipped hence PTC does not guarantee order and continuous sequence.

Only the uniqueness of the sequence number is guaranteed.

Check the article: CS113612 - Auto-numbering of objects not incrementing correctly in Windchill PDMLink 

 

For Oracle, the cached number is 20 whereas for SQL Server it is 1000.

There are ways to block the caching however it may result in a performance impact on the database level.

 

If my response helps, please mark it as the solution to help other members. Thanks for using the Community! 

Hi @Srikanth1,


 

I wanted to follow up with you on your post 'idA2A2 generation logic' to see if your question has been answered.

 

If so, please designate the appropriate post as the Accepted Solution for the benefit of other members who may have the same question.
If not, please post your current status in the public thread so that we can continue to support.


 

Thanks,

Bhushan

Top Tags