Message-Id: <10481.104476@fatcity.com> From: achoto@american.edu Date: Fri, 28 Apr 2000 15:45:30 -0400 Subject: Rollback segment full One of our rollback segments is showing as 'FULL'. There is a transaction running now for over 7 hours in that segment. Here is the message in the alert log: Failure to extend rollback segment 3 because of 1562 condition Failure to extend rollback segment 3 We use DataStage to load this table. The table seems to be loading at 16 rows per second, so far we have about 438,000 rows loaded. I don't know how many rows are still left to be loaded because I'm not familiar with the source or the process, and unfortunately the developer who knows is on vacation. This is the first time I see the status of 'FULL' in our rollback segments. We have a total of five rollback segments in the RBS tablespace for a total of 1,000MB. Usually we have approximately 8 batch jobs that start the load at about 4:30 am and finish around 8:30 am. I've never seen a transaction running for so long. Can anyone out there enlighten me as to where to look for an answer to this problem? Thanks to all of you, and have a great weekend. I hope this gets to the list because I seemed to have been unsubscribed. But, I did resubscribe. Thanks Ana E. Choto Systems Programmer American University Office of Information Technology Phone (202) 885-2275