Log shipping jobs losing flags

  • zoggling

    SSCommitted

    Points: 1996

    We have set up log shipping between two instances, and configured the log shipping job steps with @flags=12 (Log to table, Include step output in history). However, we have noticed that after a short period of time, the flags are reset to zero, and have to be manually configured again.

    We have made other amendments to the log shipping jobs (such as adding additional monitoring steps), but these do not appear to be affected.

    Is this a known issue? We've not seen it occur on other instances on the same build.

    Both instances are running:

    Microsoft SQL Server 2016 (SP2-CU4) (KB4464106) - 13.0.5233.0 (X64)

    Nov 3 2018 00:01:54

    Copyright (c) Microsoft Corporation

    Web Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)

    Attachments:
    You must be logged in to view attached files.
  • Site Owners

    SSC Guru

    Points: 80380

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • This was removed by the editor as SPAM

  • Brahmanand Shukla

    SSC-Addicted

    Points: 407

    Replication task and Integration Services package job step logging is handled by their respective subsystem. You cannot use SQL Server Agent to configure jog step logging for these types of job steps.

    https://docs.microsoft.com/en-us/sql/ssms/agent/manage-job-steps?view=sql-server-2017

  • Sue_H

    SSC Guru

    Points: 90260

    Replication task and Integration Services package job step logging is handled by their respective subsystem. You cannot use SQL Server Agent to configure jog step logging for these types of job steps.

    https://docs.microsoft.com/en-us/sql/ssms/agent/manage-job-steps?view=sql-server-2017%5B/quote%5D

     

    But the question is about log shipping jobs, not replication or integration services packages.

    Zoggling - When these "disappear", have you checked sysjobs to see if the date_modified for the job has changed? Or the creation date if the job is being recreated. Changing the step should change the date_modified. Another thought is try scripting out the job to see if the changes are there or check in sysjobsteps for the flags to make sure it's not a display issue with SSMS.

    Sue

  • zoggling

    SSCommitted

    Points: 1996

    Sue_H - the flags were definitely missing, we scripted the jobs out to check, and also stopped receiving job history information monitoring-side since the job steps were no longer logging step output in history.

    Interestingly, we upgraded to SP2 CU8 after creating this post, and the flags have not yet disappeared. Hoping this may have resolved the issue somehow.

  • Sue_H

    SSC Guru

    Points: 90260

    I hope that's it - thanks a lot for posting back! Please post back if it rears it's ugly head again. It would be good to know if this was some odd bug you hit, which it looks like it may be.

    Sue

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply