Hi All,

In our production support environment we need do the health check on our data server on time to time basis, such as after the any long activity, in the production monitoring, after the server restart, and there are lot of many more cases.

I know everyone having their own scripts for their environment , now can we combine all of our ideas and make one final scripts?

For that I need your inputs, what should we have in our script for the data server health check/QA!


After the final input consolidation, we will create one final script which either to be in shell or perl.


Guys, share your inputs/thoughts/suggestions.....!

Thanks.

AnVa,

Nice Idea.Appreciate it.
Below are my inputs w.r.t sybase dataserver monitoring.

Check 1 . Monitor Dataserver and backup server status : Running/Stopped/Hung
Check 2 . Monitor sybase error log every n minutes ('n' min based on the criticality QA/Prod) for configurable error messages like tempdb full, out of locks, infected with 11 , increase the number of index descriptors, user connections ..etc and email the alert to concerned parties.

• The script should be able to support Monitoring of Dataservers and error log files on remote machines as well.
• dataservers and error log files should be configurable (conf file can be maintained).
• Error messages to be monitored should also be configurable.

Would add if any more comes to my mind !

I believe it will defintely be useful for all the Sybase ASE DBAs.
I also think we should make one for Replication server also.

Thanks,
Joshi

Pratap J,

Thanks for your inputs. I am sure, there would be many more from your side !

After the ASE, we will surely move for the replication server.

Cheers!!

Guys,

Nice to see you coming up with consolidated Sybase ASE monitoring system.Thanks for that.
I would suggest we go through the below sybase article first and then proceed further.

Best Practice
Subject: Sybase ASE Monitoring
Author(s): Tom Oorebeek, Staff DBA, Sybase IT
Reviewer(s): Hema Seshadri, Sr. DBA Manager, Sybase IT
Abstract:

In today's information driven world, high availability and optimal performance of database infrastructure is more important than ever. Many business aspects rely on being able to retrieve real-time data from their databases. Monitoring this critical infrastructure ensures maximum uptime. Monitoring is important not just from an overall availability and performance perspective, but also from the perspective of the end-user such that business productivity is not compromised. This document discusses some of the best practice ideas on what aspects of a production ASE environment should be monitored.

Introduction.

1 Best Practices: ASE Monitoring.
1.1 ASE versions.
1.2 Operating systems.
1.3 Tools.
1.4 Monitoring aspects.
1.5 What next ?
2 What to monitor ?
2.1 The ASE itself
2.2 Licenses
2.3 Database Availability.
2.4 Data Storage.
2.5 Disk Space.
2.6 Database & Transaction Log dumps.
2.7 User Activity
2.8 Error Logs
2.9 Blocking
2.10 Data Consistency

Appendix A
Template error checking script
Filename: STARTSERVER
Filename: admindump
Filename: cnt_sessions
Filename: dba.pl
Filename: db_spy
Filename: hostname.fs_spaceused.ini
Filename: fs_spaceused
Filename: logscan.ini
Filename: logscan
Filename: object_addition
Filename: run_sysmon
Filename: sp_block.sql
Filename: sp_echotime.sql
Filename: sp_devusage.sql
Filename: sp_hogs.sql
Filename: sp_lockname.sql
Filename: sp_w.sql

Introduction

* - This Best Practices document is to help a Sybase DBA understand the various aspects of ASE monitoring and provide a quick start for setting up such monitoring.

-------------------------------------------------------------
Read the complete article by visiting the below URL.

http://www.sybase.com/detail?id=1063658

Thanks,
Kishor

Hi,

Thanks Kishor for your posting!

I would like to clear, one thing about the topic, we are getting two thoughts one for general purpose monitoring and one for health check of data server, as below:

1. Real time monitoring which we generally schedule in our crontab for database monitoring, such as log suspend, blocking, errorlog monitoring, log space monitoring etc.

The above white paper is referring the same.

2. Second one, which I am referring here is the script which we require for the dataserver/databases health check.

Suppose , we have done with one activity and restarted our db server, and after tht we need to check the health of our dataserver and dbs.

We generally login in the database, perform some checks and as per output , confirm for the dataserver health.

In our prod support enviorment, we regularly perform this task, for lot of activities.




I am looking for your input for the second point now, wht we need to check for the dataserver health,

Guys, Come up with your inputs and justification so everyone know abt the importance of your point?

What do you feel to check so that every thing is normal in the database?

For real time monitoring, will consider later.

If you have any questions and suggestions let me know . Thanks.

Guys!

Only two people replied till now. I am looking for more active participation from your side!!


Thanks.