v9 DBQueue on hold "waiting for compiler" despite full compiling

when doing the compile, did it stop with errors, telling you to correct specific scripts or templates, custom processes, etc?

Hi Troy,

even the first compile directly after transport was successful without problems.

Do you have a DBAgent running? I am asking because version 9+ needs to have the Database Agent running separately. Either as plugin in the main JobService or as the standalone executable. 

Yes, the DBAgent was running (has just been restarted. The only Warning in Log says "No Idle condition defined".

We tried changing a script to initiate a full compile. But after committing the script (just added an empty variable) to database, the yellow warning icon in the status bar (saying that the assemblies are invalid) does NOT appear. The compiler then just suggestes a basic compilation without script. Selecting Scripts with all dependenciens does NOT remove the waiting for compile entry in DBQueue and it's still on hold.

Can you please check if you have invalid entries in DialogScriptAssembly?

select count(*),* from DialogScriptAssembly where IsValid = '0'

Never seen this before. We upgraded that instance from 8.1.4 (if I remember correctly) to 9.1. a while ago. There were no transports since, but Jobs were processed.

use iam
select count(*),* from DialogScriptAssembly where IsValid = '0'

Error

Msg 8120, Level 16, State 1, Line 2
Column 'DialogScriptAssembly.UID_DialogScriptAssembly' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause.

Sorry my mistake. Bad copy and paste error. 

The correct SQL to check if you have any invalid entry in DialogScriptAssembly would be this.

select Name, XUserUpdated, XDateUpdated from DialogScriptAssembly where IsValid = 0

Sorry my mistake. Bad copy and paste error. 

The correct SQL to check if you have any invalid entry in DialogScriptAssembly would be this.

select Name, XUserUpdated, XDateUpdated from DialogScriptAssembly where IsValid = 0

Thanks, I was slightly concerned of having a major FU in the DB

use iam
select Name, XUserUpdated, XDateUpdated from DialogScriptAssembly where IsValid = 0

No results

Okay. Last thing that comes into my mind.

What are the settings in DialogDatabase in regards to potential stops?

Select IsDBSchedulerDisabled, IsJobServiceDisabled, SingleUserProcess, SingleUserStart, UpdatePhase From DialogDatabase

IsDBSchedulerDisabled IsJobServiceDisabled SingleUserProcess SingleUserStart UpdatePhase
0                                     0                                 0                               NULL                0

Mhh...out of ideas it seems....

Did you already tried to delete the entry from the DBQueue?

Which one? We have (none of them is reset):

Mark the entry of a Job server in job queue...
Increase semaphore
Reset script assemblies
Waiting for compiler
Compile system
and a lot more (Start schedules, Run deferred operations, Inheritance in roles)

Could you also give me a hint how to delete from DBQueue? Table DialogDBQueue only has tasks QBM-K-DeferredOperationExecute and QBM-K-ScheduleStart

Mmhh.... looks like your DB Queue is not processing at all. DId you check the entries in DialogJournal for errors? (You can do so in JobQueueInfo).

As this seems to be not an easy thing to solve, you might want to contact support as well.

System Journal only has some old warning of resetted Jobs (continue with error/success) and failed Logins.

The number of entries in DialogDBQueue varies within minutes, but it's only showing QBM-K-DeferredOperationExecute and QBM-K-ScheduleStart.
The table QBMDBQeueOverview show quite some entries (I guess it's the one being displayed in JobQueueInfo.
Tables QBMDBQueue_Pond and QBMDBQueueCurrent are empty.

Is there a way to give the DBQueue a little kick?

As I've said I suggest you contact support to help you out. 

Last resort Reboot (of DB- and JobServer; we got JobSVC running on both as it is our QA-Env) seemed to do the trick.

Once more: If nothing else helps and you're completely out of ideas -> Reboot.

Thanks for your effort and quick replies! 

Thanks for reporting back. It's weird that a reboot is fixing the behavior.