• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 7 replies
  • Subscribers 95 subscribers
  • Views 3922 views
  • Users 0 members are here
Options
Related

"Rebuild table index" stays in DBQueue

Denis.Mekinda
over 3 years ago

TempDB was full and we restarted SQL.

After that I see in DB Queue all the time "Rebuild table index"   and end maintenance pops up every 5 minutes.

Ind DialogDBQueue I see that person , Basetree and Basetreecollection need to run this.

How can I clear this or process it?

  • +1 over 3 years ago

    Is it getting reset? You can check this in the job queue info tool in the bottom right hand corner. You can also check the dialog journal again in the job queue info tool but on the bottom left hand side, you should see something like reindex job reset due to something.  Usually when I see this DBQeueue task and it is getting reset it means that we are stuck on a certain table when trying to reindex it, it could be that another process has a lock on that same table possibly. 

  • 0 over 3 years ago in reply to Troy Grandy

    Yes it is getting reset. ... and Looks like You might be right! I tried manualy to rebuid index on Person with 

    ALTER INDEX ALL ON person REBUILD
       and it takes really long time! ... but I do not have any frozen jobs!... is this for support?

  • +1 over 3 years ago in reply to Troy Grandy

    It looks that job service somehow prevented from running this. Stoping job service and starting it after few minutes solved the issue!

  • 0 over 3 years ago

    Every know and then, I will see in the morning that rebuild table index task is being reseted in DBQueue.

    Same ITShop request related tables every time like PersonWantsOrg, PWODecisionHistory, ShoppingCartOrder, etc

    I tried many times looking at System Journal to find out why this task is reseted but cound not find a thing ever. Seems like for this task there are is no info.

    Tried also stopping the OneID service few minutes to see if the reindexing will get the priority and do its stuff but to no avail.

    Most of the times, I solve this case by accident, meaning restarting the SQL slots again and again, killing some SQL Head Blockers and at some point it may fix by itself but that is no robust solution.

    Manually re-indexing the needed tables is not an easy option, too, as it takes too much time for that when early in the morning production is starting to being used by people.

    Any more ideas on this case?

  • 0 over 3 years ago in reply to Panos Georgakopoulos

    There should be an journal entry that coincides with the reset. Take note of what else is running in the DBQueue at the time that this occurs that might be a clue as well.

  • 0 over 3 years ago in reply to Troy Grandy

    Unfortunately, there seems to be no entry in system journal. I tried looking at it several times also in the past to no avail.

    If you ever find the entry name, please share.

    Fortunately, re-indexing cleared itself this time. Thank you for reaching out.

  • 0 over 3 years ago in reply to Troy Grandy

    Hi .... we are running version 8.1.2 and when the rebuild index task resets we do not see anything reported in the system journal.  But examining the sql processes shows us that the SQLAgent job is blocked by other processes running queries that access the table(s) being re-indexed.  Should the journal show the reason for the reset?  Or is this something that is fixed in a later version? (8.1.3+)