Trying to create a fact table,error:unable to extend temp segement

Using Oracle 10.2g
SQL>
create materialized view facts_table
(     s_id
,     g_id
,     sb_id
,     sc_id
,     y_id)
refresh with rowid
as      select s.s_id
,     g.g_id
,     sb.sb_id
,     sc.sc_id
,     y.academicyear
from      student s
,     grade g
,     subject sb
,     school sc
,     comqdhb.teachinggroup y;
ERROR at line 3:
ORA-01652: unable to extend temp segment by 1024 in tablespace POSTGRADSI am creating the fact table as materialized view because its specified for us.
I am trying to create a fact table from the dimension tables and its giving this error
what is the mistake kindly help.
Also when creating the fact table do all the columns need to be foreign keys compulsorily.
Edited by: Trooper on Jan 10, 2009 5:25 AM
Edited by: Trooper on Jan 10, 2009 6:37 AM

Well basically what your saying is absolutely right
I realized what i am doing right now is stupendous blunder.
Basically my aim is there are 5 dimensional tables that are created
Student->s_id primary key,upn(unique pupil no),name
Grade->g_id primary key,grade,exam_level,values
Subject->sb_id primary key,subjectid,subname
School->sc_id primary key,schoolno,school_name
year->y_id primary key,year(like 2008)
s_id,g_id,sb_id,sc_id,y_id are sequences
select * from student;
S_ID UPN FNAME COMMONNAME GENDER DOB
==============================
9062 1027 MELISSA ANNE       f  13-OCT-81
9000 rows selected
select * from grade;
      G_ID GRADE      E_LEVEL         VALUE
        73 A          a                 120
        74 B          a                 100
        75 C          a                  80
        76 D          a                  60
        77 E          a                  40
        78 F          a                  20
        79 U          a                   0
        80 X          a                   0
18 rows selectedThese are basically the dimensional views
Now according to the specification given, need to create a fact table as facts_table which contains all the dim tables primary keys as foreign keys in it.
The problem is when i say,I am going to consider a smaller example than the actual no of dimension tables 5 lets say there are 2 dim tables student,grade with s_id,g_id as p key.
create materialized view facts_table(s_id,g_id)
as
select  s.s_id,g.g_id
from   (select distinct s_id from student)s
,         (select distinct g_id from grade)gThis results in massive duplication as there is no join between the two tables.But basically there are no common things between the two tables to join,how to solve it?
Consider it when i do it for 5 tables the amount of duplication being involved, thats why there is not enough tablespace.
I was hoping if there is no other way then create a fact table with just one column initially
create materialized view facts_table(s_id)
as
select s_id
from student;then
alter materialized view facts_table add column g_id number;Then populate this g_id column by fetching all the g_id values from the grade table using some sort of loop even though we should not use pl/sql i dont know if this works?
Any suggestions.
Edited by: Trooper on Jan 10, 2009 6:38 AM

Similar Messages

  • Request of one report fails with error: unable to extend tablespace

    Hi All,
    When I submit one request of report, the request end up with error:
    unable to extend temp segment by 128 in tablespace XXXX
    The request costs too much tablespace in short time, but the temp is about 20 G large.
    The sever have been add storage recently, but I don't know whether it is related to the performance issue, because the request had not such issue.
    How do I deal with it ?
    Thanks,
    Xinya

    What report is it ?
    Did you try and search metalink ?
    How to handle 'ORA-01652: unable to extend the temp segment by 128 in tablespace' error messages? (Doc ID 1359238.1)
    R12 Journal Entries Report (XLAJELINESRPT) Has Performance Issue Or Fails With Error: "java.sql.SQLException: ORA-01652: unable to extend temp segment by 128 in tablespace TEMP1" (Doc ID 1141673.1)
    This forum may be the right one for your question - General EBS Discussion

  • Unable to Extend TEMP space for CLOB

    Hi,
    I have a data extract process and I am writing the data to a CLOB variable. I'm getting the error "Unable to Extend TEMP space" for the larger extracts. I was wondering if writing the data to a CLOB column on a table and then regularly committing would be better than using a CLOB variable assuming time taken is not an issue.

    You do not need to add more temp files. This is not a problem of your temp tablespace. This is the problem of temp segments in your permanent tablespace. You need to add another datafile in EDWSTGDATA00 tablepsace. This happens when you are trying to create tables and indexes. Oracle first does the processing in temp segments(not temp tablespace) and at the end oracle converted those temp segments into permanent segments.
    Also, post the result of below query
    select file_name,sum(bytes/1024/1024)in_MB,autoextensible,sum(maxbytes/1024/1024)in_MB from dba_data_files where tablespace_name='STAGING_TEST' group by file_name,autoextensible order by FILE_NAME;

  • Unable to extend temp segment by 1024 in tablespace

    Oracle : 10.2.0.4.0
    OS : AIX 5
    Hi,
    I got an error "unable to extend temp segment by 1024 in tablespace"
    Then, i have executed below 2 queries,
    SQL> SELECT tablespace_name, SUM(bytes_used), SUM(bytes_free) FROM V$temp_space_header GROUP BY tablespace_name;
    TABLESPACE_NAME SUM(BYTES_USED) SUM(BYTES_FREE)
    USER_TMP 65536 20905984
    TEMP 268435456 0
    SQL> select tablespace_name, (total_blocks*8192)/1024/1024/1000 "Avail (Gb)",(used_blocks*8192)/1024/1024/1000 "Used (Gb)", (free_blocks*8192)/1024/1024/1000 "Free (Gb)" from v$sort_segment
    2 /
    TABLESPACE_NAME Avail (Gb) Used (Gb) Free (Gb)
    TEMP .255 0 .255
    Right now, my questions are
    1> what is the difference between 'bytes_free" in V$temp_space_header and "free_blocks" in v$sort_segment?
    2> Do we need to increase size of the TEMP tablespace now?
    Thanks in advance,
    Govin

    please refer to similar posts :
    Re: ORA-01652 Unable to extend temp segment by 128 in tablespace TEMP
    Re: ORA-1652: unable to extend temp segment
    ORA-01652: unable to extend temp segment by 128
    Also your tamp tablespace size is only .255GB which is less.
    During which operation are you getting this error ?

  • How to create logical fact table in BMM layer ?

    Hello,
    I have 3 Dimension table - 2 are in one schema and last is another schema. Using this 3 dimension tables, I need to create a logical fact table.
    So, my question is whether we can create this fact table by joining these 3 dimension table which are in 2 different schema s ?
    Thanks

    Fiaz,
    you are correct. We can use tables from different subject area to create a report. However, my question was related to rpd design. Sorry, I was not very clear about the queries earlier.
    Here is the whole scenario in the physical layer of the rpd
    Table name      Databse name      Connection pool name      Schema name
    AV          AV_PXRPAM     AVAILABILITY          CRMODDEV
    OUTAGE          AV_PXRPAM     AVAILABILITY          CRMODDEV
    COMPANY          PXRPAM          PXRPAM_POOL          CRMODDEV
    AV and OUTAGE have the joins already. I want to make a join between COMPANY with OUTAGE. And then I want to include a column from each of above tables to the logical fact table in the BMM layer. then I want to do a star schema with the logical fact table to the above 3 tables in the BMM layer.
    Thanks

  • How and when to create a fact table

    hi every1,
    I am new to oracle and specially to Data Warehousing. I am using OWB 11g on windows XP.
    I have created the dimensional for a database, now i am in the implementation phase.
    i have the following questions.
    1. I don't know how and when to create a fact table. I have already created the dimensions (ROLAP).
    2. Do i need to create a mapping for a Cube. if yes, then how to load them from 4 different dimensions. how will be the join condition, they don't match?
    3. I will also try for aggregation, do i need to use MOLAP for the dimensions or ROLAP works?
    Please, give a quick reply.
    regards
    RF

    You should ask your question here:
    Warehouse Builder
    where it is on topic.

  • IWork Numbers program. I am trying to create a 'Master Table'. The table will be used on numerous sheets, when cells altered on the 'Master' it will show on all sheets using the Master table. Is this a possibility??

    iWORK NUMBERS
    I am trying to create a 'Master Table'. This table will be used on numberous sheets, however not all. Items entered into the cells in the Master Table will then reflect in the used sheets that have the Master Table linked.
    On the individual pages however, they will be able to be altered purely for that page.
    Hope I have explained myself clearly,
    Would appreciate any help,
    Cheers,

    Hi Hilary,
    The formula in the Index column of the Main table is:
    E2: =IF(A,MAX($E$1:E1)+1,"")
    Fill down to the end of column E.
    The Breakout table contains a single formula:
    A2: =IF((ROW()-1)>MAX(Main :: $E),"",OFFSET(Main :: $A$1,MATCH(ROW()-1,Main :: $E,0)-1,COLUMN()))
    Fill down and right to fill the table.
    For multiple rooms (with different data transfered to each) you'll need a column of checkboxes and a corresponding index column for each room.
    The index columns can be hidden.
    Contents in individual cells in the breakout tabel(s) can be entered directly, replacing the formula. To retun to the calculated result, select a cell adjacent to the one where text was entered, and drag the Fill control handle (small circle, bottom right of the selection rectangle) to fill the formula back into that cell.
    Regards,
    Barry

  • System copy export  -  error message unable to extend temp segment PSAPTEMP

    I am performing an export of ECC ABAP+java instance and during the export of the source system I get the following error during the ABAP export:
    ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
    ORA-27072: File I/O error
    What do I need to do with this error? I have extended the tablespace via brtools but still getting the error.
    Is this because I did not select the shutdown instance during the export? or do I need to do something more via brtools to the PSAPTEMP tablesapce?
    I am running on Oracle 10.2.0.2. unix
    Thanks
    Mikie

    Hello Mike,
    >> My PSAPTEMP is 8GB.
    I would bet the table you try to export is bigger (if you export sorted.. you will need temp space)
    >> You have said you increased it to 800GB, that is almost a terabyte. Is this correct?
    >> If so, how did you arrive at this figure.
    As i already said .. this was the temp space that i needed in a sorted exported with many parallel exports (splitted packages and splitted tables). The system that i have migrated was round about 3 TB and we need to do it very fast.. so i needed the temporary space for the many parallel actions... but this should not be the "normal" case if you have no specific values.
    >> And if you could define how you extended PSAPTEMP. Did you use brtools?
    I have extended it manually (over sqlplus) .. i have monitored it in my test cases with the view V$TEMPSEG_USAGE and increased it if necessary.
    >> did you recreate PSAPTEMP via SQLPLUS size 800GB and then dropped it and recreated to normal size?
    No, in my case i have exported and imported it at the same time (distribution monitor) so there was no need to drop it after the export, because i have build up a new target database. But under normal conditions you would only drop the tempfiles after your work has been done. This is possible with Oracle 10g (with some restrictions).
    => http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_3002.htm#i2093894
    Restrictions on Dropping Files To drop a datafile or tempfile, the datafile or tempfile:
    - Must be empty.
    - Cannot be the first file that was created in the tablespace. In such cases, drop the tablespace instead.
    - Cannot be in a read-only tablespace.
    Regards
    Stefan

  • READER_1_1_1RR_4035SQL Error [ ORA-01652: unable to extend temp segment b

    Hi,
    I am still facing the error for table space evnthough datafile is avl
    READER_1_1_1     RR_4035     SQL Error [
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
    Database driver error...
    Function Name : Execute
    SQL Stmt : SELECT
    ONLINE     DATA     PERMANENT     LOCAL     200     0.063     0.03
    ONLINE     DEV1_BIPLATFORM     PERMANENT     LOCAL     64     44.313     69.24
    ONLINE     DEV1_IAS_TEMP     TEMPORARY     LOCAL     100     0     0
    ONLINE     DEV1_MDS     PERMANENT     LOCAL     100     5.438     5.44
    ONLINE     DEV_BIPLATFORM     PERMANENT     LOCAL     64     44.313     69.24
    ONLINE     DEV_IAS_TEMP     TEMPORARY     LOCAL     100     0     0
    ONLINE     DEV_MDS     PERMANENT     LOCAL     100     5.438     5.44
    ONLINE     EXAMPLE     PERMANENT     LOCAL     975.188     109.125     11.19
    ONLINE     FLA_TBS1     PERMANENT     LOCAL     10     0.063     0.63
    ONLINE     MES_DW2     PERMANENT     LOCAL     2,091.19     1,794.19     85.8
    ONLINE     SYSAUX     PERMANENT     LOCAL     1,245.38     906.938     72.82
    ONLINE     SYSTEM     PERMANENT     LOCAL     3,300.00     2,429.44     73.62
    ONLINE     TEMP     TEMPORARY     LOCAL     24,458.00     5,020.00     20.52
    ONLINE     TOOLS     PERMANENT     LOCAL     1,050.00     0.063     0.01
    ONLINE     UNDOTBS1     UNDO     LOCAL     2,670.00     95.438     3.57
    ONLINE     USERS     PERMANENT     LOCAL     43,530.98     30,366.30     69.76

    No Sense:
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
    tablespace TEMP2
    Database driver error...
    Function Name : Execute
    SQL Stmt : SELECT
    ONLINE     DATA     PERMANENT     LOCAL     200     0.063     0.03
    ONLINE     DEV1_BIPLATFORM     PERMANENT     LOCAL     64     44.313     69.24
    ONLINE     DEV1_IAS_TEMP     TEMPORARY     LOCAL     100     0     0
    ONLINE     DEV1_MDS     PERMANENT     LOCAL     100     5.438     5.44
    ONLINE     DEV_BIPLATFORM     PERMANENT     LOCAL     64     44.313     69.24
    ONLINE     DEV_IAS_TEMP     TEMPORARY     LOCAL     100     0     0
    ONLINE     DEV_MDS     PERMANENT     LOCAL     100     5.438     5.44
    ONLINE     EXAMPLE     PERMANENT     LOCAL     975.188     109.125     11.19
    ONLINE     FLA_TBS1     PERMANENT     LOCAL     10     0.063     0.63
    ONLINE     MES_DW2     PERMANENT     LOCAL     2,091.19     1,794.19     85.8
    ONLINE     SYSAUX     PERMANENT     LOCAL     1,245.38     906.938     72.82
    ONLINE     SYSTEM     PERMANENT     LOCAL     3,300.00     2,429.44     73.62
    ONLINE     TEMP     TEMPORARY     LOCAL     24,458.00     5,020.00     20.52
    ONLINE     TOOLS     PERMANENT     LOCAL     1,050.00     0.063     0.01
    ONLINE     UNDOTBS1     UNDO     LOCAL     2,670.00     95.438     3.57
    ONLINE     USERS     PERMANENT     LOCAL     43,530.98     30,366.30     69.76
    tablespace TEMP2 doesn't exist.
    i used statement
    ALTER TABLESPACE temp
    ADD TEMPFILE 'D:\app\TEMP16.DBF' SIZE 128M autoextend on;
    ALTER TABLESPACE
    USERS ADD DATAFILE 'D:\app\SYS00.DBF' SIZE 1080M autoextend on;
    alter user DATAWAREHOUSE quota unlimited on USERS
    why add datafile in user tablespace¿?
    and you solved the issue doing the same like we told you a few days before in:
    ORA-1652: unable to extend temp segment by 128 in tablespace
    unable to create INITIAL extent for segment in tablespace USERS
    Remember close your threads:
    896398     
    Handle:      896398 
    Status Level:      Newbie
    Registered:      Nov 9, 2011
    Total Posts:      530
    Total Questions:      158 (116 unresolved)

  • Unable to extend temp segment by 4096 in tablespace  error

    Hi
    Can some help me resolving this problem .which occured when i try to import some dump file to an user.
    ORA-39171: Job is experiencing a resumable wait.
    ORA-01652: unable to extend temp segment by 4096 in tablespace HDM_INDEX
    i added 2 gb of datafile to the table space it is still shows the same .
    any expert suggestion is highly apprciated.
    thanks

    790072 wrote:
    Hi
    Can some help me resolving this problem .which occured when i try to import some dump file to an user.
    Pl post details of OS and database versions, along with the complete import command and parameters used.
    ORA-39171: Job is experiencing a resumable wait.
    ORA-01652: unable to extend temp segment by 4096 in tablespace HDM_INDEX
    i added 2 gb of datafile to the table space it is still shows the same .Pl identify the tablespace you added space to (and the commands used to add space)
    >
    any expert suggestion is highly apprciated.Pl post relevant sections from the database alert.log
    >
    >
    thanks
    ORA-1652 Error Troubleshooting          [Document 793380.1]
    ORA-01652: Estimate Space Needed to CREATE INDEX          [Document 100492.1]
    TROUBLESHOOTING GUIDE (TSG) - UNABLE TO EXTEND Errors          [Document 1025288.6]
    HTH
    Srini

  • Unable to extend TEMP segment even after adding fresh temp files

    Hi All,
    I have a huge table with rows nearly 2 million. When this table is moved to another tablespace, the command failed giving the following error:
    ORA-01652: unable to extend temp segment by 128 in tablespace XYZ
    To overcome this error, an additional temp file was added with huge size. Unfortunately, the same error appeared again when the table was tried to move to another tablespace. I wonder if the new temp file was not recognized by database, so tried to see how many files belong to temporary tablespace, but the query listed the newly added temp file also.
    What could be the possible reason for this error? Suggestions or clues are most welcome.
    Thanks,
    ...

    The temp segment is for the table that is being moved.
    Oracle creates a temporary segment when doing a move. If the target tablespace has enough space, the move succeeds and the temp segment gets converted to a Table segment. Else, if the move fails because of lack of space (the temp segment itself unable to grow), then the temp segment is dropped on failure.
    Thus, in a
    alter table ABC move tablespace MY_TBS;or
    the target tablespace MY_TBS should have enough space for ABC. While Oracle is building the copy of ABC in MY_TBS, it is being built as a temporary segment. If the copy succeeds, the temporary segment is renamed as a Table segment 'ABC' and the original table segment 'ABC' is dropped.
    This behaviour also happens when you do an ALTER TABLE .. MOVE ; into the same tablespace that it is existing in. The new copy of the table is a temporary sgement till the copy succeeds.

  • Unable to extend temp segment

    Hi All,
    I received the following error;
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
    Then I added the datafile in temp2 tablespace.
    But still it giving the same error;
    Syntax of Create tablespace is
    Create temporary tablespace temp2
    Datafile ‘\temp_01.dbf’ size 500m;
    Table contains 100000 records;
    Please help me.
    Thanks and regards,
    Prathamesh.

    Please check the allocation and deallocation of space in a temporary tablespace sort segment using the V$SORT_SEGMENT view. The V$TEMPSEG_USAGE view identifies the current sort users in those segments.
    Also, check settings of TEMP tablespace. May be it's trying to create a huge extent as NEXT (larger than available space), which is not required. In that case reduce NEXT EXTENT for this.

  • Unable to extend temp segment by 256 in tablespace PROD_REV_FACT_TS

    I get the following error
    please let me know how to solve this
    ERROR at line 31:
    ORA-01652: unable to extend temp segment by 256 in tablespace PROD_REV_FACT_TS
    Free space
    1 select tablespace_name , sum(bytes)
    2 from dba_free_space
    3 where tablespace_name ='PROD_REV_FACT_TS'
    4 group by tablespace_name
    5* order by 2 asc
    SQL> /
    TABLESPACE_NAME SUM(BYTES)
    PROD_REV_FACT_TS 1547698176
    Tables available
    SQL> select count(1) from all_tables where tablespace_name ='PROD_REV_FACT_TS';
    COUNT(1)
    0

    As William pointed out, the total amount of free space is not very revealing. Also, there are potentially more things in tablespaces than tables. Try these two queries to get a better picture of what space you have, and what is in the tablespace.
    SELECT file_id, MAX(bytes) biggest, SUM(Bytes) total
    FROM dba_free_space
    WHERE tablespace_name = 'PROD_REV_FACT_TS';
    SELECT segment_name, segment_type, owner, bytes
    FROM dba_segments
    WHERE tablespace_name = 'PROD_REV_FACT_TS';For a really detailed view of free_space you could try:
    SELECT file_id, block_id, bytes
    FROM dba_free_space
    WHERE tablespace_name = 'PROD_REV_FACT_TS'
    ORDER BY 1, 2;It sounds like you are trying to create a table or an index in that tablespace, and running out of space. When you do that, Oracle initially builds the segment as a temporary segment. When the segment is fully built, the temporary segments are changed to permanent segments. This makes cleanup easier for Oracle if the database goes down in the middle of the operation.
    HTH
    John

  • Unable to extend temp segment by 32 in tablespace   EDWSTGDAT

    Hi All,
    I'm getting the error
    ORA-1652: unable to extend temp segment by 32 in tablespace EDWSTGDATA00.
    Please let me know for this do i need to add more tempfiles or add more space in EDWSTGDATA00 tablespace.
    Regards,
    Narayan

    You do not need to add more temp files. This is not a problem of your temp tablespace. This is the problem of temp segments in your permanent tablespace. You need to add another datafile in EDWSTGDATA00 tablepsace. This happens when you are trying to create tables and indexes. Oracle first does the processing in temp segments(not temp tablespace) and at the end oracle converted those temp segments into permanent segments.
    Also, post the result of below query
    select file_name,sum(bytes/1024/1024)in_MB,autoextensible,sum(maxbytes/1024/1024)in_MB from dba_data_files where tablespace_name='STAGING_TEST' group by file_name,autoextensible order by FILE_NAME;

  • Unable to extend temp segment by 128 in tablespace PSAPTEMP

    Hi everybody!
    While processing a UNICODE coversion with SAPINST on my SAP NW2004s system (AIX 5,2  - Oracle 10.2 - BW 7.0) into my.SAPDFACT_1.log file the following errors occured:
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "HBQ20080503070541                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "si088ss1                                                        "
    (GSI) INFO: sysname  = "AIX"
    (GSI) INFO: nodename = "si088ss1"
    (GSI) INFO: release  = "2"
    (GSI) INFO: version  = "5"
    (GSI) INFO: machine  = "0031832B4C00"
    (DB) INFO: /BIC/FZHPY_LIM created #20080503200234
    (IMP) INFO: import of /BIC/FZHPY_LIM completed (133182692 rows) #20080503212420
    DbSl Trace: Error 1652 in exec_immediate() from oci_execute_stmt(), orpc=0
    DbSl Trace: ORA-1652 occurred when executing SQL stmt (parse error offset=42)
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE INDEX "/BIC/FZHPY_LIM~0" ON "/BIC/FZHPY_LIM" ( "KEY_ZHPY_LIMP", "KEY_ZHPY_LIMT", "KEY_ZHPY_LIMU", "KEY_ZHPY_LIM2", "KEY_ZHPY_LIM3", "KEY_ZHPY_LIM4", "KEY_ZH
    PY_LIM5", "KEY_ZHPY_LIM6", "KEY_ZHPY_LIM7" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
    DbSlExecute: rc = 99
      (SQL error 1652)
      error message returned by DbSl:
    ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
    (DB) INFO: disconnected from DB
    Anybody can help me?
    Thanks a lot!

    Hi Stefan!
    desc SAPSR3."/BIC/FZHPY_LIM";
    Name                                      Null?    Type
    KEY_ZHPY_LIMP                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIMT                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIMU                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM2                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM3                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM4                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM5                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM6                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM7                             NOT NULL NUMBER(10)
    /BIC/ZHCONTING                            NOT NULL NUMBER(17,2)
    /BIC/ZHD_IMP                              NOT NULL NUMBER(17,2)
    /BIC/ZHPERC2                              NOT NULL NUMBER(10)
    SELECT AVG_ROW_LEN FROM ALL_TABLES WHERE TABLE_NAME = '/BIC/FZHPY_LIM';
    AVG_ROW_LEN
    SELECT BYTES, BLOCKS FROM DBA_SEGMENTS WHERE SEGMENT_NAME = '/BIC/FZHPY_LIM';
         BYTES     BLOCKS
    7180648448     876544
    SELECT FILE_NAME, TABLESPACE_NAME, BYTES, BLOCKS, AUTOEXTENSIBLE, MAXBYTES, MAXBLOCKS FROM DBA_TEMP_FILES;
    FILE_NAME
    TABLESPACE_NAME                     BYTES     BLOCKS AUT   MAXBYTES  MAXBLOCKS
    /oracle/HBQ/sapdata1/temp_1/temp.data1
    PSAPTEMP                       1048576000     128000 YES 1.0486E+10    1280000
    /oracle/HBQ/sapdata1/temp_1/temp2.data1
    PSAPTEMP                        298844160      36480 YES 3.4359E+10    4194176
    Thanks.

Maybe you are looking for