3.5.1 MxDB-Oracle-HiAv Installation and Administration Guide

Chapter 2: Operations 46

tolerance for a long-running SQL*Plus session executing as a part of the

probe. It is, in essence, the amount of time allotted to your custom probe

actions before the solution pack considers your probe actions stalled. The

default probe actions are very light so the default setting of this

parameter is 20 seconds. If significant actions are added to a custom

probe, this value must be set to accommodate the extra processing time.

Ultimately, the value assigned to this parameter cannot exceed the total

probe timeout, which is 190 seconds by default. Because the probe core—

the actions executed in the mxdb_probe.sql script—are only a portion of

the overall activity during a probe, it is not permissible to set

MxDB_PROBE_CORE_TIMEOUT to the total probe timeout associated with

the VHOST. The total probe timeout can be adjusted via the Matrix Server

CLI or Management Console as per the Matrix Server documentation.

Supplemental Startup Scripts

MxDB-Oracle-HiAv supports supplemental startup and shutdown scripts

that are customized at your site. MxDB-Oracle-HiAv ensures that the

database instance and SQL*Net listener processes are available in the

matrix. You might also want supplemental processes to be started and

stopped each time the database is restarted or failed over to another node.

For example, if you want the Intelligent Agent to start each time the

database instance is started, a supplemental script is required.

Configuring a supplemental startup script is a simple administrative task.

However, the functionality of the script is the responsibility of the

administrator. That is, MxDB-Oracle-HiAv will call the script, but it

cannot ensure that the script will succeed because the code is

site-customized. To that end, MxDB-Oracle-HiAv treats the execution of

the supplemental script with the following caveats:

• Return Codes. The supplemental script can return success or failure

codes; however, MxDB-Oracle-HiAv ignores them. This ensures that

the database instance and SQL*Net listeners start even if the

supplemental script fails.

• Timeout. The supplemental startup script is allocated a maximum of

20 seconds execution. If the supplemental script is still executing code

after 20 seconds, it will be terminated by MxDB-Oracle-HiAv. This