Thanks for your suggestions. The log files of my application just stop when the fetchall_arrayref call is made. I'll look into how to find the DBI and dbms logs.

What does work? Perhaps a matrix will be more clear:

Machine #1 ( used for initial testing ) |-----------------------------|------------ +---------------|------------------------------| | no placeholders no results | placeholder +s with results | placeholders with no results | |-----------------------------|------------ +---------------|------------------------------| not specifying a TDS level | empty array | array of re +sult hashes | empty array | |-----------------------------|------------ +---------------|------------------------------| specifying a TDS level | empty array | array of re +sult hashes | (application hangs) | |-----------------------------|------------ +---------------|------------------------------| Machine #2 ( used for "Steps to reproduce on Ubuntu 20.04" in original + post ) |-----------------------------|------------ +---------------|------------------------------| | no placeholders no results | placeholder +s with results | placeholders with no results | |-----------------------------|------------ +---------------|------------------------------| not specifying a TDS level | (connection fails) | (connection + fails) | (connection fails) | |-----------------------------|------------ +---------------|------------------------------| specifying a TDS level | empty array | array of re +sult hashes | (application hangs) | |-----------------------------|------------ +---------------|------------------------------|
For some reason the test program in my original post doesn't connect at all on machine #2 when no TDS level is specified. This is the error message, but I believe this is not related to my problem. (Or perhaps to state it more accurately, it's not the problem I'm trying to solve)
DBI connect('server=172.28.79.294','machinename',...) failed: OpenClie +nt message: LAYER = (0) ORIGIN = (0) SEVERITY = (78) NUMBER = (49) Server 172.28.79.294, database Message String: Unexpected EOF from the server OpenClient message: LAYER = (0) ORIGIN = (0) SEVERITY = (78) NUMBER = +(34) Server 172.28.79.294, database Message String: Adaptive Server connection failed OpenClient message: LAYER = (0) ORIGIN = (0) SEVERITY = (78) NUMBER = +(34) Server 172.28.79.294, database Message String: Adaptive Server connection failed at go.pl line 14. Died at go.pl line 14.
My original code that produced this error had SQL queries included tables. My test code for reproducing the problem wouldn't produce the same results if you didn't have the same tables with the same columns, so I simplified them for testing.

In reply to Re^2: fetchall_arrayref hangs with placeholders query with no results by TieUpYourCamel
in thread fetchall_arrayref hangs with placeholders query with no results by TieUpYourCamel

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.