Loading

Data Update Job

Skip Feed
  1. DUJ ExecutionTime looks wrong

    I'm wondering if anybody else has noticed this... the overall ExecutionTime value shown in tblJobLog doesn't seem correct, and doesn't match the LastJobDuration value shown in tblSystemInfo. The value in tblSystemInfo seems to be correct, but the ExecutionTime looks wrong:

     

    Job_log_time 

    SystemInfo_time 

    I assume that everybody else sees the same difference? For us, it happens on both 9.21.1 and 9.22.1. It seems like tblSystemInfo is a better place to look if you're checking DUJ times in your database... And I suppose this also means that the ExecutionTime values in tblJobLogHistory are wrong as well?

     

    David

    Expand Post

    1 of 8
    • Why don't you use tbljoblogmetrics for comparison?

      This table do show the summary.

       

      I normally use this statement, that then also do show me the jobid from tbljobloghistory in case I need to check the details of a job.

       

      use SnowLicenseManager

      select h.jobid as HistoryJobID, m.*

      from tblJobLogMetrics m 

      left outer join (select jobid,actionstart from tblJobLogHistory where jobtype='job_run') h on m.StartTime=h.ActionStart

      -- where m.jobdate >= '2022-05-30'

      order by jobdate desc

       

      Expand Post

  2. DUJ Failed Without Errors

    Hi,

     

    SLM version : 9.14

     

    In customer premises, two days back the DUJ got stopped/failed. When we tried to find the error in logs, only empty space is there in the message. Had anyone come across this scenario? Or Do we need to only log a ticket with SNOW?

     

    Even we are ready to upgrade the SLM to 9.18. But will the upgrade resolve this issue?

     

    Thanks,

    Mohamed Riswan M

    Expand Post

    1 of 4
    • The KB article here may help in providing the relevant data to support.

       

      The table tblErrorLog typically holds any errors that occur but not always, e.g if your transaction log is full and the DUJ is stopped mid processing. Check the following if you haven't already done so...

       

      select * from SnowLicenseManager.dbo.tblErrorLog order by LogDate desc

       

      Review the Message column of the following query might give you an idea where the job stopped...

       

      select * from SnowLicenseManager.dbo.tblJobLog order by ActionStart asc

       

      ...but it looks like you may have checked this already and found them to be blank?

       

      If you wish to get your DUJ running again, you can reset the relevant tables using the following script (taken from this article)...

       

      --Step 1: Stop the job if necessary

      USE msdb

      GO

      EXEC dbo.sp_stop_job

      N'License Manager Data Update'

       

      --Step 2: Update Job Status

      USE SnowLicenseManager

      UPDATE tblJobStatus SET LastJobStatus = 'Job finished successfully'

       

      --Step 3: Update the log

      UPDATE tblJobLog SET Message = 'Job finished successfully' WHERE JobType = 'JOB_RUN'

       

      --Step 4: New Step for SLM 9 (DUJ 2.0): Zeroing out the temp tables

      UPDATE inv.tblJobParallelStep set [Status] = 0 where Status= -1

       

      --Step 5: Update System Info table (note this is needed to tell IIS to allow access to the SLM)

      UPDATE tblSystemInfo SET LastJobStatus = 'Job finished successfully'

      Expand Post

  3. DUJ Failed

    Hi,

     

    I have got the below error for DUJ failure.

     

    "Error #2627 in procedure JobInventoryComputerSoftwareProductUpdate line 101. [Violation of PRIMARY KEY constraint 'PK__#Compute__CE581D3D9A575B37'. Cannot insert duplicate key in object 'dbo.#ComputerSoftwareProduct'. The duplicate key value is (971865A54079671217C3A1D9A4EE2EE2).]"

     

    What could be the root cause here? I tried to see the procedure but it is not accessible.

     

    Thanks,

    Mohamed Riswan M

    Expand Post

    1 of 2
    • Hey,

       

      Just in case, update to 9.18 if you're not already on it. There's other things that can cause this, but it is a known issue resolved in 9.18 as well.

       

      Laim

      Expand Post

  4. How is everybody getting on with the "Complete Ruleset" DUJ?

    I posted about this last year ... I'm wondering how everybody else's complete ruleset DUJ is doing? For us, it now takes nearly 5 days to run 😲

     

    Complete Ruleset DUJ takes over 111 hours 

    So it's really impossible for us to run this every week. The best we can do it run it occasionally and even then it's very painful to have the DUJ running for a full week like this. Is anybody else having similar problems?

     

    I do have a support ticket open about the complete ruleset, but Snow Support are reluctant to investigate while we're still on SIS 6.6.3 (we don't want to upgrade to SIS 6.7 because it looks like it will make our DUJ even slower).

     

    I'm guessing other people are having similar issues with the complete ruleset?

    Expand Post

    1 of 15
    • So having had to perform a complete ruleset run (due to SRS hiccup last week), its currently 40 hours in, and sitting on the step JobInventorySoftwareApplyRules. Reviewing current SQL activity (just via Activity Monitor in SSMS) I can see the following being run....

       

      CompleteRulesetRun...query running for 36 hours with massive physical/logic reads. I'm assuming its applying all the rules against all the software. But the actual query text shows...

       

      DELETE FROM tblApplicationRuleWork

      WHERE SoftwareCheckSum IN (

      SELECT s.SoftwareCheckSum

      FROM dbo.tblSoftware s

      INNER JOIN dbo.tblApplicationRuleWork rw ON rw.SoftwareChecksum = s.SoftwareChecksum

      WHERE ((s.OSType = @ExOSType AND (s.OSType > 0 OR s.IsRegistry = @ExIsRegistry)) AND s.[Name] LIKE @ExName AND (s.[Version] LIKE @ExVersion OR s.[Version] LIKE @ExSMSVersion OR s.[Version] LIKE @ExSMSVersion2 OR ( @ExIncludeVirtualVersions = 1 AND s.[Version] LIKE @ExVTVersion ))

      AND ( s.ExecutablePath LIKE @ExExecutablePath )))

       

      ...now I don't understand the context of the query in relation to the process as a whole and indeed the query shown may just be a by-product of it waiting for another process to complete, but any queries that include so many LIKEs, ORs and @parameters are typically non-SARGable and will most likely be poor performance wise.

       

      Would be good to get Snow's input into whether they are looking to address the woeful performance of the complete ruleset DUJ runs?

      Expand Post

  5. Huge increase in DUJ times after Snow Inventory 6.7

    Hi,

     

    Has anyone else noticed a huge increase in DUJ times after installing Snow Inventory 6.7? Last week we installed SIS 6.7 in our test environment, and our DUJ times are now 3 times longer. So we have increased from an average of 2 hours 41 min to 7 hours 49m.

     

    I wondered if it is just us? We were hoping for a decrease in DUJ times because of the new Garbage Collector (which looks like a huge improvement).

     

    Thanks, David

    Expand Post

    1 of 7
    • Hi David

      Have you already rebuilt the DB index of the Snow Inventory database?

      There you can check the whole thing again for sure if there are any problems.

       

      Expand Post

  6. Issues with Snow License Manager v9.14 installer?

    Hi, I was wondering if anyone has used the v9.14 SLM installer currently available for FTP download?

     

    I have just attempted to build 2 separate environments with it. All appears to go well until I tried the DUJ, whereupon nothing appear to be processed. When checking the logs (tblJobLogMetrics, tblJobLog, tblErrorLog), the job appears to have run fine but there are hardly any steps....JobLogMetricsWhen looking at the SQL Agent Jobs, also appear to be missing all the jobs that are usually there (the ones prefixed with inv. and slm.)...

    DUJ SQL jobvs

     

    DUJ SQL job2I thought these are were generated on first DUJ run following an upgrade/install of SLM 9?

     

    I also noted an error in the tblErrorLog showing the following...

     

    Error #1088 line 1. [Cannot find the object "o365.ReadModelUsersPerSubscriptionPlan" because it does not exist or you do not have permissions.]

     

    The timing of this is at installation time though, not when the DUJ run. The object in question does actually exist.

     

    This is the first time I have used the full installer, in the past it is usually taking an older available installer and SUS-ing up to the latest version.

    Expand Post

    1 of 6
    • Quick update, found the cause....hadn't enabled the Inventory Source....

       

      InventorySource 

      This Active column defaults to False, had to go into SMACC and set it to true. Once I done that and ran the DUJ, everything got generated and started processing.

      Expand Post

  7. A brilliant idea about the complete ruleset

    I just wanted to share this idea I noticed on the Ideas Board:

     

    Setting "RUN_COMPLETE_RULESET_DAY" will redo all of it's work if DUJ fails or is stopped

     

    I imagine that many of us experience some very long DUJ times when the "complete ruleset" happens. That idea would certainly help us a lot. Feel free to put a vote on it if you also think it would help :-)

    Expand Post

    • Kristy Stroud (Flexera Software)

      Thanks so much for sharing this information. I'm sure it will be very valuable to many customers.

  8. Should we still use the "RUN_COMPLETE_RULESET_DAY" setting?

    Some years back, we were advised by Snow Support to enable the "RUN_COMPLETE_RULESET_DAY" setting. At the time I took notes:

     

    ...when new rules get added by Snow to the global database, certain parts of the process only happen once. However, sometimes there can be errors during this process which leave the rules in a state of limbo. These rules will look like they are installed when you view them in the SMACC, but in fact they will not be active. This situation can be resolved by "running the complete ruleset". This makes sure that all the rules have been fully imported.

     

    However, a lot has changed since then and the DUJ works differently now.

     

    Does anybody know if it is still advisable to run the complete ruleset every week? It makes our DUJ take a long time at weekends, and I wonder if we still need it.

     

    David

    Expand Post

    1 of 30
    • Alessandro Badin (Flexera Software)

      Hi all,

      Starting from License Manager 9.20.1, the unused software data is cleaned up from the system as part of the daily cleanup routine.

      The cleanup service update also includes improved configuration options, with multiple schedules per task now available through the appsettings.json file.

       

      To not overload the database during or immediately after the upgrade, the cleanup is performed in steps and the initial cleanup might take several days; however, when the most of the obsolete software data has been removed, the "Complete-Ruleset" Data Update Job should take less time.

       

      We are fixing the release notes to include references to (IDEA-I-102) and (IDEAS-I-968).

       

      We are also still working on much more impacting improvements.

       

      I hope this helps!

      Expand Post

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
34 Posts
Loading
Data Update Job | Flexera