Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
Hi there,
I have a problem with a job in "commonScheduleQueue".
This Job runs for at least half an hour and fills up the transaction log on my database completely (meanwhile 30GB).
The job's details:
How Do I identify, what the corresponding issue is?
I mean, if "13000302" corresponds to a (e.g.) promotion request, that is already closed, I could simply delete this Job. But currently I just do not know.
Chears /me
Solved! Go to Solution.
Hi @Mat
go to a database and perform a select
select * from WindchillDB.ScheduleItem where ida2a2='13000302' (this is for MSSQL)
You can find interesting information in a itemDescription, itemName or different column which can help to identify the schedule operation.
here is just example of one row with headers
administrativeLockIsNull | typeadministrativeLock | cancelled | classnamekeydomainRef | idA3domainRef | immediateMode | inheritedDomain | itemDescription | itemName | measurementUnit | nextTime | periodicity | principalRefIsNull | classnamekeyA5 | idA3A5 | classnamekeyB5 | idA3B5 | queueName | runCount | securityLabels | startDate | targetClass | targetMethod | createStampA2 | markForDeleteA2 | modifyStampA2 | classnameA2A2 | idA2A2 | updateCountA2 | updateStampA2 | toBeRun |
NULL | NULL | 0 | wt.admin.AdministrativeDomain | 9 | 0 | 0 | Clean up of unreferenced filevault items | purgeUnreferencedFvItems | 0 | 26:58.0 | 86400 | 0 | wt.org.WTUser | 12 | wt.queue.ScheduleQueueEntry | 14226613 | commonScheduleQueue | 2 | NULL | 27:07.0 | wt.fv.StandardFvService | purgeUnreferencedFvItems | 27:15.0 | 0 | 16:31.0 | wt.scheduler.ScheduleItem | 14226612 | 6 | 16:31.0 | -1 |
Some information could be helpful.
PetrH
oh, I forgot to mention.
After the job is "done" (or just crashes, who knows), it is rescheduled for the next day.
Hi @Mat
go to a database and perform a select
select * from WindchillDB.ScheduleItem where ida2a2='13000302' (this is for MSSQL)
You can find interesting information in a itemDescription, itemName or different column which can help to identify the schedule operation.
here is just example of one row with headers
administrativeLockIsNull | typeadministrativeLock | cancelled | classnamekeydomainRef | idA3domainRef | immediateMode | inheritedDomain | itemDescription | itemName | measurementUnit | nextTime | periodicity | principalRefIsNull | classnamekeyA5 | idA3A5 | classnamekeyB5 | idA3B5 | queueName | runCount | securityLabels | startDate | targetClass | targetMethod | createStampA2 | markForDeleteA2 | modifyStampA2 | classnameA2A2 | idA2A2 | updateCountA2 | updateStampA2 | toBeRun |
NULL | NULL | 0 | wt.admin.AdministrativeDomain | 9 | 0 | 0 | Clean up of unreferenced filevault items | purgeUnreferencedFvItems | 0 | 26:58.0 | 86400 | 0 | wt.org.WTUser | 12 | wt.queue.ScheduleQueueEntry | 14226613 | commonScheduleQueue | 2 | NULL | 27:07.0 | wt.fv.StandardFvService | purgeUnreferencedFvItems | 27:15.0 | 0 | 16:31.0 | wt.scheduler.ScheduleItem | 14226612 | 6 | 16:31.0 | -1 |
Some information could be helpful.
PetrH
Thanks @HelesicPetr
I get this result.
administrativeLockIsNull | typeadministrativeLock | cancelled | classnamekeydomainRef | idA3domainRef | immediateMode | inheritedDomain | itemDescription | itemName | measurementUnit | nextTime | periodicity | principalRefIsNull | classnamekeyA5 | idA3A5 | classnamekeyB5 | idA3B5 | queueName | runCount | securityLabels | startDate | targetClass | targetMethod | createStampA2 | markForDeleteA2 | modifyStampA2 | classnameA2A2 | idA2A2 | updateCountA2 | updateStampA2 | toBeRun |
NULL | NULL | 0 | wt.admin.AdministrativeDomain | 8 | 1 | 0 | NULL | LogTableCleanerScheduledTask | 3 | 2022-08-29 22:00:00.0000000 | 1 | 0 | wt.org.WTUser | 11 | wt.queue.ScheduleQueueEntry | 13000303 | commonScheduleQueue | 24 | NULL | 2022-08-03 22:00:00.0000000 | wt.method.jmx.LogTableCleaner | purgeOldEntries | 2022-08-02 11:13:13.0000000 | 0 | 2022-08-29 08:00:45.0000000 | wt.scheduler.ScheduleItem | 13000302 | 50 | 2022-08-29 08:00:45.0000000 | -1 |
I found this Case https://www.ptc.com/en/support/article/CS178198
I will give it a try.