| The doubts about column segment_file & relative_fno in v$sort_segment [message #606331] |
Wed, 22 January 2014 07:54  |
 |
lylklb
Messages: 12
Registered: January 2014
|
Junior Member |
|
|
1). Why the the value of the column segment_file in v$sort_segment do not correspond with any one value of the column file_id in v$tempfile !?
2). What should be the practical meaning of the column RELATIVE_FNO in v$sort_segments, such as to be assoicated with one relevant column in some dictionary view for SELECT query ?
>select TABLESPACE_NAME, current_users cur_users, SEGMENT_FILE SEG_FNO, RELATIVE_FNO REL_FNO, USED_BLOCKS U_BLKS, FREE_BLOCKS F_BLKS,
TOTAL_BLOCKS T_BLKS, TOTAL_EXTENTS T_EXTS, USED_EXTENTS U_EXTS, FREE_EXTENTS F_EXTS, EXTENT_SIZE EXT_SZ from v$sort_segment;
TABLESPACE_NAME CUR_USERS SEG_FNO REL_FNO U_BLKS F_BLKS T_BLKS T_EXTS U_EXTS F_EXTS EXT_SZ
-------------------- ------------- ----------- ------------- ----------- -------------- ------------ ----------- ----------- ---------- ---------
TEMP 9 0 0 2944 12579584 12582528 98301 23 98278 128
>select TABLESPACE_NAME, file_id, name file_name, BYTES_USED/1024/1024 U_MB, BYTES_FREE/1024/1024 F_MB, tf.bytes/1024/1024 T_MB,
(BYTES_FREE/tf.bytes)*100 f_pct, tf.status from v$temp_space_header tsh, v$tempfile tf where tf.file#=file_id;
TABLESPACE_NAME FILE_ID FILE_NAME U_MB F_MB T_MB F_PCT STATUS
------------------ ---------- --------------------------------------------- ------- -------- ------- ------- ---------
TEMP 1 /oradata/u01/temp01.dbf 32768 0 32768 0 ONLINE
TEMP 2 /oradata/u01/temp02.dbf 32768 0 32768 0 ONLINE
TEMP 3 /oradata/u01/temp03.dbf 32768 0 32768 0 ONLINE
[Updated on: Wed, 22 January 2014 07:57] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: The doubts about column segment_file & relative_fno in v$sort_segment [message #608058 is a reply to message #607999] |
Fri, 14 February 2014 10:17  |
tim2boles
Messages: 38
Registered: August 2008
Location: Clarksburg, WV
|
Member |
|
|
I don't have the systems to test this out on....and it is just going to be a wild guess.
I am guessing that you have locally managed tablespaces. These fields probably would be populated if you where using dictionary managed tablespaces.
create tablespace temp_data
datafile '/disk01/oradata/test03/temp_data.bdf'
temporary;
This fails in a locally managed system but I think it will still work in a dictionary managed system.
Again...I can not test this...I don't see any documentation that verifies what I am saying....but it is a thought.
Regards
Tim
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
