Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Trouble with ODBC SQL Polling

Trouble with ODBC SQL Polling

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 33.1k Views
  • 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.
  • X
    X
    xatteg
    wrote on last edited by
    #1

    Hello Victor,

    I've managed to build and launch ODBC subagent tried it and got some issues. Current query returns right result, but those results stored previously die or something wrong happens to them. I have included the printscreens of management console showing this and screen of collection configuration.

    Agent is configured with the following lines:
    *ODBC
    Query = SQL.MySQLQuery:mybase:SELECT COUNT(*) FROM USERS WHERE USERACTIVE = 1 AND USERDELETED = 0:60

    Normally query should return 171 or something like this.


    err4.PNG

    err1.PNG

    err2.PNG

    err3.PNG

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi!

      It looks like problem on server or in management console, because history is corrupted. Last value always good, which means that agent reports correct value. Can you try to change data type of this DCI to integer? Also, is there any other DCIs which experience same problem?

      Best regards,
      Victor

      1 Reply Last reply
      0
      • X
        X
        xatteg
        wrote on last edited by
        #3

        Hello Victor,

        Changing type to integer effectively solved the problem. All previously stored values are now displaying correctly. The one thing I don't understand is why did this happen?

        1 Reply Last reply
        0
        • V
          V
          Victor Kirhenshtein
          wrote on last edited by
          #4

          As all previously stored values displayed correctly now, that means a bug on client side - either in client library or in management console itself. Can you check any other string DCIs if you have any?

          Best regards,
          Victor

          1 Reply Last reply
          0
          • X
            X
            xatteg
            wrote on last edited by
            #5

            Hello Victor,

            I have added SNMP string polling and it has the same effect as ODBC polling. Current polled value is good and stored are ruined.

            Best regards,
            Roman

            1 Reply Last reply
            0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            Powered by NodeBB Contributors
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups