Default Storage versus Uniform size at creating Tablespace

anybody can explain if those two concepts mean same? in my practice, i need to dump all data from 9i to 10g database, in 9i a tablespace created by :
CREATE TABLESPACE DATA_TS
DATAFILE '/opt/oracle/u01/data_04.dbf' SIZE 11M AUTOEXTEND ON NEXT 1024K MAXSIZE UNLIMITED
EXTENT MANAGEMENT DICTIONARY
LOGGING
DEFAULT STORAGE(INITIAL 112K
NEXT 112K
MINEXTENTS 1
MAXEXTENTS 1017
PCTINCREASE 0)
ONLINE
PERMANENT
SEGMENT SPACE MANAGEMENT MANUAL
so in 10g I created tblsp like:
CREATE TABLESPACE DATA_TS
DATAFILE '/opt/oracle/u10/data_04.dbf' SIZE 11M AUTOEXTEND ON NEXT 1024K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 112K
LOGGING
ONLINE
SEGMENT SPACE MANAGEMENT MANUAL
are they same?

Hi,
Two concepts are not same.
Check this link:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96521/tspaces.htm
Starting with Oracle9i, the default for extent management when creating a tablespace is locally managed. However, you can explicitly specify that you want to create a dictionary-managed tablespace. For dictionary-managed tablespaces, Oracle updates the appropriate tables in the data dictionary whenever an extent is allocated, or freed for reuse.

Similar Messages

  • Uniform size value on tablespaces

    I have one question about uniform extend.
    For example:
    I set uniform extend to 16M
    I don't set storage parameters for tablespace and table.
    My questions is:
    For any tables i use one extend 16M ?
    If i use table with contains some LOB columns and i declare write this LOB out of table. How many space take one LOB value ? 16M??

    Whenever a table containing a LOB column is created, two segments are created to hold the specified LOB column. These segments are of type LOBSEGMENT and LOBINDEX. The LOBINDEX segment is used to access LOB chunks/pages that are stored in the LOBSEGMENT segment.
    Important Storage Parameters
    This section defines the important storage parameters of a LOB column (or a LOB attribute) - .
    ?fFor each definition we describe the effects of the parameter, and give recommendations for on how to get better performance and to avoid errors.
    CHUNK
    Definition
    CHUNK is the smallest unit of LOBSEGMENT allocation. It is a multiple of DB_BLOCK_SIZE.
    Points to Note
    ? For example, if the value of CHUNK is 8K and an inserted LOB is only 1K in size, then 1 chunk is allocated and 7K are wasted in that chunk. The CHUNK option does NOT affect in-line LOBs (see the definition in the next section)
    ? Choose an appropriate chunk size for best performance also to avoid space wastage. The maximum chunk size is 32K.
    ? The CHUNK parameter cannot be altered.
    Recommendation
    Choose a chunk size for optimal performance and minimum space wastage. For LOBs that are less than 32K, a chunk size that is 60% (or more) of the LOB size is a good starting point. For LOBs larger than 32K, choose a chunk size equal to the frequent update size.
    SJH
    OCP DBA

  • Create tablespace issue

    Hi;
    I wanna learn one thing...
    I have oracle ebs r11i wiht 10gr2 db, and its prod instance...
    Issue is like this:
    I have one tablespace lets us call it XXX and it has datafile like xx1.dbf,xx2.dbf..... I want to delete those dbf becouse their each size is 40 GB, and i want to create 2 new datafile which is each 10Gb.
    Would you give me steps and command how i can do that?
    Thanks

    tablespace - XXX
    datafile - xx1.dbf,xx2.dbf.....
    you want to delete those dbf becouse their each size is 40 GB, and i want to create 2 new datafile which is each 10Gb.
    1) If you want to delete 40 GB dbf's, you will loose data.
    2) If you really do not want those data, you can go ahead by dropping and creating DBF with 10 GB.
    steps and command how i can do that?
    I have give below sample commands, go through it thoroughly and go ahead.
    Best of Luck.
    =================================================================
    CREATING TABLESPACES
    ====================
    CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 100M
    AUTOEXTEND ON NEXT 5M MAXSIZE 200M;
    Locally Managed Tablespaces
    ===========================
    CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 500M
    EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K;
    Dictionary Managed Tablespaces
    ==============================
    CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 500M
    EXTENT MANAGEMENT DICTIONARY DEFAULT STORAGE ( initial 1M NEXT 1M );
    Undo Tablespace
    ===============
    CREATE UNDO TABLESPACE undo1 DATAFILE '/u01/oradata/undo101.dbf' SIZE 40M;
    Enabling Automatic Extension of Data Files
    ==========================================
    ALTER DATABASE DATAFILE '/u01/oradata/userdata02.dbf' SIZE 200M AUTOEXTEND ON NEXT 10M MAXSIZE 500M;
    SAMPLES
    =======
    SQL> CREATE TABLESPACE data01
    2 DATAFILE '$HOME/ORADATA/u04/data01.dbf' SIZE 2M
    3 EXTENT MANAGEMENT DICTIONARY;
    Tablespace created.
    SQL> CREATE TABLESPACE data02
    2 DATAFILE '$HOME/ORADATA/u03/data02.dbf' SIZE 1M
    3 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 100K;
    Tablespace created.
    SQL> CREATE TABLESPACE indx01
    2 DATAFILE '$HOME/ORADATA/u02/indx01.dbf' SIZE 1M
    3 AUTOEXTEND ON NEXT 500K MAXSIZE 2M
    4 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 4K;
    Tablespace created.
    SQL> CREATE TABLESPACE ronly
    2 DATAFILE '$HOME/ORADATA/u01/ronly01.dbf' SIZE 1M;
    Tablespace created.
    TO QUERY ALL TABLESPACES
    ========================
    SELECT * FROM v$tablespace;
    ALTER TABLESPACE
    ================
    ALTER DATABASE DATAFILE '$HOME/ORADATA/u03/data02.dbf' RESIZE 1500K;

  • Create tablespace in Oracle 10g Express

    Hi,
    I've been playing around over the last few days with Oracle 10g Express and I need to create my own tablespace and therefore create user associated with my custom table space.
    I tried with the command create tablespace, but I am not successful with configuring the parameters such as the datafile location and such. I did go through the Oracle Concepts Guide which was very helpful, but I must be missing something.
    Also assuming that my db scheme will be part of my application and therefore released to my client as script so they can re-create my database how would the table space integration work on their end.
    I would I have to place my first line of the script to create the table space and ask them for database file location?
    Any advice will be appreciated.
    Thank you in advance.

    user12359577 wrote:
    The reason why I think I should create my own tablespace is because I am creating a database scheme and thus I think it is appropriate to place my db scheme in its own tablespace instead of simply using the Users tablespace default.
    This is my command:
    create tablespace MYTBLSPACE;
    Error:
    Error starting at line 1 in command:
    create tablespace MYTBLSPACE
    Error at Command Line:1 Column:32
    Error report:
    SQL Error: ORA-02199: missing DATAFILE/TEMPFILE clause
    02199. 00000 - "missing DATAFILE/TEMPFILE clause"
    *Cause:    A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.
    *Action:   Specify a DATAFILE/TEMPFILE clause.
    I am also not sure how to specify the datafile.
    Thank you.How about checking with the fine SQL Reference manual for the syntax of the CREATE TABLESPACE command?
    Learning where to look things up in the documentation is time well spent investing in your career. To that end, you should drop everything else you are doing and do the following:
    Go to tahiti.oracle.com. Drill down to your product and version.
    Spend a few minutes just getting familiar with what is available here. Take special note of the "books" and "search" tabs. Under the "books" tab you will find the complete documentation library.
    Spend a few minutes just getting familiar with what kind of documentation is available there by simply browsing the titles under the "Books" tab.
    Open the Reference Manual and spend a few minutes looking through the table of contents to get familiar with what kind of information is available there.
    Do the same with the SQL Reference Manual.
    Do the same with the Utilities manual.
    You don't have to read the above in depth. They are reference manuals. Just get familiar with what is there to be referenced. Ninety percent of the questions asked on this forum can be answered in less than 5 minutes by simply searching one of the above manuals.
    Then set yourself a plan to dig deeper.
    - Read a chapter a day from the Concepts Manual.
    - Take a look in your alert log. One of the first things listed at startup is the initialization parms with non-default values. Read up on each one of them in the Reference Manual.
    - Take a look at your listener.ora, tnsnames.ora, and sqlnet.ora files. Go to the Network Administrators manual and read up on everything you see in those files.
    - When you have finished reading the Concepts Manual, do it again.
    Give a man a fish and he eats for a day. Teach a man to fish and he eats for a lifetime.
    Edited by: EdStevens on Mar 3, 2010 10:13 AM
    Edited by: EdStevens on Mar 3, 2010 10:15 AM

  • CREATE TABLESPACE AND ORA-03214

    when i create tablespace specifiled size less than 81,it occurs an error :ora-03214,the following code
    SQL> SELECT * FROM V$VERSION;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE    10.2.0.1.0      Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 64K;
    CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 64K
    ERROR at line 1:
    ORA-03214: File Size specified is smaller than minimum required
    SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 65K;
    CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 65K
    ERROR at line 1:
    ORA-03214: File Size specified is smaller than minimum required
    SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 79K;
    CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 79K
    ERROR at line 1:
    ORA-03214: File Size specified is smaller than minimum required
    SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 80K;
    CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 80K
    ERROR at line 1:
    ORA-03214: File Size specified is smaller than minimum required
    SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 81K;
    Tablespace created.
    SQL> SELECT TABLESPACE_NAME,BLOCK_SIZE ,INITIAL_EXTENT FROM DBA_TABLESPACES WHERE TABLESPACE_NAME = 'TEST';
    TABLESPACE_NAME               BLOCK_SIZE        INITIAL_EXTENT
    TEST                           8192                  65536why the size is 81 can create tablespace successfully? how to calculate it?

    Hi;
    One 64k header block for the datafile plus one 16k header block for the tablespace or vice versa, plus 1 empty block.
    64k + 16k + 8k(1 empty block) = 88k > 81kORA-03214: File Size specified is smaller than minimum required[b].
    how to calculate the minimum required?
    Answer:
    ORA-3214 When Creating a Tablespace [ID 153869.1]
    Regard
    Helios

  • ORA-25143: default storage clause is not compatible with allocation policy

    Dears,,
    While running the following command , it gave me error:
    ALTER TABLESPACE USER_DATA default storage (MAXEXTENTS unlimited);
    ERROR at line 1:
    ORA-25143: default storage clause is not compatible with allocation policy
    I tried a lot for that error and tested all possible solutions but without result.
    Is there any one faced this error before?
    Thanks & Best regards,,

    Dear,,
    As i said before in previous reply that:
    I can not give a default storage clause to a local managed tablespace.
    So, only i increased spaces for data files
    Also,see the following . . .
    SQL> ALTER TABLESPACE ts_name default storage (MAXEXTENTS 1000);
    ALTER TABLESPACE ts_name default storage (MAXEXTENTS 1000)
    ERROR at line 1:
    ORA-25143: default storage clause is not compatible with allocation policy
    SQL> ALTER TABLESPACE ts_name storage (MAXEXTENTS 1000);
    ALTER TABLESPACE ts_name storage (MAXEXTENTS 1000)
    ERROR at line 1:
    ORA-02142: missing or invalid ALTER TABLESPACE option
    I already solved my issue by increasing spaces for data files
    Thanks for support and help
    Best regards,,

  • Default storage for locally managed tablespaces

    the documentation says you cannot have a default storage parameter for locally managed tablespaces. Does this mean that we cannot specify
    INITIAL
    NEXT
    PCTINCREASE
    MINEXTENTS
    MAXEXTENTS for such tablespaces, or is there another way we can, without using default storage?
    thanks

    I amnot sure where you read that part that the default storage clause can't be given.Please see here,
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#sthref1149
    From the doc,
    Creating a Locally Managed Tablespace
    If the CREATE TABLESPACE statement includes a DEFAULT storage clause, then the database considers the following:
    If you specified the MINIMUM EXTENT clause, the database evaluates whether the values of MINIMUM EXTENT, INITIAL, and NEXT are equal and the value of PCTINCREASE is 0. If so, the database creates a locally managed uniform tablespace with extent size = INITIAL. If the MINIMUM EXTENT, INITIAL, and NEXT parameters are not equal, or if PCTINCREASE is not 0, the database ignores any extent storage parameters you may specify and creates a locally managed, autoallocated tablespace.
    If you did not specify MINIMUM EXTENT clause, the database evaluates only whether the storage values of INITIAL and NEXT are equal and PCTINCREASE is 0. If so, the tablespace is locally managed and uniform. Otherwise, the tablespace is locally managed and autoallocated.
    HTH
    Aman....

  • STORAGE parameter in CREATE TABLESPACE

    Hello all,
    Env: 10gR2
    I have the export of a schema of around 70Gb from 9i. I need to Import it to 10g.
    This will be used only for 'SELECT', there wont be any DML once i import the data.
    There are tables of size upto 20Gb.
    What would be the best STORAGE parameters that i should be using along with the CREATE TABLESPACE if my db block size is 8k?
    TIA,
    JJ

    If you are using locally managed tablespace then it is not required to specify storage parameters like initial, next and pctincrease. It is better to create LMT with uniform extent size. For the table with 20GB data create a seperate tablespace with uniform extent size as 1024MB. All tables of size more than 1GB can be allocated to this TS. For tabes of size between 100MB and 1GB create seperate tablespace of extent size 100MB. For all other tables create another TS with extent size 10M.
    If you are using dictionary managed tablespace then calculate the size of tables and first create empty tables with the necessary initial and next value. Then import data with the option IGNORE=Y.
    Mohan
    http://www.myoracleguide.com

  • Create table with storage parameters in a locally managed tablespace

    Hi,
    Can we create object with storage parameters in a locally managed tablespace.
    CREATE TABLE my_hash_table_6 (
    name VARCHAR2(30),
    value VARCHAR2(4000) )
    STORAGE (
    INITIAL 1M
    NEXT 512K
    PCTINCREASE 0
    MINEXTENTS 2
    MAXEXTENTS UNLIMITED )
    users default tablespace is locallly managed.
    Then this table's extent management will be managed as per the tablespace or as the storage parameters which
    were specified at the time of table creation.

    Why don't you try it yourself ?
    TEST@db102 > select * from dba_tablespaces
      2  where TABLESPACE_NAME='USERS';
    TABLESPACE_NAME                BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS
    MAX_EXTENTS PCT_INCREASE MIN_EXTLEN STATUS    CONTENTS  LOGGING   FOR EXTENT_MAN
    ALLOCATIO PLU SEGMEN DEF_TAB_ RETENTION   BIG
    USERS                                8192          65536                       1
    2147483645                   65536 ONLINE    PERMANENT LOGGING   NO  LOCAL
    SYSTEM    NO  AUTO   DISABLED NOT APPLY   NO
    TEST@db102 > CREATE TABLE my_hash_table_6 (
      2  name VARCHAR2(30),
      3  value VARCHAR2(4000) )
      4  STORAGE (
      5  INITIAL 1M
      6  NEXT 512K
      7  PCTINCREASE 0
      8  MINEXTENTS 2
      9* MAXEXTENTS UNLIMITED )
    TEST@db102 > /
    Table created.
    TEST@db102 > select * from user_segments
      2  where segment_name='MY_HASH_TABLE_6';
    SEGMENT_NAME
    PARTITION_NAME                 SEGMENT_TYPE       TABLESPACE_NAME
         BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS
    MAX_EXTENTS PCT_INCREASE  FREELISTS FREELIST_GROUPS BUFFER_
    MY_HASH_TABLE_6
                                   TABLE              USERS
       2097152        256          2        1572864                       1
    2147483645                                         DEFAULT
    TEST@db102 >

  • New to CS 6....how can I create default "print document" letter-size artboard?

    New to CS 6....how can I create  a default "print document" letter-size artboard ?

    Nothing has changed in CS6 with respect to creating Artboards. File>New and choose Print in the document type profile.

  • Cs6 opening existing file defaults to last new size created. How do I keep my file properties / size

    cs6 opening existing file defaults to last new size created. How do I keep my file properties / size the same?

    Is that all your HTML code contains?
    Where are the closing </body> and </html> tags in the end?
    Try adding this to the last lines of the file:
    </body>
    </html>
    -ST

  • How to create uniform size archive logs?

    DB version 11.2.0.3
    OS solaris.
    i have 6 online redo log groups.
    i want that my archive logs file always create of uniform size of 50MB each?

    Asad99 wrote:
    DB version 11.2.0.3
    OS solaris.
    i have 6 online redo log groups.
    i want that my archive logs file always create of uniform size of 50MB each?Why do you care about the size of an individual archivelog? What problem does that solve?
    Archivelogs are simply "backup" copies of the online redologs. So in general, an archivelog will be the same size as the online redolog that it is archiving. It may happen to be be smaller in some circumstances that cause a log switch before an online redo log is full.

  • Alter tablespace uniform size

    I'm having difficulty with the syntax to change the uniform size of an existing tablespace. I haven't found much on it. Any help would be appreciated.
    Thank you

    copy pasted from below site......
    TSharma     
    Handle:     TSharma
    Status Level:     Pro (755)
    Registered:     Feb 9, 2010
    Total Posts:     460
    http://www.dba-oracle.com/t_tablespace_extent_management_local_uniform_autoallocate.htm
    he changed Hence, you to one....did you read the OP post ....did he mentioned alter tablespace uniform to autoallocate?......just copy paste from other sites....is it right way editing some others words...without reading OP post......
    thanks,
    DBC,
    Sr DBA,
    OCE.
    Edited by: dbc001 on Mar 19, 2013 9:14 AM

  • Setting the size of a tablespace prior to its creation

    Hi guys,
    Oracle version: 10.2.0.x
    OS: Windows 32bit
    I was wondering if there are any 'conditions' in setting the intial size of a tablespace prior to its creation. This is because, one of our customers wants to export and import from one schema into another but set an initial size for a tablespace during its creation and prior to importing data into it, but we have a database wizard tool that creates the accounts/schemas by using the following underlying sql:-
    CRETE TABLESPACE <tbl_name> datafile <path><datafile_name>.dbf SIZE 100M AUTOEXTEND ON NEXT 100M MAXSIZE 32000M DEFAULT STORAGE (INITIAL 256 NEXT 256K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0) ONLINE;
    Under normal circumstances, what he would do is to use our wizard tool and create an account and then import data from an export dump.
    But he wants to create a tablespace using a SQL something like:-
    CRETE TABLESPACE <tbl_name> datafile <path><datafile_name>.dbf SIZE 2000M AUTOEXTEND ON NEXT 500M MAXSIZE 32000M DEFAULT STORAGE (INITIAL 256 NEXT 256K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0) ONLINE;
    He thinks this should be ok because his export dump would be on size 2GB and would want to import all of that 'at once' i.e. without actually using autoextend feature for the first 2GB.
    Does this make any sense? Do you guys see any difference 'performance-wise' between the 2 create tablespace statements?
    I think the second sql (with size 2000M initially) seems to be a more logical approach but I am not really sure of the implications going down the line performance-wise.
    Any help/input much appreciated!
    Thanks guys

    1) Provide the facility in your tool to change the default size of datafiles and keep autoextend off.You won't believe it...we had this option in a previous version but now it isn't there anymore!
    But why turning off AUTOEXTEND? I mean, our customers are not meant to modify anything in the database other than via using our software, hence we would want our customers to just use the software as it is but have their DBAs monitor the growth of any datafiles etc...
    2) Let your tool do what it is doing and then manually increasing the size of the datafiles and making autoextend off once you have created the tablespace and before doing import. This can be done by your tool or loggin to the database.We could do this, but we don't want our customers to manually finger the database as they are/might not be Oracle-efficient and wouldn't want production systems to crash for the same reason.
    Hence we could just give them the SQL to be replaced with the 'default' one and then create a tablespace via the tool which would create a tablespace with an initial size of 2GB+ and with greater autoextend facility (such as autoextend on 500M) rather than 100M so that there are fewer autoextends.
    Also, in your point 2, are you saying to turn off autoextend only for the import and set it back on by alter tablespace....?
    Thank you.

  • Error During Installation: ORA-02180: invalid option for CREATE TABLESPACE

    Hi all,
    This is our enviroment,
    Windows 2000 Service Pack 4
    We are installing SAP R/3 Enterprise 4.7 Ext. 200 SR1
    First we installed:
    Oracle: 9.2
    Patch: 9.2.0.7
    SAP Central Instance
    Now we are installing the DB Instance, but it gives this error:
    INFO 2007-11-22 16:58:20
    Working directory changed to C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\NUC\DB.
    ERROR 2007-11-22 16:58:21
    CJS-00084  SQL statement or script failed.DIAGNOSIS: Error message: ORA-02180: invalid option for CREATE TABLESPACE
    We are in the step 19 of 34
    Create Tablespaces
    Please some tips.
    Regards,
    Erick

    Hi! Thanks a lot for the reply.
    This is our <b>ora_sql_results.log</b>
    ================================================================================
    2007-11-23, 07:31:09 SAPINST ORACLE start logging for
    connect  /  as sysdba ;
    set newpage 0
    set space 0
    set pagesize 0
    set linesize 32767
    set markup HTML off
    set heading off
    set verify off
    set feedback off
    set trimspool on
    set sqlprompt SQL>
    set termout on
    set verify off
    set echo off
    spool ora_query3_tmp0_1.res
    SELECT STATUS FROM V$INSTANCE;
    spool off
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 9.2.0.7.0 - Production on Fri Nov 23 07:31:09 2007
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected.
    OPEN
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.7.0 - Production
    SAPINST: End of output of SQL executing program D:\oracle\TVD\920/bin/sqlplus.
    2007-11-23, 07:31:10 SAPINST ORACLE stop logging
    ================================================================================
    2007-11-23, 07:31:10 SAPINST ORACLE start logging for
    connect  /  as sysdba ;
    CREATE TABLESPACE PSAP@SCHEMAID@ DATAFILE 'E:\oracle\TVD\sapdata4\psap@schemaid@_1\psap@[email protected]' SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M  LOGGING ONLINE PERMANENT  EXTENT MANAGEMENT  LOCAL  AUTOALLOCATE  SEGMENT SPACE MANAGEMENT AUTO ;
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 9.2.0.7.0 - Production on Fri Nov 23 07:31:10 2007
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected.
    CREATE TABLESPACE PSAP@SCHEMAID@ DATAFILE 'E:\oracle\TVD\sapdata4\psap@schemaid@_1\psap@[email protected]' SIZE 2000M  REUSE  AUTOEXTEND     ON NEXT 20M MAXSIZE 10000M  LOGGING ONLINE PERMANENT  EXTENT MANAGEMENT  LOCAL     AUTOALLOCATE  SEGMENT SPACE MANAGEMENT AUTO
    ERROR at line 1:
    ORA-02180: invalid option for CREATE TABLESPACE
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.7.0 - Production
    SAPINST: End of output of SQL executing program D:\oracle\TVD\920/bin/sqlplus.
    SAPINST found errors.
    SAPINST The current process environment may be found in sapinst_ora_environment.log.
    2007-11-23, 07:31:10 SAPINST ORACLE stop logging
    And this is <b>our alert_SID.log</b>
    Dump file d:\oracle\tvd\saptrace\background\alert_tvd.log
    Thu Nov 22 16:27:45 2007
    ORACLE V9.2.0.7.0 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 4, CPU type 586
    Thu Nov 22 16:27:45 2007
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 2
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.7.0.
    System parameters with non-default values:
      processes                = 80
      sessions                 = 96
      shared_pool_size         = 251658240
      sga_max_size             = 546906620
      shared_pool_reserved_size= 24363663
      enqueue_resources        = 8000
      control_files            = E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf, E:\oracle\TVD\sapdata1\system_1\cntrl\cntrlTVD.dbf, D:\oracle\TVD\saparch\cntrl\cntrlTVD.dbf
      db_block_size            = 8192
      db_cache_size            = 251658240
      compatible               = 9.2.0
      log_archive_start        = TRUE
      log_archive_dest         = D:\oracle\TVD\oraarch\TVDarch
      log_buffer               = 1048576
      log_checkpoint_interval  = 0
      db_files                 = 254
      fast_start_mttr_target   = 900
      log_checkpoints_to_alert = TRUE
      control_file_record_keep_time= 30
      dml_locks                = 4000
      transaction_auditing     = FALSE
      undo_management          = AUTO
      undo_tablespace          = PSAPUNDO
      undo_retention           = 43200
      remote_os_authent        = TRUE
      hash_join_enabled        = FALSE
      background_dump_dest     = D:\oracle\TVD\saptrace\background
      user_dump_dest           = D:\oracle\TVD\saptrace\usertrace
      core_dump_dest           = D:\oracle\TVD\saptrace\background
      optimizer_features_enable= 9.2.0
      sort_area_size           = 2097152
      sort_area_retained_size  = 0
      db_name                  = TVD
      open_cursors             = 800
      pga_aggregate_target     = 324848844
      workarea_size_policy     = AUTO
      statistics_level         = typical
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    Thu Nov 22 16:27:48 2007
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=8
    ARC1 started with pid=9
    Thu Nov 22 16:27:48 2007
    ARC0: Archival started
    Thu Nov 22 16:27:48 2007
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Thu Nov 22 16:27:48 2007
    ARC1: Archival started
    Thu Nov 22 16:27:48 2007
    ARC0: Becoming the 'no FAL' ARCH
    Thu Nov 22 16:27:48 2007
    ARC1: Becoming the heartbeat ARCH
    Thu Nov 22 16:27:48 2007
    ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
    Thu Nov 22 16:27:48 2007
    ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
    Thu Nov 22 16:27:49 2007
    alter database mount exclusive
    Thu Nov 22 16:27:49 2007
    ORA-00202: controlfile: 'E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    Thu Nov 22 16:27:50 2007
    ORA-205 signalled during: alter database mount exclusive...
    Shutting down instance (abort)
    License high water mark = 1
    Instance terminated by USER, pid = 1768
    Thu Nov 22 16:28:05 2007
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 2
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.7.0.
    System parameters with non-default values:
      processes                = 80
      sessions                 = 96
      shared_pool_size         = 251658240
      sga_max_size             = 546906620
      shared_pool_reserved_size= 24363663
      enqueue_resources        = 8000
      control_files            = E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf, E:\oracle\TVD\sapdata1\system_1\cntrl\cntrlTVD.dbf, D:\oracle\TVD\saparch\cntrl\cntrlTVD.dbf
      db_block_size            = 8192
      db_cache_size            = 251658240
      compatible               = 9.2.0
      log_archive_start        = TRUE
      log_archive_dest         = D:\oracle\TVD\oraarch\TVDarch
      log_buffer               = 1048576
      log_checkpoint_interval  = 0
      db_files                 = 254
      fast_start_mttr_target   = 900
      log_checkpoints_to_alert = TRUE
      control_file_record_keep_time= 30
      dml_locks                = 4000
      transaction_auditing     = FALSE
      undo_management          = AUTO
      undo_tablespace          = PSAPUNDO
      undo_retention           = 43200
      remote_os_authent        = TRUE
      hash_join_enabled        = FALSE
      background_dump_dest     = D:\oracle\TVD\saptrace\background
      user_dump_dest           = D:\oracle\TVD\saptrace\usertrace
      core_dump_dest           = D:\oracle\TVD\saptrace\background
      optimizer_features_enable= 9.2.0
      sort_area_size           = 2097152
      sort_area_retained_size  = 0
      db_name                  = TVD
      open_cursors             = 800
      pga_aggregate_target     = 324848844
      workarea_size_policy     = AUTO
      statistics_level         = typical
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    Thu Nov 22 16:28:08 2007
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=8
    ARC0: Archival started
    ARC1 started with pid=9
    Thu Nov 22 16:28:08 2007
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Thu Nov 22 16:28:08 2007
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
    Thu Nov 22 16:28:09 2007
    ARC1: Archival started
    Thu Nov 22 16:28:09 2007
    ARC1: Becoming the heartbeat ARCH
    ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
    Thu Nov 22 16:28:11 2007
    CREATE DATABASE TVD CONTROLFILE REUSE  MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG CHARACTER SET WE8DEC NATIONAL CHARACTER SET UTF8 DATAFILE 'E:\oracle\TVD\sapdata1\system_1\system.data1' SIZE 550M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE 'E:\oracle\TVD\sapdata3\temp_1\temp.data1' SIZE 540M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M UNDO TABLESPACE PSAPUNDO DATAFILE 'E:\oracle\TVD\sapdata2\undo_1\undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    LOGFILE GROUP 1 ('E:
    oracle/TVD/origlogA/log_g11m1.dbf',
    'D:
    oracle/TVD/mirrlogA/log_g11m2.dbf') SIZE 50M  REUSE ,
    GROUP 2 ('E:
    oracle/TVD/origlogB/log_g12m1.dbf',
    'D:
    oracle/TVD/mirrlogB/log_g12m2.dbf') SIZE 50M  REUSE ,
    GROUP 3 ('E:
    oracle/TVD/origlogA/log_g13m1.dbf',
    'D:
    oracle/TVD/mirrlogA/log_g13m2.dbf') SIZE 50M  REUSE ,
    GROUP 4 ('E:
    oracle/TVD/origlogB/log_g14m1.dbf',
    'D:
    oracle/TVD/mirrlogB/log_g14m2.dbf') SIZE 50M  REUSE
    Thu Nov 22 16:28:12 2007
    Database mounted in Exclusive Mode.
    Thu Nov 22 16:28:29 2007
    Successful mount of redo thread 1, with mount id 1434613531
    Assigning activation ID 1434613531 (0x5582771b)
    Thread 1 opened at log sequence 1
    Thu Nov 22 16:28:30 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:28:31 2007
      Current log# 1 seq# 1 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G11M1.DBF
      Current log# 1 seq# 1 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G11M2.DBF
    Successful open of redo thread 1
    Thu Nov 22 16:28:31 2007
    ARC0: Media recovery disabled
    Thu Nov 22 16:28:31 2007
    SMON: enabling cache recovery
    Thu Nov 22 16:28:32 2007
    WARNING: Default passwords for SYS and SYSTEM will be used.
             Please change the passwords.
    Thu Nov 22 16:28:32 2007
    create tablespace SYSTEM datafile  'E:\oracle\TVD\sapdata1\system_1\system.data1' SIZE 550M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
      EXTENT MANAGEMENT LOCAL online
    Thu Nov 22 16:28:51 2007
    Completed: create tablespace SYSTEM datafile  'E:\oracle\TVD\
    Thu Nov 22 16:28:51 2007
    create rollback segment SYSTEM tablespace SYSTEM
      storage (initial 50K next 50K)
    Completed: create rollback segment SYSTEM tablespace SYSTEM
    Thu Nov 22 16:29:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:29:10 2007
    CREATE UNDO TABLESPACE PSAPUNDO DATAFILE  'E:\oracle\TVD\sapdata2\undo_1\undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    Thu Nov 22 16:29:35 2007
    Successfully onlined Undo Tablespace 1.
    Completed: CREATE UNDO TABLESPACE PSAPUNDO DATAFILE  'E:\orac
    Thu Nov 22 16:29:36 2007
    CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE  'E:\oracle\TVD\sapdata3\temp_1\temp.data1' SIZE 540M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    Completed: CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE  'E:
    Thu Nov 22 16:29:36 2007
    ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTEMP
    Completed: ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTE
    Thu Nov 22 16:29:39 2007
    SMON: enabling tx recovery
    Thu Nov 22 16:29:39 2007
    Beginning local checkpoint up to RBA [0x1.538b.10], SCN: 0x0000.000019d9
    Completed checkpoint up to RBA [0x1.538b.10], SCN: 0x0000.000019d9
    kwqplbsc: open notifier exception err 604
    replication_dependency_tracking turned off (no async multimaster replication found)
    Completed: CREATE DATABASE TVD CONTROLFILE REUSE  MAXLOGFILES
    Thu Nov 22 16:30:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:31:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:31:28 2007
    Beginning log switch checkpoint up to RBA [0x2.2.10], SCN: 0x0000.00006489
    Thread 1 advanced to log sequence 2
    Thu Nov 22 16:31:28 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:31:29 2007
      Current log# 2 seq# 2 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G12M1.DBF
      Current log# 2 seq# 2 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G12M2.DBF
    Thu Nov 22 16:32:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:33:08 2007
    ARC0: Media recovery disabled
    Thu Nov 22 16:33:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:33:16 2007
    Completed checkpoint up to RBA [0x2.2.10], SCN: 0x0000.00006489
    Thu Nov 22 16:33:26 2007
    Beginning log switch checkpoint up to RBA [0x3.2.10], SCN: 0x0000.00009227
    Thread 1 advanced to log sequence 3
    Thu Nov 22 16:33:26 2007
    ARC0: Media recovery disabled
    Thu Nov 22 16:33:26 2007
      Current log# 3 seq# 3 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G13M1.DBF
      Current log# 3 seq# 3 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G13M2.DBF
    Thu Nov 22 16:34:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:35:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:35:19 2007
    Completed checkpoint up to RBA [0x3.2.10], SCN: 0x0000.00009227
    Thu Nov 22 16:35:28 2007
    Beginning log switch checkpoint up to RBA [0x4.2.10], SCN: 0x0000.0000b0ac
    Thread 1 advanced to log sequence 4
      Current log# 4 seq# 4 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G14M1.DBF
    Thu Nov 22 16:35:28 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:35:28 2007
      Current log# 4 seq# 4 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G14M2.DBF
    Thu Nov 22 16:36:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:37:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:38:08 2007
    ARC0: Media recovery disabled
    Thu Nov 22 16:38:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:38:51 2007
    Completed checkpoint up to RBA [0x4.2.10], SCN: 0x0000.0000b0ac
    Thu Nov 22 16:38:59 2007
    Beginning log switch checkpoint up to RBA [0x5.2.10], SCN: 0x0000.0000e12b
    Thread 1 advanced to log sequence 5
    Thu Nov 22 16:38:59 2007
      Current log# 1 seq# 5 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G11M1.DBF
      Current log# 1 seq# 5 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G11M2.DBF
    Thu Nov 22 16:39:00 2007
    ARC0: Media recovery disabled
    Thu Nov 22 16:39:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:40:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:41:08 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:41:09 2007
    Completed checkpoint up to RBA [0x5.2.10], SCN: 0x0000.0000e12b
    Thu Nov 22 16:41:18 2007
    Beginning log switch checkpoint up to RBA [0x6.2.10], SCN: 0x0000.0000ee94
    Thread 1 advanced to log sequence 6
      Current log# 2 seq# 6 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G12M1.DBF
      Current log# 2 seq# 6 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G12M2.DBF
    Thu Nov 22 16:41:18 2007
    ARC1: Media recovery disabled
    Thu Nov 22 16:42:08 2007
    Fri Nov 23 07:38:10 2007
    ARC1: Media recovery disabled
    Regards,
    Erick

Maybe you are looking for