Message-Id: <25988.338920@fatcity.com> From: "Dawtrey, Lindsay L" Date: Tue, 22 Jul 2003 19:12:21 +0200 Subject: RE: Please help with ORA-01555 Snapshot too old This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C35074.69AD2850 Content-Type: text/plain; charset="iso-8859-1" You can try committing less frequently in the batch load e.g. if you are committing every 10000 rows then try every 30000 (assuming of course that the you have space left in the RBS to allow for this) or you can try adding rollback segments. Metalink docs give some good ideas as to the real causes of this error. The error message text itself is sometimes misleading. Cheers Lindsay -----Original Message----- From: Smith, Ron L. [mailto:rlsmith@kmg.com] Sent: Tuesday, July 22, 2003 5:04 PM To: Multiple recipients of list ORACLE-L Subject: Please help with ORA-01555 Snapshot too old Help! I have a production and a test database, both with 3000mg RBS tablespaces with two datafiles. Both have db_block_buffers set at 1000. The only difference is the production db has 7 rollback segments and the test db has 8. The rollback segments are sized at 50mg each on both databases. The problem is, at night when the batch load is running (by itself), the load fails with a ORA-01555. The data is the same on both loads. Nothing else is going on in the database during the load. Any ideas? Ron __________________________________________________________________________________________________________________________________ For information about the Standard Bank group visit our web site __________________________________________________________________________________________________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. ___________________________________________________________________________________________________________________________________ ------_=_NextPart_001_01C35074.69AD2850 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message =
You=20 can try committing less frequently in the batch load e.g. if you are comm= itting=20 every 10000 rows then try every 30000 (assuming of course that the you ha= ve=20 space left in the RBS to allow for this) or you can try adding rollback=20 segments.
Metalink docs give some good ideas as to the real causes of= =20this=20 error. The error message text itself is sometimes=20 misleading.
Cheers
Lindsay 
=20
-----Original Message-----
From: Smith, Ron L.=20 =20 [mailto:rlsmith@kmg.com]
Sent: Tuesday, July 22, 2003 5:04 = =20 PM
To: Multiple recipients of list ORACLE-L
Subject:<= /B>=20 =20 Please help with ORA-01555 Snapshot too old

=20
Help!
=20
 
=20
I=20 =20 have a production and a test database, both with 3000mg RBS tablespac= es with=20 =20 two datafiles.  Both have db_block_buffers set at 1000.  Th= e only=20 =20 difference is the production db has 7 rollback segments and the&= nbsp;test=20 =20 db has 8.  The rollback segments are sized at 50mg each on both = =20 databases.
=20
 
=20
The=20 =20 problem is, at night when the batch load is running (by itself), the = load=20 =20 fails with a ORA-01555.  The data is the same on both loads.&nbs= p;=20 =20 Nothing else is going on in the database during the load.
=20
 
=20
Any=20 =20 ideas?
=20
 
=20
Ron
=20
=20
=20
= <= ![if !supportEmptyParas]><= /FONT>&nb= sp;
_________________________________________________________= _________________________________________________________________________=
For information about the Standard Bank group visit our web site <= ;www.standardbank.co.za>
= _________________________________________________________= _________________________________________________________________________=
 
Disclaimer=20 and confidentiality note
Everything in this e-mail and any attachment= s=20 relating to the official business of Standard Bank Group Limited  is= =20 proprietary to the group.
It is confidential, legally privileged and = protected by law.
Standard Bank does not own and endorse any other co= ntent.=20 Views and opinions are those of the sender unless clearly stated as being= =20that=20 of the group.
The person addressed in the e-mail is the sole authoris= ed=20 recipient. Please notify the sender immediately if it has unintentionally= =20 reached you and do not read,
disclose or use the content in any=20 way.
Standard Bank can not assure that the integrity of this communica= tion=20 has been maintained nor that it is free of errors, virus, interception or= =20 interference.