rbs settings in limited diskspace
Hi,
Is there any good standard to follow when configuring the RBS. Currently running 8.1.6 using the default rbs created when db was created using the Installer. There are 8 rbs segments under its' own tablespace called RBS.
We have a huge transaction that cause the rbs to grow till the entire file system becomes full (100%), thus hanging the entire database. The RBS tablespace is autoextensible. We were thinking of making the RBS tablespace non-extensible to prevent such a case from happening. Does this have any impact?
Another question, when a rollback occurs, due to a process that is killed before commiting, will archive logs be generated because of this?
Thanks.
Re: rbs settings in limited diskspace
Quote:
Originally posted by feng11
Hi,
We were thinking of making the RBS tablespace non-extensible to prevent such a case from happening. Does this have any impact?
Surely u will face probs, if transaction are tooo big....u will get snapshot error or rollback seg too small error........
TO overcom.....commit the TRAN in program regularly........
abhay.