| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: (no subject)
My hunch is that the export is not causing the error. Rather, other
transactions are changing the data, and when the export process tries to
reconstruct the state of the data when the export started, the old data
is no longer available in the rollback segments. Assuming this is the
case, assigning the export process to a larger rollback segment will
have no effect.
If you were on 9i, you could use automatic undo management to greatly simplify the problem. If you are stuck with manual undo management via rollback segments, you will have to figure out why the rollback information isn't available when your query needs it. It may be that you have very small rollback segments that wrap too frequently, so increasing the size of the rollback segments will help. It may be that you need to increase the optimal size of your rollback segments. It may be that you need more rollback segments. So many possibilities :-(
If possible, can you run export when the database is less busy? Are you specifying that the export should be consistent on the command line? Do you actually need a consistent export?
Justin Cave
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Computer Centre -
NIIPL
Sent: Wednesday, June 02, 2004 2:27 AM
To: ORALCE LIST
Subject: (no subject)
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.
Thanks in Advance,
Balu,
Oracle DBA
This mail is scaned by eScan Anti Virus Software
 |
 |