Home | Index/DBAmon Doc. | DBAmon Version/Change History | DBAmon Event/Error Doc. | What DBAmon Monitors | DBAmon Download | Free Oracle Tool: orastat | Request Support

User Exits

User Exits have now been supplied to provide additional opportunity to customize DBAmon without making code changes. All users exits must be stored in /opt/dbamon/bin/userexit and must be named the names specified below. They may be coded in any scripting language (KSH, Perl, Awk, ...) providing that they supply the correct #! string in the first line. They must be executable.

If a particular User Exit exsits, then it is invoked. For example, when DBAmon deems it necessary to create a Help Desk ticket, it looks for an executable called /opt/dbamon/bin/userexit/ticket. If it exists, then DBAmon will invoke it with the proper environment (see below). If /opt/dbamon/bin/userexit/ticket does not exist, then DBAmon takes no action.

In the install package all exits will be provide in EXAMPLE form, not activated. When you install DBAmon, if you look in the /opt/dbamon/bin/userexit directory, you will see:

-rwxr-xr-x    1 dbamon   vhost         137 Jul  1  1998 pager.EXAMPLE
-rwxr-xr-x    1 dbamon   vhost         316 May 14 13:42 ticket.EXAMPLE
-rwxr-xr-x    1 dbamon   vhost         143 Jul  1  1998 warn_msg.EXAMPLE
For example, to active the "ticket" User Exit:

User Exits Currently Provided:

This Document: http://dbamon.com/config/userexit.shtml