Here is the client's stack trace. I have none on the server.
org.apache.derby.client.am.SqlException: Run out of sections to use,sections
limited to 32k currently
at org.apache.derby.client.am.SectionManager.getSection(Unknown Source)
at org.apache.derby.client.am.SectionManager.getDynamicSection(Unknown
Source)
at org.apache.derby.client.am.Statement.flowExecute(Unknown Source)
at org.apache.derby.client.am.Statement.executeUpdateX(Unknown Source)
at org.apache.derby.client.am.Statement.executeUpdate(Unknown Source)
The exception occurs after the insert of ~1600 rows in table a and ~23000
rows in table b. Each row in table a leads an insert of ~15 rows in table b.
After 100 rows in table a and therefore ~1500 rows in table b I call
Connection.commit(). I can query the db after the exception occured and it
seems that all the commited entries are ok.
I can compile the derby sources to get a stack trace with line numbers it it
would help.
Thanks,
Harrus
> --- Ursprüngliche Nachricht ---
> Von: [EMAIL PROTECTED]
> An: Derby Discussion <[email protected]>
> Betreff: Re: SqlException: Run out of sections to use
> Datum: Sat, 12 Nov 2005 19:53:23 +0100
>
> [EMAIL PROTECTED] writes:
>
> > Hallo,
> >
> > I'm new to Derby and try to port a java app from MySQL to Derby. When I
> try
> > to insert several 1000 rows I get the following SqlException:
> > Run out of sections to use,sections limited to 32k currently
>
> How many is "several"?
> >
> > After every 100 inserts I perform a commit.
>
> Hmm, that should not be a problem... how large is each row?
>
> > I found no hint in the documentation about his problem and also google
> > didn't help.
>
> > Derby runs as server with default settings and the client connects via
> > derbyclient.jar.
>
> Could you possibly post a complete stack trace? Preferably from
> derby.log if it happens on the server...
>
> --
> dt
>
>
--
Telefonieren Sie schon oder sparen Sie noch?
NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
