commit;

Youcan verify the above is correct by running:

select utl_inaddr.get_host_name('127.0.0.1')from dual;

For this example on RedHat, run:

chkconfig -add orabbix

Verify with:

chkconfig -list

Create a Host entry in Zabbix for the DB Instance/s you are planning to monitor, and import the templates found at: /opt/orabbix/template

Please note, instructions for this step can befound in the Zabbix Manual at

http://www.zabbix.com/documentation.php

With this step, ensure the name of yourhost in Zabbix is the same name of the SID or Oracle instance name.

Configuration

Nowwe need to configure your Orabbix setup. The tags below are listed as they willappear within the respective configuration files. The first you will need tomodify is your config.props file to define your connection properties forZabbix and Oracle.

config.props

Theconfig.props file can be found at /opt/orabbix/conf/config.props

ZabbixServerList

#comma separed list of Zabbix servers

Thesettings under this tag allow you to configure your Zabbix Server information.Orabbix can also be configured to send your Oracle data to multiple Zabbixservers.

This can be beneficial for distributedmonitoring scenarios, server migrations or replicating Orabbix data to a Disaster Recovery site or server.

Replacewith your Zabbix Server info where appropriate;

ZabbixServerList=ZabbixServer1,ZabbixServer2

ZabbixServer1.Address=192.168.0.1

ZabbixServer1.Port=10051

ZabbixServer2.Address=192.168.0.2

ZabbixServer2.Port=10051

OrabbixDaemon

Entriesunder this tag allow you to set your Orabbix Daemon parameters.

#MaxThreadNumber should be >= than thenumber of your databases

Setthe number of threads the Orabbix Daemon should have inside his internal poolof DB Jobs. This number should be at least equal to (or more than) then numberof databases monitored by Orabbix, now this parameter if not set isautomatically calculated.

e.g.For 50 Databases, we are using 100 threads

OrabbixDaemon.MaxThreadNumber=100

#pidFile

Nextyou can set the location of the Daemons PID file. Default location is:/opt/orabbix/logs

OrabbixDaemon.PidFile=./logs/orabbix.pid

NOTE: Relative path is permitted here

TIP: With the features of the OrabbixDaemon, it is possible to clone Orabbix and use different configurations.

As such, it is therefore possible to haveone Daemon that checks your TEST databases, another iteration that checks your

DEVELOPMENT databases and a third thatchecks your PRODUCTION databases, each with different timings and check loops!

DatabaseList

Thisis where you define your database instances. You can specify more than oneinstance here, separated using a comma.

DatabaseList=EXAMPLE1,EXAMPLE2

NOTE: The names of the instances must match those you have specified asyour HOST name in Zabbix

#Configuration of Connection pool

Fromhere, you will configure settings that are specific to the connection pool. Asthe comments in config.props suggest, if you do not specify these values,Orabbix will use default values which have been hard-coded.

#Maximum number of active connection insidepool