Messages corrupting DB when engine moving from RDB to EDB

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Messages corrupting DB when engine moving from RDB to EDB

  • Creator
    Topic
  • #53070
    Andre van Olden
    Participant

      We’ve had two separate instances of this on the same interface in about a 30 day period ( Cloverleaf 5.7 on AIX ).  Process panic’s with the following errors.

      [dbi :dbi :ERR /0:  srz10_xlate:04/30/2012 15:25:11] [0.0.23392598] dbiDeleteLogMsg: msg body scan/delete failed

      [xlt :xlat:ERR /0:  srz10_xlate:04/30/2012 15:25:11] [0.0.23392609] removal from db failed: 4

      ****** DETAILS ******

      Reference to MID remains viewable utilizing the hcidbdump command on the RDB, but you cannot access ( view or remove ) from the DB.

      eg:

      hcidbdump -r

                             C  

                             l T

                             a y F

                             s p w

      Created  Message Id     s e d Prio State Length Source          Dest



      – – – —-





      [0:_hcidbdump_] [0.0.23392603] Unable to read msg data chain

      [0:_hcidbdump_] [0.0.23392598] Unable to read msg data chain

      [0:_hcidbdump_] [0.0.23392590] Unable to read msg data chain

      [0:_hcidbdump_] [0.0.23392609] Unable to read msg data chain

      15:25:11 [0.0.23392587] E D N 5120     7    222 srz10nrz10_in   srz00soar_out  

      15:25:11 [0.0.23392592] E D N 5120     7    222 srz10nrz10_in   srz00soar_out  

      15:25:11 [0.0.23392597] E D N 5120     7    222 srz10nrz10_in   srz00soar_out  

      [0:_hcidbdump_] [0.0.23392609] Unable to read msg data chain

      Unable to read message [0.0.23392609]

      Processed 0 messages

      *****

      The same MID is also in the EDB, but you can extract ( see below ) – it is a message of all nulls and we cannot find this as having come from any inbound system.

      hcidbdump -e

                             C  

                             l T

                             a y F

                             s p w

      Created  Message Id     s e d Prio State Length Source          Dest



      – – – —-





      15:25:11 [0.0.23392595] P D N 5120   500    222 srz10nrz10_in                  

      15:25:11 [0.0.23392603] E D N 5120   500    222 srz10nrz10_in   srz00soar_out  

      15:25:11 [0.0.23392598] E D N 5120   500    222 srz10nrz10_in                  

      15:25:11 [0.0.23392609] E D N 5120   500    222 srz10nrz10_in   srz00soar_out  

      15:25:11 [0.0.23392590] P R N 5120   500     26 srz00soar_out   srz10nrz10_in  

      Done. 5 messages selected.

      msg: 0x3000003c

         msgType           : DATA

         msgClass          : ENGINE

         msgState          : Internal failure: unable to read msg data chain (500)

         msgPriority       : 5120

         msgRecoveryDbState: 3

         msgFlags          : 0x8002

         msgMid            : [0.0.23392609]

         msgSrcMid         : [0.0.23392598]

         msgSrcMidGroup    : midNULL

         msgOrigSrcThread  : srz10nrz10_in

         msgOrigDestThread : srz00soar_out

         msgSrcThread      : srz10nrz10_in

         msgDestThread     : srz00soar_out

         msgXlateThread    :

         msgSkipXlate      : 0

         msgSepChars       :

         msgNumRetries     : 0

         msgGroupId        : 0

         msgDriverControl  :

         msgRecordFormat   :

         msgRoutes         :

         msgUserData       :

         msgStaticIsDirty  : 0

         msgVariableIsDirty: 0

         msgTimeStartIb    : 1335817511.700(15:25:11)

         msgTimeStartOb    : 1335817511.660(15:25:11)

         msgTimeCurQueStart: 1335817511.737(15:25:11)

         msgTimeTotalQue   : 0.027

         msgTimeRecovery   : 1335818111.712(15:35:11)

         msgEoConfig       : 0x0

         msgData (BO)      : 0x30000110

         message           : ‘x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00’

      Any help on this would be appreciated

    Viewing 3 reply threads
    • Author
      Replies
      • #76453
        Russ Ross
        Participant

          Since it is complaining about the data chain you might give these commands a try:

          Code:


          keybuild rlog; dchain rlog
          keybuild elog; dchain elog

          Russ Ross
          RussRoss318@gmail.com

        • #76454
          Andre van Olden
          Participant

            Thanks Russ,

            Did all the Raima recovery commands we could…to no avail.  ended up having to dump the good messages and then reinit the DB.

            My main focus at this point is to see what may be causing this.  I know it is wide open, but was hoping someone else may have run into a similar issue.

          • #76455
            Richard Hart
            Participant

              Hi Andre.

              I don’t have a fix, but I have had similar issue recently in development – self inflicted – where the only recovery was a DB cleanup.

              Our ‘resend’ module is required in up to four different contexts, depending on configuration and I missed one.

            • #76456
              Bob Richardson
              Participant

                One and All,

                From my understanding here (perhaps confirm with Lawson

                Cloverleaf R & D):  embedded nulls x00 can be interpreted internally as end of record in low level modules like the drivers.  Embedded nulls are a death sentence to Cloverleaf regardless of platform.   Who knows what other side effects they have – in this case, the Raima database cannot tolerate them.  The original error message context was “invalid data” and “scan” failures in Raima.

                We are just exploring the features of the Integrator 5.8.5 engine with its various protocol options on specifying data encoding.  Perhaps a solution may be available in this Integrator Release.

                I would suggest opening a CASE with Lawson support to confirm or deny

                my allegations here.

                Or get the sending system to NOT send these messages in the first place.

                Good luck.

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