Support Center

Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Log tables not showing anything against last few runs

Faisal Oct 19, 2016 07:31AM CDT

Minion Reindex job is scheduled to run on weekly basis and is running fine but the log is showing nothing against last a few runs. Does this mean that it's doing nothing? Does anybody know what might be the reason?

Up 0 rated Down
Sean McCown Oct 19, 2016 08:09AM CDT MinionWare Agent

So has logged its work in the past? It’s just stopped logging in the last few runs?
If that’s the case, then I’d say that it appears as though nothing needs to be done so there’s nothing to log.
However, if you’d like to test it then run it with @StmtOnly = 1 and see if any statements show up in the Messages tab of SSMS.
If not then it looks like you’re good to go. If something does show up, the run it again with @StmtOnly = 0 and see if the expected rows show up in the log.

Up 0 rated Down
Faisal Oct 19, 2016 09:31AM CDT
Really appreciate your prompt response.

Yes Sean, logging was fine till September. Log is not available for the last three runs only since Oct, 1st.

Furthermore, I ran it with @StmtOnly=1 and it returned some databases in the result set and statements in the messages tab. After that, i executed it with @StmtOnly=0 in SSMS rather than the job, keeping rest of the parameters same as given in the job and the log is getting modified properly now.

Let me explain my scenario further, that would help you understand the issue easily:

I have two jobs running on my server, first job is scheduled to run daily except Saturday with the following parameters:

[Minion].[IndexMaintMaster] @IndexOption = 'All', @ReorgMode = 'REORG', @RunPrepped = 0, @PrepOnly = 0, @StmtOnly = 0, @Include = NULL, @Exclude = NULL, @LogProgress = 1

Second job is running on Saturday only with the following parameters:

[Minion].[IndexMaintMaster] @IndexOption = 'All', @ReorgMode = 'All', @RunPrepped = 0, @PrepOnly = 0, @StmtOnly = 0, @Include = NULL, @Exclude = NULL, @LogProgress = 1

Any idea why the log was not modified by both jobs since 1st October? That would really help me to fix the issue permanently. Please let me know if you need further details. Thanks again.
Up 0 rated Down
Sean McCown Oct 19, 2016 09:55AM CDT MinionWare Agent

Well, we know the routine works because you were able to process and log tables manually. If it still isn’t logging properly when it runs automatically then my best guess would be permissions? Maybe the agent acct has had a permissions change, or maybe the job owner was switched to someone who doesn’t have perms. I’d say make sure the job is owned by sa or by you and see how that goes. Currently the routine doesn’t log when it can’t log a row, because where would it log it?

When you ran it manually about how many tables were processed? Was it a lot or just a small handful. If it were just a handful it’s possible it hasn’t needed to do anything. If it were a lot then it’s possible you’re having the issue above. Let me know what happens and if it continues I’ll try to come up with a way to help you ferret this out.

Up 0 rated Down
Sean McCown Oct 31, 2016 10:23PM CDT MinionWare Agent

I haven’t heard back from you on this.

Up 0 rated Down
Sean McCown May 08, 2017 08:38AM CDT MinionWare Agent

Closed due to inactivity.

Post Your Public Answer

Your name (required)
Your email address (required)
Answer (required)
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found