<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic oopss..look here Oracle Error with C program in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476394#M776286</link>
    <description>Sorry, hit enter too soon..&lt;BR /&gt;&lt;BR /&gt;Got this error on a job that's been running with NO problems for the last 3 years !!!  It is coded in C (which nobody still here knows...)&lt;BR /&gt;&lt;BR /&gt;"Oracle 01458 - Oracle invalid length inside variable character string"&lt;BR /&gt;&lt;BR /&gt;Has anyone seen this????&lt;BR /&gt;&lt;BR /&gt;I can tell you the job does a qsort (which is not a reliable sort...), and that it blows off at different points, but nothing constant other than this error.  The DBA's and the Programmers are about to the end of the line....&lt;BR /&gt;Everything I've checked is fine....no new patches have been added that might have affected it (libc).  I am running out of things to try...&lt;BR /&gt;&lt;BR /&gt;Will this week ever end???ha ha ha</description>
    <pubDate>Fri, 22 Dec 2000 20:55:22 GMT</pubDate>
    <dc:creator>Rita C Workman</dc:creator>
    <dc:date>2000-12-22T20:55:22Z</dc:date>
    <item>
      <title>oopss..look here Oracle Error with C program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476394#M776286</link>
      <description>Sorry, hit enter too soon..&lt;BR /&gt;&lt;BR /&gt;Got this error on a job that's been running with NO problems for the last 3 years !!!  It is coded in C (which nobody still here knows...)&lt;BR /&gt;&lt;BR /&gt;"Oracle 01458 - Oracle invalid length inside variable character string"&lt;BR /&gt;&lt;BR /&gt;Has anyone seen this????&lt;BR /&gt;&lt;BR /&gt;I can tell you the job does a qsort (which is not a reliable sort...), and that it blows off at different points, but nothing constant other than this error.  The DBA's and the Programmers are about to the end of the line....&lt;BR /&gt;Everything I've checked is fine....no new patches have been added that might have affected it (libc).  I am running out of things to try...&lt;BR /&gt;&lt;BR /&gt;Will this week ever end???ha ha ha</description>
      <pubDate>Fri, 22 Dec 2000 20:55:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476394#M776286</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2000-12-22T20:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: oopss..look here Oracle Error with C program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476395#M776287</link>
      <description>Hi Rita,&lt;BR /&gt;&lt;BR /&gt;When you try to use a char[] variable in a C program, yo have to make sure of the following:&lt;BR /&gt;1. your variable has been given a size like in:&lt;BR /&gt;char my_string[64];&lt;BR /&gt;or by using malloc() if your variable has been defined as a pointer.&lt;BR /&gt;2. you're NOT trying to store more data that your variable can actually contain.&lt;BR /&gt;&lt;BR /&gt;If you're trying to store more than 64 chars in the string my_string defined here above, you'll have a "segmentation violation" error if the surrounding code doesn't check it before.&lt;BR /&gt;&lt;BR /&gt;The same could happen if you're addressing the (n + x)th element of an array defined with size n.&lt;BR /&gt;&lt;BR /&gt;The error message could be that the surrounding oracle code is checking the size of the data BEFORE storing it in a variable, which is good practice. &lt;BR /&gt;&lt;BR /&gt;As data contained in a database is by definition extremely variable, it is well possible that on of the latest records exceeds the hard coded limits. Maybe you simply never reached that limit before.&lt;BR /&gt;&lt;BR /&gt;Try investigating which part of the code, putting some milestones like 'printf("my string is %s\n",my_string);'&lt;BR /&gt;This would allow you to know where the problem appears.&lt;BR /&gt;If you don't feel confident in doing this, don't hesitate to attach your code so that I could quickly check it if it's not too long. I used to be quite 'fluent' in C although "time flies"... ;-)&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Dan&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 23 Dec 2000 08:49:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476395#M776287</guid>
      <dc:creator>Dan Hetzel</dc:creator>
      <dc:date>2000-12-23T08:49:18Z</dc:date>
    </item>
    <item>
      <title>Re: oopss..look here Oracle Error with C program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476396#M776288</link>
      <description>I supose your C code is a PRO*C:&lt;BR /&gt;&lt;BR /&gt;Strings are defined as structure with&lt;BR /&gt;&lt;BR /&gt;an array variable and a length variable.&lt;BR /&gt;&lt;BR /&gt;sprintf(grant.arr,"GRANT CONNECT , DBA TO %s IDENTIFIED BY %s ",logint,logint);                                      &lt;BR /&gt;grant.len=strlen(grant.arr);  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Your variable.len must be invalid.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Dec 2000 09:26:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476396#M776288</guid>
      <dc:creator>Carlos Fernandez Riera</dc:creator>
      <dc:date>2000-12-26T09:26:28Z</dc:date>
    </item>
    <item>
      <title>Re: oopss..look here Oracle Error with C program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476397#M776289</link>
      <description>Rita &lt;BR /&gt;&lt;BR /&gt;see if this helps &lt;BR /&gt;&lt;BR /&gt;ORA-01458: invalid length inside variable character string &lt;BR /&gt;&lt;BR /&gt;Cause: An attempt was made to bind or define a variable character string with a buffer length less than the two-byte&lt;BR /&gt;minimum requirement. &lt;BR /&gt;&lt;BR /&gt;Action: Increase the buffer size or use a different type. &lt;BR /&gt;&lt;BR /&gt;obtained from &lt;A href="http://www.cs.umbc.edu/help/oracle8/errmsg/A54625_01/newch2d.htm" target="_blank"&gt;http://www.cs.umbc.edu/help/oracle8/errmsg/A54625_01/newch2d.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps &lt;BR /&gt;&lt;BR /&gt;Jon</description>
      <pubDate>Tue, 26 Dec 2000 13:10:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476397#M776289</guid>
      <dc:creator>jherring</dc:creator>
      <dc:date>2000-12-26T13:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: oopss..look here Oracle Error with C program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476398#M776290</link>
      <description>Thank you very much Dan, Carlos &amp;amp; Jon.&lt;BR /&gt;&lt;BR /&gt;It seems the problem was with the data (array) being corrupted by something introduced that was 'too small'.  &lt;BR /&gt; A special thank you to Jon for the additional Oracle site info.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Rita</description>
      <pubDate>Tue, 26 Dec 2000 13:28:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oopss-look-here-oracle-error-with-c-program/m-p/2476398#M776290</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2000-12-26T13:28:07Z</dc:date>
    </item>
  </channel>
</rss>

