DBA_TABLES. NULL for tables partitioned, yet Nom_tablespace DBMS_METADATA. GET_DDL displays a name...

Hello

Hence the name of tablespace comes when you make one

~ Select DBMS_METATDATA. GET_DDL ('TABLE', 'tname', 'owner')...

on a table partitioned, where you see things like:

~ CREATE TABLE...

~ ...

~ STORAGE(INITIAL 134217728 NEXT 134217728 MINEXTENTS 1 MAXEXTENTS 2147483645)

(~ DEFAULT USER_TABLES)

~ TABLESPACE "ABCD_LOGD2".

before all the blocks related to the different partitions of this table, where a

~ Select nom_tablespace from dba_tables where table_name = 'TNOM '...

Returns a null value?

Whence dbms_metatdata this ABCD_LOGD2 value? (in what dictionary?,)

DBA_SEGMENTS/extents display only the partitions information...)

Thank you...

SEB

Hello

What is the value of 'deffered_segment_creation '.

Take a look of it

Select def_tablespace_name in the dba_part_tables where table_name = 'tname'--> your table

Concerning

Tags: Database

Similar Questions

NULL values in partition Table of Partition key

Hi all
I'm using Oracle 11.2.0.3.
I can add a null value on partition of Partition table key.
If so, how?
Kind regards.
- You cannot specify NULL in the VALUES clause.
Referring to clauses PARTITION you set - not the data that you insert.

If you cannot define a range partition that uses the VALUES LESS THAN and use null to this division. But you CAN use NULL values in the VALUES of integration clause.

DROP TABLE mytable;

CREATE TABLE MyTable

(

CREATION_DATE DATE,

Identification number

)

PARTITION BY RANGE (CREATION_DATE)

(

PARTITION prior_to_2016 VALUES LESS THAN (TO_DATE ('2016-01-01', 'YYYY-MM-DD'));

LESS THAN PARTITION of VALUES undesirable (MAXVALUE)

)

Insert into myTable values (null, null)

You can use a VALUES clause to insert NULL values - this line will go into the MAXVALUE partition.

Statisctis for the partition table
I want to collect statistics for a partition of the table (say part1) instead of gathering statistics for the entire partition table. Is this possible and if yes how can I do this.
Experts entered are highly appreciated.
DB version: 9.2.0.6
Thank you all...
Yes it is possible using the partname parameter:

exec dbms_stats.gather_table_stats (-online 'owner' ownname, tabname => partname-online 'partname', 'table');

Become table partitioning
Hi I have a table where about 260 bln + records. and actionaly of infromation inserted. the structure of the table.

CREATE TABLE NUM_CALLS
(
NUMBER OF N_BLK
NUMBER,
NUMBER OF SRV_A
NUMBER OF SRV_B
NUMBER OF IND_B
START DATE,
NUMBER OF PTT,
NUMBER OF AIR,
NUM VARCHAR2 (2000 BYTE),
NUMBER OF HARD,
VARCHAR2 (240 BYTE) SERVICES,
STATUS VARCHAR2 (1 BYTE),
VARCHAR2 (240 BYTE) DSC,
INCOMING NUMBER,
THE NUMBER LEAVING,
NUMBER OF BILLPAR
NUMBER OF AIR_SUB
NUM_A VARCHAR2 (2000 BYTE),
NUMBER OF PTT_SUB
DIR CHAR (1 BYTE).
YOUR VARCHAR2 (5 BYTE)
NUMBER OF PTT_TOLL
NUMBER OF R_ROAMFILE_SEQ
NUMBER OF INDICATED,
NUMBER OF SRV_TOLL
PTT_TOLL2 NUMBER,
SRV_TOLL2 NUMBER,
IMEI VARCHAR2 (50 BYTE),
RTYPE VARCHAR2 (10 BYTE),
NUMBER OF R_MSCID
NUMBER OF R_CALLS_LOG
NUMBER OF UTC,
NUMBER OF TRANSACTIONS,
NUMBER OF SRC_SEQN
NUMBER OF FWD_TYPE
NUMBER OF TM_EVENTS
DST VARCHAR2 (20 BYTE),
ACCUM RAW (2000).
UTTYPE CHAR (1 BYTE),
TM_MODIFIERS RAW (2000)
)
TABLESPACE CDR
PCTUSED 40
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE)
80K INITIAL
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 0
FREELISTS 1
FREELIST GROUPS 1
DEFAULT USER_TABLES
)
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
NOMONITORING;

There is no primary key on the table, and this table records are not unique.

I want to become this table partitioning column by TRT (date) by date. is it possible to become the partitioning table after and if this table actionaly used? If possible then how can I do?
Create the new table with a different name, but same structure as NUM_CALL with no data ex create table new_table in new_table select * from YOUR_TABLE_NAME where 1 = 2;
or just get ddl for the use of this table:

SELECT DBMS_METADATA. GET_DDL('TABLE','YOUR_TABLE_NAME') FROM dual;

Modify this script, create the new table, and then create the partition you want (daily, monthly, annual) of course you can also create a subpartition.

prepare a few anonymous PLSQL block, and then insert the data into the new partition table, that's all.

stop the execution of the process, drop old table and rename the new table with the old name (deleted table)

NULL for repeated records

Hi team,

According to the sub query Deptno column is repeated results must show that it is null

my output should be

    DEPTNO ENAME             SAL         RN        RNK       DRNK
---------- ---------- ---------- ---------- ---------- ----------
        10 KING             5000          1          1          1 
            CLARK            2450          2          2          2 
            MILLER           1300          3          3          3 
        20 SCOTT            3000          1          1          1 
            FORD             3000          2          1          1 
           JONES            2975          3          3          2 
        30 BLAKE            2850          1          1          1 
            ALLEN            1600          2          2          2 
            TURNER           1500          3          3          3 
           MARTIN           1250          4          4          4 
           WARD             1250          5          4          4 
           JAMES             950          6          6          5

14 selected lines

select deptno
  , ename,sal,
     row_number()
       over (partition by deptno
             order by sal desc)rn,
     rank()
       over (partition by deptno
             order by sal desc)rnk,
     dense_rank()
       over (partition by deptno
            order by sal desc)drnk
    from emp
   order by deptno, sal desc
   /
   DEPTNO ENAME             SAL         RN        RNK       DRNK
---------- ---------- ---------- ---------- ---------- ----------
        10 KING             5000          1          1          1 
        10 CLARK            2450          2          2          2 
        10 MILLER           1300          3          3          3 
        20 SCOTT            3000          1          1          1 
        20 FORD             3000          2          1          1 
        20 JONES            2975          3          3          2 
        20 ADAMS            1100          4          4          3 
        20 SMITH             800          5          5          4 
        30 BLAKE            2850          1          1          1 
        30 ALLEN            1600          2          2          2 
        30 TURNER           1500          3          3          3 
        30 MARTIN           1250          4          4          4 
        30 WARD             1250          5          4          4 
        30 JAMES             950          6          6          5 


 14 rows selected

Hello

If you need to do this in SQL, and then use an expression BOX to return deptno for the first line of each deptno and NULL for all others. ROW_NUMBER can determine which is the first line, like this:

Select

CASE

WHEN ROW_NUMBER () OVER (PARTITION BY deptno

Sal of ORDER BY DESC

) = 1

THEN deptno

ANOTHER NULL - Default; can be omitted

END AS deptno

ename, sal,

ROW_NUMBER()

courses (deptno partition

order by sal desc) rn,.

Rank()

courses (deptno partition

order by sal desc) rnk.

DENSE_RANK()

courses (deptno partition

order by sal desc) drnk

from scott.emp

order by EMP. DeptNo, sal desc

Notice how I used emp.deptno in the ORDER byclause in the query. Simply deptno in this place means that the results of the CASE, not the original column expression.

Slow running queries on a table partitioned by date

I have a table partitioned by COLDATE, when I write a query to get the data is slow, even if I try to only get 1 day data. How can I correct this query runs faster?

Oracle Version: 10g

Number of lines:

See the below query

select COL1, COL2 RANK() OVER (PARTITION BY   COL1, COLDATE ORDER BY OTHER_DATE DESC) SHOW_RANK
from 
SAMPLETABLE
where COLDATE BETWEEN '01-JAN-2015' AND '01-JAN-2015'


create table SAMPLETABLE
(
  COL1   NUMBER(10) not null,
  COL2        NUMBER(10) not null,
  COLDATE       DATE not null,
  OTHER_DATE DATE
)
partition by range (COLDATE)
(
  partition PARTITION_01_2015 values less than (TO_DATE(' 2015-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace MYTABLESPACE_2015
    pctfree 20
    initrans 1
    maxtrans 255
    storage
    (
      initial 64K
      minextents 1
      maxextents unlimited
    ),
  partition PARTITION_02_2015 values less than (TO_DATE(' 2015-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace MYTABLESPACE_2015
    pctfree 20
    initrans 1
    maxtrans 255
    storage
    (
      initial 64K
      minextents 1
      maxextents unlimited
    ),
  .
  .
  .
  .
  .
  .
  partition PARTITION_12_2016 values less than (TO_DATE(' 2017-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace MYTABLESPACE_2016
    pctfree 20
    initrans 1
    maxtrans 255
    storage
    (
      initial 64K
      minextents 1
      maxextents unlimited
    )

Force the session in parallel mode and check with the parallel hint option.

SQL > alter session force parallel dml.

SQL > select / * + parallel (table_name, none of the servers) * / colA, colB from table_name;

How to collect statistics for a partition?

Hi all
I create a table partition. I need to collect statistics for this partition only. Before I used to analyze it, but now I need to analyze using DBMS_STATS.
What is the best way to analyze the partition using DBMS_STATS?
How long will it take to complete?
How can I estimate the time of accomplishment for DBMS_STATS before starting?
Thank you

I create a table partition. I need to collect statistics for this partition only. Before I used to analyze it, but now I need to analyze using DBMS_STATS.

What is the best way to analyze the partition using DBMS_STATS?

Follow the documented instructions: INCREMENTIELLE TRUE and GRANULARITY on AUTO.

See the section "Partitioned objects statistics" the doc of performance tuning

http://docs.Oracle.com/CD/B28359_01/server.111/b28274/stats.htm#i42218

With partitioned tables, the new data is usually loaded into a new partition. As new partitions are added and loaded, statistical data must be collected on the new partition and statistics need to be updated. If the INCREMENTAL for a partition table is set to the value TRUE , and collect you statistics on the table with the GRANULARITY parameter defined on AUTO , Oracle will collect statistics on the new partition and update statistics on the overall table by scanning only those partitions which have been modified and not the entire table. If the INCREMENTAL for the partitioned table is set to the value FALSE (the default), then a full table scan is used to maintain the global statistics. It is a highly resource intensive and time-consuming for large party.

How long will it take to complete?

No way to know - using an estimate of 10% takes less time than with an estimated of 40%, which takes less time than using 100%.

How can I estimate the time of accomplishment for DBMS_STATS before starting?

By comparing the amount of data and the percentage of estimate for the data that you have in the other partitions and the time required to collect statistics on other partitions.,.

Table partitioning
I have a table in my DB with stored more then 24 million and is growing every day. Growth rate increases with the passage of time. I want this partition table, in such a way that three first partitions such as each partition contains 10 years of data, and the remaining partition such as each partition contains data for 5 years.
This is the first time that I am any table partitioning, I understand following sql is not correct, I need your help in resolving this issue.
```
ALTER TABLE cb_pen_pmt_slip_dtl
ADD
PARTITION BY range (payment_date)
INTERVAL (NUMTOYMINTERVAL(5,'YEAR'))
(PARTITION p1 VALUES LESS THAN (TO_DATE('2000-01-01','YYYY-MM-DD'))
partition p2 values less than (maxvalue));
```
Hello

This link can help you...
>

Kind regards

Table Partitioned parallelized vs
Hello
(11.2 server, OS = OL5)

I have a table that contains more than 50 million lines. I created this table with option 'parallel degree (x).

It seems that the time required to execute a query on this table does not change when I share that, for example partition range dividing the table to 3 partitions.

(access the request a unique index in the table and the query criteria match exactly one of the partitions)

the question:
1. What is the difference of strategy parallelism between «Parallel degree...» "and the"Division "?
2. which of them are better in what scenario?
3. is it better to use PARALLEL_AUTOMATIC_TUNING?
4 and especially why the performance doesn't change even with a local index on the partitions?

Thank you
SMSK.
>
It seems that the time required to execute a query on this table does not change when I share that, for example partition range dividing the table to 3 partitions
. . .
(access the request a unique index in the table and the query criteria match exactly one of the partitions
. . .
@Adam Martin: thanks, but I was explained to question 4 that the performance does not change when I toggle locality index.
>
I do not see why it would be necessarily change just of partitioning. What is your reason to think so?

If the index access is used it is basically to get the IDENTIFIER of a line of interest. The line can then be retrieved using the ROWID. The recovery time will be essentially the same way regardless of the line in a partitioned table or non-partitioned table, and regardless of whether the line of partition. This is because the ROWID is (simple explanation here) a FILE ID (which file?), a BLOCK number (relative block in the file) and a LINE NUMBER (which line in the block. It doesn't matter if the segment that is the block is a segment of the table, partitioned table segment, segment index, etc.

It is the only factor that COULD change the time of the query when the index is used if the access of the index itself is more effective when the table is partitioned when the table is not partitioned.

Clearly if it is an overall index, there is a change since the index access itself will be the same.

The only factor now that MIGHT change the time of the request is so if 1) the index is changed locally and 2) the local index has a different structure than the old index that allows to find the best performing required index entries.

You have not published information on the index of structure, so let me give you an analogy which shows a scenario where it is clear that the access to the index would not change.

Assume that the overall index is analogous to a catalogue of cards with 26 entries - one for each letter of the alphabet. My query accesses the entries beginning with the letter 'F' As discussed above in table access to aid a ROWID obtained from the index will be the same, if the table is partitioned or not.

So now I have the partition table and have 26 partitions - one for each letter of the alphabet.

With the help of the global index of the access to the partition of 'F' will be the same.

Now, if I create a local index (instead of global) it's almost as if I now 26 index, one for each letter of the alphabet. The first entry for the 'F' in the global index can be found by reading the root node and perhaps one or two other nodes - then that an index scan can be performed.

The first entry for the 'F' in the local index is at the beginning of the index - no need to jump or to do a binary search to ignore the 'A', 'B', etc. entered.

This time difference is microscopic.

Once I found the first entry for the 'F' either in the overall index, or local 'F' remaining entries in the index are consecutive, so access time will be the same.

I don't know if there is a structural difference between the indices and the that you tried, but the above should show if the structure (order) has not changed it would not be a noticeable difference in access.

grant for dbms_metadata.get_ddl on objects in another schema

In Oracle 11 g R2, I use dbms_metadata.get_ddl to get the DDL to another schema, but I got an error:

ORA-31603: object not found 'IS_SNMP_DATA' of type TABLE in the schema "TXV.

that grant is necessary for this package to get from another schema ddl?
I tried with authid current_user (that I found on google), but no result...

See the following example:

SQL> create user us_one identified by us1;
User created.

SQL> grant connect, resource to us_one;
Grant succeeded.

SQL> create user us_two identified by us2;
User created.

SQL> grant connect, resource to us_two;
Grant succeeded.

SQL> conn us_one/us1
Connected.
SQL> create table t (id number);

Table created.

SQL> grant select on t to us_two;
Grant succeeded.

SQL> conn / as sysdba
Connected.

SQL> grant execute on dbms_metadata to us_two;

Grant succeeded.

SQL> conn us_two/us2
Connected.

SQL> select dbms_metadata.get_ddl('TABLE','T','US_ONE') from dual;
ERROR:
ORA-31603: object "T" of type TABLE not found in schema "US_ONE"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA", line 2806
ORA-06512: at "SYS.DBMS_METADATA", line 4333
ORA-06512: at line 1

no rows selected

SQL> conn / as sysdba
Connected.
SQL> grant select_catalog_role to us_two;

Grant succeeded.

SQL> conn us_two/us2
Connected.
SQL> select dbms_metadata.get_ddl('TABLE','T','US_ONE') from dual;

DBMS_METADATA.GET_DDL('TABLE','T','US_ONE')
--------------------------------------------------------------------------------

  CREATE TABLE "US_ONE"."T"
   (    "ID" NUMBER
   ) PCTFREE 10 PCTUSED 40 INITRA

SQL>

get the table script using dbms_metadata.get_ddl but with clob field

Thus, Oracle 11g R2...
I use dbms_metadata.get_ddl for table scripts and it works fine...

now, I have a table with clob field, and it does not work... I got an error "missing a closing parenthesis (ora-0907) '...
I could paste a script I had, but I don't think that it makes no sense...

does anyone have an experience on the use of this package on clob tables?

TNX

See this code.

DECLARE
  myddl clob;
  PROCEDURE print_clob(p_clob in clob) as
    l_offset number default 1;
  BEGIN
    loop
      exit when l_offset > dbms_lob.getlength(p_clob);
      dbms_output.put_line(dbms_lob.substr(p_clob, 255, l_offset));
      l_offset := l_offset + 255;
    end loop;
  END print_clob;
  FUNCTION get_metadata return clob is
    h   number;
    th  number;
    doc clob;
  BEGIN
    h := dbms_metadata.open('TABLE');
    dbms_metadata.set_filter(h, 'SCHEMA', 'HR');
    dbms_metadata.set_filter(h, 'NAME', 'EMPLOYEES');
    th := dbms_metadata.add_transform(h, 'MODIFY');
    th := dbms_metadata.add_transform(h, 'DDL');
    --dbms_metadata.set_transform_param(th,'SEGMENT_ATTRIBUTES',false);
    doc := dbms_metadata.fetch_clob(h);
    dbms_metadata.CLOSE(h);
    return doc;
  END get_metadata;
BEGIN
  myddl := get_metadata;
  print_clob(myddl);
END;

This procedure of print_ddl I took of the documentation.
Use of the long VALUE. See, in the first example out put is truncated.

SQL> SELECT dbms_metadata.get_ddl('TABLE','EMP','SCOTT') FROM dual;

DBMS_METADATA.GET_DDL('TABLE','EMP','SCOTT')
--------------------------------------------------------------------------------

  CREATE TABLE "SCOTT"."EMP"
   (    "EMPNO" NUMBER(4,0),
        "ENAME" VARCHAR2(10),

SQL> set long 10000
SQL> /

DBMS_METADATA.GET_DDL('TABLE','EMP','SCOTT')
--------------------------------------------------------------------------------

  CREATE TABLE "SCOTT"."EMP"
   (    "EMPNO" NUMBER(4,0),
        "ENAME" VARCHAR2(10),
        "JOB" VARCHAR2(9),
        "MGR" NUMBER(4,0),
        "HIREDATE" DATE,
        "SAL" NUMBER(7,2),
        "COMM" NUMBER(7,2),
        "DEPTNO" NUMBER(2,0),
         CONSTRAINT "PK_EMP" PRIMARY KEY ("EMPNO")

DBMS_METADATA.GET_DDL('TABLE','EMP','SCOTT')
--------------------------------------------------------------------------------
  USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
  TABLESPACE "USERS"  ENABLE,
         CONSTRAINT "FK_DEPTNO" FOREIGN KEY ("DEPTNO")
          REFERENCES "SCOTT"."DEPT" ("DEPTNO") ENABLE
   ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
  TABLESPACE "USERS"

SQL> SET LINESIZE 132
SQL> SET pagesize 0
SQL> SET LONG 1000000
SQL> /

  CREATE TABLE "SCOTT"."EMP"
   (    "EMPNO" NUMBER(4,0),
        "ENAME" VARCHAR2(10),
        "JOB" VARCHAR2(9),
        "MGR" NUMBER(4,0),
        "HIREDATE" DATE,
        "SAL" NUMBER(7,2),
        "COMM" NUMBER(7,2),
        "DEPTNO" NUMBER(2,0),
         CONSTRAINT "PK_EMP" PRIMARY KEY ("EMPNO")
  USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
  TABLESPACE "USERS"  ENABLE,
         CONSTRAINT "FK_DEPTNO" FOREIGN KEY ("DEPTNO")
          REFERENCES "SCOTT"."DEPT" ("DEPTNO") ENABLE
   ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
  TABLESPACE "USERS"

SQL>

Why SQL_ID is null for another session
Hello

I use Oracle XE 10 g installed on windows XP. I have connected to DB using SQL * more demand twice but the user names are different

SQL > Connect sys as sysdba
Password: *.
Connected.
SQL > Select sid, username from V$ session where the username is not null;
SID username
31 SYS

Open the SQL * plus the 2nd times

SQL > Connect Danae
Password: *.
Connected.

SQL > user to see the
SYS
SQL > select sid, username from V$ session where the username is not null
SID username
Danae 29
31 SYS

SQL > show user
Danae
SQL > select * sample;
NUM name
ABC 1
.
..
3 selected lines.

SQL > shoe user sys
SQL > select sid, sql_id from V$ session where the username is not null

SID SQL_ID
29
31 7xhp0k7jdb4z

Why SQL_ID is null for the SID = 29?

Can you please explain...
I think we may need to quickly check the documentation:
http://download.Oracle.com/docs/CD/B28359_01/server.111/b28320/dynviews_3016.htm
"SQL_ID: identifier SQL in the SQL statement that is currently running.
"PREV_SQL_ID: the last SQL statement executed SQL identifier.

This implies that SQL_ID holds a value when the session is running of a SQL statement. You can check by querying also the PREV_SQL_ID column:
```
select sid,sql_id,PREV_SQL_ID from V$session where username is not null;
```
Charles Hooper
Co-author of "Expert Oracle practices: Oracle Database Administration of the Oak Table.
http://hoopercharles.WordPress.com/
IT Manager/Oracle DBA
K & M-making Machine, Inc.

Vertical line for tables
Hi all
We have challenges to the vertical lines of the tables
Draw us lines between the horizontal lines. When data needed more space, the distance range for more data. But the vertical lines did not apply.

We found variable elasticity for vertical lines.

If you have any experience, please share it to us.

Thanks for once again,

NY
F4 or Double click
NULL for repeat image

http://nyapex.blogspot.com/2010/07/vertical-line-for-tables.html

Mark useful or correct accordingly

Count values not null for each column in a database
Hello

I need to write a routine that counts how many values a not null for each column in a database.
The first idea would be to loop on all_tables / all_tab_cols and write a select statement as
```
EXECUTE IMMEDIATE 'SELECT COUNT(*) FROM '||table_name||' WHERE '||column_name||' IS NOT NULL' INTO v_count;
```
However, this would mean a complete table for all columns not indexed scan. It's about when I have a maximum of 59 columns for a table with millions of rows.

A better idea? I don't have the exact number. For example, for the number of rows in a table, I just use all_tables.num_rows.

Concerning
Marcus
Ask the NUM_NULLS of the ALL_TAB_COLS column (and subtracting the total of the lines).

Why cannot create the table partitioned successfully?

SQL> create table hr.gps_log_his
(id number,
name varchar2(10),
time date)
tablespace ts_log_his
PARTITION BY RANGE (TIME)
(PARTITION udp_part09110707 VALUES LESS THAN (TO_DATE('09110708','yymmddhh24')),
PARTITION udp_part09110708 VALUES LESS THAN (TO_DATE('09110709','yymmddhh24')),
PARTITION udp_part09110709 VALUES LESS THAN (TO_DATE('09110710','yymmddhh24')),
PARTITION udp_part09110710 VALUES LESS THAN (maxvalue)
);

(PARTITION udp_part09110707 VALUES LESS THAN (TO_DATE('09110708','yymmddhh24')),
Error on line 7: 
ORA-14120: DATE columns did not specify the complete partitioning limits.

The detailed error message is as follows:

ORA-14120: incompletely specified partition bound for a DATE column

Cause: An attempt was made to use a date expression whose format does not fully
(i.e. day, month, and year (including century)) specify a date as a partition bound
for a DATE column. The format may have been specified explicitly (using TO_DATE()
function) or implicitly (NLS_DATE_FORMAT).

Action: Ensure that date format used in a partition bound for a DATE column supports
complete specification of a date (i.e. day, month, and year (including century)). If
NLS_DATE_FORMAT does not support complete (i.e. including the century) specification
of the year, use TO_DATE() (e.g. TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully
express the desired date.

Action: Change to_date('09110708','yymmddhh24') to
to_date('2009110708','yyyymmddhh24')

DBA_TABLES. NULL for tables partitioned, yet Nom_tablespace DBMS_METADATA. GET_DDL displays a name...

Similar Questions

Maybe you are looking for