Home » RDBMS Server » Server Administration » Re: Massive Rollback Segment
Re: Massive Rollback Segment [message #54523] Wed, 20 November 2002 10:12
tma
Messages: 5
Registered: October 2002
Junior Member
Any commit that you issue within your batch job causes your large rollback segment to go offline and become unavailable...You can either get rid of your mid-commits or bring the rollback segment back online and re-issue the set transaction command to keep your batch job from using other rollback segments.
Previous Topic: PK Index on different TableSpace
Next Topic: Re: remote connecting oracle and MS Access
Goto Forum:
  


Current Time: Thu Sep 19 18:05:39 CDT 2024