Clovertech

CL 6.0 Cycle Saving unexpectedly

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › CL 6.0 Cycle Saving unexpectedly

  • Creator
    Topic
  • December 13, 2016 at 4:00 pm #55268
    John Stafford
    Participant

      I was reviewing messages for a new thread and I noticed that the SMAT file had cycled-saved unexpectedly, which overwrote the previous .old file, losing those messages. I do not see any error messages in the output, only a confirmation that the file had been copied. The thread had not been cycled, and there is not any indication that anything was prompting the cycle save.

      Any thoughts?

      Code:

      Engine idle — 12/13/2016 09:18:40

      Engine idle — 12/13/2016 09:19:08

      Engine idle — 12/13/2016 09:19:36

      Engine idle — 12/13/2016 09:19:51

      File successfully copied.
      Engine idle — 12/13/2016 09:20:06

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • December 14, 2016 at 1:26 pm #84752
        Peter Heggie
        Participant

          We had a similar problem with 6.1, with smat dbs. We could never pin down the exact cause. I thought it happened when someone was looking at the file and a new message arrived, but I could not prove it or correlate it 100%. The problem went away with an update.

          Peter Heggie

        • December 14, 2016 at 2:10 pm #84753
          Keith McLeod
          Participant

            Seems like multiple circumstances trigger that cycling.  I would suggest enabling SMAT History so that at least it does not overwrite or for that matter create .old smat files, but creates a SmatHistory Subdirectory and date and time stamps the file with each cycle.

            I think when I started on these it was triggered by bouncing the process or possibly even the thread.

            Hope this helps…

          • December 15, 2016 at 6:11 pm #84754
            bill bearden
            Participant

              Peter,

              What version did you upgrade to that fixed it for you?

              Thanks

            • December 15, 2016 at 6:18 pm #84755
              Peter Heggie
              Participant

                we went to 6.1.2, but I have to say also that we decided to enable SmatHistory everywhere. So now I can’t say if it was the upgrade or the SmatHistory that fixed it.

                We needed to control the amount and number of Smat DB files available for searching, enough of a date range so that most queries could be answered with what we had in the process directory and SmatHistory directory, and then the rest were moved off to another file system (automatically/weekly). So we rolled this out to all processes and sites.

                This certainly prevents the .old files from being overwritten, but I have not seen any ‘extra’ Smat DB files in SmatHistory either.

                Peter Heggie

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.