|
The fact that your RBS tablespace was full does not
have anything to do with running in ARCHIVELOG mode.
Rollback segments are online redo logs do work hand in
hand to manage transactions consistency. Running in
ARCHIVELOG mode is just a way of storing the data in
the online redo logs for future usage, by archiving
the data to another location.
It sounds more like your archive log destination
(specified by the LOG_ARCHIVE_DEST parameter) is full.
When this disk device becomes full, the database comes
to a halt until space is made available. After all, if
you are archiving transactions then how can you allow
more transactions if you can't store them anywhere. So
check your archive log destination. Make sure that you
have enough disk space. If necessary, copy the old
archive logs to another disk volume, or to tape.
Your RBS tablespace becoming full is a sign that you
do not have enough space dedicated to holding rollback
information for your load process you were doing.
You'll need to increase the size of this tablespace.
You can stay up infinitely in ARCHIVELOG mode,
provided that you have enough space in the archivelog
destination device. Since no device has infinite
space, this means that you'll occasionally have to
remove old, obsolete archived redo logs from that
device. When do these logs become obsolete? Any logs
older than your backup are no longer needed. But many
DBAs keep multiple generations of backups around.
Let's say that you perform a weekly backup. And you
want to keep three generations of backups on hand.
Then you'll need to keep three weeks worth of archived
redo logs. But you can move them around if needed to
clear up room.
For More Information
|
