Very Useful Command to perform Health check of SAP Sybase ASE Replication Server

Very Useful Command to perform Health check of SAP Sybase ASE Replication Server

We will cover few basic commands today which is a must to have for DBA who is supporting SAP Sybase ASE Replication Server and is responsible to keep the replication in a healthy state. Please note that these commands could be stored as a sql query file and can be invoked using a shell script, same can be scheduled through a cron job scheduler. Output of these files could be stored in an out or txt file and should be reviewed periodically to understand the overall health of replication server.

List of commands are as follows:

admin health
go

This command would help in understanding the health of replication server in nutshell, output will have four columns as:

Mode Quiesce Status Loss Status

You can refer each column and what should be the value for each of them for a healthy replication server. Sample output for healthy replication server is as below:

NORMAL FALSE HEALTHY NO LOSS

The output in the Status should be nothing but Healthy, if it is something else then you need to run few more diagnostic command to see underlying issue.

Second command in the list will be:

admin who
go

This command is kind of master command and will list all the logical connection and their state. Below is the column list which will be output of this command:

Spid Name State Info

Third command in the list will be to check details about SQM(Stable Queue Manager) threads:

admin who, sqm
go

The output will have different segments to go through however state column will be mostly populated with “Awaiting Message”.

Next command in the list will be to check status of SQT(Stable queue transaction interface) threads:

admin who, sqt
go

The output will again have different segments to go through and state column should be mostly populated with “Awaiting Wakeup” or “Awaiting Message”.

Next command in the list is to check status about each DSI(Data Server Interface) scheduler at replication server:

admin who, dsi
go

The output will again have different segments to go through and state column should be mostly populated with “Awaiting Message”.

Having above command will help DBA to understand overall state of replication server at any given point of time. Below are list of these commands at one place:

admin health
go
admin who
go
admin who, sqm
go
admin who, sqt
go
admin who, dsi
go

I have covered in one of the earlier post on how to check the memory usage and other details of memory at replication server Replication Server failed with fatal error while allocating memory. Most likely, there is not enough memory. Replication Server is going to abort.

Please leave your comment if you liked this post or helped you.

Leave a Comment

Your email address will not be published.