Re: (no subject)

From: Jared Still <jkstill_at_cybcon.com>
Date: Wed, 02 Jun 2004 06:43:57 -0700
Message-Id: <1086183837.15792.513.camel@poirot>

On Wed, 2004-06-02 at 01:26, Computer Centre - NIIPL wrote:
> Dear All,
>
> We are getting the following error during database export.
>
> ORA-1555 :- snapshot too old.
>
> How to assign a big RBS to the export session.
>

There are methods to deal with this.

If you are using a third party app, and downtime is not available, fixing the app, as has been suggested already, may not be possible.

One method is to create new rollback segments with a very large tablespace, larger than you expect to need during the duration of the export.

Assign a transaction to each rollback segment, and do not commit it. This will force the rollback segs to extend rather than wrap.

When done, drop the temp RBS, bring the old ones back online, drop the temp RBS tablespace and data files.

This has worked very well for me in the past with very long running SAP jobs ( couldn't fix the source code ).

Details may be found at ixora.com.au ( of course )

Jared

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Wed Jun 02 2004 - 08:31:25 CDT