Experience with Orabbix 1.0.4
Comments from working with version 1.0.4
RAC Environments.
Since the default queries in orabbix monitor instances using the v$ views and the underlying database using the DBA views, have you had thoughts about breaking the queries out into instance monitoring verses database monitoring queries? This would avoid multiple database alerts in a RAC environment or having to build complicated Triggers.
Null field returned in query
Appears if a field is returned as null, a Java java.lang.NullPointerException error is returned. Is that expected, or can it be added as an enhacement request?
XDB
Not everyone has XDB installed and consequently cannot run UTL_INADDR queries in 11g. I have modified the dbversion query accordingly:
A couple of queries that I have modified.
archive
To prevent alerts when daylight savings time ends, check that first_time is also less than the current time.
From:
To:
locks
For some reason, I have locks on occasion in my 11.1.0.7 database there the LMODE in v$lock is 0 which in the original SQL causes a java.lang.NullPointerException error because the field being returned in NULL. Similiarly the DECODE for REQUEST should have a default value too.
From:
To:
Just wanted to share some of my experiences.
Thanks,
Brian
Comments from working with version 1.0.4
RAC Environments.
Since the default queries in orabbix monitor instances using the v$ views and the underlying database using the DBA views, have you had thoughts about breaking the queries out into instance monitoring verses database monitoring queries? This would avoid multiple database alerts in a RAC environment or having to build complicated Triggers.
Null field returned in query
Appears if a field is returned as null, a Java java.lang.NullPointerException error is returned. Is that expected, or can it be added as an enhacement request?
XDB
Not everyone has XDB installed and consequently cannot run UTL_INADDR queries in 11g. I have modified the dbversion query accordingly:
Code:
select COMP_ID||' '||COMP_NAME||' '||VERSION||' '||STATUS||' <br />' from dba_registry union SELECT ' - SERVERNAME = <b>'||host_name ||'</b><br />'from v$instance union SELECT ' - DB_NAME = <b>'||SYS_CONTEXT ('USERENV', 'DB_NAME') ||'</b> - INSTANCE_NAME = <b>' ||SYS_CONTEXT ('USERENV', 'INSTANCE_NAME')||'</b> <br />' FROM dual
archive
To prevent alerts when daylight savings time ends, check that first_time is also less than the current time.
From:
Code:
WHERE FIRST_TIME >= (sysdate -10/60/24)
Code:
WHERE FIRST_TIME >= (sysdate -10/60/24) and first_time < sysdate
For some reason, I have locks on occasion in my 11.1.0.7 database there the LMODE in v$lock is 0 which in the original SQL causes a java.lang.NullPointerException error because the field being returned in NULL. Similiarly the DECODE for REQUEST should have a default value too.
From:
Code:
decode(LMODE, \
1, 'Null', \
2, 'Row-S (SS)', \
3, 'Row-X (SX)', \
4, 'Share', \
5, 'S/Row-X (SSX)', \
6, 'Exclusive') lock_type, \
Code:
decode(LMODE, \
0, 'None', \
1, 'Null', \
2, 'Row-S (SS)', \
3, 'Row-X (SX)', \
4, 'Share', \
5, 'S/Row-X (SSX)', \
6, 'Exclusive', \
'Unknown') lock_type, \
Just wanted to share some of my experiences.
Thanks,
Brian
ool_free_mem] error: Type of received value [97,87] is not suitable for value type [Numeric (float)]
Comment