Windchill upgrades - publisher queue entries, are they brought forward during upgrade, or lost?

[danhumme]

I (was) using Windchill PDMLink Release 10.2 and Datecode with CPS M030-CPS28

General question, and yes we know that version 10.2 is no longer supported. We just recently upgraded. My question is, for any of the upgrade steps from 10.2 to 11.x, then to 12.x, then to 13.x, is it required that the CAD publisher queues be emptied first? Or if we have jobs in those queues that we are holding on to for purposes of trying to fix them, will the contents of the publisher queues be brought forward into the new version so that they are not lost? Thank you.

[SWeiler_9940261]

I have never seen an instance of items in the publisher queue causing any problems with an upgrade. 

[avillanueva]

Agree with @SWeiler_9940261. I would not have them executing when you shutdown the server or in ready state. What could happens is that during the upgrade, it will try and start republishing them and likely fail if things are not ready to go. Better to disable the queue so you can start it back up post upgrade. The entries should not matter.

[HelesicPetr · Accepted solution]

Hi @danhumme 

general information.

The queue entries are stored in the database, and during the upgrade you move the database to new version and the entries are not lost.

So you do not have to clean up the queue entries.

Just keep in mind that the queues should be stopped and disabled during the upgrade phase.

PetrH

[danhumme]

Hi @HelesicPetr , 

The info you provided is very helpful. Thank you. One more part to this puzzle, though... When our third-party was doing our "rehearsal1" and "rehearsal2" upgrades, he did not clear the publisher queues on the product server, and in fact I had checked the new server and found that the queue entries were there on the new server, which made me very happy and alleviated my concerns. But when it came time for the production upgrade, about a half hour before the scheduled start all of a sudden the publishing jobs that I was trying to republish to get them completed (some fail sometimes on us), started disappearing. (I also had about 500 entries from the past months that needed to be re-published after the upgrade and after we had a chance to fix our CAD workers.) Turned out that the third-party was deleting all queue entries on me, saying that the upgrades required the queues to be empty, and saying that he had also deleted the entries from the production server during the two rehearsals, which he did not. Anyway, if those entries are stored in the database, is it possible that they entries still exist in the database, just with a "deleted flag" and they could be recovered, made available in the queues again? The job numbering continued on as it was so the numbers would still be unique. Here's hoping! 

[HelesicPetr]

Hi @danhumme 

If the queues are empty during the upgrade phase it involves just a performance of the upgrade.

That could be the reason why they say that queues should be empty but it is not necessary for the upgrade.

If the queue entry is deleted, it is also deleted from the database. 

You can recover the entries just from a database backup.

PetrH

[avillanueva]

If you can identify roughly the items that failed to publish, you could also trigger them to be republished. It depends upon your publishing configuration but those that were deleted should be missing representations. You can use the WVS Job Scheduler Admin to batch publishing things with missing representations. It could also be that some of these succeeded and the job was cleared. Either way, you can use this to see what is lacking a representation (by running but pausing the queue) and you can even prune it before resuming queue.  These jobs might generate more jobs that you wanted but you can control what gets published and when.

[anursingh]

Hi @danhumme,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation. 

Thanks,
Anurag