dbaspot
Tags Register FAQ Calendar Search Today's Posts Mark Forums Read

problem with sqlora32.dll - Gupta Database

This is a discussion on problem with sqlora32.dll - Gupta Database ; Hi everybody, we are using DTD 2005 with Oracle Database 10g and have the problem that SQL-statements that are longer than about 30,000 bytes crash our system. We generate these SQL statements automatically so it is not possible to make ...


Home > Database Forum > Other Databases > Gupta Database > problem with sqlora32.dll

Reply

 

LinkBack Thread Tools Display Modes
  #1  
Old 11-22-2007, 11:09 AM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default problem with sqlora32.dll

Hi everybody,
we are using DTD 2005 with Oracle Database 10g and have the problem
that SQL-statements that are longer than about 30,000 bytes crash our
system.
We generate these SQL statements automatically so it is not possible
to make them smaller.
Does anyone have ever seen this problem?
Does anybody have a solution for this?

legolas13
Reply With Quote
  #2  
Old 11-23-2007, 07:05 PM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: problem with sqlora32.dll

On Nov 22, 7:09 am, "goo...@heinemann-wetter.de" wetter.de> wrote:
> Hi everybody,
> we are using DTD 2005 with Oracle Database 10g and have the problem
> that SQL-statements that are longer than about 30,000 bytes crash our
> system.
> We generate these SQL statements automatically so it is not possible
> to make them smaller.
> Does anyone have ever seen this problem?
> Does anybody have a solution for this?
>
> legolas13


You might try increasing the output message buffer (set in SQL.INI;
see the docs for exact wording of this parm. and Unify's Connectivity
PDF for specifics for Oracle) to be sure it is a value > 30K (like 64K
or 128K). As I recall, 'out' is where any statement from the front-end
is buffered before going to the back-end. This *may* be the problem,
though I've never heard of this issue before.

If that doesn't work (and you can't find anything else), then I can
only suggest what you don't want to hear: you will need to rearrange
your appl. so your auto-builds are smaller, or 'filter' your output by
parsing the SQL into 2 statements with 2 Sql Handles and 2 fetches.
Without knowing your code, tough to say which is easier (or which
would be impossible).

What are you into? A single row of data to a form window? Populating a
table window? Query for a report? That may make a difference as to how
easy or difficult it would be.

Best Regards,
Jeff @ PC Design
info. & samples: www.JeffLuther.net/gupta/
Reply With Quote
Reply

Thread Tools
Display Modes



All times are GMT -4. The time now is 05:16 AM.