Ad Widget

Collapse

Probleme from upgrade zabbix 3.0 to 3.2 with database monitor

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • colloque
    Member
    • Feb 2010
    • 72

    #1

    Probleme from upgrade zabbix 3.0 to 3.2 with database monitor

    Hello,

    I have a problem with zabbix 3.2 avec a database monitor.

    My Query SQL is:

    select round(b.bytes_free) "free B"
    from ( select f.tablespace_name,
    sum(f.bytes) bytes_alloc,
    sum(decode(f.autoextensible, 'YES',f.maxbytes,'NO',
    f.bytes)) maxbytes
    from dba_data_files f
    group by tablespace_name) a,
    ( select f.tablespace_name,
    sum(f.bytes) bytes_free
    from dba_free_space f
    group by tablespace_name) b
    where a.tablespace_name = b.tablespace_name and a.tablespace_name='CAT_DATA'


    information
    Numeric (unsigned)
    Decimal
    B

    Now since the upgrade to zabbix 3.2 i have the following error (see attachment file)




    Do you have an idea ?

    Thanks in advance
    Attached Files
    Last edited by colloque; 08-09-2016, 17:24.
  • colloque
    Member
    • Feb 2010
    • 72

    #2
    Hello,

    I have applied the PATCH:

    ZBX-11213.patch

    and it works now.

    Thanks.

    Comment

    • mark.chan
      Member
      • Mar 2016
      • 35

      #3
      Could you teach me/tell me where I can know how to install the patch?
      Many Thanks.

      Comment

      • scarrijo
        Junior Member
        • May 2014
        • 1

        #4
        I have the same problem

        after upgrading from 3.0 to 3.2 all the triggers I had stopped working, and those ones that has a decimal value as a return has status as Not Supported .

        Comment

        • GPegel
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • Dec 2015
          • 113

          #5
          I had the exact same problem. This morning I did a "yum update" on my CentOS servers and I saw the newest update for Zabbix Server and that solved my problem. I've upgraded from 3.0.5 to 3.2.2 and all works well now.

          Comment

          Working...