Just a warning in case theres information in this thread that you have missed- I tried this
trace point and it works ok - until certain sessions fail with a stack dump.
Repeatedly. Turning off sc930 fixed it.
Robert
-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Robert Kibble
Sent: Wednesday, 16 September 2009 11:15 p.m.
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] SC930 log file format
In tm:
set trace record '/tmp/mydirectory'\p\g
set trace point sc930 1\p\g
/tmp/mydirectory needs to exist.
You will then get trace files appearing in that directory containing information on everything coming into the dbms.
It is a recent feature, though, so 'set trace record' might not exist if you're using an old Ingres.
-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of jamesb
Sent: 16 September 2009 11:45
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] SC930 log file format
How do I get a SC930 trace log? It looks like a very useful feature!
Roy Hann wrote:
Quote:
The entries in the session log are of the form <type of
message>:<timestamp1>/<timestamp2>:<other info>, where <timestamp> is
described as being two four-byte integers containing the most accurate
time available in the environment. Here's an example fragment:
_______________________________________________
|
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://www.kettleriverconsulting.com...fo/info-ingres
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://www.kettleriverconsulting.com...fo/info-ingres
Confidentiality/Privilege Notice:
This communication is confidential and may be legally privileged. If you are not the intended recipient please delete the message and notify the sender at Ports of Auckland Limited. Any use, disclosure, copying, distribution or retention of this communication is strictly prohibited.