New features added on this release:
- Added support for Sybase Anywhere
- Added support HP Allbase databases
those two point are made with the effort of:
Andreas Pohl
Andreas thank you for all your work!!!
fixed other issue introduced by a refactoring.
The complete diagram of the supported platform is the following:
Please referred to the wiki for the official documentation.
I’ve made a script to create an Orabbix/DBforBIX user with the minimum grants available.
CREATE USER ZABBIX IDENTIFIED BY <REPLACE WITH PASSWORD> DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP PROFILE DEFAULT ACCOUNT UNLOCK; GRANT ALTER SESSION TO ZABBIX; GRANT CREATE SESSION TO ZABBIX; GRANT CONNECT TO ZABBIX; ALTER USER ZABBIX DEFAULT ROLE ALL; GRANT SELECT ON V_$INSTANCE TO ZABBIX; GRANT SELECT ON DBA_USERS TO ZABBIX; GRANT SELECT ON V_$LOG_HISTORY TO ZABBIX; GRANT SELECT ON V_$PARAMETER TO ZABBIX; GRANT SELECT ON SYS.DBA_AUDIT_SESSION TO ZABBIX; GRANT SELECT ON V_$LOCK TO ZABBIX; GRANT SELECT ON DBA_REGISTRY TO ZABBIX; GRANT SELECT ON V_$LIBRARYCACHE TO ZABBIX; GRANT SELECT ON V_$SYSSTAT TO ZABBIX; GRANT SELECT ON V_$PARAMETER TO ZABBIX; GRANT SELECT ON V_$LATCH TO ZABBIX; GRANT SELECT ON V_$PGASTAT TO ZABBIX; GRANT SELECT ON V_$SGASTAT TO ZABBIX; GRANT SELECT ON V_$LIBRARYCACHE TO ZABBIX; GRANT SELECT ON V_$PROCESS TO ZABBIX; GRANT SELECT ON DBA_DATA_FILES TO ZABBIX; GRANT SELECT ON DBA_TEMP_FILES TO ZABBIX; GRANT SELECT ON DBA_FREE_SPACE TO ZABBIX; GRANT SELECT ON V_$SYSTEM_EVENT TO ZABBIX;
NOTE: If you have made some custom query you need to grant the select privilege on your used tables.
I’ve received from Johan Nilsson a nice way to check the failed scheduled jobs .
He sent to me a nice query to do that, the query is the following:
- For Oracle 10g and Oracle 11i:
broken_jobs.Query=select * from
( select job_name, count(*) “failures” ,status
from dba_scheduler_job_log
where log_date > sysdate-1
and status != ‘SUCCEEDED’
and status is not null
group by job_name, status
union all
select what,failures,’Status: ‘||decode(broken, ‘Y’,’Broken’,’N’,’Working’)
from dba_jobs
where failures > 0 )
- For earlier versions:
broken_jobs.Query=select job,what,failures,’Status: ‘||decode(broken, ‘Y’,’Broken’,’N’,’Working’)
from dba_jobs
where failures > 0
and we need to add a default value when “no data found”
broken_jobs.NoDataFound=none
After that you need to add the Item too on Oracle’s template and the relate trigger that will go on fire if there is something that is different from “none”
on next release I’m going to include this new feature.
Thank you Johan for your contribute!
David Rooke has kindly notified to me an issue on DBforBIX’s templates.
The issue it’s about “alive”. The item key should be:
DBforBIX.[PostgreSQL|Oracle|MySQL|DB2|MSSQL].alive
I’ve modified the template and reposted the package.
You can modify your own template or download DBforBIX 0.5
Tags: database, db2, dbforbix, linkedin, monitoring
