Re: SQR error messages

[George Jansen <GJANSEN@AFLCIO.ORG>]

1. Max extents exceeded.  A segment--table, index, or temporary (for
sorting) segment--needed one more chunk (extent) of space, but had
already taken all the extents it was allowed to get. See your DBA. He or
she should decide how to fix this.

2. Oracle uses multi-version concurrency; while running a select, you
see the database as it existed at the beginning of the statement. Blocks
that have been since modified you get from a "rollback segment". Your
select went to the rollback segment for a piece of data and found that
it had since been overwritten by another transaction; it could not get a
consistent view of the data, and it bailed out. Again, your DBA needs to
help you with this. Either you need to larger rollback segments, or you
may need to schedule query & update work differently.


>>> arkadiy@JPS.NET 04/06/00 01:17PM >>>
Recently while executing 2 SQR programs I received 2 unrelated error
messages:
1. max extents ...
2. snapshot too old ...
unfortunately I was not able to write down the full text of the
messages. Does anyone know what they mean based on that information?
Thank you.