The sp_qstatmon script monitors the status of the capture and post queues for message backlogs. You can configure the script to alert you if the number of messages in a queue exceeds a defined threshold (limit), indicating that there is a potential data, system or network problem. This gives you time to correct the problem before the queues exceed their allocated space on the filesystem.
After each analysis of the queues, the sp_qstatmon script prints a notice in the capstat.log file for the capture queue or the poststat.log file for the post queue, as well as an e-mail message if that option is enabled.
Before running the script, perform the following tasks.
See Requirements for using the monitoring scripts before using this script. Note: The script must be run in the ksh shell.
The script creates some temporary files in the util sub-directory of the SharePlex product directory. Assign write permission to that directory to the sp_qstatmon module.
To execute sp_qstatmon with e-mail notification, you must first must define the e-mail address(es) in the script. Notification messages are sent to all addresses coded in the script. Unless email notification is enabled, sp_qstatmon only logs errors to the log file.
You can specify as many addresses as you want.
Add the address strings after the MailUserName= variable. Use the full e-mail and/or pager address. Separate multiple entries with a comma, as shown in the following example.
Run the script from the util sub-directory of the SharePlex product directory, not from app-modules. When you run it from the util directory, you actually make a soft link that runs a utility which first sets up the correct environment before running the script itself.
nohup sp_qstatmon -v path -t n -p port_number [-c integer ] [-d integer ] [-m] > /dev/null &
Table 9: Required arguments
|nohup sp_qstatmon||Directs the script to continue running in the background if the user logs out. This ensures continuous monitoring. The sp_qstatmon component runs the script.|
|-v path||Sets the path to the SharePlex variable data directory for the instance of sp_cop that you want to monitor. Without this variable, sp_qstatmon fails and prints an error message requesting a valid path.|
|-t n||Sets the time interval between scans in seconds. This value can be any positive integer.|
|-p port||Sets the port number for the instance of sp_cop that you are monitoring. You can monitor different SharePlex instances by running sp_qstatmon for each one, using different values for this argument.|
|&||Runs the script in the background.|
Table 10: Optional arguments
|/dev/null||Redirects the notification output to the /dev/null device on the local system so that the monitoring process continues to run in the background and generate output. To have the output appear on screen, omit this argument.|
|-c integer||Sets the number of messages in the capture queue at which the script issues a warning message. This value can be any positive integer. Without this parameter, sp_qstatmon defaults to 100 messages.|
|-d integer||Sets the number of messages in the post queue at which the script issues a warning message. This value can be any positive integer. Without this parameter, sp_qstatmon defaults to 100 messages.|
|-m||Enables the e-mail/paging option. Without this parameter, sp_qstatmon only logs errors to the log file.|
SharePlex provides the Sp_Nt_Mon script for monitoring processing Windows systems. Sp_Nt_Mon runs in the background to monitor SharePlex and notify you of events and conditions that can adversely affect replication. This script provides a monitoring mechanism without the need for frequent status checks through sp_ctrl.
Important! Do not rename this script.
The Sp_Nt_Mon script detects and reports the following conditions by email:
To configure and run Sp_Nt_Mon
Refer to the following table to modify the properties in the sp_nt_mon.txt file. Sp_Nt_Mon reads input from this file. To make comments in this file, start each comment line with the # symbol.
|Time Interval||60 seconds||Sets a time interval, in seconds, between monitoring polls.|
|Send Email alert||1 (enabled)||
Enables or disables email alerts. Email is the only reporting option.
0 = disabled
1 = enabled
|SMTP Server Name||none||Specifies the name of the SMTP server for the e-mail account.|
Specifies one or more email addresses that will receive monitor notifications. Separate each email address with a space, for example:
Email Address: Your.Name@YourCompany.com Other.Name@YourCompany.com
|0 (do not monitor)||
Specifies processes to monitor. A value of 1 enables monitoring and must be set for each process that you want to monitor. For example, to monitor Capture and Export, set the properties as follows:
|0 (do not monitor)||
Sets the maximum number of messages that a queue can contain before an alert message is triggered.
Set a positive numeric value for each queue that you want to monitor. Set a value that is well below the amount of disk space that is allocated to this queue. This gives you enough time to add disk space or resolve any problems that are causing a backlog.
|Monitor the Event Log||0 (do not monitor)||
Enables or disables the monitoring of supported Event Log messages.
0 = disabled
1 = enabled
The following messages are monitored:
SharePlex was shutdown
System call error
Queue partition is full
Host is down
Out of sync
Parameter was changed Activate config
Bad config file
sp_cop was shutdown
Child process failed
ORA-error number errors
|Monitor Redo Logs||0 (do not monitor)||
(Oracle only) Enables or disables the monitoring of Capture latency.
0 = disabled
1 = enabled
|Redo Threshold||2 logs||(Oracle only) Sets a value for the maximum permissible number of logs for Oracle to be ahead of SharePlex in the redo stream. When the value is reached, an alert is triggered. Use when Monitor Redo Logs is enabled.|
SharePlex provides agent support for Simple Network Management Protocol (SNMP) on all Unix, Linux, and Windows platforms supported by SharePlex replication.
Note: SharePlex provides only agent support for SNMP. It only sends SNMP traps. SharePlex does not provide an SNMP signal daemon (SNMP manager) to intercept the traps. Use the SharePlex SNMP feature only if you have a Network Management Station (NMS) to manage SNMP signals. The SharePlex SNMP agent is named snmptrap and is installed with SharePlex in the bin sub-directory of the SharePlex product directory. Do not run this program.
To enable SNMP monitoring of SharePlex replication, set the SP_SLG_SNMP_ACTIVE parameter to 1. By default, the parameter is set to 0 (disabled).
The following parameters configure the SNMP agent to communicate with the NMS. Each parameter must have a value if the SP_SLG_SNMP_ACTIVE parameter is enabled.
|SP_SLG_SNMP_HOST||The name of the system (host) to which the traps will be sent|
|SP_SLG_SNMP_COMMUNITY||The community security string|
|SP_SLG_SNMP_MJR_ERRNUM||The major error number to be used by the traps|
|SP_SLG_SNMP_MNR_ERRNUM||The minor error number to be used by the traps|
The following parameters specify required information for a custom MIB.
|SP_SLG_SNMP_ENTERPRISE_OID||The enterprise object identifier to send with the trap. The default is 126.96.36.199.188.8.131.52.1 .|
|SP_SLG_SNMP_TRAP_OID||A custom object identifier to bind to the trap. The default is 184.108.40.206.220.127.116.11.0.|
|SP_SLG_SNMP_TRAP_PROGRAM||The name of the trap program. The default is iwsnmptrap.|
The following parameters configure the SNMP agent to send traps for specific replication events. The message or error text for the event is included in the trap and is the same error that appears in the Event Log.
To enable an SNMP trap for an event, set the corresponding parameter to a value of 1. By default all traps are disabled (parameter value of 0).
|SP_SLG_SNMP_INT_ERROR||SharePlex logic errors and errors that cause processes to exit|
|SP_SLG_SNMP_SYS_ERROR||System-related errors encountered by SharePlex|
|SP_SLG_SNMP_ERROR||Other SharePlex errors|
|SP_SLG_SNMP_OUT_OF_SYNC||Replication is out of synchronization|
|SP_SLG_SNMP_STARTUP||SharePlex starts up|
|SP_SLG_SNMP_SHUTDOWN||SharePlex shuts down|
|SP_SLG_SNMP_LAUNCH||A SharePlex process starts|
|SP_SLG_SNMP_EXIT||A SharePlex process stops|
This section contains solutions to many of the common questions and problems that can arise during replication, and it also suggests preventive measures for avoiding problems.