Hello tp all,
We want to extract rows from ASE 10.0.1 Error folg file by
As I can see in the rows in this file there is no number
that references the severity of the message.
On the other hand in the sysmessages table there is severity
attached to each and every message.
How can I see the severity of the message in the error log
file withought sql queries in the database? Is there a
stored procedure that will enable this info to be shown in
the log file?
From: Stojcevski Dejan
Subject: ASE 15 Error Log Format
X-Mailer: WebNews to Mail Gateway v1.1t
Date: 26 May 2009 03:19:20 -0700
X-Trace: forums-1-dub 1243333160 10.22.241.41 (26 May 2009 03:19:20 -0700)
X-Original-Trace: 26 May 2009 03:19:20 -0700, 10.22.241.41
Xref: forums-1-dub sybase.public.ase.general:27785
Article PK: 77039
Hello tp all,
User-Agent: Thunderbird 126.96.36.199 (Windows/20070221)
Subject: Re: ASE 15 Error Log Format
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Antivirus: avast! (VPS 090523-0, 05/23/2009), Outbound message
Date: 26 May 2009 04:46:40 -0700
X-Trace: forums-1-dub 1243338400 10.22.241.152 (26 May 2009 04:46:40 -0700)
X-Original-Trace: 26 May 2009 04:46:40 -0700, vip152.sybase.com
Xref: forums-1-dub sybase.public.ase.general:27787
Article PK: 77042
If what you're looking for is a catalog of messages and their severities you can either a) have your log monitoring
process run a query against system message tables or b) have some program/stored proc periodically dump the contents of
the system message tables to the errorlog (which would then be picked up by the log monitoring process).
If what you're looking for is a way to improve upon the information dumped to the errorlog by the dataserver ... you
can't do that.
What I've seen a lot of folks do with their log monitoring processes is define a couple files with sample text strings
from various error messages. One file might be called 'warnings.txt' while the other is called 'serious.txt'; the idea
being to use these lookup files to manage messages based on your own severity levels (eg, if an entry in the errorlog
matches an entry in the 'warnings.txt' file then send a low-priority email to the DBA group; if an entry in the errorlog
matches an entry in the 'serious.txt' file then send a high-priority email to the DBA and SA groups, and a page to the
oncall DBA pager; etc).
Obviously (?) the number of such sample text files, the name of the files, and what you do when you find matches in said
files ... is all up to you.
You may also want to do some web searches for any monitoring tools (free or co$tly) which may implement (something
similar to) what you're looking for.