Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Shorten date/time info in error log

13 posts in Product Futures Discussion Last posting was on 2002-08-16 03:43:57.0Z
Carl Kayser Posted on 2002-03-10 15:07:41.0Z
From: "Carl Kayser" <kayser_c@bls.gov>
Subject: Shorten date/time info in error log
Date: Sun, 10 Mar 2002 10:07:41 -0500
Lines: 9
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <WWuSAZEyBHA.206@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: 146.142.35.25
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:703
Article PK: 94231

I really love getting a horde of numbers, of which only the last part is
usually meaningful, in the error log. It does a great job of creating
wraparound and making it harder for me to read the important stuff. Very
annoying. Now that we are well past January 1, 2000 could there be a
startup flag that allows for the shorter (i.e., pre ISO 2000?) format?


Roger Broadbent Posted on 2002-03-11 11:15:34.0Z
From: "Roger Broadbent" <RBroadbent@wilco-int.com>
References: <WWuSAZEyBHA.206@forums.sybase.com>
Subject: Re: Shorten date/time info in error log
Date: Mon, 11 Mar 2002 11:15:34 -0000
Lines: 51
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <n16b97OyBHA.206@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: wilcohost-180.wilco-int.com 212.36.174.180
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:702
Article PK: 94228

Why do you want to break your error log for y3k compatibility?

Unless you are Slave to the Evil Empire of William Gates Esq., you could use
a simple "cut" script to shorten the length of output dynamically as you
read it. E.g, rather than doing:

%less error.log

(remember, less is more)

you could do:

% cut -c 1-15,18- SYB_SMALL.log | less

This example will get rid of only the leading "20" of the date - if you are
brave, you could cut more of the leading numbers.

Of course, this is more typing; if you are allergic to typing like me, you
could create a shell file:

% cat > lesslog
#! /bin/sh


cut -c 1-15,18- $* | less
^D
% chmod +x lesslog
% lesslog error.log

If you do use Windows in any of its incarnations, I suggest you look at
using Cygwin or a similar product that will allow you to do the same hting.


--
Roger Broadbent
Technical Consultant
Wilco International Ltd

Carl Kayser <kayser_c@bls.gov> wrote in message
news:WWuSAZEyBHA.206@forums.sybase.com...
> I really love getting a horde of numbers, of which only the last part is
> usually meaningful, in the error log. It does a great job of creating
> wraparound and making it harder for me to read the important stuff. Very
> annoying. Now that we are well past January 1, 2000 could there be a
> startup flag that allows for the shorter (i.e., pre ISO 2000?) format?
>
>
>
>


Carl Kayser Posted on 2002-03-12 13:57:56.0Z
From: "Carl Kayser" <kayser_c@bls.gov>
References: <WWuSAZEyBHA.206@forums.sybase.com> <n16b97OyBHA.206@forums.sybase.com>
Subject: Re: Shorten date/time info in error log
Date: Tue, 12 Mar 2002 08:57:56 -0500
Lines: 73
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <oPFiZ7cyBHA.204@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: 146.142.35.25
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:685
Article PK: 94210

Thanks for the assist. Obviously my UNIX skills are minmal. We are NT
client based and use Chameleon. Also Hummingbird if you pay $. With FTP
TelNet I can use "cut" as you suggested and it certainly helps. The basic
problem is that Telnet truncates the right-hand margins. UGH. With
Chameleon FTP the text is in Notepad or Word. (This has advantages and
disadvantages. I don't want to get into a religious war.)

The situation is that there are standards (and options) and a product was
chosen because it was Y2K compliant. Chameleon was not a popular choice
from the people in the trenches. So if we can't "fix" the front-end I
thought that we might try to "enhance" the back-end.

I don't consider myself a "slave to Bill" but I work with what I am given.

"Roger Broadbent" <RBroadbent@wilco-int.com> wrote in message
news:n16b97OyBHA.206@forums.sybase.com...
> Why do you want to break your error log for y3k compatibility?
>
> Unless you are Slave to the Evil Empire of William Gates Esq., you could
use
> a simple "cut" script to shorten the length of output dynamically as you
> read it. E.g, rather than doing:
>
> %less error.log
>
> (remember, less is more)
>
> you could do:
>
> % cut -c 1-15,18- SYB_SMALL.log | less
>
> This example will get rid of only the leading "20" of the date - if you
are
> brave, you could cut more of the leading numbers.
>
> Of course, this is more typing; if you are allergic to typing like me, you
> could create a shell file:
>
> % cat > lesslog
> #! /bin/sh
>
>
> cut -c 1-15,18- $* | less
> ^D
> % chmod +x lesslog
> % lesslog error.log
>
> If you do use Windows in any of its incarnations, I suggest you look at
> using Cygwin or a similar product that will allow you to do the same
hting.
>
>
> --
> Roger Broadbent
> Technical Consultant
> Wilco International Ltd
>
> Carl Kayser <kayser_c@bls.gov> wrote in message
> news:WWuSAZEyBHA.206@forums.sybase.com...
> > I really love getting a horde of numbers, of which only the last part is
> > usually meaningful, in the error log. It does a great job of creating
> > wraparound and making it harder for me to read the important stuff.
Very
> > annoying. Now that we are well past January 1, 2000 could there be a
> > startup flag that allows for the shorter (i.e., pre ISO 2000?) format?
> >
> >
> >
> >
>
>


Anthony Mandic Posted on 2002-03-12 15:07:35.0Z
Message-ID: <3C8E19B7.1EA99020@start.com.au>
Date: Wed, 13 Mar 2002 01:07:35 +1000
From: Anthony Mandic <sp_am_block@start.com.au>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Shorten date/time info in error log
References: <WWuSAZEyBHA.206@forums.sybase.com> <n16b97OyBHA.206@forums.sybase.com> <oPFiZ7cyBHA.204@forums.sybase.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 36
NNTP-Posting-Host: 203.3.176.10
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:684
Article PK: 94206


Carl Kayser wrote:
>
> Thanks for the assist. Obviously my UNIX skills are minmal. We are NT
> client based and use Chameleon. Also Hummingbird if you pay $. With FTP
> TelNet I can use "cut" as you suggested and it certainly helps. The basic
> problem is that Telnet truncates the right-hand margins. UGH. With
> Chameleon FTP the text is in Notepad or Word. (This has advantages and
> disadvantages. I don't want to get into a religious war.)

Like fixed versus non-fixed fonts?

I remember having been forced to use Exceed once. The damn
tool bar kept popping up from the bottom and pushing my
xterms up. X-Win32 was better. Eventually, I scored an
old Sparc 5 with 32MB of RAM, installed Solaris 8 and
I couldn't have been happier. As an alternative, I considered
Solaris x86 but the PCs were so crappy they weren't on
the Hardware Compatibility List.

> The situation is that there are standards (and options) and a product was
> chosen because it was Y2K compliant. Chameleon was not a popular choice
> from the people in the trenches. So if we can't "fix" the front-end I
> thought that we might try to "enhance" the back-end.

You could try for a better telnet client. The MS ones are
probably the worst around.

> I don't consider myself a "slave to Bill" but I work with what I am given.

It doesn't hurt to blame your tools once in a while.

-am © 2002


Michael Peppler Posted on 2002-03-12 16:27:39.0Z
From: Michael Peppler <mpeppler@peppler.org>
Subject: Re: Shorten date/time info in error log
Date: Tue, 12 Mar 2002 08:27:39 -0800
References: <WWuSAZEyBHA.206@forums.sybase.com> <n16b97OyBHA.206@forums.sybase.com> <oPFiZ7cyBHA.204@forums.sybase.com> <3C8E19B7.1EA99020@start.com.au>
User-Agent: Pan/0.11.2 (Unix)
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Comment-To: "Anthony Mandic" <sp_am_block@start.com.au>
Message-ID: <8EqlSPeyBHA.304@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 41
NNTP-Posting-Host: gw.peppler.org 206.55.243.57
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:681
Article PK: 94209


On Tue, 12 Mar 2002 07:07:35 -0800, Anthony Mandic wrote:

> Carl Kayser wrote:
>>
>> Thanks for the assist. Obviously my UNIX skills are minmal. We are NT
>> client based and use Chameleon. Also Hummingbird if you pay $. With
>> FTP TelNet I can use "cut" as you suggested and it certainly helps. The
>> basic problem is that Telnet truncates the right-hand margins. UGH.
>> With Chameleon FTP the text is in Notepad or Word. (This has
>> advantages and disadvantages. I don't want to get into a religious
>> war.)
>
> Like fixed versus non-fixed fonts?
>
> I remember having been forced to use Exceed once. The damn tool bar
> kept popping up from the bottom and pushing my xterms up. X-Win32 was
> better. Eventually, I scored an old Sparc 5 with 32MB of RAM, installed
> Solaris 8 and I couldn't have been happier. As an alternative, I
> considered Solaris x86 but the PCs were so crappy they weren't on the
> Hardware Compatibility List.

Me I use linux as my primary OS, and I run VmWare to have a WinNT option
when I need one. While VmWare isn't exactly cheap it does remove the need
to reboot the box to get WinNT functionality, and allows easy cut/paste
between the linux and windows sessions.

VmWare can also do the reverse (i.e. use WinNT as the host OS, and run
linux [or FreeBSD, or Solaris x86] in a window as a "client" OS).

Michael
--
Michael Peppler Data Migrations, Inc.
mpeppler@peppler.org *or* mpeppler@mbay.net
http://www.mbay.net/~mpeppler
International Sybase User Group: http://www.isug.com


Anthony Mandic Posted on 2002-03-13 03:19:36.0Z
Message-ID: <3C8EC548.4F17B200@start.com.au>
Date: Wed, 13 Mar 2002 13:19:36 +1000
From: Anthony Mandic <sp_am_block@start.com.au>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Shorten date/time info in error log
References: <WWuSAZEyBHA.206@forums.sybase.com> <n16b97OyBHA.206@forums.sybase.com> <oPFiZ7cyBHA.204@forums.sybase.com> <3C8E19B7.1EA99020@start.com.au> <8EqlSPeyBHA.304@forums.sybase.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 17
NNTP-Posting-Host: DC-27-63.bpb.bigpond.com 203.40.27.63
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:680
Article PK: 94211


Michael Peppler wrote:

> Me I use linux as my primary OS, and I run VmWare to have a WinNT option
> when I need one. While VmWare isn't exactly cheap it does remove the need
> to reboot the box to get WinNT functionality, and allows easy cut/paste
> between the linux and windows sessions.

Yes, Linux is a good choice. Since Sybase support it you could
also use the Open Client libraries locally (something that Solaris
x86 no longer has).

> VmWare can also do the reverse (i.e. use WinNT as the host OS, and run
> linux [or FreeBSD, or Solaris x86] in a window as a "client" OS).

There's always more than one way, isn't there?

-am © 2002


Roger Broadbent Posted on 2002-03-12 14:59:52.0Z
From: "Roger Broadbent" <RBroadbent@wilco-int.com>
References: <WWuSAZEyBHA.206@forums.sybase.com> <n16b97OyBHA.206@forums.sybase.com> <oPFiZ7cyBHA.204@forums.sybase.com>
Subject: Re: Shorten date/time info in error log
Date: Tue, 12 Mar 2002 14:59:52 -0000
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <aUGxAedyBHA.204@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: wilcohost-180.wilco-int.com 212.36.174.180
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:683
Article PK: 94207


Carl Kayser <kayser_c@bls.gov> wrote in message
news:oPFiZ7cyBHA.204@forums.sybase.com...
> I don't consider myself a "slave to Bill" but I work with what I am given.
>

This comment was made with tongue firmly in cheek. I too have to work with
Microsoft products more often than I would like.

--
Roger Broadbent
Technical Consultant
Wilco International Ltd


Anthony Mandic Posted on 2002-03-12 14:07:22.0Z
Message-ID: <3C8E0B9A.DD4D94B6@start.com.au>
Date: Wed, 13 Mar 2002 00:07:22 +1000
From: Anthony Mandic <sp_am_block@start.com.au>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Shorten date/time info in error log
References: <WWuSAZEyBHA.206@forums.sybase.com> <n16b97OyBHA.206@forums.sybase.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 16
NNTP-Posting-Host: 203.3.176.10
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:687
Article PK: 94214


Roger Broadbent wrote:

> Unless you are Slave to the Evil Empire of William Gates Esq., you could use
> a simple "cut" script to shorten the length of output dynamically as you
> read it. E.g, rather than doing:
>
> %less error.log
>
> (remember, less is more)
>
> you could do:
>
> % cut -c 1-15,18- SYB_SMALL.log | less

You can also use the right arrow key to step to the right in
less. It doesn't work quite too well but I suspect it could
be trained. Of course, any file viewer running on X should
have a horizontal scrollbar as well a vertical one.

-am © 2002


Sethu Posted on 2002-03-12 02:33:19.0Z
Message-ID: <3C8D68EF.FB095783@sybase.com>
Date: Mon, 11 Mar 2002 18:33:19 -0800
From: Sethu <sethu@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Roger Broadbent <RBroadbent@wilco-int.com>
Subject: Re: Shorten date/time info in error log
References: <WWuSAZEyBHA.206@forums.sybase.com> <n16b97OyBHA.206@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 48
NNTP-Posting-Host: 10.22.91.118
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:697
Article PK: 94226

An alternate solution with ASE 12.5 is to create proxy table
to the errorlog file with space delimited. Then you can
take the date column and use all sql functionality to
filter your errorlog.

One can also use the ASE 12.5 jXML solution to create
transformation on this proxy errorlog table and
you can view it thro' the browser.

Sethu

Roger Broadbent wrote:
>
> Why do you want to break your error log for y3k compatibility?
>
> Unless you are Slave to the Evil Empire of William Gates Esq., you could use
> a simple "cut" script to shorten the length of output dynamically as you
> read it. E.g, rather than doing:
>
> %less error.log
>
> (remember, less is more)
>
> you could do:
>
> % cut -c 1-15,18- SYB_SMALL.log | less
>
> This example will get rid of only the leading "20" of the date - if you are
> brave, you could cut more of the leading numbers.
>
> Of course, this is more typing; if you are allergic to typing like me, you
> could create a shell file:
>
> % cat > lesslog
> #! /bin/sh
>
> cut -c 1-15,18- $* | less
> ^D
> % chmod +x lesslog
> % lesslog error.log
>
> If you do use Windows in any of its incarnations, I suggest you look at
> using Cygwin or a similar product that will allow you to do the same hting.
>
> --
> Roger Broadbent
> Technical Consultant
> Wilco International Ltd
>
> Carl Kayser <kayser_c@bls.gov> wrote in message
> news:WWuSAZEyBHA.206@forums.sybase.com...
> > I really love getting a horde of numbers, of which only the last part is
> > usually meaningful, in the error log. It does a great job of creating
> > wraparound and making it harder for me to read the important stuff. Very
> > annoying. Now that we are well past January 1, 2000 could there be a
> > startup flag that allows for the shorter (i.e., pre ISO 2000?) format?
> >
> >
> >
> >


George Saylor Posted on 2002-03-11 12:43:45.0Z
From: "George Saylor" <gmsayloriii@email.msn.com>
References: <WWuSAZEyBHA.206@forums.sybase.com>
Subject: Re: Shorten date/time info in error log
Date: Mon, 11 Mar 2002 07:43:45 -0500
Lines: 34
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <ILOxcpPyBHA.304@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: tow9dhcp209.towson01.md.comcast.net 68.33.9.209
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:701
Article PK: 94229

I like the sound of better formatting in the errorlog, reduces human error
etc...and as Carl has suggested using a startup flag, so that you don't
break anyones existing log scans.

While your in there, some sort of flag for a guaranteed tag to simplify
coding could be good, an event id tag perhaps

server event: 122232: 03/11/2002 07:30:20 begin diagnostic for read
failure....:
...lines of pain....
server event 122232

this prevents perl/sed/awk scripts that look like the typist dragged their
elbow on the top row of the keyboard, as well as simplfying getting a stack
trace into a database with minimal scrubbing.

Automatic log rotation would be nice too.

George

"Carl Kayser" <kayser_c@bls.gov> wrote in message
news:WWuSAZEyBHA.206@forums.sybase.com...
> I really love getting a horde of numbers, of which only the last part is
> usually meaningful, in the error log. It does a great job of creating
> wraparound and making it harder for me to read the important stuff. Very
> annoying. Now that we are well past January 1, 2000 could there be a
> startup flag that allows for the shorter (i.e., pre ISO 2000?) format?
>
>
>
>


David Wein Posted on 2002-03-18 19:19:39.0Z
From: "David Wein" <dwein@sybase.com>
References: <WWuSAZEyBHA.206@forums.sybase.com> <ILOxcpPyBHA.304@forums.sybase.com>
Subject: Re: Shorten date/time info in error log
Date: Mon, 18 Mar 2002 13:19:39 -0600
Lines: 60
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID: <T6iEoLrzBHA.288@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: 10.22.120.77
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:662
Article PK: 94190

Believe it or not, all that junk at the beginning of the log entries helps
us in support out. As somebody who reads a lot of errorlogs (and doesn't
have to write and manage a monitoring tool), I like it. I can look at any
line of the log and tell you:

a) which engine put it there
b) if this was caused by a worker thread
c) the spid that put it there
d) obvious date / time
e) what layer (kernel / server) it belonged to.

That being said, some form of freely available log API would nice. Using
the API, ASE would write message information out to a socket where it could
be picked up by either a local or centralized monitoring tool.

Cheers,
Dave
Sr. PSE
Sybase, Inc.

"George Saylor" <gmsayloriii@email.msn.com> wrote in message
news:ILOxcpPyBHA.304@forums.sybase.com...
> I like the sound of better formatting in the errorlog, reduces human error
> etc...and as Carl has suggested using a startup flag, so that you don't
> break anyones existing log scans.
>
> While your in there, some sort of flag for a guaranteed tag to simplify
> coding could be good, an event id tag perhaps
>
> server event: 122232: 03/11/2002 07:30:20 begin diagnostic for read
> failure....:
> ...lines of pain....
> server event 122232
>
> this prevents perl/sed/awk scripts that look like the typist dragged their
> elbow on the top row of the keyboard, as well as simplfying getting a
stack
> trace into a database with minimal scrubbing.
>
> Automatic log rotation would be nice too.
>
> George
>
>
> "Carl Kayser" <kayser_c@bls.gov> wrote in message
> news:WWuSAZEyBHA.206@forums.sybase.com...
> > I really love getting a horde of numbers, of which only the last part is
> > usually meaningful, in the error log. It does a great job of creating
> > wraparound and making it harder for me to read the important stuff.
Very
> > annoying. Now that we are well past January 1, 2000 could there be a
> > startup flag that allows for the shorter (i.e., pre ISO 2000?) format?
> >
> >
> >
> >
>
>


Anthony Mandic Posted on 2002-03-19 03:29:30.0Z
Message-ID: <3C96B09A.459F045A@start.com.au>
Date: Tue, 19 Mar 2002 13:29:30 +1000
From: Anthony Mandic <sp_am_block@start.com.au>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Shorten date/time info in error log
References: <WWuSAZEyBHA.206@forums.sybase.com> <ILOxcpPyBHA.304@forums.sybase.com> <T6iEoLrzBHA.288@forums.sybase.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 34
NNTP-Posting-Host: DC-26-102.bpb.bigpond.com 203.40.26.102
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:657
Article PK: 94183


David Wein wrote:
>
> Believe it or not, all that junk at the beginning of the log entries helps
> us in support out.

Yes, I've found it helpful for that reason too.

> As somebody who reads a lot of errorlogs (and doesn't
> have to write and manage a monitoring tool), I like it. I can look at any
> line of the log and tell you:
>
> a) which engine put it there
> b) if this was caused by a worker thread
> c) the spid that put it there
> d) obvious date / time
> e) what layer (kernel / server) it belonged to.

This should be in the docs, but perhaps you can post a quick
example to illustrate how a DBA can interpret the log entries
and thus have a better understanding of what ASE is reporting.

> That being said, some form of freely available log API would nice. Using
> the API, ASE would write message information out to a socket where it could
> be picked up by either a local or centralized monitoring tool.

See the thread on "less intrusive/high performance auditing". I
suggested writing the log to a table as well, since it naturally
lends itself to this. The columns would obviously be the above list
as well as a message string. I'm not sure about stack traces
though. Maybe a little thought is required to flesh it out
properly but I don't see any real impediments.

-am © 2002


David Wein Posted on 2002-08-16 03:43:57.0Z
Message-ID: <3D5C74FC.A9C43C2A@sybase.com>
Date: Thu, 15 Aug 2002 22:43:57 -0500
From: David Wein <dwein@sybase.com>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Shorten date/time info in error log
References: <WWuSAZEyBHA.206@forums.sybase.com> <ILOxcpPyBHA.304@forums.sybase.com> <T6iEoLrzBHA.288@forums.sybase.com> <3C96B09A.459F045A@start.com.au>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 47
NNTP-Posting-Host: 10.22.120.30
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:320
Article PK: 93492

For the record, several months later....

The System Administration guide has a very nice explanation of the error log
format. In the 12.5 docs it is in Chapter 4, "Diagnosing System Problems",
section "Adaptive Server error logging", subsection "Error log format." Pages 51
to 52 in volume 1 if you have the paper set.

-Dave

Anthony Mandic wrote:

> David Wein wrote:
> >
> > Believe it or not, all that junk at the beginning of the log entries helps
> > us in support out.
>
> Yes, I've found it helpful for that reason too.
>
> > As somebody who reads a lot of errorlogs (and doesn't
> > have to write and manage a monitoring tool), I like it. I can look at any
> > line of the log and tell you:
> >
> > a) which engine put it there
> > b) if this was caused by a worker thread
> > c) the spid that put it there
> > d) obvious date / time
> > e) what layer (kernel / server) it belonged to.
>
> This should be in the docs, but perhaps you can post a quick
> example to illustrate how a DBA can interpret the log entries
> and thus have a better understanding of what ASE is reporting.
>
> > That being said, some form of freely available log API would nice. Using
> > the API, ASE would write message information out to a socket where it could
> > be picked up by either a local or centralized monitoring tool.
>
> See the thread on "less intrusive/high performance auditing". I
> suggested writing the log to a table as well, since it naturally
> lends itself to this. The columns would obviously be the above list
> as well as a message string. I'm not sure about stack traces
> though. Maybe a little thought is required to flesh it out
> properly but I don't see any real impediments.
>
> -am © 2002