monitors:xym-oracle [Xymonton]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Oracle plugin for xymon ======

^ Author | [[ javierblanco@sysdba.net | Javier Blanco ]] |
^ Compatibility | Hobbit & Xymon servers |
^ Requirements | Linux, sh, ksh, oracle |
^ Download | http://sourceforge.net/projects/xymoracle/files/xym-oracle-1.0.tar.gz |
^ Mirror | http://sysdba.net/reposoft/xym-oracle-1.0.tar.gz |
^ Last Update | 2012-04-25 |
===== Description =====
Fork of deadcat's bb-moracle.sh. Adapted to hobbit & xymon server new versions and improved with new added features.

Tested with Oracle 11G (al releases)
===== Installation =====
=== Client side ===
1. Create an oracle user for hobbit monitoring:

<code>
SQL> create user check_bb identified by my_passwd
  2  default tablespace users;
User created.
SQL> 
</code>

2. Grant to check_bb user these rol and permissions:

<code>
grant connect to check_bb;
grant alter session, create session, select any table to check_bb;
grant select on sys.dba_data_files to check_bb;
grant select on sys.dba_free_space to check_bb;
grant select on sys.dba_segments to check_bb;
grant select on sys.v_$backup to check_bb;
grant select on sys.v_$datafile to check_bb;
grant select on sys.v_$process to check_bb;
grant select on sys.v_$session to check_bb;
grant select on sys.v_$recovery_file_dest to check_bb;
grant select on sys.v_$sql to check_bb;
grant select on dba_users to check_bb;
grant select on dba_objects to check_bb;

</code>

3. Copy xym-oracle.sh and xym-oracle_def files to hobbit extensions' directory, usually "$HOBBITCLIENTHOME/ext/".

4. Configure hobbit client to make the test, add this content to clientlaunch.cfg:

<code>
[oracle]
        ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
        CMD $HOBBITCLIENTHOME/ext/xym-oracle.sh
        LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
        INTERVAL 5m
</code>

5. Edit this parameters at xym-oracle_def with your oracle's settings:

<code>
ORACLE_HOME=YOUR_ORACLE_HOME; export ORACLE_HOME
ORACLE_SIDS="YOUR_ORACLE_SID OR SIDS WITH SPACES"; export ORACLE_SIDS 
DB_PASSWORD="YOUR_CHECK_BB_ORACLE_PWD"; export DB_PASSWORD
</code>

6. Edit this parameter at xym-oracle.sh with your hobbit client settings:

<code>
XYMHOME=/usr/lib/hobbit/client; export BBHOME
</code>

7. Restart your hobbit client


* NOTE: To enable or disable oracle sub-tests go to xym-oracle_def and change "Y" to "N" or "N" to "Y":

<code>
LISTENER_CHECK="Y"; export LISTENER_CHECK
LISTENER_CHECK_VERBOSE="Y"; export LISTENER_CHECK_VERBOSE
DATABASE_CHECK="Y"; export DATABASE_CHECK
TABLESPACE_CHECK="Y"; export TABLESPACE_CHECK
EXTENT_CHECK="Y"; export EXTENT_CHECK
SHADOW_CHECK="Y"; export SHADOW_CHECK
USER_CHECK="Y"; export USER_CHECK
USER_CHECK_VERBOSE="Y"; export USER_CHECK_VERBOSE
USER_PASSWD_EXPIRE="Y"; export USER_PASSWD_EXPIRE
INVALID_OBJECTS_CHECK="Y"; export INVALID_OBJECTS_CHECK
RMAN_NEED_BACKUP="Y"; export RMAN_NEED_BACKUP
RECOVERY_AREA="Y"; export RECOVERY_AREA
</code>

=== Server side ===
None

===== Source =====

There's a link to the extention at the top of the page!

===== Known  Bugs and Issues =====

* Oracle test with all tests enabled each 5 minutes could be heavy to some oracle servers, in this case you can change the execution time to 10m.

* If Oracle has usually many open sessions and "USER_CHECK_VERBOSE" is set to "Y" can appears purple reports in oracle test. It happens 'case the output's monitor is too big to hobbit. I suggest to disable this sub-test in this scenario.
===== To Do =====
I'm working in a subtest to monitoring oracle blocked sessions.
===== Credits =====
xym-oracle project at https://sourceforge.net/projects/xymoracle/

This development is under fsf gnu 3.0 licence or better if exists.

More info at http://www.gnu.org/licenses/gpl-3.0.html
===== Changelog =====

Initial version features:

* Monitoring listener status.
* Monitoring database status.
* Monitoring tablespace occupation.
* Monitoring database extents.
* Monitoring database shadow processes.
* Monitoring database user passwords.
* Monitoring database objects state.
* Monitoring RMAN policy.
* Monitoring recovery area occupation.