Occurs when a replication job status is Waiting for Thread. The database server uses threads to identify and store information for each individual user or a particular service request. The server uses the stored information to complete user and service requests. Threads help ensure that work is being performed for some user connections even when other connections are blocked (for example, when waiting for a disk read or write operation to complete). A replication job cannot complete when its status is Waiting for Thread.
When the indication occurs often enough to trigger an event, the event delivers a message to the Tivoli Enterprise Console in the following format:
<application_label>: The Microsoft SQL Server Replication Job
<MSSQLReplicationJobName> for server <MSSQLServerName> is waiting for a thread.
If you have Tivoli Business Systems Manager configured for your system, Tivoli Enterprise Console forwards the message to Tivoli Business Systems Manager. You can check the health of this resource model in the IBM Tivoli Monitoring Web Health Console. For more information, see the IBM Tivoli Monitoring Web Health Console documentation.
The indication has the following attributes: application_class
The registered object’s Tivoli Management Environment (TME) class. application_label
The registered object’s Tivoli Management Environment (TME) label. application_oid
The registered object’s Tivoli Management Environment (TME) object identifier.
application_version
The managed resource’s version; for example, v7, or 2k. MSSQLReplicationJobName
MSSQLServerName
The Microsoft SQL Server server name on which the replication job is running.
This indication has no thresholds.
The following table describes the default settings for this indication.
Setting Default value
Send indications to Tivoli Enterprise Console Yes Send indications to Tivoli Business Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have Tivoli Business Systems Manager configured for your systems, Tivoli Enterprise Console automatically forwards events to Tivoli Business Systems Manager. Do not change the configuration of the indication to send events to Tivoli Business Systems Manager.
Thresholds
NoneParameters
The following table lists the parameter that can be set for the Replication Jobs resource model. The table shows the name, a short description, and the default value for each parameter:
Parameter Description Default value
Ignored Jobs Type any job names you want to exclude from monitoring.
When this parameter is blank, the resource model monitors all replication jobs.
The wildcard character (*) is supported.
The following examples illustrate how to code your parameter:
v To match a single job such as″XYZ,″use the
following expression:
XYZ
v To match a job that begins with″ABC,″use the
following expression:
ABC*
v To match a job that contains″DEF,″use the
following expression:
*DEF*
v To match a job that begins with″A″and ends
with″Z,″use the following expression:
A*Z
Note: The″|″character is not supported in these expressions.
Blank (monitors all replication jobs)
Refresh Monitored Jobs Frequency
Defines how often the resource model receives a new list of monitored jobs from the Microsoft SQL Server. The value represents the number of resource model cycles between retrieving a new list of replication jobs to monitor.
For example, if the cycle time is 60 seconds and this parameter is set to 5, the resource model receives the list of replication jobs every 5 minutes. When a replication job is added, it is monitored the next time the list of replication jobs is retrieved. Specify only one entry for this parameter.
5
Tasks and built-in actions
NoneLogging
You can log data for the properties of the managed resource listed in the following table. The table shows the context of the managed resource and the properties that the resource model logs for the IBM Tivoli Monitoring Web Health Console.
Managed resource Context Properties
MSSQLJobCategory Status
MSSQLJobCategory.MSSQLJobCategory*
The job category of the specified Microsoft SQL Server job.
MSSQLServerReplication.MSSQLServerName*
The name of the Microsoft SQL Server server.
MSSQLReplicationJobName
The name of the selected Microsoft SQL Server replication job.
MSSQL_Replication_Job_Between_Retries
The time duration in seconds between retries of a successful execution for the specified replication job.
MSSQL_Replication_Job_Canceled
Specifies whether the specified replication job is canceled. A returned status of “1” indicates the replication job is canceled. A returned status of “0” indicates a status other than canceled.
MSSQL_Replication_Job_Executing
Specifies whether the specified replication job is executing. A returned status of “1” indicates the replication job is executing. A returned status of “0” indicates a status other than executing.
MSSQL_Replication_Job_Failed
Specifies whether the specified replication job failed. A returned status of “1” the replication job failed. A returned status of “0” indicates a status other than failed.
MSSQL_Replication_Job_Idle
Specifies whether the specified replication job is idle. A returned status of “1” the replication job is idle. A returned status of “0” indicates a status other than idle.
MSSQL_Replication_Job_In_Progress
Specifies whether the specified replication job is in progress. A returned status of “1” the
replication job is in progress. A returned status of “0” indicates a status other than in progress.
MSSQL_Replication_Job_Performing_Completion_Actions
Specifies whether the specified replication job is performing completion actions. A returned status of “1” indicates the replication job is performing completion actions. A returned status of “0” indicates a status other than performing completion actions.
Managed resource Context Properties
MSSQLJobCategory Status
MSSQL_Replication_Job_Retry
Specifies whether the specified replication job is retrying. A returned status of “1” indicates the replication job is retrying. A returned status of “0” indicates a status other than retrying.
MSSQL_Replication_Job_Succeeded
Specifies whether the specified replication job succeeded. A returned status of “1” indicates the replication job succeeded. A returned status of “0” indicates a status other than success.
MSSQL_Replication_Job_Suspended
Specifies whether the specified replication job is suspended. A returned status of “1” indicates the replication job is suspended. A returned status of “0” indicates a status other than suspended.
MSSQL_Replication_Job_Waiting_For_Thread
Specifies whether the specified replication job is waiting for a thread. A returned status of “1” indicates the replication job is waiting for a thread. A returned status of “0” indicates a status other than waiting for a thread.
Note: An asterisk (*) denotes a key property.
Return codes
Table 2 on page 7 contains a listing of resource model return codes, their
description, and what action you can take to resolve each code. The return code number is displayed in the IBM Tivoli Monitoring Web Health Console status field, or by using the wdmlsengcommand.
CLI example
wdmeditprf -P $Prof1 -edit Microsoft_SQL_Server_Replication_Jobs \ -AddPar Replication_Job_Names "Agent history clean up: distribution" \ -AddPar Replication_Job_Names "Distribution clean up: distribution" \ -AddPar Replication_Job_Names "Reinitialize subscriptions having
data validation failures" \
-AddPar Replication_Job_Names "Replication agents checkup" \ -e Microsoft_SQL_Server_WaitingForThread_Replication_Job \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -"$MyTec" \ -e Microsoft_SQL_Server_Idle_Replication_Job \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -"$MyTec" \ -e Microsoft_SQL_Server_Failed_Replication_Job \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -"$MyTec" \ -e Microsoft_SQL_Server_Cancelled_Replication_Job \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -"$MyTec" \ -e Microsoft_SQL_Server_Suspended_Replication_Job \