Clovertech

Large Message Stuck in Recovery DB State 5?

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Large Message Stuck in Recovery DB State 5?

  • Creator
    Topic
  • August 31, 2012 at 3:58 pm #53257
    Jennifer Hardesty
    Participant

      I have a message stuck in the Recovery DB State 5 (pre-Xlate queue).

      Anyone know what might cause this and/or how to get it moving on?

      I will say that it’s a rather large message — 27M+ — which the Xlate will break down if I can get it there.

      We are on CL 5.7rev2.  CL choked ftp’ing the file over too, so I need to find a work around for getting the file to CL.

      Is the file just too large for CL to handle?  This is a Lawson xx527 mfn inventory file and they apparently expect to send these multiple times a day.  (I’ve recommended that they use a different method of delivery but this is their choice.)

      Thanks in advance!

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • August 31, 2012 at 5:20 pm #77071
        Levy Lazarre
        Participant

          Jennifer,

          I have no experience trying to move such a large file through an Xlate and I am not sure it’s a wise thing to do.

          I receive a daily IC527 inventory file from Lawson for our Surgical Manager application. In “TPS Inbound Data” of the inbound thread, I placed a Tcl script that breaks the Lawson file into individual MFN messages. I then send each message to Translation. It works very well.

          Perhaps you should try something like that; break the file by Tcl script pre-Xlate instead of having the Xlate do the splitting.

          I hope this helps.

        • August 31, 2012 at 5:30 pm #77072
          Levy Lazarre
          Participant

            I forgot to mention that I don’t use ftp to get the file from Lawson.

            I have our Unix Admin copy the IC527 file from the Lawson server to the Cloverleaf server. Therefore I am able to use a fileset-local thread to pick up and process the inventory file.

          • September 5, 2012 at 4:51 am #77073
            Jennifer Hardesty
            Participant

              I’ve written a tcl proc to break up the large message into individual messages.  However, when I attempt to run it in the Testing Tool, it doesn’t ever come back with anything.

              This is becoming extremely stressful.  There are apparently over 31,000 items in this single message.  I don’t understand why Lawson can’t give us the items in batches of 10,000.

              It’s bad enough that we are supposed to check 2x an hour for this file because the users want the update “real time”.  If they are going to send that much data every time, multiple times a day…per facility…Gosh, I thought the increased traffic from Epic was going to endanger the server, but maybe the Lawson inventory updates will bring it down…

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