You run into the errors similar to the following when running sp_eventmon monitoring utility:
$SP_BINDIR/../util/iwgrep -f$SP_BINDIR/../util/error_list -s"u2199" -mu2199.mrk $SP_SYS_VARDIR/log/event_log
QS_999_program - iwerrors.txt is nonexistent or unreadable.
Shareplex monitoring utility sp_eventmon gives error.
First of all the monitoring scripts are provided as template and need to be customized according to one's environment. For this specific error try the following as workaround. Set the parameter IW_HOME -path where iwgrep is located in your environment and run the command. You need to set IW_HOME pointing to iwerrors.txt and iwgrep executable. ie. export IW_HOME=$PRODIR/util/
The above workaround has worked for some customers. If the above does not work, you may want to check if any of the following apply to your situation:
* The scripts must be customized to reflect your environment, such as the type of email or paging available.
* To use the monitoring utilities, start sp_cop with the -uname option, where name can be an identifier of your choice. Suggestions are:
--the SharePlex port number
--the ORACLE_SID of the instance for which replication is being monitored
--the SharePlex Administrator's name
See "Starting sp_cop with the -u option on UNIX systems" by searching the Admin Guide for instructions and syntax.
* SharePlex must be running prior to executing a monitoring script.
* The monitoring utility scripts must remain together in the installed directory (/SharePlex_product_directory/util). Do not move these scripts to a different directory.
* The monitoring scripts make use of sp_ctrl commands. Before you use the scripts, make a link in the util sub-directory to the sp_ctrl binary in the bin sub-directory of the SharePlex product directory. Do not copy the binary itself, because that makes it difficult to maintain patches to sp_ctrl.
* Users of the monitoring utilities must have the following rights:
--local access to sp_ctrl and permission to run the script on the system on which the sp_cop to be monitored is running.
--Korn (ksh) shell access and ps permission from the UNIX command line.
--read, write and execute permissions to the directory where the scripts reside.
* The permission on the iwgrep utility must be 755.
* The monitoring utilities use the mailx program to send e-mail notifications. Before using a script, make sure mailx is configured to send e-mail on all systems where the monitoring scripts will be deployed.
* Paging requires that your service provider supports receiving e-mails on your paging device.
* Verify the ORACLE_HOME (the path to the ORACLE_HOME directory) for each Oracle instance being monitored.
