Prev: oracle10g SQLBEX giving 114 with Oracle Dynamic SQL Method 4 (ora9 works well)
Next: The next step to take
From: Robert on 24 Jan 2008 08:53
On Thu, 24 Jan 2008 01:00:42 -0800 (PST), bine <sabine.hubrig-schaumburg(a)sungard.de>
wrote:

>Our Application uses (in one context) Oracle Dynamic SQL Method 4
>(plus 3 and 2 as well) and that fails on AIX5.3-64bit with oracle
>10.2.0.1 or 10.2.0.3 (and MF-ServerExpress 4) whereas 9.2.0.4 (with
>ServerExpress 2.2) worked well.
>The same goes for 10.2.0.3.0 on Linux SLES9 and ServerExpress 5,
>whereas the older UnitedLinux with oracle 9.2.0.4 and ServerExpress4
>worked well.
>
>We get
>Execution error : file '/v3/v3f4/hubrig/Amain90/temp/114-TK/5-ALOEXMPL/
>metalink/10.2.0.1.0/ALOEXMPL.gnt'
>error code: 114, pc=0, call=1, seg=0
>114 Attempt to access item beyond bounds of memory (Signal 11)
>
>and after debugging (or due to the messages of DISPLAYS in that
>testexample program) are sure that it is that special SQLBEX in that
>context that fails with oracle10g.
>
>Of course I will create an SR in oracle metalink today, but if anybody
>has made some experiences in that context I'd appreciate the answers
>here as well.

SQLBEX means you are using Pro*Cobol, which is buggy and poorly supported by Oracle.
Your best solution is to abandon Pro*Cobol , switch to OpenESQL.
 | 
Pages: 1
Prev: oracle10g SQLBEX giving 114 with Oracle Dynamic SQL Method 4 (ora9 works well)
Next: The next step to take