Re: Limit on row inserts when using TRANSACTION_SERIALIZABLE?

Well let me clarify the problem:

1. set isolation_level = serializable
2. insert several thousand rows into table 1 without a commit
3. insert into table 2 'select rows from table 1' without a commit, which uses selects from table1

Then the problem appears at step 3 (I never get through to the commit).

Could a part of the problem be that the Oracle transaction log run full?
Anyway in such a case then I would expect a SQLException.

I've tried to use the same code on DB/2 and here everything worked fine.

The only way I can get this to work on Oracle is by using TRANSACTION_READ_COMMITTED Best regards
Thomas

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<996933185.23215.0.nnrp-10.9e984b29_at_news.demon.co.uk>...
> Can I clarify this:
>
> you set isolation_level = serializable
> you insert several thousand rows into table 1 without a commit
> you insert into table 2 'select rows from table 1' without a commit.
> you commit.
>
> You find that rows that SHOULD have been inserted into table2
> have not been inserted.
>
> Are these rows that you inserted into table 1 in the previous step,
> or are they rows that pre-existed in table 1 before you did the
> 'set isolation_level = serializable' ?
>
> When you insert rows into table 1 is it an array insert, or
> a series of single row inserts, or an 'insert select ...' ?
>
>
> --
> Jonathan Lewis
>
> Host to The Co-operative Oracle Users' FAQ
> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
>
> Author of:
> Practical Oracle 8i: Building Efficient Databases
> See http://www.jlcomp.demon.co.uk/book_rev.html
>
> Seminars on getting the best out of Oracle
> See http://www.jlcomp.demon.co.uk/seminar.html
>
> Screensaver or Lifesaver: http://www.ud.com
> Use spare CPU to assist in cancer research.
>
>
>
>
Received on Tue Aug 21 2001 - 14:55:36 CDT