Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

error retrieving database records

 8 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Mick
Veteran Member
Posts: 82
Veteran Member
12/27/2018 12:21 AM
    It seems after a reboot of the three servers ,lsf, IPA and MSCM.
    within a couple of hours receive 'error retrieving database records'
    Infor suggest it is a 'defect' but no solution.
    The work around is to stop the offending websphere server (yes we are clustered) run srgen then start that server.

    This is not resolving the issue only a work around.
    Any thoughts would be appreciated.
    windows 2012, lsf 10.09, msp 7 websphere 8.5.5.9
    dmcdougald
    Posts: 3
    12/27/2018 1:53 PM
      Are you able to view the same records through portal? Can you view the records with your own odbc account directly?
      Trying to isolate where the issue is occurring.
      Mick
      Veteran Member
      Posts: 82
      Veteran Member
      12/28/2018 1:20 PM
        What records? I don't know what they are doing, this happened about 2-2:30 am so not sure what 'they' ? are doing.
        John Henley
        Posts: 3353
        12/28/2018 1:47 PM
          I researched this for another client a while back, and off the top of my head I remember it had to do either with database replication being out of sync (are your databases replicated?) or with maintenance plans competing with the IPA server and starving out resources.
          Thanks for using the LawsonGuru.com forums!
          John
          Jimmy Chiu
          Veteran Member
          Posts: 641
          Veteran Member
          1/2/2019 1:30 AM
            is your database clustered also?
            Alex Tsekhansky
            Veteran Member
            Posts: 92
            Veteran Member
            1/3/2019 5:43 PM
              Do you HAVE TO run SRGEN to fix the issue? Do you need to run anything else, like xscrgen?

              If you do, the issue might be related to the timestamps of the sr/or files. Have you done investigation on those and compiled programs (real values vs what's stored in GEN)?
              Have you checked permissions on the ser directory where WAS stores its temp files when you run forms?
              Mick
              Veteran Member
              Posts: 82
              Veteran Member
              1/20/2019 4:03 PM
                Yes,
                the Database is clustered.
                Ethan
                Advanced Member
                Posts: 28
                Advanced Member
                1/21/2019 3:54 PM
                  We are having this same issue and have been working with Infor for the last few months on resolving it.We have Win 2012, SQL Server 2012, LSF 10.0.10, MSP 10.0.8, WAS 8.5.5.12, Portal 10.1. We didn't start encountering the issue until upgrading to LSF 10.0.10, MSP 10.0.8, and Portal 10.1. We notice the issue occurs after we cycle the Windows LSF box (which hosts all of the DBs, S3, Landmark, LSO, etc). We can bring Lawson and WAS down and up and do not encounter the issue. The issue does not occur immediately, typically 24-48 hours after bringing the environment back up.

                  John, when you mentioned "maintenance plans", was this Windows maintenance, SQL maintenance,etc.?

                  Also wanted to note that the "SRGEN, cycle app server" solution was suggested by Infor and has been resolving the issue as it comes up. I think the SRGEN suggestion initially came from users encountering the "error retrieving database records" on the search and drill functions.
                  Alex Tsekhansky
                  Veteran Member
                  Posts: 92
                  Veteran Member
                  1/23/2019 1:15 PM
                    On Windows platform the most common "theme" related to that error - Lawson is set on a VM, and SQL server is on a different VM. All VMs are VMWARE. VMWARE has a curious error related to the VMOTION capabilities that cause applications to lose current connection to SQL. Since Lawson does not reestablish lost connections automatically, hence the issues. This usually does NOT happen if the SQL is located on the same box as LSF.
                    So,
                    1. Do you run LSF and/or SQL on VMWARE, other virtual platform, or physical server(s)?
                    2. Do you run LSF and SQL on the same box?
                    3. If it's VMWARE, is the VMOTION enabled?
                    4. If VMOTION is enabled, is it possible to disable it for LSF-related servers?
                    5. If it's NOT enabled, do you have enough resources to pre-allocate RAM for all servers related to the LSF setup (virtual memory sharing can cause this as well)?