Re: Relocating LOB segment
- From: Brent Day <coloradodba@xxxxxxxxx>
- To: Yong Huang <yong321@xxxxxxxxx>
- Date: Fri, 6 Feb 2015 08:57:53 -0700
We actually set db_aecurefile parameter to always on all of our instances
and have only seen positive results.
Of course the setting change only applies to newly created lobs after the
setting is changed. LOBs created before have to be converted through a
move/reorganize.
Of course the tablespace has to be ASSM or you will get the respective
error.
We own advanced compression and advanced security and the deduplicte that
come with advanced compression has proven very beneficial for several of
our apps.
The Lob compression works very well and I have found medium compression on
LOBS to work well. I tried high but the CPU usage outweighed the benefit
for our needs.
As always YMMV
Brent
On Friday, February 6, 2015, Yong Huang <yong321@xxxxxxxxx> wrote:
> > If you are on 11.2 and use SecureFiles then you can export with parallel
>
> It actually started at 11.1.
>
> Now I have a question. Can anybody think of anything bad about setting
> db_securefile to always in Oracle 11g so all LOBs are created as SecureFile
> instead of BasicFile? We're recommended to use SecureFile LOB (see Doc
> 1467662.1 and many others), and it's the default in 12c. Other than the
> restriction that SecureFile LOB can't be created in a non-ASSM i.e. MSSM
> tablespace, I see only benefit, no disadvantage. Without the advanced
> security or compression license, users have to be careful not to
> accidentally add certain clauses to trigger usage of these licenses. But
> that's a minor concern.
>
> Yong Huang
>
>
Other related posts:
