Autoextend without next

Hello
Regarding the autoextend issue, If I specify autoextend on,and omit next clause,by default the datafile
will extend 1 block.(not OMF)
Consider the datafile is full and segments are extended uniformly or autoallocate.
When oracle attempts to extend the segment, it has to extend datafile 1 block.and then 1 block
until autoallocate or uniform size.
and Finally new extent will be allocated to segment.
Is that right?
or
Does oracle have internal algorithm to prevent this poor performace issue?

Hello,
With Locally Managed Tablespace you have 2 options:
- Uniform size
- Autoallocate
With Uniform size you set the size of the Extend (for instance 1 Mo). So it's useful if you have an idea of the Size of your Tables/Indexes
With Autoallocate the size of the Extend depends on the size of the Tables/Indexes.
I mean, the first extend are about 64K then (after the 16th Extend) 1 Mo, then after the N1th extends 8Mo and after the N2th extends 64 Mo.
So by that way the small Tables have only small Extends and large Tables can have larger extends.
This is for the Segment.
For the datafile if you didn't set NEXT option on the Autoextend clause on the Datafile then, the datafile will normally extend by a default value.
Hope it can help,
Best Regards,
Jean-Valentin Lubiez
Edited by: Lubiez Jean-Valentin on Nov 7, 2009 7:49 AM

Similar Messages

  • How to calculate AUTOEXTEND ON NEXT in tablespace clause

    hi
    Please explain How to calculate AUTOEXTEND ON NEXT in tablespace clause.
    whether AUTOEXTEND ON NEXT 50M or 100M or 500M
    Thanks

    174313 wrote:
    hi
    Please explain How to calculate AUTOEXTEND ON NEXT in tablespace clause.
    whether AUTOEXTEND ON NEXT 50M or 100M or 500M
    ThanksThe autoextend size depends on the following :-
    1) Tablespace type Dictionary managed (DMT) or Locally managed (LMT)
    2) Segment space management manual or Auto.
    3) Extent allocation management Autoallocate or uniform.
    If your tablespace is Locally managed with segment management Auto (ASSM) and with extent management is uniform , the autoextend size will be uniform for all the extents , initial and next extents all will be uniform size .
    If your tablespace is Locally managed with segment management Auto (ASSM) and with extent management is autoallocate, Oracle will size the extents automatically starts with 64KB and can go upto 64MB.
    If you have dictionary managed tablespace you will specify the next size at tablespace creation.
    Hope this helps.

  • Autoextend on next size

    hi experts,
    I would like to know what is the best tablespace "autoextend on next" size for the performance of the db?
    oracle 11gR2 on redhat
    users.dbf (is the only tablespace for tables) size is 330 gb
    daily db growth is between 1 gb and 2 gb
    tablespace ddl is:
    CREATE BIGFILE TABLESPACE "USERS" DATAFILE
    'path/users01.dbf' SIZE 268435456000
    AUTOEXTEND ON NEXT 1310720 MAXSIZE 33554431M
    LOGGING ONLINE PERMANENT BLOCKSIZE 8192
    EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEM
    ENT AUTO
    ALTER DATABASE DATAFILE
    'path/users01.dbf' RESIZE 351655690240
    do I undestand it right that the unit of "AUTOEXTEND ON NEXT 1310720" is byte?
    this meand that the minimum autoextend size is 1,25 mb.
    what is the maximum autoextend size per 1 autoextend operation? I havent found any info on this in the documentation.
    how often should the autoextend operation happen for the good performance in the db with much DML ?
    thanks in advance!

    920748 wrote:
    1) there is a SYSTEM EVENT trigger available for extent allocation ?No.
    2) the next (maybe increasing) extent size is predictable for segments in LM tablespaces with ALLOCATION_TYPE=SYSTEM ?Yes, it is predictable. The algorithm isn't published and potentially changes in different versions of Oracle. You can easily enough, though, create a test table, fill it with tons of data, and see the sizes of the extents. However, at the point that you want to do this, you're probably at a point where you shouldn't be using automatic extent allocation. If you want to be able to predict the size of the next extent, use uniform extents.
    Here's an example from askTom that discusses the algorithm in Oracle 9.2.
    3) Oracle will allocate smaller extents if the requested size is not available continuously?No.
    I would like to check remaining tablespace after every extent allocationIt seems highly unlikely that you really want to do this sort of thing every time a new extent is allocated. Presumably, you know roughly how quickly your application's tables are supposed to grow. So, presumably, it's not terribly hard to ensure that you have, say, a month's worth of growth allocated as free space in the tablespace. If you keep a reasonable amount of free space around in general, you can then monitor the free space on a periodic basis (daily maybe even hourly) via a scheduled job and then add more free space at a convenient time whenever your free space drops below whatever threshold you set (in this example, a month). That should give you plenty of time between the threshold being tripped and the system actually running short of space and give you plenty of buffer in case you get swamped by a legitimate increase in activity.
    Justin

  • Paginate 1-15 16-30... without next link?

    I have a report with more than 100 rows in it on some occasions, I have selected Pagination Scheme of Row Ranges 1-15 16-30 (with set pagination) under Layout and Pagination on the Report Attributes tab.
    My problem is with that Next > (and < Previous) link, that appears, when there is more than 75 rows on the report. I understand the meaning of it, but I would like there to be just links 76-90 etc following the others NOT the link Next, because:
    * it might confuse some users, who would think that it leads to the next set of rows not the next set of pagination (eg when viewing rows 1-15 they would expect it to go to rows 16-30, but what it does is to change the pagination set)
    * when looking at a pagination like this I don't know whether there are just 76 rows on the report or over some 1000
    * it appears to be absolutely uncustomizable - I would like to change the image of > to match my web design, but I haven't found a way (except for changing the very image in HTMLDB image directory, which I don't want to do, because some other apps use the same picture and renewing HTMLDB version probably replaces it again). And, I would like to translate it into estonian, but that is also impossible.
    So, is it possible to have all row ranges without that next link? Or is it possible at least customize the link so that it would look as if intended on the place? Or is the only way to make my own pagination with Use Externally Created Pagination Buttons (or is it impossible even then?)?

    though the current implementation of that row ranges pagination scheme doesn't let you not show those previous and next links, you'll find quite a few pagination template customization options available at the bottom of the report template definition pages. you'd be able to enter your estonian Next and Previous strings there, too. you could also consider using application level substitution strings for those Next and Previous strings. that way your app would be more translation-friendly. so you'd define app-level sub strings as something like MY_NEXT_TEXT and MY_PREVIOUS_TEXT and you'd refer to them in your report template's pagination section (in the "Next Page Template" and "Previous Page Template" fields) as &MY_NEXT_TEXT. and &MY_PREVIOUS_TEXT.
    hope this helps,
    raj

  • Recover database without controlfile and redo logs

    Hi guys,
    I am doing a testing with an Oracle Database 11.1.0.7.0, I want recover a database in this scenario without using RMAN:
    -All controlfiles are missing
    -All redo logs are missing
    -I have a Backup Controlfile To Trace Resetlogs (bkp_controlfile.sql)
    -The database is in archivelog mode
    -The database was created with OMF (Oracle Managed Files)
    So I have done this steps:
    1) When the database was opened I rename all controlfiles and all redo logs
    2) Shutdown Abort
    3) I run the bkp_controlfile.sql, here I have a problem...
    The database put in NOMOUNT, the controlfile was created and started the RECOVER DATABASE USING BACKUP CONTROLFILE, but when run ALTER DATABASE OPEN RESETLOGS; appear this:
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1:
    '/u02/app/oracle/oradata/OMF/datafile/o1_mf_system_68hzcb2z_.dbf'I wasn´t expect this because I don´t want recover a datafile, I only want open with resetlogs.
    Any suggestion to help me?
    Thanks a lot.

    Excelent! Thanks for your answers Markus and Hemant.
    In conclusion...
    - If we have all redo logs availables we can recreate the control file and recover the database without any problems using backup controlfile to trace noresetlogs*.
    - if we haven´t all redo logs availables, there are 2 situations:
    1) If the database shutdown properly:_ We will be able to open the database using recover database using backup controlfile until cancel*.
    2) If the database doesn´t shutdown properly:_ We won´t be able to open the database with only a backup controlfile to trace.
    With all this I close this thread. Was very good experience.
    If anyone would add something will be welcome.
    Thanks for all
    I wish add the results of one of my tests: if I did all the steps in only one session of sqlplus I can shutdown properly the database, but if do the shutdown immediate* in a new session I can´t shutdown properly the database. Here I post the output:
    ALL IN ONE SESSION*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    Database opened.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> @/home/oracle/bkp_controlfile.sql
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Control file created.
    SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
    ORA-00279: change 398764 generated at 09/22/2010 14:09:49 needed for thread 1
    ORA-00289: suggestion :
    /u02/app/oracle/flash_recovery_area/OMF/archivelog/2010_09_22/o1_mf_1_40_%u_.arc
    ORA-00280: change 398764 for thread 1 is in sequence #40
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL> ALTER DATABASE OPEN RESETLOGS;
    Database altered.
    SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u02/app/oracle/oradata/OMF/datafile/o1_mf_temp_69n3z3vv_.tmp' SIZE 50331648  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    Tablespace altered.
    SQL>
    ALL IN DIFERENT SESSIONS*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:55:47 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/home/oracle/bkp_controlfile.sql' RESETLOGS;
    Database altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP MOUNT
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    SQL> ALTER DATABASE ARCHIVELOG;
    Database altered.
    SQL> ALTER DATABASE OPEN;
    Database altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> SHUTDOWN IMMEDIATE
    ORA-00210: cannot open the specified control file
    ORA-00202: control file: '/u02/app/oracle/oradata/OMF/controlfile/o1_mf_69n3x6n5_.ctl'
    ORA-27041: unable to open file
    Linux Error: 2: No such file or directory
    Additional information: 3

  • How autoextend affects the performance of a big data load

    I'm doing a bit of reorganization on a datawarehouse, and I need to move almost 5 TB worth of tables, and rebuild their indexes. I'm creating a tablespace por each month, using BIGFILE tablespaces, and assigning to them 600GB, that is the approximate of size of the tables for each month. The process of just assigning the space takes a lot of time, and I decided to try a different approach and change the datafile to AUTOEXTEND ON NEXT 512M, and then run the ALTER TABLE MOVE command to move the tables. The database is Oracle 11g Release 2, and it uses ASM. I was wondering what would be the best approach between these two:
    1. Create the tablespace, with AUTOEXTEND OFF, and assign 600GB to it, and then run the ALTER TABLE MOVE command. The space would be enough for all the tables.
    2. Create the tablespace, with AUTOEXTEND ON, and without assigning more than 1GB, run the ALTER TABLE MOVE command. The diskgroup has enough space for the expected size of the tablespace.
    With the first approach my database is taking 10 minutes approx moving each partition (there's one for each day of the month). Would this number be impacted in a big way if the database has to do an AUTOEXTEND each 512 MB?

    If you measure the performance as the time required to allocate the initial 600 GB data file plus the time to do the load and compare that to allocating a small file and doing the load, letting the data file autoextend, it's unlikely that you'll see a noticable difference. You'll get far more variation just in moving 600 GB around than you'll lose waiting on the data file to extend. If there is a difference, allocating the entire file up front will be slightly more efficient.
    More likely, however, is that you wouldn't count the time required to allocate the initial 600 GB data file since that is something that can be done far in advance. If you don't count that time, then allocating the entire file up front will be much more efficient.
    If you may need less than 600 GB, on the other hand, allocating the entire file at once may waste some space. If that is a concern, it may make sense to compromise and allocate a 500 GB file initially (assuming that is a reasonable lower bound on the size you'll actually need) and let the file extend in 1 GB chunks. That won't be the most efficient approach and you may waste up to a GB of space but that may be a reasonable compromise.
    Justin

  • Are AUTOEXTEND, MAXSIZE settings a headache for a DBA?

    DB Version :10g Release2
    OS version : AIX 5.3
    It seems that if you use AUTOEXTEND AND MAXSIZE while creating a tablespace or adding datafiles to a tablespace, the df -g command of AIX to display avaialable space will not reflect newly added datafiles size. ie if you are using the below command to add a datafile
    ALTER TABLESPACE mydatatbs
      ADD DATAFILE '/u03/oradata/oratest35_mydatatbs02.dbf' SIZE 200M AUTOEXTEND ON NEXT 20M MAXSIZE 4000M;
    Filesystem    GB blocks      Free %Used    Iused %Iused Mounted on
    /dev/hd4           5.00      4.94    2%     3481     1% /
    /dev/hd2           5.00      2.68   47%    44359     7% /usr
    /dev/hd9var        5.00      4.99    1%      454     1% /var
    /dev/hd3          10.00      9.33    7%     2224     1% /tmp
    /dev/hd1          10.00      8.03   20%      773     1% /home
    /proc                 -         -    -         -     -  /proc
    /dev/hd10opt       5.00      4.92    2%     1300     1% /opt
    /dev/fslv00        4.00      0.47   89%    16704    13% /u01
    /dev/fslv01      150.00    136.13   10%     2530     1% /u02
    /dev/fslv02      100.00     99.15    1%       47     1% /u03
    /dev/fslv03      100.00     99.83    1%        9     1% /u04The free space available should be reduced to around 94.15. But it doesn't. But when i omit the AUTOEXTEND and MAXSIZE clause and use a command without AUTOEXTEND and MAXSIZE,
    ALTER TABLESPACE mydatatbs
    ADD DATAFILE '/u03/oradata/oratest35_mydatatbs03.dbf' SIZE 4000M;
    Now the df -g command reflects the 4gb being taken from the File system. Is this AIX's fault? Is it the same for Solaris?

    It is not AIX's fault.
    It is your fault, not reading documentation, dumping your question rightaway, not trying to understand the difference between SIZE and MAXSIZE, which is documented.
    You are quickly entering in the league of some other forum members, who never read docs.
    Sybrand Bakker
    Senior Oracle DBA

  • PSAPSR3 autoextend

    HI Gurus
    can any one guide me how to make table AUTOEXTEND ON. For my system  tablespacePSAPSR3 autoextend is showing off at GUI level(db02),   Where from brtools it is showing for PSAPSR3 autoextend is ON, still space left at file system level...but it is giving dump like
    Database error text........: "ORA-01688: unable to extend table
    SAPSR3./BIC/B0000095000 partition /BIC/B00000950000000000002 by 8192 in
    tablespace PSAPSR3"
    Internal call code.........: "[RSQL/INSR//BIC/B0000095000 ]"
    Please check the entries in the system log (Transaction SM21).
    But why it is showing differnet entries at brtools(psapsr3 autoextend :ON and at GUI level:DB02(psapsr3 autoextend  : OFF)
    How can i change autoextend ON for PSAPSR3 at db02 or using tcode
    Thanks in advance.

    Hi Balaji,
    the big misunderstanding (that of course happens to many others as well) is that the AUTOEXTEND functionality is not a tablespace setting but a datafile setting.
    As DB02 shows you the information just tablespace wise it will report AUTOEXTEND ON as soon as at least one of the datafiles has AUTOEXTEND ON.
    Anyhow: it can happen that Oracle chooses one of the datafiles that are not autoextensible and tries to write data into it. If then the freespace is not sufficient, Oracle won't move to another file and try to store the data there. Instead it will stop that transaction and you see the error e.g. your ORA-1688.
    Therefore, make sure that either none of the datafiles is autoextensible or all of them.
    You can easily check this setting via BRTOOLS:
    (2 - Space management -> 7 - Additional space functions -> 1 = Show tablespaces)
    List of database tablespaces
    Pos.  Tablespace     Type  Status    ExtMan.  SegMan.  Backup  Files/AuExt.
          Total<KB>   Used<%>    Free<KB>  ExtSize<KB>  FreeExt.    Largest<KB>
      1 - PSAPBUT        DATA  ONLINE    LOCAL    AUTO      NO         6/5
          18075712     99.92       13696       819200        10      819200+:4096:1984:1024:1024
      2 - PSAPBUT620     DATA  ONLINE    LOCAL    AUTO      NO         4/4
           8704000     93.62      555520       819200        88      819200+:24576:16384:11200:10240
    As you can see PSAPBUT has 6 datafiles but only 5 of them are set to be autoextensible.
    DB02 will anyhow report that PSAPBUT is autoextensible.
    To change this setting BRTOOLS are just fine.
    The following is an example on my testmachine 'BUT'.
    BR0656I Choice menu 5 - please make a selection
    Database space management
    1 = Extend tablespace
    2 - Create tablespace
    3 - Drop tablespace
    4 - Alter tablespace
    5 - Alter data file
    6 - Move data file
    7 + Additional space functions
    8 - Reset program status
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    5
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.09
    BR0663I Your choice: '5'
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.09
    BR0657I Input menu 85 - please check/enter input values
    BRSPACE options for alter data file
    1 - BRSPACE profile (profile) ....... <initBUT.sap>
    2 - Database user/password (user) ... </>
    3 ~ Alter data file action (action) . <>
    4 ~ Tablespace names (tablespace) ... <>
    5 ~ Data file names (file) .......... <>
    6 - Confirmation mode (confirm) ..... <yes>
    7 - Scrolling line count (scroll) ... <20>
    8 - Message language (language) ..... <E>
    9 - BRSPACE command line (command) .. <-p initBUT.sap -s 20 -l E -f dfalter>
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    4
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.11
    BR0663I Your choice: '4'
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.11
    BR0681I Enter string value for "tablespace" <>:
    PSAPBUT
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.13
    BR0683I New value for "tablespace": 'PSAPBUT'
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.13
    BR0657I Input menu 85 - please check/enter input values
    BRSPACE options for alter data file
    1 - BRSPACE profile (profile) ....... <initBUT.sap>
    2 - Database user/password (user) ... </>
    3 ~ Alter data file action (action) . <>
    4 ~ Tablespace names (tablespace) ... <PSAPBUT>
    5 ~ Data file names (file) .......... <>
    6 - Confirmation mode (confirm) ..... <yes>
    7 - Scrolling line count (scroll) ... <20>
    8 - Message language (language) ..... <E>
    9 - BRSPACE command line (command) .. <-p initBUT.sap -s 20 -l E -f dfalter -t PSAPBUT>
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    c
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.16
    BR0663I Your choice: 'c'
    BR0259I Program execution will be continued...
    BR0291I BRSPACE will be started with options '-p initBUT.sap -s 20 -l E -f dfalter -t PSAPBUT'
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.16
    BR0670I Enter 'c<ont>' to continue, 'b<ack>' to go back, 's<top>' to abort:
    c
    BR0280I BRTOOLS time stamp: 2008-04-16 17.14.17
    BR0257I Your reply: 'c'
    BR0259I Program execution will be continued...
    BR1001I BRSPACE 6.40 (45)
    BR1002I Start of BRSPACE processing: sdxsgncr.dfa 2008-04-16 17.14.17
    BR0484I BRSPACE log file: E:\oracle\BUT\sapreorg\sdxsgncr.dfa
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.19
    BR1009I Name of database instance: BUT
    BR1010I BRSPACE action ID: sdxsgncr
    BR1011I BRSPACE function ID: dfa
    BR1012I BRSPACE function: dfalter
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.19
    BR0656I Choice menu 314 - please make a selection
    Alter data file main menu
    1 - Set data file online
    2 - Set data file offline
    3 - Turn on and maintain autoextend
    4 - Turn off autoextend
    5 - Resize data file
    6 - Show data files
    7 - Show tablespaces
    8 - Show disk volumes
    9 * Exit program
    10 - Reset program status
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    3
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.25
    BR0663I Your choice: '3'
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.28
    BR0659I List menu 315 + please select one or more entries
    List of data files for alter
    Pos.  Tablespace     Status  Type     Size<KB> AuExt. File
       1 - PSAPBUT        ONLINE  FILE     3051520   YES   E:\ORACLE\BUT\SAPDATA1\BUT_1\BUT.DATA1
       2 - PSAPBUT        ONLINE  FILE     3051520   YES   E:\ORACLE\BUT\SAPDATA1\BUT_2\BUT.DATA2
       3 - PSAPBUT        ONLINE  FILE     3031040   YES   E:\ORACLE\BUT\SAPDATA1\BUT_3\BUT.DATA3
       4 - PSAPBUT        ONLINE  FILE     2756672   YES   E:\ORACLE\BUT\SAPDATA4\BUT_4\BUT.DATA4
       5 - PSAPBUT        ONLINE  FILE     3092480   YES   E:\ORACLE\BUT\SAPDATA4\BUT_5\BUT.DATA5
       6 - PSAPBUT        ONLINE  FILE     3092480   NO    E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your selection:
    6
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.33
    BR0663I Your selection: '6'
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.33
    BR0657I Input menu 316 - please check/enter input values
    Options for alter of data file E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6
    1 * Current data file status (status) ....... <FIXSIZE>
    2 * Current data file size in MB (currsize) . <3020>
    3 * Alter data file action (action) ......... <autoext>
    4 # Force offline mode (force) .............. <no>
    5 ? Maximum file size in MB (maxsize) ....... <>
    6 ? File increment size in MB (incrsize) .... <>
    7 # New data file size in MB (size) ......... <>
    8 - SQL command (command) ................... <alter database datafile 'E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6' autoextend on next M maxsize M>
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    5
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.38
    BR0663I Your choice: '5'
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.38
    BR0682I Enter integer value for "maxsize" (0-32767) <>:
    3500
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.48
    BR0683I New value for "maxsize": '3500'
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.48
    BR0657I Input menu 316 - please check/enter input values
    Options for alter of data file E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6
    1 * Current data file status (status) ....... <FIXSIZE>
    2 * Current data file size in MB (currsize) . <3020>
    3 * Alter data file action (action) ......... <autoext>
    4 # Force offline mode (force) .............. <no>
    5 - Maximum file size in MB (maxsize) ....... <3500>
    6 ? File increment size in MB (incrsize) .... <>
    7 # New data file size in MB (size) ......... <>
    8 - SQL command (command) ................... <alter database datafile 'E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6' autoextend on next M maxsize 3500M>
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    6
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.55
    BR0663I Your choice: '6'
    BR0280I BRSPACE time stamp: 2008-04-16 17.14.55
    BR0682I Enter integer value for "incrsize" (1-32767) <>:
    1
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.01
    BR0683I New value for "incrsize": '1'
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.01
    BR0657I Input menu 316 - please check/enter input values
    Options for alter of data file E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6
    1 * Current data file status (status) ....... <FIXSIZE>
    2 * Current data file size in MB (currsize) . <3020>
    3 * Alter data file action (action) ......... <autoext>
    4 # Force offline mode (force) .............. <no>
    5 - Maximum file size in MB (maxsize) ....... <3500>
    6 - File increment size in MB (incrsize) .... <1>
    7 # New data file size in MB (size) ......... <>
    8 - SQL command (command) ................... <alter database datafile 'E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6' autoextend on next 1M maxsize 3500M>
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    6
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.04
    BR0663I Your choice: '6'
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.04
    BR0682I Enter integer value for "incrsize" (1-32767) <1>:
    50
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.05
    BR0683I New value for "incrsize": '50'
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.05
    BR0657I Input menu 316 - please check/enter input values
    Options for alter of data file E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6
    1 * Current data file status (status) ....... <FIXSIZE>
    2 * Current data file size in MB (currsize) . <3020>
    3 * Alter data file action (action) ......... <autoext>
    4 # Force offline mode (force) .............. <no>
    5 - Maximum file size in MB (maxsize) ....... <3500>
    6 - File increment size in MB (incrsize) .... <50>
    7 # New data file size in MB (size) ......... <>
    8 - SQL command (command) ................... <alter database datafile 'E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6' autoextend on next 50M maxsize 3500M>
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    c
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.07
    BR0663I Your choice: 'c'
    BR0259I Program execution will be continued...
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.08
    BR0370I Directory E:\oracle\BUT\sapreorg\sdxsgncr created
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.10
    BR0319I Control file copy created: E:\oracle\BUT\sapreorg\sdxsgncr\cntrlBUT.old 6955008
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.10
    BR1016I SQL statement 'alter database datafile 'E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6' autoextend
    n next 50M maxsize 3500M' executed successfully
    BR1078I Data file E:\ORACLE\BUT\SAPDATA4\BUT_6\BUT.DATA6 altered successfully into status 'autoext
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.10
    BR0340I Switching to next online redo log file for database instance BUT ...
    BR0321I Switch to next online redo log file for database instance BUT successful
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.13
    BR0319I Control file copy created: E:\oracle\BUT\sapreorg\sdxsgncr\cntrlBUT.new 6955008
    BR0280I BRSPACE time stamp: 2008-04-16 17.15.13
    BR0256I Enter 'c<ont>' to continue, 's<top>' to cancel BRSPACE:
    As you see, I just chose to alter a datafile from the tablespace PSAPBUT. Then I got a list of the datafiles and could easily manage the autoextend setting via the menu without having to deal with SQL commands.
    Hope that helps,
    Lars

  • How to autoextend tablespace in Oracle 9i

    Dear All,
    I have currenctly a tablespace ABC. Database is failing to writing. I want to alter tablespace ABC and want to make its AUTOEXTEND ON. Could any body please suggest the SQL Query how to do this.
    Regards,

    Hi,
    It depends on what you really want to do .... Lets suppose that I want to enable autoextend feature on my datafile 4 below that belongs to tablespace ABC. I have some options:
    SYS> select file_id,file_name from dba_data_files where tablespace_name='ABC';
       FILE_ID FILE_NAME
             4 C:\ORACLE\ORADATA\DB01\ABC01.DBF
    SYS> alter database datafile 4 autoextend on maxsize unlimited;
    Banco de dados alterado.
    or
    SYS> alter database datafile 'C:\ORACLE\ORADATA\DB01\ABC01.DBF' autoextend on next 5m maxsize 900m;
    Banco de dados alterado.For more detailed information, you can take a look at documentation
    Cheers
    Legatti

  • Online backup without PSAPTEMP

    Hello,
    one question, i have recover a database 10.2.0.2 from a online backup.
    before i have delete all files in the sapdata's.
    the database and the sap-system runs well.
    now i became this error:
    orasms> brbackup -q
    BR0051I BRBACKUP 7.00 (18)
    BR0055I Start of database backup: bdvwpovw.qub 2007-08-08 16.29.28
    BR0477I Oracle pfile /oracle/SMS/102_64/dbs/initSMS.ora created from spfile /oracle/SMS/102_64/dbs/spfileSMS.ora
    BR0280I BRBACKUP time stamp: 2007-08-08 16.29.29
    BR0301E SQL error -1187 at location BrDbfInfoGet-1, SQL statement:
    'OPEN curs_3 CURSOR FOR'
    'SELECT TS.TABLESPACE_NAME, TS.STATUS, TS.BLOCK_SIZE, TS.CONTENTS, TS.EXTENT_MANAGEMENT, DF.FILE_NAME, DF.FILE_ID, NVL(DF.STATUS, ' '), NVL(DF.BYTES, 0), NVL(DF.AUTOEXTENSIBLE, 'NO'), NVL(DF.MAXBYTES, 0), NVL(DF.INCREMENT_BY, 0) FROM DBA_TABLESPACES TS, DBA_DATA_FILES DF WHERE TS.TABLESPACE_NAME = DF.TABLESPACE_NAME UNION ALL SELECT TS.TABLESPACE_NAME, TS.STATUS, TS.BLOCK_SIZE, TS.CONTENTS, TS.EXTENT_MANAGEMENT, TF.FILE_NAME, TF.FILE_ID * -1, NVL(TF.STATUS, ' '), NVL(TF.BYTES, 0), NVL(TF.AUTOEXTENSIBLE, 'NO'), NVL(TF.MAXBYTES, 0), NVL(TF.INCREMENT_BY, 0) FROM DBA_TABLESPACES TS, DBA_TEMP_FILES TF WHERE TS.TABLESPACE_NAME = TF.TABLESPACE_NAME ORDER BY 1, 6'
    ORA-01187: cannot read from file 255 because it failed verification tests
    ORA-01110: data file 255: '/oracle/SMS/sapdata1/temp_1/temp.data1'
    BR0314E Collection of information on database files failed
    BR0056I End of database backup: bdvwpovw.qub 2007-08-08 16.29.29
    BR0280I BRBACKUP time stamp: 2007-08-08 16.29.29
    BR0054I BRBACKUP terminated with errors
    orasms>
    the file oracle/SMS/sapdata1/temp_1/temp.data1 come not with the online-backup.
    in my other systems with oracle 9.2. i find the psaptemp in the protocol from online-backup. is this new with oracle 10... ?? how can i create the tablespace psaptemp ?
    Thanks !

    most probably PSAPTEMP is now temporary locally managed. If this is the case, it is not backed up with brbackup and you must create it's datafile. Check in the backup controlfile to know how to create them:
    sqlplus / as sysdba
    ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/oracle/SMS/CONTROLFILE_TRACE.txt' reuse;
    exit
    then, add the temp datafile such as :
    ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/SMS/sapdata1/TEMP_1/TEMP.DATA1' SIZE 20704M REUSE AUTOEXTEND ON NEXT 67108864  MAXSIZE 24000M;
    good luck

  • View value of NEXT parameter of data file

    Good day!
    How can I view|query value of NEXT parameter (property of data file)
    For example, when I create tablespace or add datafile, I can set up value for this parameter:
    create tablespace ....
    autoextend on
    next 10M
    Bun I couldn't find value of this parameter in any table of view.

    I think it is right for tablespace scope, but not for datafile, because tablespace may consist of several datafiles
    I find useful information in dba_data_files table and INCREMENT_BY column (in db blocks)

  • Undo tablespace growing without reusing space

    Hi,
    I'm running an Oracle9i database on Solaris. I am using the automatic undo management and I have one undo tablespace. The UNDO_RETENTION value is 900. I have created the undo tablespace this way (clause in create database statement):
    UNDO TABLESPACE "UNDOTBS1" DATAFILE '/u04/oracle/oradata/my_dbname/undotbs01.dbf' SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    The undo tablespace datafile is now close to 3G. I have other servers running the same setup, and their undo datafile size is still 200M. There is currently no active transaction in the database. Any idea why this is happening? Is there any tables I can check for clues?
    Many thanks,
    Gloria

    Should Oracle automatically shrink the undo tablespace (datafile) when it is not needed anymore? Say at one point the database really needs 3G of undo tablespace, but afterwards only 10M is needed, would the datafile be 'shrunk' back?
    Also, how can I check if the database really needed the 3G of undo tablespace at one point? (I guess it's checking the level of activities in the database, but how do I do that for past data?)
    I'm trying to decide whether the undo tablespace really grew due to a need at some point or is it a case of Bug 2660394 (documented in metalink note271119.1). The bug basically says that "An auto extensible undo tablespace MAY grow before reusing expired extents leading to more space use than actually needed".

  • Autoextend tablespace query question

    I set my regular tablespace datafile to autoextend the next 400 meg up until 1 gig. What query can I use to see what these two values are when I know a datafile is set to be autoextend, but I also want to know what the next and max values were set to when that dba set that datafile to be autoextend. I know this time because I know I ran the alter database datafile autoextend command with next 400 and maxsize 1 gig, but what if I didn't know that?
    What is the query?
    Thanks,
    --Justin                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    SQL> desc dba_data_files
    Name                            Null?    Type
    FILE_NAME                             VARCHAR2(513)
    FILE_ID                             NUMBER
    TABLESPACE_NAME                        VARCHAR2(30)
    BYTES                                  NUMBER
    BLOCKS                              NUMBER
    STATUS                              VARCHAR2(9)
    RELATIVE_FNO                             NUMBER
    AUTOEXTENSIBLE                         VARCHAR2(3)
    MAXBYTES                             NUMBER
    MAXBLOCKS                             NUMBER
    INCREMENT_BY                             NUMBER
    USER_BYTES                             NUMBER
    USER_BLOCKS                             NUMBER
    ONLINE_STATUS                             VARCHAR2(7)

  • AUTOEXTEND ON IN TABLESPACE

    Hi
    In the create tablespace script i found that below ' AUTOEXTEND ON NEXT 8K ' this 8k is default parameter or is it taking the block size specified in pfile.
    I s there any parameter to that we have to specify in pfile.
    As a i read in article using ' alter tablespace <tbsname> autoextend on next 20g'
    CREATE TABLESPACE TS_GR DATAFILE
    '+DATA/grdcimd1/datafile/ts_gr_01.dbf' SIZE 6689472K AUTOEXTEND ON NEXT 8K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    SEGMENT SPACE MANAGEMENT AUTO;

    ora wrote:
    Hi
    In the create tablespace script i found that below ' AUTOEXTEND ON NEXT 8K ' this 8k is default parameter or is it taking the block size specified in pfile.
    I s there any parameter to that we have to specify in pfile.There is no parameter to be specified in pfile.
    You need to mention the parameter in create tablespace command or you can alter it using alter tablespace command.
    Regards
    Rajesh

  • Autoextend ON question

    To enable autoextend on a datafile, we issue something similar to the following:
    alter database datafile '<file_name>' autoextend on next 100m maxsize 4g;
    So, what is the default value for "next" and "maxsize" ?
    I mean, what will be the value of next & maxsize, If I run a command such as :
    alter database datafile '<file_name>' autoextend on;
    Thanks.

    Hi,
    Default maxsize is dependent on the datablock size of the datafile. For an 8k blocksize, if i don't set autoextend on the default is 32G and it is also the maximum size which you can achieve for a data file with 8k block size.
    If my block size is 16K, the default maxsize will be 64 g and this is also the maximum size for the data file which you can have for a 16k block size tablespace
    Salman

Maybe you are looking for