Re: Oracle Reports Error
Date: 1996/08/12
Message-ID: <320F48CA.3B61_at_pop.erols.com>#1/1
Richard Foster wrote:
>
> Okay Oracle gurus, show me your knowledge.
>
> Potentially pertinent information:
> Server: Oracle 7.1.4
> Solaris 2.4
> Oracle Reports 2.0 (moving to 2.5)
>
> Error Encountered: ORA-01555 Snapshot too old(rollback segment too small)
>
> I am running a sequence of reports from a C-Shell script using the R20RUN
> Responses to e-mail please.
>
> Rich Foster
> rafoster_at_ix.netcom.com
> --
> Richard Foster |But whoso committeth adultery with a woman
> Ft Meade, MD |lacketh understanding: he that doeth it
> rafoster_at_ix.netcom.com |destroyeth his own soul. Prov 6:32
I have seen this many times. I believe that the information you were
given is left over from V6.
Use one Rollback tablespace or several
Create rollback segments such that they all could potentially grow huge via optimal.
If DB block size =2048 maxextents=121
if higher - max extents are higher.
use (initial 1M next 1M pctincrease 0 maxextents 255 optimal 2M)
then again, the problem could be the other reference - snapshot too old.
Oracle is also using the rollback segment to maintain a read consistent veiw of the data you are reporting on. It may be the case that Oracle can not keep up with the occuring transactions and the report - just too much rollback generated by the table changeing to handle. -
Solution - run report at a slower business time. -- In other words - batch & Transactions never mix well on any platform or DB.
-- ______________________________________________________________________ Michael J. Hillanbrand II Dulcian, Inc. Oracle Data Base Administration Voice: 215-773-7307 Fax: 610-277-2966 mjhii_at_pop.erols.com mjh_at_salts.icpphil.navy.mil Delaware Valley Oracle Users Group, Inc. Contact me for Newsletter ads, articles, book reviews & Website Info.Received on Mon Aug 12 1996 - 00:00:00 CEST