Re: LOB segment space usage
- From: andreik <spamme.andreik@xxxxxxxxx>
- Date: Sat, 18 Aug 2007 13:12:36 -0000
On Aug 18, 12:11 am, Maxim Demenko <mdeme...@xxxxxxxxx> wrote:
andreik schrieb:
On Aug 17, 5:29 pm, Maxim Demenko <mdeme...@xxxxxxxxx> wrote:
andreik schrieb:
I can hardly explain your results, because my tests can't confirm them
SQL> SET SERVEROUTPUT ON
SQL> SELECT * FROM V$VERSION
2 /
BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Prod
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for Linux: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production
SQL> SELECT VALUE
2 FROM NLS_DATABASE_PARAMETERS
3 WHERE PARAMETER = 'NLS_CHARACTERSET'
4 /
VALUE
-----------------------------------------------------------------------------------------------------------------------------
AL32UTF8
You have UTF and your database charset that's why your LOBs have 2
bytes per character even in CLOBS. And I have a simple single-char
character set in my database so my clobs were not supposed to be 2
byted.
Anyway, the 60K overhead per block was the answer to my question.
But thanks for your help! Tanel's document is a real good one. Helped
me a lot.
-- Andrei
.
- References:
- LOB segment space usage
- From: andreik
- Re: LOB segment space usage
- From: andreik
- Re: LOB segment space usage
- From: Maxim Demenko
- LOB segment space usage
- Prev by Date: Re: LOB segment space usage
- Next by Date: Re: Oracle NULL vs '' revisited
- Previous by thread: Re: LOB segment space usage
- Next by thread: Re: LOB segment space usage
- Index(es):
Relevant Pages
|