Autoextend on/off

Hi,
In NW2004s BI7, under windows 2003 server, oracle 10g plateform I am trying to change Autoextend On
1. login sql as system
2. SELECT * from dba_data_files where tablespace_name = 'PSAPSR3DB';
3. its shows all table name with path
4. ALTER DATABASE DATAFILE 'F:\ORACLE\PIP\SAPDATA4\SR3DB_1\SR1.DATA1' AUTOEXTEND ON;
5. ALTER DATABASE DATAFILE 'F:\ORACLE\PIP\SAPDATA4\SR3DB_2\SR1.DATA2' AUTOEXTEND ON;
6. ALTER DATABASE DATAFILE 'F:\ORACLE\PIP\SAPDATA4\SR3DB_3\SR1.DATA3' AUTOEXTEND ON;
COMMIT;
But when I check DB02 and Tablespace --> overview (still shows autoextend off)
how to I fixed that
Regards;

Hi Kishore Soma,
Thanks for reply,
login sqlplus /as sysdba
I tried 10 times commit;
Restart SAP and DB instance
DB02OLD and refresh (perform database check and db check and updates)
Still PSAPSR3700 table space shows autoextend NO
any other clue... or what is the normal procedure to change autoextend YES

Similar Messages

  • Maxsize 0 after autoextend turned off for Temp tablespace!

    Hi,
    DB:11.1.0.7
    We had earlier the tempfiles with maxszie unlimited as below:
    select FILE_NAME,TABLESPACE_NAME,BYTES/(1024*1024) "Size",MAXBYTES/(1024*1024) "Maxsize",AUTOEXTENSIBLE from dba_temp_files;
    February 10, 2011 Tablespace used by DEV database
    ===================================
    FILE_NAME
    TABLESPACE_NAME Size Maxsize AUT
    /oradata/DEV/temp01.dbf
    TEMP 1024 32767.9844 YES
    /oradata/DEV/temp02.dbf
    TEMP 1024 32767.9844 YES
    /oradata/DEV/temp03.dbf
    TEMP 3072 32767.9844 YES
    Now after turning autoextend off, why maxsize is showing as '0' instead of being at unlimited as earlier?
    Please see below:
    select FILE_NAME,TABLESPACE_NAME,BYTES/(1024*1024) "Size",MAXBYTES/(1024*1024) "Maxsize",AUTOEXTENSIBLE from dba_temp_files;
    February 10, 2011 Tablespace used by DEV database
    ===================================
    FILE_NAME
    TABLESPACE_NAME Size Maxsize AUT
    /oradata/DEV/temp01.dbf
    TEMP 1024 0 NO
    /oradata/DEV/temp02.dbf
    TEMP 1024 0 NO
    /oradata/DEV/temp03.dbf
    TEMP 3072 0 NO
    Could anyone please explain?
    Thanks for your time!
    Regards,

    Handle:      user10088255
    Status Level:      Newbie
    Registered:      Mar 4, 2009
    Total Posts:      87
    Total Questions:      62 (62 unresolved)
    so many questions without ANY answers.
    http://forums.oracle.com/forums/ann.jspa?annID=718

  • Tablespace Autoextend

    Hi
    In our R/3 landscape, the status of some of the tablespaces is "autoextend On" and some are "autoextend off" mode. We would like to turn the autoextnd mode OFF from ON.
    What is the best way to turn the autoextend mode OFF. As per my understanding, if we turn off all the datafiles of the tablespace using SQLPLUS , it will automatically change the status of the autoextend mode from ON to OFF.
    Pls confirm or suggest any other method to turn tablespace autoextend mode OFF.
    Regards
    Amar

    Hi,
    Use SQL. Don't know any other tool thats used for changing the mode.
    Cheers,
    Kedar

  • Adding data file with out using  brtools /sapdba

    Hi all,
    How to add data file to table spaces with out using  brtools /sapdba.Please let meknow.
    Satya.

    why would you do that? whats your requirement?
    You can use sql commands (I prefer doing it via brtools),
    example
    alter tablespace <name of the tablespace> add datafile '<path of the datafile>' size <size in Mb>M autoextend <on/off> next <size> maxsize <size>;
    regards
    Juan

  • Hard Disk filling up on AIX

    I am running Oracle 9.2.0.1.0 on AIX 5.5.1. We are experiencing problems in that our /ora1 file system, which is the mount point where Oracle is installed and our one database has its control files, system tablespace, and undo tablespace (the other database files for this database are on another file system). All of those datafiles have autoextend turned off.
    For the past week, I have been deleting as much stuff as I could, even to the extent of blowing away our development database (which really only freed up about 500 MB, since it also only had its control, system, and undo files there), and the file system keeps filling up. What could be causing this?
    I'm also only marginally good at unix, is there an easy command I can run to see what files have a timestamp in the past 24 hours (since I blew away my development database)?
    Thanks!
    Marcia Thomasson

    Nevermind, I found the problem. For anyone else who is interested, the database was running in archive log mode. It wasn't supposed to be, since this is a QA database and not a production database. The archive logs were filling up the hard disk.

  • How to deal with tablespaces in Oracle XE (10g)

    Hi,
    First want to say I'm not a DBA so my knowledge on how to work with tablespaces is very limited. I built an application in Apex 3.2.1 on Oracle XE 10g and today for the first time I received this error when trying to save information to the database:
    ORA-01691: Unable to extend lob segment by .... for table space FLOW....
    What is the best way to deal with this? For now, after doing some google searching, I set my tablespace to AUTOEXTEND (it had reached about 500MB which was its max size). Is this the correct way to deal with this situation? Or should I create a new tablespace? I've never changed any of the default settings/tablespaces that came with the Apex/Oracle XE installation.
    Any advice would be greatly appreciated....
    Thanks,
    Francois
    Edited by: HighTen76 on May 1, 2012 2:02 PM

    ORA-01691: Unable to extend lob segment by .... for table space FLOW....
    It seem related to tablespace is full and not able to extend more due to low hdd space or autoextend off or xe datasize limit(4g) reached!!!!
    SELECT sum(BYTES/1024)/1024 AS SIZE_IN_MB FROM DBA_DATA_FILES;
    SIZE_IN_MB must not be more then 4gb
    If SIZE_IN_MB is less then 4g then check that Autoextend is off or on.
    I hope this help
    Regards
    Hitgon
    Edited by: hitgon on May 2, 2012 12:26 PM

  • Undo tablespace problem

    Hello, I was processing a batch job that commits every 5,000 records. I have the UNDO_RETENTION set to 10,800. UNDO_MANAGEMENT is set to AUTO. at some point the database shut down
    with the following errors in the alert log:
    ORA-1654: unable to extend index CRM.XIF35CUSTOMER by 16 in tablespace      RCRMCUSTIX01
    ORA-1654: unable to extend index CRM.XIF35CUSTOMER by 16 in tablespace      RCRMCUSTIX01
    ORA-1654: unable to extend index CRM.XIF35CUSTOMER by 16 in tablespace      RCRMCUSTIX01
    ORA-1654: unable to extend index CRM.XIF35CUSTOMER by 16 in tablespace      RCRMCUSTIX01
    Fri Jun 09 02:19:48 2006
    KCF: write/open error block=0x1faa4f online=1
    file=2 C:\ORACLE\ORADATA\CRMMGG\UNDOTBS01.DBF
    error=27069 txt: 'OSD-04026: Invalid parameter passed. (OS 2075215)'
    Fri Jun 09 02:19:48 2006
    Errors in file c:\oracle\admin\crmmgg\bdump\crmmgg_dbw0_20680.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01114: IO error writing block to file 2 (block # 2075215)
    ORA-01110: data file 2: 'C:\ORACLE\ORADATA\CRMMGG\UNDOTBS01.DBF'
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
    OSD-04026: Invalid parameter passed. (OS 2075215)
    I noticed the the undo datafile is over 16GB. I reset the UNDO_RETENTION to 5 seconds. The undo tablespace data file is staying at 16GB. Is there any way to shring this file. It is a test DB so I can rebuild if necessary. What is the best way to recover from this? Thak you,
    David

    You are facing a generic problem on Windows platforms, when datafiles configured as AUTOEXTEND ON reach a 4GB boundary (4GB,8GB,...). The best way to avoid the problem is switch AUTOEXTEND to OFF and define the appropriate number of single datafiles for the tablespace. From metalink:
    ALERT: Problems with Datafile AUTOEXTEND/RESIZE on NT/2000 Platforms
    Doc ID:148894.1
    Werner

  • Tablespaces are 100% full

    Hi All,
    In our SAP ECC 6.0 system 3 tablespaces are full. ( 100% used ) but file settings for these tablespaces is AUTO Extend ON .( oracle version is 10.2.0 )
    We have sufficient space at file system level.
    Please suggest:
    1. Should I have to add files to those tablespaces or no need ?
    2. Shall I change file settings from Auto Extend On to Off at any time with SQL or BRtools?
    Thanks & Regards,
    Veera

    >>1. One of my BASIS colleague suggested to add 4gb space to existing datafile ? How can I extend 4GB space to a data file which is autoextend ON?
    Autoextend on / off has advantage and disadvantages.
    You datafile automatically extended as the data grow. But you need to make sure the disk has sufficient freespace. Also make sure your tablespaces not growing fastly.
    What's you monthly DB growth. If below 10 GB then I suggest you can swith off autoextend and add 32 GB datafile and add more space as you need in future. This way you will have control on your DB growth and also filesystem (disk)
    Both option requires monitoring of your DB and filesystems.
    >>2. If tablespace are 100% ( file settings are auto extend on ) full will it effect on performance.
    There is no performance impact but depends how much size you are extending you datafile by. If you extened you db by less than 1GB or so you may have some performance issue.

  • ORA-1652: unable to extend temp segment by 187502

    Hi ,
    OS=AIX 5.2
    DB= Oracle8i , 8.1.7.4.0.
    I've seen few ORA-1652 in alert log file, and the TS that it shows with error is permanant and dictionary managed Tablespace as there is no temporary tablespace in the database, its autoextend is off.
    This Tablespace is of total 13 GB , with 2 datafiles (9G + 4 G). one datafile is almost 30 % Free the other is 80 % free. that shows that there is enough free space in the tablespace and on the filesystem there is also enough freespace.
    initital extent and next extent are 1 Mb with pct increase 10.
    If somebody can help to solve out this issue, and why this error occured.
    Thanks in advance!

    Are you sure the user runing the large sort is using the right temp-tablespace?
    If not then he uses the system tablespace for temp, and that might be something you should not want.
    And if i am correct Oracle does not clean out the temp-tablespace in ways of showing the free space it actualy has. At least in Oracle 9 this is the case, the temp tablespace will show a used percentage of what it ever was used and not how much actualy is being used. It can be free actualy, but showing a 100% used in the tablespace-list (in the oracle enterprise manager).
    This makes me feel that if you say the temp-tablespace still has unused space, the query does not use the right temp-tablespace.

  • Exponential Growth of LOBSEGMENTS

    I have an oracle 9i database that has many tables, lobindexes and lobsegments. The tablespace under which these items are located was originally sized as 500 MB. Autoextend is off. 1,000 of inserts affect these tablespaces daily. During this time, I see the lobsegments growing quite large so that soon it no longer fits within the confines of the 500 MB size. I add additional datafiles, but it only helps for a while. Can these old lobsegments be recycled? Is there some setting I'm missing that causing this problem?
    The segment breakdown is as follows:
    OWNER BYTES
    TESTTBSP 3,145,089,024
    OWNER type name BYTES
    TESTTBSP TABLE T_SECTIONMARKER_USAGE 516,096
    TESTTBSP TABLE T_OUTPUTDEVICE_USAGE 516,096
    TESTTBSP TABLE T_STREAMRECIPIENT_USAGE 516,096
    TESTTBSP TABLE T_MARKERDEVICE_USAGE 516,096
    TESTTBSP TABLE T_JOBRUN 516,096
    TESTTBSP TABLE T_REVISIONUNIT 516,096
    TESTTBSP TABLE T_USEREXIT_FUNCTIONS 516,096
    TESTTBSP TABLE T_WORKFLOWDATA 516,096
    TESTTBSP TABLE T_WORKFLOWACCESS 516,096
    TESTTBSP TABLE T_WORKFLOWSTATUS 516,096
    TESTTBSP TABLE T_WORKFLOWDEF 516,096
    TESTTBSP TABLE T_ACCESSRIGHT 516,096
    TESTTBSP TABLE T_USER 516,096
    TESTTBSP TABLE T_RULEUSAGE 516,096
    TESTTBSP TABLE T_DOCUMENT 516,096
    TESTTBSP TABLE T_LICENSEDMACHINES 516,096
    TESTTBSP TABLE EXTENDED_FONTFILE 516,096
    TESTTBSP TABLE T_JOBS 516,096
    TESTTBSP TABLE EXTENDED_XIMAGE 516,096
    TESTTBSP TABLE IMAGEFAMILY_USAGE 516,096
    TESTTBSP TABLE T_BARCODEUSE 516,096
    TESTTBSP TABLE T_BARCODES 516,096
    TESTTBSP TABLE T_OPRECIPIENTS 516,096
    TESTTBSP TABLE T_DISTRIBUTIONDEF 516,096
    TESTTBSP TABLE T_FORMATDEF 516,096
    TESTTBSP TABLE T_CRUUID 516,096
    TESTTBSP TABLE T_VARIABLEOPFIELDMAPPING 516,096
    TESTTBSP TABLE T_APPATTRSET 516,096
    TESTTBSP TABLE T_CONTENTLOCK 516,096
    TESTTBSP TABLE T_DEFAULTLOCALES 516,096
    TESTTBSP TABLE T_LOCALE 516,096
    TESTTBSP TABLE T_IDGENERATOR 516,096
    TESTTBSP TABLE T_VARIABLEFORMATPATTERNS 516,096
    TESTTBSP TABLE T_RULESDBLOCATION 516,096
    TESTTBSP TABLE T_WORKITEM_HISTORY 516,096
    TESTTBSP TABLE T_PRINTINFO 516,096
    TESTTBSP TABLE T_MAILINFO 516,096
    TESTTBSP TABLE T_LICENSEDCOMPONENTS 516,096
    TESTTBSP TABLE T_LICENSEDATA 516,096
    TESTTBSP TABLE T_QUEUEDASSEMBLEDDOCS 516,096
    TESTTBSP TABLE T_OPVALUES 516,096
    TESTTBSP TABLE T_OPFIELDS 516,096
    TESTTBSP TABLE T_OPMAPPING 516,096
    TESTTBSP TABLE T_CUSTOMERTABLES 516,096
    TESTTBSP TABLE T_CUSTOMDATASOURCE 516,096
    TESTTBSP TABLE T_DATASOURCEGROUP 516,096
    TESTTBSP TABLE T_ATTRCOLMAP 516,096
    TESTTBSP TABLE T_ATTRSETATTRIBUTES 516,096
    TESTTBSP TABLE T_ATTRSETTABLE 516,096
    TESTTBSP TABLE T_VALIDVALUE 516,096
    TESTTBSP TABLE T_ATTRDEF 516,096
    TESTTBSP TABLE T_PRECOMPOSEDPAGEATTR 516,096
    TESTTBSP INDEX SYS_C001896 516,096
    TESTTBSP INDEX SYS_C001891 516,096
    TESTTBSP INDEX SYS_C001888 516,096
    TESTTBSP INDEX PK_T_STREAMDISTRIBUTIONOUTPUT 516,096
    TESTTBSP INDEX SYS_C001878 516,096
    TESTTBSP LOBINDEX SYS_IL0000006687C00004$$ 516,096
    TESTTBSP INDEX SYS_C001877 516,096
    TESTTBSP LOBINDEX SYS_IL0000006683C00003$$ 516,096
    TESTTBSP INDEX SYS_C001876 516,096
    TESTTBSP LOBINDEX SYS_IL0000006678C00007$$ 516,096
    TESTTBSP INDEX SYS_C001873 516,096
    TESTTBSP INDEX SYS_C001868 516,096
    TESTTBSP INDEX SYS_C001865 516,096
    TESTTBSP INDEX WORKFLOWSTATUS_INDEX 516,096
    TESTTBSP INDEX SYS_C001862 516,096
    TESTTBSP INDEX SYS_C001859 516,096
    TESTTBSP INDEX T_ACCESSRIGHT_INDEX1 516,096
    TESTTBSP INDEX SYS_C001857 516,096
    TESTTBSP INDEX SYS_C001854 516,096
    TESTTBSP INDEX INX_RULEUSAGE1 516,096
    TESTTBSP INDEX SYS_C001957 516,096
    TESTTBSP INDEX SYS_C001956 516,096
    TESTTBSP LOBINDEX SYS_IL0000006770C00007$$ 516,096
    TESTTBSP INDEX SYS_C001955 516,096
    TESTTBSP INDEX SYS_C001954 516,096
    TESTTBSP INDEX SYS_C001946 516,096
    TESTTBSP INDEX SYS_C001944 516,096
    TESTTBSP INDEX SYS_C001942 516,096
    TESTTBSP INDEX PK_EXTEXT_ID 516,096
    TESTTBSP INDEX INX_CONTENTGROUP 516,096
    TESTTBSP INDEX INX_RULEELEMENT2 516,096
    TESTTBSP INDEX INX_RULELEMENTUSG2 516,096
    TESTTBSP INDEX INX_RULEELEMENT 516,096
    TESTTBSP INDEX INX_RULEELEMENTUSG 516,096
    TESTTBSP INDEX SYS_C001976 516,096
    TESTTBSP INDEX SYS_C001975 516,096
    TESTTBSP LOBINDEX SYS_IL0000006798C00004$$ 516,096
    TESTTBSP INDEX SYS_C001974 516,096
    TESTTBSP INDEX SYS_C001973 516,096
    TESTTBSP LOBINDEX SYS_IL0000006792C00003$$ 516,096
    TESTTBSP INDEX SYS_C001972 516,096
    TESTTBSP INDEX SYS_C001968 516,096
    TESTTBSP INDEX SYS_C001967 516,096
    TESTTBSP INDEX PK_RECIPIENT_USAGE 516,096
    TESTTBSP INDEX SYS_C001959 516,096
    TESTTBSP INDEX SYS_C001958 516,096
    TESTTBSP LOBINDEX SYS_IL0000006776C00005$$ 516,096
    TESTTBSP INDEX GENXMLIDX6201 516,096
    TESTTBSP INDEX PK_MARKER_NAME 516,096
    TESTTBSP INDEX PK_MARKER_ID 516,096
    TESTTBSP LOBINDEX SYS_IL0000007899C00004$$ 516,096
    TESTTBSP INDEX UN_DEVICE_NAME 516,096
    TESTTBSP INDEX PK_DEVICE_ID 516,096
    TESTTBSP LOBINDEX SYS_IL0000007893C00004$$ 516,096
    TESTTBSP INDEX UN_STAMP_NAME 516,096
    TESTTBSP INDEX PK_STAMP_ID 516,096
    TESTTBSP LOBINDEX SYS_IL0000007887C00004$$ 516,096
    TESTTBSP INDEX UN_STREAM_NAME 516,096
    TESTTBSP INDEX PK_PUBLISHSTREAM 516,096
    TESTTBSP LOBINDEX SYS_IL0000007881C00003$$ 516,096
    TESTTBSP INDEX UN_NAME 516,096
    TESTTBSP INDEX PK_USEREXIT_ID 516,096
    TESTTBSP INDEX IND_CRC 516,096
    TESTTBSP INDEX PK_JOBRUN_ID 516,096
    TESTTBSP TABLE T_SESSIONLIST 516,096
    TESTTBSP TABLE TEMP_T_DLSTRANS 516,096
    TESTTBSP TABLE T_NOTES 516,096
    TESTTBSP TABLE T_ECM_SERVER 516,096
    TESTTBSP TABLE T_ECM_CONFIG 516,096
    TESTTBSP TABLE T_CLIENTNOTES 516,096
    TESTTBSP TABLE T_ARCHIVEINFO 516,096
    TESTTBSP TABLE T_REVISIONUNIT_ATTR 516,096
    TESTTBSP TABLE T_JOBDOCRUN 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006611C00006$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006603C00003$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006736C00002$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006808C00017$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006808C00014$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006808C00012$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006696C00007$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006715C00003$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006707C00003$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006702C00008$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006687C00004$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006683C00003$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006678C00007$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006770C00007$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006798C00004$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000006792C00003$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000007899C00004$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000007893C00004$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000007887C00004$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000007881C00003$$ 516,096
    TESTTBSP INDEX INX_ARCHIVEINFO 516,096
    TESTTBSP INDEX PK_NOTE_ID 516,096
    TESTTBSP INDEX PK_ECMSERVER_ID 516,096
    TESTTBSP INDEX PK_ECMCONFIG_ID 516,096
    TESTTBSP INDEX SYS_C002073 516,096
    TESTTBSP LOBINDEX SYS_IL0000007929C00003$$ 516,096
    TESTTBSP INDEX PK_T_RU_ATTR 516,096
    TESTTBSP LOBINDEX SYS_IL0000007925C00002$$ 516,096
    TESTTBSP INDEX PK_DLSTRANS_ID 516,096
    TESTTBSP INDEX PK_ARCHIVE_ID 516,096
    TESTTBSP INDEX PK_JOBDOCRUN_ID 516,096
    TESTTBSP INDEX PK_JOBSTEPRUN_ID 516,096
    TESTTBSP INDEX SYS_C001831 516,096
    TESTTBSP INDEX SYS_C001829 516,096
    TESTTBSP INDEX SYS_C001827 516,096
    TESTTBSP INDEX CATEGORY_INDEX 516,096
    TESTTBSP INDEX SYS_C001825 516,096
    TESTTBSP INDEX SYS_C001822 516,096
    TESTTBSP INDEX SYS_C001819 516,096
    TESTTBSP INDEX SYS_C001815 516,096
    TESTTBSP INDEX SYS_C001812 516,096
    TESTTBSP INDEX DATASINDEX 516,096
    TESTTBSP INDEX SYS_C001809 516,096
    TESTTBSP LOBINDEX SYS_IL0000006611C00006$$ 516,096
    TESTTBSP INDEX GRPINDEX 516,096
    TESTTBSP INDEX SYS_C001806 516,096
    TESTTBSP LOBINDEX SYS_IL0000006603C00003$$ 516,096
    TESTTBSP INDEX INX_ATTRSETTABLE 516,096
    TESTTBSP INDEX INX_ATTRDEF 516,096
    TESTTBSP INDEX SYS_C001803 516,096
    TESTTBSP INDEX SYS_C001800 516,096
    TESTTBSP INDEX ATINDEX 516,096
    TESTTBSP INDEX SYS_C001797 516,096
    TESTTBSP INDEX SYS_C001792 516,096
    TESTTBSP INDEX SYS_C001790 516,096
    TESTTBSP INDEX SYS_C001787 516,096
    TESTTBSP INDEX SYS_C001786 516,096
    TESTTBSP INDEX SYS_C001785 516,096
    TESTTBSP LOBINDEX SYS_IL0000006581C00002$$ 516,096
    TESTTBSP INDEX IND_DATAID 516,096
    TESTTBSP INDEX SYS_C001784 516,096
    TESTTBSP INDEX INDEX_ST201 516,096
    TESTTBSP INDEX SYS_C002025 516,096
    TESTTBSP INDEX GENXMLIDX6101 516,096
    TESTTBSP INDEX GENXMLIDX5101 516,096
    TESTTBSP INDEX INDEX_MT101 516,096
    TESTTBSP INDEX SYS_C002023 516,096
    TESTTBSP INDEX INDEX_ST101 516,096
    TESTTBSP INDEX SYS_C002021 516,096
    TESTTBSP INDEX IND_MVUSAGEID 516,096
    TESTTBSP INDEX PK_MV_PK 516,096
    TESTTBSP INDEX IND_SVCONTENTID 516,096
    TESTTBSP INDEX IND_PRODUCTID 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000007929C00003$$ 516,096
    TESTTBSP LOBSEGMENT SYS_LOB0000007925C00002$$ 516,096
    TESTTBSP INDEX PK_USAGE_ID 516,096
    TESTTBSP INDEX INX_RULEUSAGE16 516,096
    TESTTBSP INDEX INX_RULEUSAGE10 516,096
    TESTTBSP INDEX INX_T_RULE 516,096
    TESTTBSP INDEX INX_RULEUSAGE8 516,096
    TESTTBSP INDEX INX_RULE2 516,096
    TESTTBSP INDEX INX_RULE1 516,096
    TESTTBSP INDEX INX_RULEUSAGE5 516,096
    TESTTBSP INDEX INX_RULEUSAGE4 516,096
    TESTTBSP INDEX INX_RULEUSAGE3 516,096
    TESTTBSP INDEX INX_RULEUSAGE2 516,096
    TESTTBSP INDEX INX_PRINTINFO 516,096
    TESTTBSP INDEX INX_MAILINFO 516,096
    TESTTBSP INDEX SYS_C001939 516,096
    TESTTBSP INDEX PK_MAIL_ID 516,096
    TESTTBSP INDEX SYS_C001932 516,096
    TESTTBSP INDEX SYS_C001931 516,096
    TESTTBSP LOBINDEX SYS_IL0000006736C00002$$ 516,096
    TESTTBSP INDEX SYS_C001929 516,096
    TESTTBSP INDEX OPINDEX 516,096
    TESTTBSP INDEX SYS_C001926 516,096
    TESTTBSP INDEX SYS_C001922 516,096
    TESTTBSP INDEX SYS_C001917 516,096
    TESTTBSP LOBINDEX SYS_IL0000006724C00002$$ 516,096
    TESTTBSP INDEX SYS_C001915 516,096
    TESTTBSP INDEX PK_PAGESEQUENCES 516,096
    TESTTBSP INDEX PK_SUBDOCS_IDS 516,096
    TESTTBSP INDEX PK_REFERENCE_ID 516,096
    TESTTBSP INDEX PK_DOCBASENAME 516,096
    TESTTBSP INDEX PK_LOGICTRAY_ID 516,096
    TESTTBSP INDEX PK_CS_USAGE_ID 516,096
    TESTTBSP INDEX PK_OPFIELDMAPPING 516,096
    TESTTBSP INDEX SYS_C001851 516,096
    TESTTBSP INDEX SYS_C001848 516,096
    TESTTBSP INDEX DLINDEX1 516,096
    TESTTBSP INDEX SYS_C001847 516,096
    TESTTBSP INDEX SYS_C001844 516,096
    TESTTBSP INDEX SYS_C001842 516,096
    TESTTBSP INDEX SYS_C001840 516,096
    TESTTBSP INDEX SYS_C001839 516,096
    TESTTBSP INDEX SYS_C001838 516,096
    TESTTBSP INDEX UN_JOBDEF_NAME 516,096
    TESTTBSP INDEX PK_JOBDEF_JOB_ID 516,096
    TESTTBSP INDEX SYS_C001834 516,096
    TESTTBSP INDEX SYS_C001985 516,096
    TESTTBSP INDEX SYS_C001984 516,096
    TESTTBSP INDEX SYS_C001983 516,096
    TESTTBSP INDEX SYS_C001982 516,096
    TESTTBSP INDEX SYS_C001979 516,096
    TESTTBSP LOBINDEX SYS_IL0000006808C00017$$ 516,096
    TESTTBSP LOBINDEX SYS_IL0000006808C00014$$ 516,096
    TESTTBSP LOBINDEX SYS_IL0000006808C00012$$ 516,096
    TESTTBSP INDEX SYS_C001978 516,096
    TESTTBSP INDEX SYS_C001977 516,096
    TESTTBSP LOBINDEX SYS_IL0000006696C00007$$ 516,096
    TESTTBSP INDEX SYS_C001913 516,096
    TESTTBSP INDEX SYS_C001910 516,096
    TESTTBSP LOBINDEX SYS_IL0000006715C00003$$ 516,096
    TESTTBSP INDEX UN_RECIPIENT 516,096
    TESTTBSP INDEX SYS_C001906 516,096
    TESTTBSP INDEX SYS_C001905 516,096
    TESTTBSP LOBINDEX SYS_IL0000006707C00003$$ 516,096
    TESTTBSP INDEX SYS_C001901 516,096
    TESTTBSP LOBINDEX SYS_IL0000006702C00008$$ 516,096
    TESTTBSP TABLE T_JOBSTEPRUN 516,096
    TESTTBSP TABLE T_DISTRIBUTIONITEM 516,096
    TESTTBSP TABLE T_DISTRIBUTIONPROFILE 516,096
    TESTTBSP TABLE T_BUSINESSDOCTEMPLATE 516,096
    TESTTBSP TABLE T_BUSINESSCATEGORY 516,096
    TESTTBSP TABLE T_APPCATEGORYDATASOURCE 516,096
    TESTTBSP TABLE T_APPCATEGORY 516,096
    TESTTBSP TABLE T_CATEGORYDATASOURCEGROUP 516,096
    TESTTBSP TABLE T_PRECOMPOSEDDOCATTR 516,096
    TESTTBSP TABLE T_TEXTDATA 516,096
    TESTTBSP TABLE T_CONTENTATTR 516,096
    TESTTBSP TABLE ST201 516,096
    TESTTBSP TABLE MT101 516,096
    TESTTBSP TABLE ST101 516,096
    TESTTBSP TABLE MV_US_REGULATORY 516,096
    TESTTBSP TABLE SV_US_REGULATORY 516,096
    TESTTBSP TABLE T_MISC_INFO 516,096
    TESTTBSP TABLE T_BARCODE_CHARMAP 516,096
    TESTTBSP TABLE T_PAGESEQUENCES 516,096
    TESTTBSP TABLE T_SUBDOCUMENTS 516,096
    TESTTBSP TABLE T_REFERENCE 516,096
    TESTTBSP TABLE T_DOCUMENTUM_DOCBASE 516,096
    TESTTBSP TABLE T_LOGICTRAY 516,096
    TESTTBSP TABLE COLORSCHEME_USAGE 516,096
    TESTTBSP TABLE T_LOCK 516,096
    TESTTBSP TABLE T_JOBDEFINITION 516,096
    TESTTBSP TABLE T_BDTDISTRIBUTIONPROFILE 516,096
    TESTTBSP TABLE T_COMPLETEDITEM 516,096
    TESTTBSP TABLE T_WORKITEM 516,096
    TESTTBSP TABLE FONT_SUBFAMILY_ALIAS 516,096
    TESTTBSP TABLE FONT_FAMILY_ALIAS 516,096
    TESTTBSP TABLE EXTENDED_FONT 516,096
    TESTTBSP TABLE T_FONTMAPPING 516,096
    TESTTBSP TABLE T_OUTPUTPROFILE 516,096
    TESTTBSP TABLE T_OPSTREAMFORMATDEFDISTDEFUSE 516,096
    TESTTBSP TABLE T_STREAMDISTRIBUTIONOUTPUT 516,096
    TESTTBSP TABLE T_OUTPUTDEFINITION 516,096
    TESTTBSP TABLE T_OPSTREAM 516,096
    TESTTBSP TABLE T_OPSTREAMDEFINITION 516,096
    TESTTBSP TABLE T_BDTOUTPUTPROFILE 516,096
    TESTTBSP TABLE T_TRACKCHANGE 516,096
    TESTTBSP TABLE EXTENDED_VMF 516,096
    TESTTBSP TABLE EXTENDED_IMAGE 516,096
    TESTTBSP TABLE EXTENDED_DOC 516,096
    TESTTBSP TABLE EXTENDED_TEXT 516,096
    TESTTBSP TABLE EXTENDED_IMAGEFAMILY 516,096
    TESTTBSP TABLE DDG_USAGE 516,096
    TESTTBSP TABLE EXTENDED_DDG 516,096
    TESTTBSP TABLE T_COLORSCHEME 516,096
    TESTTBSP TABLE T_OUTPUTPROFILE_USAGE 516,096
    TESTTBSP TABLE T_OPTIONALGROUP 516,096
    TESTTBSP TABLE T_CONTENTGROUP 516,096
    TESTTBSP TABLE T_RECIPIENT_USAGE 516,096
    TESTTBSP TABLE T_RULEELEMENTUSAGE 516,096
    TESTTBSP TABLE T_RULEUSEREXIT_USAGE 516,096
    TESTTBSP TABLE T_PUBLISHSTREAM 516,096
    TESTTBSP TABLE T_CONTENTSTAMP 516,096
    TESTTBSP TABLE T_DEVICE 516,096
    TESTTBSP TABLE T_MARKER 516,096
    TESTTBSP TABLE T_STREAMSTAMP_USAGE 516,096
    TESTTBSP TABLE T_STREAMMARKER_USAGE 516,096
    TESTTBSP TABLE T_BINARYDATA 1,032,192
    TESTTBSP TABLE T_DLSTRANS 1,032,192
    TESTTBSP INDEX PK_DOCTRACKING_ID 1,032,192
    TESTTBSP LOBSEGMENT SYS_LOB0000006776C00005$$ 1,032,192
    TESTTBSP INDEX SYS_C002027 2,064,384
    TESTTBSP INDEX INDEX_MT201 2,064,384
    TESTTBSP TABLE T_RULEELEMENT 2,580,480
    TESTTBSP TABLE T_RULE 2,580,480
    TESTTBSP INDEX GENXMLIDX5201 3,612,672
    TESTTBSP LOBINDEX SYS_IL0000006585C00002$$ 4,644,864
    TESTTBSP TABLE T_IDOCTABLE 5,160,960
    TESTTBSP TABLE MT201 8,257,536
    TESTTBSP LOBSEGMENT SYS_LOB0000006724C00002$$ 20,643,840
    TESTTBSP LOBSEGMENT SYS_LOB0000006581C00002$$ 52,125,696
    TESTTBSP LOBSEGMENT SYS_LOB0000006585C00002$$ 2,869,493,760

    No need to paste screens of ouput. I doubt anyone is going to go through every lobsegment individually and calculate your total is correct.
    Are the LOB segments stored in an ASSM AUTO tablespace? If so then you are likely hitting bugs 2886369 and 2670703.
    Message was edited by:
    stellios.k

  • Should Datafile Autoextend feature be turned on or off?

    Hi Guys,
    I have a questions on datafile auto extend on/off feature. I am hearing that this feature should be turned off and no one in my network seems to have a convincing answer for their claim. Is it true that it should be turned off? If yes, why? I am not seeing any evidence that it should not be turned on. Databases in question are 9i and 10g on Solaris and Linux. Any suggestions/comments are welcome.
    --MM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    I believe that autoextend feature should be set to “on” for most tablespaces (their datafiles to be exact).
    First, some thoughts about monitoring (and forecasting) tablespace size. Those important activities should be done in any production system. I even wrote a presentation (NYOUG, Brainsurface VirthaThon) on (among many other things) how to forecast tablespace size using the data in the OEM repository (http://iiotzov.files.wordpress.com/2011/08/iotzov_oem_repository.pdf) . Manual or automatic, simple or complex, all monitoring and forecasting methods have a significant limitation – they cannot handle a sudden change in the growth pattern (a surge). That’s where “autoextend on” comes in. It is very important to use “autoextend on” in addition to proper monitoring/forecasting, not in lieu of it.
    Imagine you have an ASM disk group with 50G free space. You do not use “autoextend on”, so one small (3G data + 2G free) tablespace gets a surge of data (around 4G) and runs out of disk space. Your boss asks: “So how did we run out of disk space when there was more than 40G free at all times?” What do you say? “The application team did not inform us”.”It was an unexpected situation”. One can do better than that...
    Now, about the valid concern that unchecked “autoextend” growth can fill the disk and cause DB-wide problems. Proper planning can practically eliminate those concerns:
    ->TEMP and UNDO tablespaces should not have autoextent on
    ->All tablespaces should have free space already allocated, so there would be enough to hold the data for some time (3 months for instance) without growing the data files. That would ensure that the system works properly even if there is no disk space to grow the data files.
    ->Archive log should be in a separate disk group
    -> The amount a single tablespace can grow should be less than the available free space at all times. If we have 50G free space, no single tablespace should be able to grow more than 45G. The policies how much a tablespace can grow can be even more strict - like no tablespace can grow more than 20G, no two tablespaces can fill the system.
    Iordan Iotzov
    http://iiotzov.wordpress.com/

  • Autoextend off / on?

    I have been having pbs with rman backups and this is due to the fact that during rman backup, a datafile is being extend and it gives the error below.
    RMAN-10035: exception raised in RPC: ORA-19575: expected 820995 blocks in file /u05/oradata/MTNPRD/applsysx01.dbf, found 820990
    RMAN-10031: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
    Now, I will like to change the datafile from autoextend on to off but before doing that, I will like to have some advice as I wanna know the up and downside of it!
    Thanks
    DID

    You can turn off autoextend, but if the tablespace needs to autoextend an error will be raised. Another option is to adjust your backup time to a time where the tablespace is less likely to autoextend if possible.

  • Tablespace autoextend Off

    Hello expert
    we are using oracle 10.2.0.4 on HP-UX for SAP ECC6.0.
    currently SAP Tablespace auto extend is ON but we want to OFF this coz when we try to backup Full+offline backup sometimes
    its terminated unsuccessfully due to auto extend property & some times we felt slow response coz of this.
    could you plz suggest me how can i OFF this autoextend, or in future how can i add DATAFILE on tablespace, how can i extend tablespace size or last what precaution should we have to make on DR server.
    kindly help me, I am not DBA person and facing so much problem due to this.
    plz could you suggest me any document to over come my oracle knowledge.
    Best Regards
    Deepak Singh

    Hello Deepak,
    You can turned off autoextend  on all data files for more control of space.
    But make sure to keep eye on the growth.
    You can use the Oracle command:
    alter tablespace ... autoextend off
    SQL : you need to do this for all datafiles of the tablespace one by one which are auto extendable.
    alter database datafile '/oracle/PRD/sapdata11/sr_11/data11.dbf' autoextend off
    Or
    Brtools
    Space Mangement - Alter Data File - Alter Data File Action
    Turn off autoextend
    When adding  datafile, you can use brtools
    brtools -> space management -> extend tablespace -> enter the tablespace name.... etc
    If you adding , new  datafile to the primary server, make sure to set the DR or SB parameter to AUTO
    STANDBY_FILE_MANAGEMENT = AUTO
    Genus Power wrote:
    > when we try to backup Full+offline backup sometimes  its terminated unsuccessfully due to auto extend property
    You may increase the extending amount, depending on the growth
    If its a small value then, it may trying to extend in shorter periods. So after considering the workload , select a value to auto extend.
    how you says , that backup fails due to auto-extending property. Whats the logs implies
    regards,
    Zerandib

  • Datafile autoextend off possible in Physical standby?

    Hi,
    I am making datafiles auto extend off in primary database. is there anything i should do in standy database as well?
    i have 10.2.0.4 version in IBM AIX machines with physical standby database configured...
    I have standby_file_management is AUTO...
    Any suggestions?
    Thanks,
    Raman.
    standby_file_management string AUTO
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE 10.2.0.4.0 Production
    TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
    NLSRTL Version 10.2.0.4.0 - Production

    Means standy database will automatically propgate change of auto extend off? as DBA we dont do anything?Well, i have not tested it recently, but in back of my memories which i am trying to recall i have done it.For datafile/tablespace related standby_file_management parameter has to be set to auto, which is already set so you must must not face any problem.You can monitor the alert log file of the standby database.
    Anand

  • SQL Query to check which datafiles have AutoExtend on?

    I want to turn autoextend off on almost all my datafiles(obviously not on system). Using the Java Enterprise Manager you can visually see which datafiles have autoextend on. I'd prefer to find out using sqlplus which files have autoextend on so I can script turning it off. I don't see it in the v$tablespace or v$datafile views.. Where can i find this??
    Paul

    Hi,
      1* select substr(file_name,1,50), AUTOEXTENSIBLE from dba_data_files
    SQL> /
    SUBSTR(FILE_NAME,1,50)                             AUT
    /data/ora/H89UCBAC/u05/system/system01.dbf         YES
    /data/ora/H89UCBAC/u05/rbs/psundots01.dbf          YES
    /data/ora/H89UCBAC/u01/psdefault/psdefault.dbf     NO
    /data/ora/H89UCBAC/u01/aaapp/aaapp.dbf             NO
    /data/ora/H89UCBAC/u01/aalarge/aalarge.dbf         NO
    /data/ora/H89UCBAC/u01/adapp/adapp.dbf             NO
    /data/ora/H89UCBAC/u01/amapp/amapp.dbf             NO
    /data/ora/H89UCBAC/u01/avapp/avapp.dbf             NO
    /data/ora/H89UCBAC/u01/bdapp/bdapp.dbf             NO
    /data/ora/H89UCBAC/u01/bnapp/bnapp.dbf             NO
    /data/ora/H89UCBAC/u01/bnlarge/bnlarge.dbf         NO
    ...Nicolas.

Maybe you are looking for

  • Differences between EBS BIP and BIP EE

    Hi Folks, IHAC who currently runs EBS 11.5.10.x and use BIP embedded within the product. They would like to get a document that outlines the capability differences between what they currently own and BI Publisher Enterprise Edition. Besides the fact

  • Reg:Verify Error

    When execeting my application am getting Java.lang.verify error with Incompatible object argument for function call.. I dont have any idea abt that verify error..Any one please suggest me abt this error.

  • Microsoft Word Office 2011 crashes after upgrade to OSX 10.10.3

    Hi Microsoft Office 2011 crahses at opening after I upgraded to OSX 10/10.3,  I installed the latest version of Office, but get this message when it crahses: Microsoft Error Reporting log version: 2.0 Error Signature: Exception: EXC_BAD_ACCESS Date/T

  • Help in cross tabs.

    I have a cross tab defined. can we show levels hierarchy in cross tabs? I have a hierarchy described. I have a cross tab such a way that, In th description on cross tab: If value at Level4 = 'computers' this table gives us the all sublevels under lev

  • Editing entries in CO1P

    Hi all, I have set ' later in backgroud' in OPKC (Process control) for automatic goods receipt. My Query - Is it possible to edit these entries in CO1P? For e.g. changing the storage location. Regards, Yogesh