Tablespace Fragmentation !! [message #164374] |
Thu, 23 March 2006 03:48 |
AlinaC
Messages: 45 Registered: November 2005 Location: India
|
Member |
|
|
FRAGMENTATION_STATUS of some tablespaces shows Bubble Frag. Can it create any problem to create procedure in database? how does it impact on overall performance of the databse? is it possible to convert dictionary managed tablespace to locally managed table space, and what is the command?
Regards,
Alina
|
|
|
|
|
|
Re: Tablespace Fragmentation !! [message #164416 is a reply to message #164402] |
Thu, 23 March 2006 06:21 |
|
Mahesh Rajendran
Messages: 10708 Registered: March 2002 Location: oracleDocoVille
|
Senior Member Account Moderator |
|
|
You have to this as SYS user and database should be in restricted mode.
Sql> Startup restrict;
sql> exec your_procedure.
If SYS user is not doing this, you need to give execute priviliges on the USER executing this.
More information in documentation.
[Updated on: Thu, 23 March 2006 06:25] Report message to a moderator
|
|
|
|
Re: Tablespace Fragmentation !! [message #164431 is a reply to message #164426] |
Thu, 23 March 2006 07:07 |
|
Mahesh Rajendran
Messages: 10708 Registered: March 2002 Location: oracleDocoVille
|
Senior Member Account Moderator |
|
|
Please search Orafaq.com about what fragmentation is and what LMT can do for it. As long as you have the LMT with UNIFORM extent size, you can very minimise this. Technically sttill, you cannot completely avoid fragmentation in the block level( depends on your PCTFREE/PCTUSED) or row level ( a row migration/chaining cannot be avoided). For now, it is ***almost*** safe to say,
Use LMT with UNIFORM extent size and there is no fragmentation.
[Updated on: Thu, 23 March 2006 07:07] Report message to a moderator
|
|
|