Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Unable to monitor database

    Using ProTop
    3
    5
    2504
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      Kynan last edited by

      I have 5 databases that I would like to monitor (v10.2B on windows 2012 server) and 4 of them work perfectly. The 5th one gives the error: Unable to attach shared memory Global\sharemem.c.spserver.data.ams.amsdata.0, error 0. (1720)

      Has anyone any suggestions please?

      1 Reply Last reply Reply Quote 0
      • jdpjamesp
        jdpjamesp last edited by

        I asked Kynan to post here to hopefully pool knowledge.

        So far we have tried reducing the -B on the database. This is 32bit Progress executables.
        We have also tried running the dbmonitor manually from an elevated proenv session.

        Neither of these have worked.

        1 Reply Last reply Reply Quote 0
        • tom
          tom administrators last edited by tom

          Older 32 bit releases sometimes have attitude problems about allocating shared memory that don't become apparent until a batch client or character client attaches to them. Try starting your databases with -shmsegsize 128.

          (Ok, actually the problem is probably that the old oe10 _progres.exe was not improved to handle larger segments at the same time that the db server executables were.)

          1 Reply Last reply Reply Quote 0
          • K
            Kynan last edited by

            That has worked. Thank you

            tom 1 Reply Last reply Reply Quote 1
            • tom
              tom administrators @Kynan last edited by

              @kynan great!

              1 Reply Last reply Reply Quote 1
              • First post
                Last post