Creating table: Tablespace determination?

Similar Questions

• Creating table in the desired tablespace

  Hello

  I created the CUZK_BACKUP tablespace:

  
  
  CREATE the TABLESPACE CUZK_BACKUP DATAFILE ' / oradata/RUIAN/cuzk_backup01.dbf' SIZE 3 G AUTOEXTEND ON NEXT 100 M MAXSIZE 15 G;
  
  
  Now I'm trying to create table in this space of table like this:
  
  

  BEGIN

  -zjisti, if jiz existuji tabulky ve schematu centrumadmin (0 - no, 1 - year)

  SELECT COUNT (*) in the nCount_aud FROM dba_tables owner WHERE to = 'CENTRUMADMIN' and table_name = "$ _BACKUP2";

  SELECT COUNT (*) in the nCount_fga FROM dba_tables owner WHERE = 'CENTRUMADMIN' and table_name = "FGA_LOG$ _BACKUP2";

  IF (nCount_aud < = 0)-pokud tabulka neexistuje, vytvor ji partisnovanou po mesici

  THEN

  v_sql_aud: =' CREATE TABLE CENTRUMADMIN. AUD$ _BACKUP2

  TABLESPACE CUZK_BACKUP

  storage (initial 500 m next 50 m maxextents unlimited)

  PARTITION BY RANGE (NTIMESTAMP #)

  INTERVAL (NUMTOYMINTERVAL (1, "MONTHS"))

  (

  P_2013 PARTITION VALUES LOWER THAN (TO_DATE ("01/01/2014", "DD-MM-YYYY"));

  P_2014_01 PARTITION VALUES LOWER THAN (TO_DATE ("02/01/2014", "DD-MM-YYYY"));

  P_2014_02 PARTITION VALUES LOWER THAN (TO_DATE ("03/01/2014", "DD-MM-YYYY"));

  P_2014_03 PARTITION VALUES LOWER THAN (TO_DATE ("04/01/2014", "DD-MM-YYYY"));

  P_2014_04 PARTITION VALUES LOWER THAN (TO_DATE ("05/01/2014", "DD-MM-YYYY"));

  P_2014_05 PARTITION VALUES LESS THAN (TO_DATE ("06/01/2014", "DD-MM-YYYY")))

  AS select * from SYS. AUD$ where 1 = 2';

  EXECUTE IMMEDIATE v_sql_aud;

  DBMS_OUTPUT. Put_line ('Vytvorena tabulka CENTRUMADMIN.) AUD$ _BACKUP2.') ;

  ON THE OTHER

  DBMS_OUTPUT. Put_line (' CENTRUMADMIN Tabulka.) AUD$ _BACKUP2 jiz existuje.') ;

  END IF;

  Table is created, but not in the CUZK_BACKUP tablespace:

  Select table_name, tablespace_name from dba_tables where owner = "CENTRUMADMIN";

  TABLE_NAME, TABLESPACE_NAME

  ------------------------------ ------------------------------

  CUZK_SLUZBY OKO_USR_SCD

  CUZK_LOG_BEHU OKO_USR_SCD

  CUZK_LOG_FAZE OKO_USR_SCD

  CUZK_LOG_CHYBY OKO_USR_SCD

  AUD$ _BACKUP

  AUD$ _BACKUP2

  FGA_LOG$ _BACKUP

  FGA_LOG$ _BACKUP2

  Why there is no tablespace and how to make it work?

  Thank you

  Honza

  
  
  
  

  For a partitioned table, the actual segments are at the Partition level.  If a query DBA_TAB_PARTITIONS and DBA_SEGMENTS.

  Hemant K Collette

• ARCHIVELOG created in Tablespace, CATS and NOLOGGING table

  Hi all

  Archiving log is created, even if the table space, table is in NOLOGGING. And also I am trying to create a table using CATS (create table test_table AS Select...)

  The Version of database: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production

  alter tablespace DATA11 NOLOGGING;

  ALTER session enable parallel dml.

  create table test_table

  tablespace DATA11

  Parallel (level 8)

  NolOGGING

  AS

  SELECT / * + append * /.

  CREATED_BY,

  CREATED,

  ....

  ....

  Of

  Table_1;

  Table_1: lines 50M

  It creates an archive huge. All possible ways to avoid creating any archivelogs? other than "alter database noarchivelog.

  You may need to check whether DBA logging of strength at the database level.

• Create index partition in the partition table tablespace

  Hello
  
  I am running a work custom that
  
  * Creates a tablespace by day
  * Creates the daily table partition in the created tablespace
  * Removes the days tablepartition X
  * Removes the storage space for this partition of X + 1 day.
  
  The work above works perfectly, but it has problems with the management of the index for these partitioned tables. In the old database (10g - single node), all indexes and partitions exist in a BIG tablespace and when I imported the table creation script in the new database, I changed all the partitions table & index to go in their respective space.
  
  For example:
  
  Table_name... Nom_partition... Index_Part_name... Tablespace_name
  ============...================............====================...........=================
  TABL1... TABL1_2012_07_16... TABL1_IDX_2012_07_16... TBS_2012_07_16
  TABL1... TABL1_2012_07_15... TABL1_IDX_2012_07_15... TBS_2012_07_15
  
  
  But now, when the job is run, it creates the index in the tablespace TBS_DATA default.
  
  Table_name... Nom_partition... Index_Part_name... Tablespace_name
  ============...================.............====================...........=================
  TABL1... TABL1_2012_08_16... TABL1_IDX_2012_08_16... TBS_DATA
  TABL1... TABL1_2012_08_15... TABL1_IDX_2012_08_15... TBS_DATA
  
  
  I can issue alter index rebuild to move the index to its tablespace default, but how can I make sure that the index is created in the designated tablespace?
  
  NOTE: the partition/tablespace management work that I run only creates the partition of the table and not the index.
  
  
  The new env is a cluster of CARS of 2 nodes 11 GR 2 on Linux x86_64.
  
  
  Thanks in advance,
  aBBy.

  try something like this

  ALTER table tab_owner.tab_name add the partition v_new_part_nm
  values less (to_date('''|| v_new_part_dt_formatted ||'') ((', "DD-MON-YYYY)) tablespace ' | part_tbs
  update the index (ind1_name (partition ind_partition_name tablespace ind_part_tbs)
  ind2_name (partition tablespace ind_part_tbs ind_partition_name))
  ;

• CREATE TABLE to another OWNER/SCHEMA and in a different TABLESPACE?

  I am connected to a user of the SYSTEM. Now, I want to create a table of aaa. The owner of this table should not be SYSTEM but user KARL. and STORAGE space should not be SYSTEM but the tdtc TABLESPACE (existing).
  
  As far as I know I can do this by running the following command:
  
  CREATE TABLE KARL.aaa (an INTEGER,...) Tttt TABLESPACE;
  
  Regarding the TABLESPACE parameter, I'm not sure. Is it possible to return a user Karl TABLE in a TABLESPACE that is not assigned to him?
  
  In addition, I have another problem.
  I have a script with hundreds of CREATE TABLE, ALTER TABLE + CREATE INDEX DDL statements.
  Each of them are not prefixed with schema/owner and a TABLESPACE clause.
  
  I can put a single statement at the top of the script somehow that such Oracle
  to use
  -Karl OWNER as a schema/owner for all DDL stements
  -Thomas TABLESPACE as TABLESPACE for all DOF stements
  ?
  
  In MYsql, there is a statement «use < database >» Is soemthing similar to Oracle?
  
  Thank you
  Peter

  Yes... you can do. For example, a user who has a secret password that you do not want to give... as a schema of the application. User B needs to make paintings/objects in A schema and you want to follow this as user B. First configure Oracles Fine grain auditing and then grant "connect via" user A to user B as follows:
  -----

  SQL> create user b identified by abc123
    2    quota unlimited on users;
  
  User created.
  SQL> grant create session to b;
  
  SQL> create user a identified by abc123
    2    quota unlimited on users;
  
  User created.
  
  SQL> grant create table
    2      , create session
    3     to a;
  
  Grant succeeded.
  
  SQL> alter user a grant connect through b;
  
  User altered.
  
  SQL> connect b[a]/abc123@a486
  Connected.
  
  SQL> show user
  USER is "A"
  SQL> create table a.my_proxy_table
    2  ( c1 number
    3  , c2 varchar2(50)
    4  , c3 date
    5  );
  
  Table created.
  

  -----
  See I have connected using the syntax "username [proxyuser]." Also note that user B is by proxy user has, as evidenced by my order 'show user '. The connection through can be granted/revoked as needed without disclosing A goes to B. In addition, your audit tables or xml logs will follow the fact that user B created the table a.my_proxy_table.

  Hope this helps,
  John

• How to specify the tablespace for a India primary key in create table statement

  How to specify the storage space for a primary key index in a create table statement?
  Does the following statement is true?

  CREATE TABLE 'GPS'||TO_CHAR(SYSDATE+1,'YYYYMMDD')
              ("ID" NUMBER(10,0) NOT NULL ENABLE, 
              "IP_ADDRESS" VARCHAR2(32 BYTE), 
              "EQUIPMENT_ID" VARCHAR2(32 BYTE), 
              "PACKET_DT" DATE, 
              "PACKET" VARCHAR2(255 BYTE), 
              "PACKET_FORMAT" VARCHAR2(32 BYTE), 
              "SAVED_TIME" DATE DEFAULT CURRENT_TIMESTAMP, 
               CONSTRAINT "UDP_LOG_PK" PRIMARY KEY ("ID") TABLESPACE "INDEX_DATA"
               )            
               TABLESPACE "SBM_DATA";   

  Thank you
  
  Published by: qkc November 9, 2009 13:42

  As orafad noted, you can use the documentation using ESCALATION clause, i.e.

  SQL> ed
  Wrote file afiedt.buf
  
    1  CREATE TABLE GPS
    2              ("ID" NUMBER(10,0) NOT NULL ENABLE,
    3              "IP_ADDRESS" VARCHAR2(32 BYTE),
    4              "EQUIPMENT_ID" VARCHAR2(32 BYTE),
    5              "PACKET_DT" DATE,
    6              "PACKET" VARCHAR2(255 BYTE),
    7              "PACKET_FORMAT" VARCHAR2(32 BYTE),
    8              "SAVED_TIME" DATE DEFAULT CURRENT_TIMESTAMP,
    9               CONSTRAINT "UDP_LOG_PK" PRIMARY KEY ("ID") USING INDEX TABLESP
  ACE "USERS"
   10               )
   11*              TABLESPACE "USERS"
  SQL> /
  
  Table created.
  

  Justin

• As sysdba, how to grant create table to a user for a particular tablespace?

  I did the PRACTICE tablespace and user SEAN. How can I give SEAN the privilege to create a table in the practical tablespace?
  
  CREATE TABLESPACE PRACTICE
  DATA FILE
  ' F:\DBM\FALLB\DB2046\ORACLE\ADMIN\ORAC...
  SIZE 20 M
  DEFAULT STORAGE OF DICTIONARY OF MANAGEMENT MEASURE (1 M INITIAL FOLLOWING 1 M MAXEXTENTS 20 PCTINCREASE 0);
  
  CREATE USER SEAN
  IDENTIFIED BY SEAN
  PRACTICE OF TABLESPACE DEFAULT;
  GRANT CREATE SESSION TO SEAN;
  
  -----------------------------------------------
  -----------------------------------------------
  SEAN GRANT SYSDBA;
  +
  Sean/[email protected] CONNECT as sysdba
  
  Works, but what happens if I don't want SEAN have sysdba privileges?
  
  -----------------------------------------------
  -----------------------------------------------
  Another question would be if I don't give SEAN sysdba privileges and then I connect like sean and then perform a
  SELECT * FROM TAB;
  to display the available tables, how can I do so that I can only see the paintings I do myself instead of all tables in the database?

  Hello

  Connect as sys and grant after privs to SEAN, I added a few privileges as well.

  Do not give any user other than SYS sysdba priv, unless you intend to use user SEAN as a user administrative addition to SYS.

  GRANT RESOURCE TO SEAN;
  GRANT CONNECT TO SEAN;
  GRANT CREATE SESION TO SEAN;
    -- GRANT UNLIMITED TABLESPACE TO SEAN;
  GRANT CREATE VIEW TO  SEAN;
  GRANT CREATE PROCEDURE TO SEAN ;
  GRANT CREATE TABLE TO SEAN
    -- 1 Tablespace Quota for SEAN
  ALTER USER  SEAN QUOTA UNLIMITED ON PRACTICE;
   
  

  Concerning

• Create table ORA-01031: insufficient privileges

  SQL > indicate user USER is 'TEST_RPT.

  SQL > CREATE TABLE mytest (id NUMBER); - it does not work

  CREATE TABLE mytest (id NUMBER)

  * ERROR at line 1: ORA-01031: insufficient privileges

  SQL > CREATE TABLE TEST_RPT.mytest (id NUMBER).

  Table created. SQL >

  
  

  SQL > select * from session_privs;

  PRIVILEGE

  ----------------------------------------

  ANY PROCEDURE DEBUG

  DEBUGGING SESSION CONNECT

  CREATE INDEXTYPE

  OPERATOR TO CREATE

  CREATE THE TYPE

  CREATE THE TRIGGER

  CREATE PROCEDURE

  CREATE SEQUENCES

  CREATE VIEW

  CREATE SYNONYM

  CREATE THE CLUSTER

  CREATE TABLE

  UNLIMITED TABLESPACE

  ALTER SESSION STATEMENT

  CREATE SESSION

  Try this:

  SELECT USER, SYS_CONTEXT('USERENV','CURRENT_SCHEMA') FROM DUAL;

  The two identical values? CURRENT_SCHEMA is what will determine the owner of the table you create, if you do not specify an owner.

  This can be changed by

  ALTER SESSION SET CURRENT_SCHEMA = whatever_you_want_it_to_be;

• what need parameter should be ignored for creating table in LMT

  Hi all
  
  I have locally managed tablespace (LMT) with the type of ventilation SYSTEM and segment_space_management is AUTOMATIC. My database is Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi.
  
  I have for example:
  
  create table (ID)
  PCTFREE 5
  INITTRANS 2
  STORAGE (Initial...).
  
  
  Oracle documnetation, I found that it is recommended to omit the storage clause when you use LMT.
  
  I want to know, I do also omit PCTFREE 5, INITTRANS 2 of the create table statement?
  
  Thanks for any advice.

  Dear spur230,

  Yes, you can omit these parameters either.

  Here's the answer to your question;

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/tspaces.htm#sthref1153

  +"+
  * + Creating a locally managed Tablespace + *.

  + Create a locally managed tablespace by specifying IN clause of the CREATE TABLESPACE statement SCOPE MANAGEMENT. This is the default value for new permanent storage space, but you must specify the EXTENT MANAGEMENT LOCAL clause if you want to specify the AUTOALLOCATE or the UNIFORM clause. You can have the database to manage extensions for you automatically with the clause AUTOALLOCATE (default), or you can specify that the tablespace is managed with uniform extents of a specific size (UNIFORM). +

  + If you plan the tablespace contains objects of various sizes, requiring many scopes with different sizes, then AUTOALLOCATE is the best choice. AUTOALLOCATE is also a good choice if it is not important for you to have a lot of control over the allocation of space and the deallocation, because it simplifies the management of the table space. A space may be wasted with this parameter, but the advantage of having the Oracle database manage your space probably outweigh this disadvantage. +

  + If you want exact control on unused space, and you can predict exactly the space to allocate for an object or objects and the number and size of extensions, and then UNIFORM is a good choice. This setting ensures that you will never have the unusable space in your tablespace. +

  * + When you do not explicitly specify the type of management, database Oracle determines management extended as follows: + *.

  + * _If the CREATE TABLESPACE statement omits the DEFAULT storage clause, then the database creates a locally managed tablespace autoallocated. _ +
  + * _If the CREATE TABLESPACE statement includes a default storage clause, then the database considers the following: _ +.
  + O _If you specified AS MINIMUM clause, the database evaluates if MEASURE MINIMUM values, INITIAL, FOLLOWING are equal, and the value for PCTINCREASE is 0. If so, the database creates a locally managed tablespace uniform with size = INITIAL measurement. If the parameters to MEASURE MINIMUM INITIAL and NEXT are not equal, otherwise PCTINCREASE is not 0, the database ignores storage extent parameters you specify and creates a locally managed tablespace autoallocated. _ +
  + o _If you have not specified a MEASURE MINIMUM clause, the database evaluates only if the values of storage are the same INITIAL and NEXT and PCTINCREASE is 0. If so, the tablespace is locally managed and uniform. Otherwise, the tablespace is locally managed and autoallocated. _ +

  + The following statement creates a managed tablespace locally named lmtbsb and specifies AUTOALLOCATE: +.

  + CREATE TABLESPACE lmtbsb DATAFILE ' / u02/oracle/data/lmtbsb01.dbf' SIZE 50 +.
  + EXTENT MANAGEMENT LOCAL AUTOALLOCATE; +

  + AUTOALLOCATE causes tablespace system managed with a volume of minimum extent of 64K. +

  + The alternative to AUTOALLOCATE is UNIFORM. who says that the tablespace is managed with uniform size extents. You can specify the size of the uniform SIZE clause. If you omit the SIZE, the default size is 1 M. +

  + The following example creates a tablespace with uniform extents of 128 K. (In a database with 2 K blocks, each would amount to 64 blocks of data). Each measure 128K is represented by a bit in the bitmap extent for this file. +

  + CREATE TABLESPACE lmtbsb DATAFILE ' / u02/oracle/data/lmtbsb01.dbf' SIZE 50 +.
  + EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K; +

  + You can not specify the storage, TEMPORARY or MEASURE MINIMUM clause by DEFAULT when you explicitly specify EXTENT MANAGEMENT LOCAL. If you want to create a locally managed temporary tablespace, use the statement to CREATE a TEMPORARY TABLESPACE. +
  +"+

  Hope that helps.

  Ogan

• Column of type BLOB in own tablespace in partition in the table, tablespace to move

  Hi all

  First off I use Oracle Database 11.2.0.2 on AIX 5.3.

  We have a table is partitioned on a monthly basis.

  In this table, there is a partition (BOTTOM), this lower score is 1.5 TB in size thanks to a BLOB column called (ATTACHMENT).

  The rest of the table is not large, about 30 GB, it's the BLOB column that uses all the space.

  The lower part is in its own default tablespace (DefaultTablespace), the BLOB column in the lower score is also in its own tablespace (TABLESPACE_LOB) - 1.5 to

  I was invited in order to free up space by moving the TABELSPACE_LOB (from the low partition) to a data archive, confirming the data is there and then remove the lower score of the production.

  I do not have enough free space (or time) make an expdp, I think not only its doable with data so much.

  CREATE TABLE tablename
  (
    xx                          VARCHAR2(14 BYTE),          
    xx                          NUMBER(8),    
    xx         NUMBER,
    ATTACHMENT   BLOB,
    xx             DATE,
    xx             VARCHAR2(100 BYTE),
    xx                     INTEGER,
  )
  LOB (ATTACHMENT) STORE AS (
    TABLESPACE  DefaultTablespace
    ENABLE      STORAGE IN ROW
  NOCOMPRESS
  TABLESPACE DefaultTablespace
  RESULT_CACHE (MODE DEFAULT)
  
  
  PARTITION BY RANGE (xx)
  ( 
    PARTITION LOWER VALUES LESS THAN ('xx')
      LOGGING
      COMPRESS BASIC
      TABLESPACE DefaultTablespace
      LOB (ATTACHMENT) STORE AS (
        TABLESPACE  TABLESPACE_LOB
        ENABLE      STORAGE IN ROW
  )
  
  ...>>
  
  

  My idea was to take a table, excluding the attachment column datapump, export using external tables.

  Then to create the table on the database archive 'with' the attachment column.

  Import data only, as I understand that if you use a dump file that has too many columns Oracle he will manage, I hope it will work the other way around.

  Then on the production, make the TABLESPACE_LOB read-only and move it to the new file system.

  It's a little more complicated that a normal gesture of tablespace because of how the table is split.

  Any advice would be much appreciated.

  I was thinking about an approach as:

  SWAP PARTITION allows to separate the partition of the table

  • Create a non-partitioned table which is otherwise identical in structure to tablename (nonpart_tablename)
  • ALTER TABLE TableName LOWER WITH nonpart_tablename SWAP PARTITION

  Move the segment of the table at TABLESPACE_LOB, or to a different tablespace on its own. It is, as you say, only 30 GB and I think (but not strongly enough to go forward without testing/validation on a smaller scale) that the displacement of the segment of the table in this way does not disrupt the LOB segment, as long as you don't say MOVE LOB.

  • ALTER TABLE nonpart_tablename MOVE TABLESPACE TABLESPACE_LOB

  Now the TABLESPACE_LOB tablespace is self-contained and you can make it transportable.

• creating table of partition with null values

  Hello
  
  I have a table with 20 GB of data. I changed this table in the table to partition with partition of the range
  the column with which I took for range (date), holding the values null
  
  can I have a partition for null values?

  Hello

  CREATE TABLE ICBS. KNET_STMT_EXTRACT_NEW_P
  (
  SRVC_TYPE VARCHAR2 (200 BYTE),
  FILLER_1 VARCHAR2 (200 BYTE),
  RTE_STAT VARCHAR2 (200 BYTE),
  TRAN_DATE VARCHAR2 (200 BYTE),
  TRAN_TIME VARCHAR2 (200 BYTE),
  POST_DATE VARCHAR2 (200 BYTE),
  DATE OF REC_INSERT_DT,
  DATE OF PROCESSED_DATE,
  KNET_RECON_RESSON VARCHAR2 (100 BYTE),
  NEW_TRAN_DATE VARCHAR2 (10 BYTE),
  REASON VARCHAR2 (200 BYTE)
  REASON_IND NUMBER (5),
  NODE_ID VARCHAR2 (8 BYTE),
  PROGRAM_ID VARCHAR2 (8 BYTE),
  USER_ID VARCHAR2 (8 BYTE),
  TIME_STAMP DATE
  )
  ICBS TABLESPACE
  PCTUSED 0
  PCTFREE 10
  INITRANS 1
  MAXTRANS 255
  STORAGE)
  64K INITIALS
  MINEXTENTS 1
  MAXEXTENTS UNLIMITED
  PCTINCREASE 0
  DEFAULT USER_TABLES
  )
  LOGGING
  PARTITION BY RANGE (REC_INSERT_DT)
  (

  KNET_STMT_EXTRACT_NEW_P_DEC11 PARTITION VALUES LESS THAN (TO_DATE (' 2012-01-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN '))
  LOGGING
  NOCOMPRESS
  ICBS TABLESPACE
  PCTFREE 10
  INITRANS 1
  MAXTRANS 255
  STORAGE)
  INITIAL 1 M
  MINEXTENTS 1
  MAXEXTENTS UNLIMITED
  DEFAULT USER_TABLES
  ),
  KNET_STMT_EXTRACT_NEW_P_JAN12 PARTITION VALUES LESS THAN (TO_DATE (' 2012-02-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN '))
  LOGGING
  NOCOMPRESS
  ICBS TABLESPACE
  PCTFREE 10
  INITRANS 1
  MAXTRANS 255
  STORAGE)
  INITIAL 1 M
  MINEXTENTS 1
  MAXEXTENTS UNLIMITED
  DEFAULT USER_TABLES
  ),
  PARTITION KNET_STMT_EXTRACT_NEW_P_MVAL VALUES LESS THAN (MAXVALUE)
  LOGGING
  NOCOMPRESS
  TABLESPACE TBL_MAXVALUE
  PCTFREE 10
  INITRANS 1
  MAXTRANS 255
  STORAGE)
  INITIAL 1 M
  MINEXTENTS 1
  MAXEXTENTS UNLIMITED
  DEFAULT USER_TABLES
  )
  NOCOMPRESS
  NOCACHE
  NOPARALLEL
  MONITORING
  ALLOW THE MOVEMENT OF THE LINE;

  Published by: hitgon on April 30, 2012 10:56

  Published by: hitgon on April 30, 2012 10:58

  Published by: hitgon on April 30, 2012 10:59

• Create table as select execution Issues

  I have a table that is 190 million lines (TableA). The database is on the storage of very old and slow. I'll try the following: create table TableB in the select * from TableA where field1 < 10000 [this should translate into about 36 million lines for the new table]
  
  The problem is: I started this work at 20:00 and 02:00 is still not create the table. My thoughts are that it accumulates the lines into a temporary table, initially based on the where clause and then it goes to create the table. fix? That being said, the customer has a problem with the execution of this request during the opening hours, BUT it does start in writing during the outage window (20:00-02:00) and, in fact, I never get to this point. In fact, the early stages making the ETG is not this CPU intensive, I should be able to start the ETG before 20:00 without too much grumbling and I hope that the part of writing occurs during the window [i.e.: start the ETG at 14:00]. Is there a way to determine how long a DEC will take before you actually create the table?
  
  Anyone know if I'm wrong about the way that Oracle treats this type of DEC?
  
  Thank you

  To speed up the DEC options

  (1) NOLOGGING
  (2) PARALLEL

  http://download.Oracle.com/docs/CD/E11882_01/server.112/e25523/parallel003.htm#BEIFIDIE

  How useful PARALLEL might be depends on your environment (in particular, the number of processors).

  Werner

• Create Table As select from a PLSQL Package

  Hello
  
  I'm trying to use an Assignment statement in a stored procedure using Execute Immediate.
  
  I first create the script in a variable:
  
  v_sql: = 'CREATE TABLE ' | v_archive_partition_name |
  "TABLESPACE TBS_ARCHIVE |
  "STORAGE (INITIAL 20 M) |
  "AS COMPRESS |
  ' SELECT *' |. '
  'FROM ' | v_table_name |
  «PARTITION (' |)» v_archive_partition_name | ' ) ' ||
  "ORDER BY". v_sort_order | '';
  
  Then I run:
  
  EXECUTE IMMEDIATE v_sql;
  
  When I run the present, I get an error of incorrect permissions, but if I run the SQL that is created manually by using the same user it creates the table correctly.
  
  Can someone tell me what grants should I apply for my procedure create this table correctly?

  Can someone tell me what grants should I apply for my procedure create this table correctly?

  acquired through ROLE privileges do not apply in the PL/SQL procedure named.
  GRANT must be explicitly made

  IMO, application should NOT do the DOF between application version releases.

• syntax error in create table

  Could someone help me please as to what's wrong in the creation under the structure of the table:
  
  create table test (select * from schema.tablename where 1 = 2)
  TABLESPACE PCR_ARCHIVE_DATA_04
  PCTUSED 0
  PCTFREE 10
  INITRANS 1
  MAXTRANS 255
  STORAGE)
  64K INITIALS
  MINEXTENTS 1
  MAXEXTENTS UNLIMITED
  PCTINCREASE 0
  DEFAULT USER_TABLES
  )
  NOLOGGING
  COMPRESS
  NOCACHE
  PARALLEL (INSTANCES OF 6 1 DEGREE)
  MONITORING;

  SELECT AS comes after the physical attributes, such as

  create table test TABLESPACE PCR_ARCHIVE_DATA_04
  PCTUSED 0
  PCTFREE 10
  INITRANS 1
  MAXTRANS 255
  STORAGE (
  INITIAL 64K
  MINEXTENTS 1
  MAXEXTENTS UNLIMITED
  PCTINCREASE 0
  BUFFER_POOL DEFAULT
  )
  NOLOGGING
  COMPRESS
  NOCACHE
  PARALLEL ( DEGREE 6 INSTANCES 1 )
  MONITORING
  as (select * from schema.tablename where 1=2)
  

  Best regards

  Maxim

• error in creating tables

  When I try to create a table in Oracle Application Express 4.0, I get this error
  
  Failed to create table "Assessment.1".
  Failed creating Table ORA-01658: cannot create as INITIAL segment in tablespace FLOW_2195 ORA-00942: table or view does not ORA-06510: PL/SQL: unhandled by user-defined exception
  
  I mention that in the previous version of the SUMMIT I have dd I don't have this problem.
  Please, what can I do?
  Thank you

  It seems that the storage space on which the table was created, cannot allocate space to a new table.
  You DBA should be able to fix it.