Ad Widget

Collapse

Node Setup; Oracle Issues

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cronuscronus
    Junior Member
    • Jan 2010
    • 29

    #1

    Node Setup; Oracle Issues

    Hey all. So I have 4 nodes I'm trying to setup and it looks like there are some Oracle bugs in 1.8.3.

    The first issue I have is that configuration data seems to throw lots of Oracle errors saying "missing comma". I've tracked it down to the trigger comment insert:
    insert into triggers (triggerid,expression,description,url,status,value ,priority,lastchange,dep_level,comments,error,temp lateid,type) values (200200000012007,'{200200000011007}<10240','lmemFr eeMem on {HOSTNAME} is too High',NULL,0,1,3,0,0,0x20,NULL,0,0);

    The comment "0x20" is invalid. Any ideas how to fix this?

    The other is in nodesender.c. MD5 is not a built in oracle function. The use of an nclob also presents issues.

    The following changes seem to fix it:
    -- Line 113
    default :
    zbx_snprintf_alloc(&sql, &sql_allocated, &sql_offset, ZBX_FIELDNAME_LEN + 6, "TO_NCLOB(ORA_HASH(%s))",
    tables[t].fields[f].name);
    break;
  • untergeek
    Senior Member
    Zabbix Certified Specialist
    • Jun 2009
    • 512

    #2
    This is a show-stopper for us. We are about to roll out Zabbix DM and we're an Oracle shop. If the nodesender issue is for real, we don't want to recompile just to permit this. This will need to be fixed before we decide to go with DM.

    Comment

    Working...