| jay |
Posted: Sep 08, 2008 05:42:09 AM |
Total Post: 6
Joined: Jun, 2008
|
| In our database there are two temporary tablespace when i login through DBA STUDIO i always seen them in high water mark why this happen it is locally manage tablespace so they should colase them. Only after database restart they become zero.Database is 8i.Even one tablespace is offline it is showing at high water mark |
|
|
 vino |
| Posted: Sep 08, 2008 06:32:23 AM |  |
|
Total Post: 357
Joined: Aug, 2008
|
Hi Jay,
Please note that there is no concept of LMT in your database since your database is oracle 8i. Hence, try to coalese the tablespace manually.
The tablespace is coalesed after the db restarted bcoz, smon will done that.
|
|
|
|
|
| jay |
| Posted: Sep 09, 2008 05:26:21 AM | |
|
Total Post: 6
Joined: Jun, 2008
|
I am not satisfied by this answer bz what i know and what i get from site is this
Extent management has traditionally been controlled by system tables, causing contention in busy systems with lots of inserts and deletes. In Oracle 8i the EXTENT MANAGEMENT clause was introduced into the CREATE TABLESPACE statement allowing extent management to be LOCAL or DICTIONARY. Locally Manages Tablespaces (LMT) have a bitmap of the blocks, or groups of blocks, they contain allowing them to track extent allocation without reference to the data dictionary.
for more information u can click on this link
http://www.oracle-base.com/articles/8i/LocallyManagedTablespaces.php
|
|
|
|
|
| vino |
| Posted: Sep 09, 2008 07:55:17 AM | |
|
Total Post: 357
Joined: Aug, 2008
|
S, of course the LMT concept is avail from Oracle 8.1.5.. But bfore that LMT is not available..
|
|
|
|
|
| GOPU |
| Posted: Sep 09, 2008 04:23:26 PM | |
|
Total Post: 340
Joined: Apr, 2008
|
but here the case it TEMP tablespace.....why it becomes zero after restart
|
|
|
|
|
| vino |
| Posted: Sep 10, 2008 05:50:55 AM | |
|
Total Post: 357
Joined: Aug, 2008
|
SMON coalesces free space (extents) into larger, contiguous extents every 2 hours and even then, only for a short period of time.
SMON will not coalesce free space if a tablespace's default storage parameter "pctincrease" is set to 0. With Oracle 7.3 one can manually coalesce a tablespace using the ALTER TABLESPACE ... COALESCE; command, until then use:
SQL> alter session set events 'immediate trace name coalesce level n';
where 'n' is the tablespace number you get from SELECT TS#, NAME FROM SYS.TS$;
You can get status information about this process by selecting from the SYS.DBA_FREE_SPACE_COALESCED dictionary view.
|
|
|
|
|
| Time Zone: EDT |
Send this thread to your friend |
