<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">You could try attaching a debugger to the DBMS server and setting a break point in dmxe_abort.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">You won’t have a debug process but this will tell you if you are hitting an abort during the first insert/update and you<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">could obtain the stack at that point even if you end up needing to the resolve the function names<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">from nm output.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Running out of ideas about how you can get closer to the problem without logging an issue and supplying a test case.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Alex<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> info-ingres-bounces@lists.planetingres.org <info-ingres-bounces@lists.planetingres.org>
<b>On Behalf Of </b>Mark<br>
<b>Sent:</b> 17 May 2018 12:12<br>
<b>To:</b> info-ingres@lists.planetingres.org<br>
<b>Subject:</b> Re: [Info-ingres] Weird problem in Ingres 10<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On Wed, 16 May 2018 12:40:48 -0400, Karl and Betty Schendel<br>
<<a href="mailto:schendel@kbcomputer.com">schendel@kbcomputer.com</a>> wrote:<br>
<br>
>SC930 tracing is server wide and runs until you stop it with set notrace sc930.<br>
>So you can connect to any database, do the set trace record '/some/ingres-writable/dir'<br>
>and the set trace point sc930, go to the trace record directory you gave it and<br>
>ensure that there's at least something there (should be one or more sessNNNNN files),<br>
>and then you can run your esql program until the fault happens.<br>
><br>
>You don't actually need to put the sc930 into the esql program unless you want to<br>
>do it that way.<br>
><br>
>Once you capture what you need to capture, set notrace point sc930 turns it off.<br>
><br>
>You'll need the trace point privilege, simplest is to do it as the installation owner<br>
>(user ingres, traditionally).<br>
<br>
Thanks again. We now have traces but they don't help me. The traces<br>
include the SQL statement and the data but, pretty much, nothing else.<br>
<br>
The only notable thing I observed is that the data is traced twice for<br>
the failed transaction and only once for the successful ones.<br>
<br>
There are no error messages.<br>
<br>
>Karl<br>
><br>
>> On May 16, 2018, at 11:12 AM, Mark <<a href="mailto:i@dontgetlotsofspamanymore.net">i@dontgetlotsofspamanymore.net</a>> wrote:<br>
>> <br>
>> On Wed, 16 May 2018 12:11:08 +0000, Martin Bowes<br>
>> <<a href="mailto:martin.bowes@ndph.ox.ac.uk">martin.bowes@ndph.ox.ac.uk</a>> wrote:<br>
>> <br>
>>> Just to expand on Karl's sc930...You may already know this...<br>
>>> <br>
>>> To turn it on, make a recording directory...mkdir /full/path/to/directory'<br>
>>> <br>
>>> And then...<br>
>>> sql iidbdb << SQL_END<br>
>>> set trace record '/full/path/to/directory';<br>
>>> set trace point sc930 1;<br>
>>> \p\g<br>
>>> \q<br>
>>> SQL_END<br>
>> <br>
>> Do I need to run this on the server account? I have implemented it<br>
>> currently in the embedded SQL of my program.<br>
>> <br>
>>> FYI. The digit after the sc930 indicates a tracing level, 1 should be sufficient.<br>
>>> <br>
>>> Run the errant query.<br>
>>> <br>
>>> And turn off the sc930.<br>
>>> sql iidbdb << SQL_END<br>
>>> set trace point sc930 0;<br>
>>> \p\g<br>
>>> \q<br>
>>> SQL_END<br>
>>> <br>
>>> You can now access the recording directory and start scanning the files for any sign of life from your query.<br>
>>> <br>
>>> Marty<br>
>>> <br>
>>> -----Original Message-----<br>
>>> From: Karl and Betty Schendel [<a href="mailto:schendel@kbcomputer.com">mailto:schendel@kbcomputer.com</a>]
<br>
>>> Sent: 16 May 2018 12:54<br>
>>> To: Ingres and related product discussion forum<br>
>>> Subject: Re: [Info-ingres] Weird problem in Ingres 10<br>
>>> <br>
>>> On May 16, 2018, at 7:44 AM, Mark <<a href="mailto:i@dontgetlotsofspamanymore.net">i@dontgetlotsofspamanymore.net</a>> wrote:<br>
>>>> <br>
>>>> On Tue, 15 May 2018 12:27:09 -0400, Karl and Betty Schendel<br>
>>>> <<a href="mailto:schendel@kbcomputer.com">schendel@kbcomputer.com</a>> wrote:<br>
>>>> <br>
>>>>> It's certainly not something I have heard of or seen before. Do you have any rules<br>
>>>>> defined on the relevant tables? Try enabling LOG_TRACE if the problem is<br>
>>>>> sufficiently predictable, or do a logdump after the problem occurs if it's not;<br>
>>>>> the idea being to try to see whether you actually got any PUT (insert) or<br>
>>>>> REP (replace) log records that were then rolled back, or whether the insert / update<br>
>>>>> was never executed at all.<br>
>>>> <br>
>>>> After enabling log_trace all I got was:<br>
>>>> <br>
>>>> LOG: SAVEPOINT Size written/reserved: 0/ 0 Flags:<br>
>>>> -------------------------------------------------------------------<br>
>>> <br>
>>> So the insert/update isn't ever being executed. Either it's failing with some sort of<br>
>>> silent error, which would seem odd, or it's not reaching the backend at all, or<br>
>>> it's being pre-empted by a before rule. I think the next step would be to enable<br>
>>> sc930 tracing and see if the backend is getting the insert-update, and what<br>
>>> end-of-query status it's recording. There should be KB articles on enabling<br>
>>> SC930 tracing.<br>
>>> <br>
>>> Karl<br>
>>> <br>
>>> _______________________________________________<br>
>>> Info-ingres mailing list<br>
>>> <a href="mailto:Info-ingres@lists.planetingres.org">Info-ingres@lists.planetingres.org</a><br>
>>> <a href="http://lists.planetingres.org/mailman/listinfo/info-ingres">
http://lists.planetingres.org/mailman/listinfo/info-ingres</a><br>
>> <br>
>> -- <br>
>> <insert witty sig here><br>
>> _______________________________________________<br>
>> Info-ingres mailing list<br>
>> <a href="mailto:Info-ingres@lists.planetingres.org">Info-ingres@lists.planetingres.org</a><br>
>> <a href="http://lists.planetingres.org/mailman/listinfo/info-ingres">
http://lists.planetingres.org/mailman/listinfo/info-ingres</a><br>
<br>
-- <br>
<insert witty sig here><br>
_______________________________________________<br>
Info-ingres mailing list<br>
<a href="mailto:Info-ingres@lists.planetingres.org">Info-ingres@lists.planetingres.org</a><br>
<a href="http://lists.planetingres.org/mailman/listinfo/info-ingres">http://lists.planetingres.org/mailman/listinfo/info-ingres</a><o:p></o:p></p>
</div>
</body>
</html>