Table spaces and extent sizes

hi all,
how can we set the table spaces and extent sizes

Hi
All the things you can do when you are trying to create a table.
You create a table using SE11.
After that you have assign the fields to the table and later you need to give the technical settings to a table.
Here you need to specify the table size which you call it as Extents.
Table spaces are also defined to a table there itself.
Reward if useful

Similar Messages

  • What is difference between table space and shchema

    what is difference between table space and shchema ?

    784633 wrote:
    so each user has it own space of tables - schema ?yes, but let's clarify a bit ....
    The "schema" is the collection of all objects owned by a particular user. So if user SCOTT creates two tables, EMP and DEPT, and a view EMP_RPT, and a procedure GET_MY_EMP, those objects (tables, views, procedures) collectively make up the SCOTT schema.
    Those objects will be physically stored in a tablespace.
    A tablespace is a named collection of data files. So tablespace USERS will be made up of one or more data files. A specific datafile can belong to one and only one tablespace. If a tablespace has more than one data file, oracle will manage those files as a collection invisible to the application - much like the OS or disk subsystem handles striping across multiple physical disks.
    A specific object in the SCOTT schema can exist in only one tablespace, but not all objects of the schema have to be in the same tablespace. Likewise a tablespace can contain objects from multiple schemas.
    and can one user to access tables of other users?As others have said - FRED can access tables belonging to SCOTT as long has SCOTT has granted that access to FRED.

  • Table space and recollection of released space after client deletion

    Dear All,
    I have two questions:
    1.Can any1 tell me how to determine the fastest growing table and how to reorganize table space.
    2. Is there any way by which we can recollect the space released:say after client deletion. I had deleted one client two  weeks back and when I saw the SAP/user drive I fow free space available remains the same.
    I searched but found no relevant clue.
    regards,
    Ashutosh

    1.- You can see the largest table report in ST04 (as far as i remember)...
    2.- You can reorganize your db using brtools - brspace...
    Read,
    http://help.sap.com/saphelp_erp2004/helpdata/en/32/0d0c888839164ba4245b3ff7969c59/frameset.htm
    Regards
    Juan

  • SWAP space and RAM size

    Hi all,
         However there is no specific measurement for providing SWAP space,there is a ganeral rule says that "SWAP space must be twice the amount of RAM"...Why this specific value(twice of RAM)..Why it cant be the thrice amount? May i know what is the reason for telling this rule?
    Please can anyone tell me?
    Jasmine

    Hi
    The minimum requirement should be twice the size of RAM.This is because when a core dump occurs the whole active process avaulable in RAM will be written as a core file .the file will be initially written in the swap.The swap has to hold the full amount of memory and inturn swap will also have some files active.So as a minimum requirement you should have twice the amount of RAM as Swap Space.If you have a high storage and you dont know what to do give to to swap,No issue in that.

  • Table spaces and Users

    I have created a new user and have specified separate tablespaces for both data and index for this users.
    Now the problem is the schema objects are to be imported from another database which only has system tablespace, I wanted to know if this schema/user (single) is imported under the one I created in my database, then would it take the tablespaces automatically?

    Also you can do import with parameter indexfile=[some file name here]. This won't do the actual import but instead will generate a file containing the sql necessary to create all tables and indexes. You can then manually edit this file to change the tablespace names and then run it to pre-create the tables (without data) and indexes in the correct tablespaces. Be sure to also remove the REM in front of all the create table statements as they will be commented out otherwise.
    Then, do your import specifying ignore=y. This will ignore the errors generated by the tables already existing, and insert the data into the tables you already created.

  • Tablespaces and block size in Data Warehouse

    We are preparing to implement Data Warehouse on Oracle 11g R2 and currently I am trying to set up some storage strategy - unfortunately I have very little experience with that. The question is what are general advices in such considerations according table spaces and block size? I made some research and it is hard to find some clear answer, there are resources advising that block size is not important and can be left small (8 KB), others state that it is crucial and should be the biggest possible (64KB). The other thing is what part of data should be placed where? Many resources state that keeping indexes apart from its data is a myth and a bad practice as it may lead to decrease of performance, others say that although there is no performance benefit, index table spaces do not need to be backed up and thats why it should be split. The next idea is to have separate table spaces for big tables, small tables, tables accessed frequently and infrequently. How should I organize partitions in terms of table spaces? Is it a good idea to have "old" data (read only) partitions on separate table spaces?
    Any help highly appreciated and thank you in advance.

    Wojtus-J wrote:
    We are preparing to implement Data Warehouse on Oracle 11g R2 and currently I am trying to set up some storage strategy - unfortunately I have very little experience with that. With little experience, the key feature is to avoid big mistakes - don't try to get too clever.
    The question is what are general advices in such considerations according table spaces and block size? If you need to ask about block sizes, use the default (i.e. 8KB).
    I made some research and it is hard to find some clear answer, But if you get contradictory advice from this forum, how would you decide which bits to follow ?
    A couple of sensible guidelines when researching on the internet - look for material that is datestamped with recent dates (last couple of years), or references recent - or at least relevant - versions of Oracle. Give preference to material that explains WHY an idea might be relevant, give greater preference to material that DEMONSTRATES why an idea might be relevant. Check that any explanations and demonstrations are relevant to your planned setup.
    The other thing is what part of data should be placed where? Many resources state that keeping indexes apart from its data is a myth and a bad practice as it may lead to decrease of performance, others say that although there is no performance benefit, index table spaces do not need to be backed up and thats why it should be split. The next idea is to have separate table spaces for big tables, small tables, tables accessed frequently and infrequently. How should I organize partitions in terms of table spaces? Is it a good idea to have "old" data (read only) partitions on separate table spaces?
    It is often convenient, and sometimes very important, to separate data into different tablespaces based on some aspect of functionality. The performance thing was mooted (badly) in an era when discs were small and (disk) partitions were hard; but all your other examples of why to split are potentially valid for administrative. Big/Small, table/index, old/new, read-only/read-write, fact/dimension etc.
    For data warehouses a fairly common practice is to identify some sort of aging pattern for the data, and try to pick a boundary that allows you to partition data so that a large fraction of the data can eventually be made read-only: using tablespaces to mark time-boundaries can be a great convenience - note that the tablespace boundary need not match the partition boudary - e.g. daily partitions in a monthly tablespace. If you take this type of approach, you might have a "working" tablespace for recent data, and then copy the older data to "time-specific" tablespace, packing it and making it readonly as you do so.
    Tablespaces are (broadly speaking) about strategy, not performance. (Temporary tablespaces / tablespace groups are probably the exception to this thought.)
    Regards
    Jonathan Lewis

  • Dropping Rollback table space in export dump and use the undo table space

    Hi,
    I want to upgrade my DB which is on 9.2.0.1.0 to 10.2.0.1.
    I have done an export.
    In order to import the DB I have created all the table spaces identical that of my export copy. While creating the Blank database I have already created Undo table space. In the exported DB I have a table space called rollback, how can I drop this table space and use undo table space. I believe this is the recommended table space that should be used in new releases
    Thank you

    Very briefly, these are the steps you will need to perform:
    1) Create an UNDO tablespace the same size as the Rollback tablespace, e.g.:
    CREATE UNDO TABLESPACE undo
    DATAFILE ‘/ora/$ORACLE_SID/001/oradata/$ORACLE_SID/undo_01.dbf’ size 1000M;
    2) Add the initialisation parameters UNDO_MANAGEMENT=AUTO, UNDO_TABLESPACE=UNDO. Omit the UNDO_RETENTION parameter unless it is to be set to a value other then the default of 900 (seconds)
    3) Remove the initialisation parameter ROLLBACK_SEGMENTS
    4) Bounce the database to bring the new parameters into effect.
    5) Drop the Rollback tablespace including contents and datafiles
    Cheers,
    Jason

  • List size of table spaces

    Hello,
    I would like to list the name and size of table spaces and also extend them if they are almost filled. Since I'm more familiar with T/SQL I would greatly appreciate your help

    SQL> select u.tblspc "TBLSPC", a.fbytes "ALLOC", u.ebytes USED, a.fbytes-u.ebytes UNUSED,
    2 (u.ebytes/a.fbytes)*100 USEDPCT
    3 from (select tablespace_name tblspc, sum(bytes) ebytes
    4 from sys.dba_extents
    5 group by tablespace_name) u,
    6 (select tablespace_name tblspc, sum(bytes) fbytes
    7 from sys.dba_data_files
    8 group by tablespace_name) a
    9 where u.tblspc = a.tblspc
    10 ;
    TBLSPC ALLOC USED UNUSED USEDPCT
    CARTEST_DATA 891289600 488701952 402587648 54,8308824
    CARTEST_IDX 83886080 46465024 37421056 55,390625
    CARTMPTEST_DATA 41943040 26935296 15007744 64,21875
    RBS 541065216 104857600 436207616 19,379845
    SYSTEM 471859200 373547008 98312192 79,1649306
    TEMP 209715200 58654720 151060480 27,96875
    6 rows selected.
    SQL>
    Joel P�rez

  • Temp Tables space problem with ORA-01114 and  ORA-27072:

    RDBMS :Oracle:9.2.0
    OS: Linux AS3
    Storage: SAND arrray (RAID 5)
    Problem on exeuting dml statement
    SQL> select * from myview ;
    select * from myview
    ERROR at line 1:
    ORA-01114: IO error writing block to file 201 (block # 3977)
    ORA-27072: skgfdisp: I/O error
    Linux Error: 28: No space left on device
    Additional information: 3976
    ORA-01114: IO error writing block to file 201 (block # 3977)
    ORA-27072: skgfdisp: I/O error
    Linux Error: 28: No space left on device
    Additional information: 3976
    With Regards
    Joy

    Hello joy,
    So, still looking for solution. I suggest you a sloution and it works well only if as you mentioned (in your previous post) that file causing error is temp file. So, get rid of this better you create new temporary table space and drop old one and then delete the old files manually.
    But this will work only for Temp Tablespace not for normal tablespaces and datafiles. Prepare new temporary tablespace at different location from the previous one, try to make it on different disk beacuse it may be due to corruption of physical medium too.
    Try this. If it works... you are through... otherwise i have no other options...
    Please update.....

  • Information about table spaces.

    Hi!
    I have a requirement to   create a Bex by which I can display the  list of table spaces available and status of  those  table spaces like memory free, Used. Though we can get this information from  DB02  I need to generate a  report and  broadcast that to users.
    Can anyone help me in telling me the table name  where you can get the list of table spaces  and infomation or any function module which lists the  table spaces name and  status of them. 
    Regards
    Venkat

    Hello,
    Could you please share more information about this? We need to do the same thing. How did you create your generic datasource? what table/Function module did you used?
    Thank you
    Ramona

  • When do i need to create table spaces ?

    hi all,
    i know that any database has one table space and one data file at first creation , but
    when do i need to create another table space or data file ? do i need that when oracle tells me that there is no space anymore or what ?
    thanks

    newbi_egy wrote:
    hi all,
    i know that any database has one table space and one data file at first creation , but
    when do i need to create another table space or data file ? do i need that when oracle tells me that there is no space anymore or what ? In oracle database, the concept of storage segregation is done by two ways, using the schema and using the tablespace. So assume that you have two applications . One is used for HR related work and another is used for Finance and both kind of data is stored in one single database only. So how would you maintain such requirement? There are two ways to do it. One, you make two different schemas for each of the application and call them, for example HR schema and Fin schema. Now, you can create objects related to each of the application in it's own schema and store it in may be a single tablespace, Users. But this is going to be a little problematic like what would happen if you have lost the data file of that tablespace? You would be losing the data related to both the applications. So the better option would be to use two different tablespaces and store the data related to each application in both of them.
    Understand that tablespace is a logical structure only. The only thing that's physical is going to be those data files which are stored under the tablespace. So if you are just running out of space in a data file of a tablespace, you do not need to create another tablespace. Take it like this that if you are running out of space for your family in the house, you can either make a new house for them or you can even build a new floor for them. Which one would be easier to manage, the new floor since a lot of ground work is already done for you. And that's what is the case if you have run out of the space in the data file. For this,you can simply create a new datafile(building a new floor) or even extend the existing one(construct a new room in the same floor, if you have space) . But creating a new tablespace won't be something that you should be doing for the reason of space being exhausted IMO.
    Aman....

  • Edit next extent size of the Cluster table

    Hi Guys
    I need to change the next extent size of the a table.
    I ran se14 but i am not able to get into edit mode, because there is no button for edit mode.
    Reason: Cluster table
    Two questions:
    1. Why there is no Edit button? Is it because this table doesnot exixt at DB level.
    2. How can i change the next extent size for a Cluster table from sql prompt or from brtools if possible.
    Information:
    I am facing this issue only in DEV, QAS boxes, where as in Production its fine.
    Regards
    Ricky
    Edited by: Ricky kayshap on Dec 9, 2008 3:52 PM

    Hi,
    Cluster Tables doesn't exist in DB, Because of that you can't make changes to extents at DB level.
    if you experiencing some space issue. I woud suggest to check the underline Transparent tables and make changes to those.
    hope this helps.
    Kalyan.

  • How to extent table space in ecc6 sap with aix

    Dear ALL,
    how to extent table space in ecc6 sap with aix
    REGARDS,
    ashutosh

    Hi Ashutosh,
    You can use brtools/sapdba in oracle and increase tablespace. You have not mentioned which database and version using.
    Regards,
    Anil

  • Migrating LONG RAW to BLOB and optimizing extent size

    Hi all,
    I got a quite fragmented table with a LONG RAW column I want to migrate to BLOB and defragment.
    DB version is Oracle9i Release 9.2.0.4.0 and this is a production environment.
    I know MOVE and/or CTAS are not possible with LONG RAW columns
    So, how can I do that? Is ALTER TABLE MODIFY the only possibility to migrate from LOING RAW to BLOB?
    Since ALTER TABLE MODIFY will lock the whole table preventing any DML operation, I need at least a rough estimate of the time needed for this operation. How can I do that?
    Since this table is quite fragmented, I also want to rebuilt it using a different extent size.
    I think I should issue a ALTER TABLE MOVE... after having performed the "ALTER TABLE MODIFY".
    Can I do something better to minimize unavailability to DML operations?
    thanks,
    andrea

    Hi,
    Is this an OCCI question?
    I don't see that "to_blob" is documented anywhere. The "to_lob" function can be used to convert long raw columns, but its use is pretty specific and certainly not for general query use.
    Regards,
    Mark
    EDIT1: Well, my local documentation set does not have "to_blob" in it at all. However, it is in the 11.1 SQL Language Reference on OTN:
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/functions186.htm#sthref2358
    Despite the fact that the documentation mentions "long raw" the function appears to only work with "raw" data in my 11.1 tests.
    What's your goal here?
    Edited by: Mark Williams on Jun 8, 2009 7:15 PM

  • Snap Shot too old error And UNDO Table space.

    I posted [This Question|http://forums.oracle.com/forums/thread.jspa?threadID=718704&tstart=0] in PL/SQL forum. Now thought this would be a better place.
    Thanks,
    Karthick.

    Karthik,
    Its actually not the same thing when we talk about manual Rollback Segments and Automatic Undo Segments. Besides the fact that the former is created by us and thus needs to be managed properly in the terms of the size and other things, the later one is far more performance oriented. There are couple of enhancements which are done in terms of Automatic Undo , to quote a few, Undo Stealing is one .Another is the on the fly making the undo segments offfline and while starting up the database, only the needed ones are available . This enables the fast instance startup.
    Wont oracle automatically adjust the UNDO_RETENTION parameter based on the UNDO table space size.
    If you have read it from Orcle docs than you must have seen this advice is correct when the release is 10.2 onwards and the tablespace is autoextensible. If the tablespace is autoextensible than from 10.2 onwards, you don't need to worry about the undo_retention period. It will be set automatically. If the tablespace is not autoextensible than Oracle would set the parameter value to the duration of the query.
    For the snapshot too old error, I would suggest you read this link,
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:275215756923
    There is no other document AFAIK which explains it more clearly than this one.
    HTH
    Aman....

Maybe you are looking for