JDeveloper, Table with Partitions

Hi,
iḿ designing a database with JDeveloper 11, but in the table object does not appear the partitioning option as manual shows.
(I'm following the example in the help.)
What's the problem ?
cheers
campos

campos,
Try checking the "advanced" checkbox in the edit table dialog (Frank - FYI it's in the "edit a offline database table"). This should make the partitioning option visible (note, tested on 11.1.1.3)
John

Similar Messages

ORA-00604 ORA-00904 When query partitioned table with partitioned indexes

Got ORA-00604 ORA-00904 When query partitioned table with partitioned indexes in the data warehouse environment.
Query runs fine when query the partitioned table without partitioned indexes.
Here is the query.
SELECT al2.vdc_name, al7.model_series_name, COUNT (DISTINCT (al1.vin)),
al27.accessory_code
FROM vlc.veh_vdc_accessorization_fact al1,
vlc.vdc_dim al2,
vlc.model_attribute_dim al7,
vlc.ppo_list_dim al18,
vlc.ppo_list_indiv_type_dim al23,
vlc.accy_type_dim al27
WHERE ( al2.vdc_id = al1.vdc_location_id
AND al7.model_attribute_id = al1.model_attribute_id
AND al18.mydppolist_id = al1.ppo_list_id
AND al23.mydppolist_id = al18.mydppolist_id
AND al23.mydaccytyp_id = al27.mydaccytyp_id
AND ( al7.model_series_name IN ('SCION TC', 'SCION XA', 'SCION XB')
AND al2.vdc_name IN
('PORT OF BALTIMORE',
'PORT OF JACKSONVILLE - LEXUS',
'PORT OF LONG BEACH',
'PORT OF NEWARK',
'PORT OF PORTLAND'
AND al27.accessory_code IN ('42', '43', '44', '45')
GROUP BY al2.vdc_name, al7.model_series_name, al27.accessory_code

I would recommend that you post this at the following OTN forum:
Database - General
General Database Discussions
and perhaps at:
Oracle Warehouse Builder
Warehouse Builder
The Oracle OLAP forum typically does not cover general data warehousing topics.

Is it possible to create table with partition in compress mode

Hi All,
I want to create a table in compress option, with partitions. When i create with partitions the compression isnt enabled, but with noramal table creation the compression option is enables.
My question is:
cant we create a table with partition/subpartition in compress mode..? Please help.
Below is the code that i have used for table creation.
CREATE TABLE temp
TRADE_ID                    NUMBER,
SRC_SYSTEM_ID               VARCHAR2(60 BYTE),
SRC_TRADE_ID                VARCHAR2(60 BYTE),
SRC_TRADE_VERSION           VARCHAR2(60 BYTE),
ORIG_SRC_SYSTEM_ID          VARCHAR2(30 BYTE),
TRADE_STATUS                VARCHAR2(60 BYTE),
TRADE_TYPE                  VARCHAR2(60 BYTE),
SECURITY_TYPE               VARCHAR2(60 BYTE),
VOLUME                      NUMBER,
ENTRY_DATE                  DATE,
    REASON                      VARCHAR2(255 BYTE),
TABLESPACE data
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
NOLOGGING
COMPRESS
NOCACHE
PARALLEL (DEGREE 6 INSTANCES 1)
MONITORING
PARTITION BY RANGE (TRADE_DATE)
SUBPARTITION BY LIST (SRC_SYSTEM_ID)
SUBPARTITION TEMPLATE
(SUBPARTITION SALES VALUES ('sales'),
   SUBPARTITION MAG VALUES ('MAG'),
   SUBPARTITION SPI VALUES ('SPI', 'SPIM', 'SPIIA'),
   SUBPARTITION FIS VALUES ('FIS'),
   SUBPARTITION GD VALUES ('GS'),
   SUBPARTITION ST VALUES ('ST'),
   SUBPARTITION KOR VALUES ('KOR'),
   SUBPARTITION BLR VALUES ('BLR'),
   SUBPARTITION SUT VALUES ('SUT'),
   SUBPARTITION RM VALUES ('RM'),
   SUBPARTITION DEFAULT VALUES (default)
PARTITION RMS_TRADE_DLY_MAX VALUES LESS THAN (MAXVALUE)
    LOGGING
        TABLESPACE data
     ( SUBPARTITION TS_MAX_SALES VALUES ('SALES')      TABLESPACE data,
    SUBPARTITION TS_MAX_MAG VALUES ('MAG')      TABLESPACE data,
    SUBPARTITION TS_MAX_SPI VALUES ('SPI', 'SPIM', 'SPIIA')      TABLESPACE data,
    SUBPARTITION TS_MAX_FIS VALUES ('FIS')      TABLESPACE data,
    SUBPARTITION TS_MAX_GS VALUES ('GS')      TABLESPACE data,
    SUBPARTITION TS_MAX_ST VALUES ('ST')      TABLESPACE data,
    SUBPARTITION TS_MAX_KOR VALUES ('KOR')      TABLESPACE data,
    SUBPARTITION TS_MAX_BLR VALUES ('BLR')      TABLESPACE data,
    SUBPARTITION TS_MAX_SUT VALUES ('SUT')      TABLESPACE data,
    SUBPARTITION TS_MAX_RM VALUES ('RM')      TABLESPACE data,
    SUBPARTITION TS_MAX_DEFAULT VALUES (default)      TABLESPACE data)); Edited by: user11942774 on 8 Dec, 2011 5:17 AM

user11942774 wrote:
I want to create a table in compress option, with partitions. When i create with partitions the compression isnt enabled, but with noramal table creation the compression option is enables. First of all your CREATE TABLE statement is full of syntax errors. Next time test it before posting - we don't want to spend time on fixing things not related to your question.
Now, I bet you check COMPRESSION value of partitioned table same way you do it for a non-partitioned table - in USER_TABLES - and therefore get wrong results. Since compreesion can be enabled on individual partition level you need to check COMPRESSION in USER_TAB_PARTITIONS:
SQL> CREATE TABLE temp
2 (
3    TRADE_ID                    NUMBER,
4    SRC_SYSTEM_ID               VARCHAR2(60 BYTE),
5    SRC_TRADE_ID                VARCHAR2(60 BYTE),
6    SRC_TRADE_VERSION           VARCHAR2(60 BYTE),
7    ORIG_SRC_SYSTEM_ID          VARCHAR2(30 BYTE),
8    TRADE_STATUS                VARCHAR2(60 BYTE),
9    TRADE_TYPE                  VARCHAR2(60 BYTE),
10    SECURITY_TYPE               VARCHAR2(60 BYTE),
11    VOLUME                      NUMBER,
12    ENTRY_DATE                  DATE,
13      REASON                      VARCHAR2(255 BYTE),
14    TRADE_DATE                  DATE
15 )
16 TABLESPACE users
17 PCTUSED    0
18 PCTFREE    10
19 INITRANS   1
20 MAXTRANS   255
21 NOLOGGING
22 COMPRESS
23 NOCACHE
24 PARALLEL (DEGREE 6 INSTANCES 1)
25 MONITORING
26 PARTITION BY RANGE (TRADE_DATE)
27 SUBPARTITION BY LIST (SRC_SYSTEM_ID)
28 SUBPARTITION TEMPLATE
29    (SUBPARTITION SALES VALUES ('sales'),
30     SUBPARTITION MAG VALUES ('MAG'),
31     SUBPARTITION SPI VALUES ('SPI', 'SPIM', 'SPIIA'),
32     SUBPARTITION FIS VALUES ('FIS'),
33     SUBPARTITION GD VALUES ('GS'),
34     SUBPARTITION ST VALUES ('ST'),
35     SUBPARTITION KOR VALUES ('KOR'),
36     SUBPARTITION BLR VALUES ('BLR'),
37     SUBPARTITION SUT VALUES ('SUT'),
38     SUBPARTITION RM VALUES ('RM'),
39     SUBPARTITION DEFAULT_SUB VALUES (default)
40    )
41 (
42   PARTITION RMS_TRADE_DLY_MAX VALUES LESS THAN (MAXVALUE)
43      LOGGING
44          TABLESPACE users
45       ( SUBPARTITION TS_MAX_SALES VALUES ('SALES')      TABLESPACE users,
46      SUBPARTITION TS_MAX_MAG VALUES ('MAG')      TABLESPACE users,
47      SUBPARTITION TS_MAX_SPI VALUES ('SPI', 'SPIM', 'SPIIA')      TABLESPACE users,
48      SUBPARTITION TS_MAX_FIS VALUES ('FIS')      TABLESPACE users,
49      SUBPARTITION TS_MAX_GS VALUES ('GS')      TABLESPACE users,
50      SUBPARTITION TS_MAX_ST VALUES ('ST')      TABLESPACE users,
51      SUBPARTITION TS_MAX_KOR VALUES ('KOR')      TABLESPACE users,
52      SUBPARTITION TS_MAX_BLR VALUES ('BLR')      TABLESPACE users,
53      SUBPARTITION TS_MAX_SUT VALUES ('SUT')      TABLESPACE users,
54      SUBPARTITION TS_MAX_RM VALUES ('RM')      TABLESPACE users,
55      SUBPARTITION TS_MAX_DEFAULT VALUES (default)      TABLESPACE users));
Table created.
SQL>
SQL>
SQL> SELECT PARTITION_NAME,
2          COMPRESSION
3    FROM USER_TAB_PARTITIONS
4    WHERE TABLE_NAME = 'TEMP'
5 /
PARTITION_NAME                 COMPRESS
RMS_TRADE_DLY_MAX              ENABLED
SQL> SELECT COMPRESSION
2    FROM USER_TABLES
3    WHERE TABLE_NAME = 'TEMP'
4 /
COMPRESS
SQL> SY.

Where's the metadata for STORE IN clause of a table with partition?

Hi Experts,
I created a table with a range-interval partition with STORE IN clause. It's definition:
CREATE TABLE interval_part (
person_id NUMBER(5) NOT NULL,
first_name VARCHAR2(30),
last_name VARCHAR2(30))
PARTITION BY RANGE (person_id)
INTERVAL (100) STORE IN (TSP_1, TSP_2, TSP_3) (
PARTITION p1 VALUES LESS THAN (101))
TABLESPACE TSP_1;
I can not find the metadata for STORE IN clause in ALL_TAB_PARTITIONS, ALL_TABLES. Where is the metadata for the STORE IN clause? How can I find the tablespace list (TSP_1, TSP_2, TSP_3)?
Thanks,
David

DBMS_METADATA.GET_DDL returns the definition of the table. But I just need the value of the tablespace list, for example, TSP_1, TSP_2, TSP_3. Is there any view which stored the value?
Thanks,
David

Troubles editing tables with partitions

I'm running SQL Developer 1.5.3 against Oracle 10/11 databases and SQL Developer has trouble with my partitioned tables. Both the schema owner and sys users experience the same problems.
The first time I try to edit a table, I get an "Error Loading Objects" dialog with a NullPointException message. If I immediately turn around and try to edit the table again, I get the Edit Table dialog. That's annoying but there's at least a work-around.
Next, if I select the Indexes pane, I can view the first index but selecting another one results in an "Index Error on <table>" error dialog. The message is "There are no table partitions on which to define local index partitions". At this point, selecting any of the other panes (Columns, Primary Key, etc.) results in the same dialog. While the main Partitions tab shows my partitions, I cannot see them in the Edit Table dialog. In fact, the Partition Definitions and Subpartition Templates panes are blank.
Does anyone else see this behavior? Version 1.5.1 behaved the same way so it's not new.
Of course I've figured out how to do everything I need through SQL but it would be handy if I could just use the tool.
Thank you.

Most of my tables are generated from a script so this morning I decided to just create a very basic partitioned table. It contained a NUMBER primary key and a TIMESTAMP(6) column to use with partitioning. That table worked just fine in SQL Developer.
At that point I tried to figure out what is different about my tables and I finally found the difference... Oracle Spatial. If I add an MDSYS.SDO_GEOMETRY column to my partitioned table, SQL Developer starts having issues.
I also have the GeoRaptor plugin installed so I had to wonder if it was interfering with SQL Developer. I couldn't find an option to uninstall an extension so I went into the sqldeveloper/extensions directory and removed GeoRaptorLibs and org.GeoRaptor.jar. GeoRaptor doesn't appear to be installed in SQL Developer anymore but I still see the same behavior.
It appears that there is an issue in SQL Developer with Oracle Spatial and partitioning. Can someone confirm this?

Possible to alter table with partitions to also have subpartitions online?

The subject says it all....
Is it possible to add hash sub-partitioning to an existing range partitioned table 'in-the-fly', or will it be necessary to create the new table structure first and reload the data?

You have to create a new table first.

Will there performance improvement over separate tables vs single table with multiple partitions?

Will there performance improvement over separate tables vs single table with multiple partitions? Is advisable to have separate tables than having a single big table with partitions? Can we expect same performance having single big table with partitions? What is the recommendation approach in HANA?

Suren,
first off a friendly reminder: SCN is a public forum and for you as an SAP employee there are multiple internal forums/communities/JAM groups available. You may want to consider this.
Concerning your question:
You didn't tell us what you want to do with your table or your set of tables.
As tables are not only storage units but usually bear semantics - read: if data is stored in one table it means something else than the same data in a different table - partitioned tables cannot simply be substituted by multiple tables.
Looked at it on a storage technology level, table partitions are practically the same as tables. Each partition has got its own delta store & can be loaded and displaced to/from memory independent from the others.
Generally speaking there shouldn't be too many performance differences between a partitioned table and multiple tables.
However, when dealing with partitioned tables, the additional step of determining the partition to work on is always required. If computing the result of the partitioning function takes a major share in your total runtime (which is unlikely) then partitioned tables could have a negative performance impact.
Having said this: as with all performance related questions, to get a conclusive answer you need to measure the times required for both alternatives.
- Lars

Insert performance issue with Partitioned Table.....

Hi All,
I have a performance issue during with a table which is partitioned. without table being partitioned
it ran in less time but after partition it took more than double.
1) The table was created initially without any partition and the below insert took only 27 minuts.
Total Rec Inserted :- 2424233
PL/SQL procedure successfully completed.
Elapsed: 00:27:35.20
2) Now I re-created the table with partition(range yearly - below) and the same insert took 59 minuts.
Is there anyway i can achive the better performance during insert on this partitioned table?
[ similerly, I have another table with 50 Million records and the insert took 10 hrs without partition.
with partitioning the table, it took 18 hours... ]
SQL> select * from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 4195045590
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 643K| 34M| | 12917 (3)| 00:02:36 |
|* 1 | HASH JOIN | | 643K| 34M| 2112K| 12917 (3)| 00:02:36 |
| 2 | VIEW | index$_join$_001 | 69534 | 1290K| | 529 (3)| 00:00:07 |
|* 3 | HASH JOIN | | | | | | |
| 4 | INDEX FAST FULL SCAN| PK_ACCOUNT_MASTER_BASE | 69534 | 1290K| | 181 (3)| 00:00
| 5 | INDEX FAST FULL SCAN| ACCOUNT_MASTER_BASE_IDX2 | 69534 | 1290K| | 474 (2)| 00:00
PLAN_TABLE_OUTPUT
| 6 | TABLE ACCESS FULL | TB_SISADMIN_BALANCE | 2424K| 87M| | 6413 (4)| 00:01:17 |
Predicate Information (identified by operation id):
1 - access("A"."VENDOR_ACCT_NBR"=SUBSTR("B"."ACCOUNT_NO",1,8) AND
"A"."VENDOR_CD"="B"."COMPANY_NO")
3 - access(ROWID=ROWID)
Open C1;
Loop
Fetch C1 Bulk Collect Into C_Rectype Limit 10000;
Forall I In 1..C_Rectype.Count
Insert test
     col1,col2,col3)
Values
     val1, val2,val3);
V_Rec := V_Rec + Nvl(C_Rectype.Count,0);
Commit;
Exit When C_Rectype.Count = 0;
C_Rectype.delete;
End Loop;
End;
Total Rec Inserted :- 2424233
PL/SQL procedure successfully completed.
Elapsed: 00:51:01.22
Edited by: user520824 on Jul 16, 2010 9:16 AM

I'm concerned about the view in step 2 and the index join in step 3. A composite index with both columns might eliminate the index join and result in fewer read operations.
If you know which partition the data is going into beforehand you can save a little bit of processing by specifying the partition (which may not be a scalable long-term solution) in the insert - I'm not 100% sure you can do this on inserts but I know you can on selects.
The APPEND hint won't help the way you are using it - the VALUES clause in an insert makes it be ignored. Where it is effective and should help you is if you can do the insert in one query - insert into/select from. If you are using the loop to avoid filling up undo/rollback you can use a bulk collect to batch the selects and commit accordingly - but don't commit more often than you have to because more frequent commits slow transactions down.
I don't think there is a nologging hint :)
So, try something like
insert /*+ hints */ into ...
Select
     A.Ing_Acct_Nbr, currency_Symbol,
     Balance_Date,     Company_No,
     Substr(Account_No,1,8) Account_No,
     Substr(Account_No,9,1) Typ_Cd ,
     Substr(Account_No,10,1) Chk_Cd,
     Td_Balance,     Sd_Balance,
     Sysdate,     'Sisadmin'
From Ideaal_Cons.Tb_Account_Master_Base A,
     Ideaal_Staging.Tb_Sisadmin_Balance B
Where A.Vendor_Acct_Nbr = Substr(B.Account_No,1,8)
   And A.Vendor_Cd = b.company_no
      ;Edited by: riedelme on Jul 16, 2010 7:42 AM

Flashack table and partitions??

Hi All,
Can We use the flash back tables with partitions...
Any idea or any document about Flash back table and partitions relationship in 11 or 10g would help...
Thanks

Hi,
we need to input PRT material Number and get in which and all tasklists it is being used
Our PRT material number is of 12 digits and i could not find any suitable field to input the PRT material number in the table PLFH
our PRT is like this
FA115200A001
how to input these PRT material numbers and get the required data
regards,
Madhu Kiran

Index on Partitioned Table with Some ReadOnly Tablespaces

We have a warehouse with fact tables range partitioned on date - daily partitions with each month worth of partitions put into a specific monthly tablespace. Each month, we set the prior month's tablespace to READONLY. So our table ends up having data in readonly and read-write tablespaces.
We now have a change we need to make to one of the fact tables - we need to add a new column AND add an index to that column. But because we have partitions in readonly state, Oracle doesn't let us create the index and it also doesn't let us update the local unique key (unique index).
Is there a way we can do this without having to put the tablespaces in read-write mode? As importantly, what happens when we offline or drop some of the older tablespaces (for archiving purposes)? We need to find a way to add the index on just the read-write partitions.
Thanks.

We have a warehouse with fact tables range
partitioned on date - daily partitions with each
month worth of partitions put into a specific monthly
tablespace. Each month, we set the prior month's
tablespace to READONLY. So our table ends up having
data in readonly and read-write tablespaces.
We now have a change we need to make to one of the
fact tables - we need to add a new column AND add an
index to that column. But because we have partitions
in readonly state, Oracle doesn't let us create the
index and it also doesn't let us update the local
unique key (unique index).
Is there a way we can do this without having to put
the tablespaces in read-write mode? As importantly,
what happens when we offline or drop some of the
older tablespaces (for archiving purposes)? We need
to find a way to add the index on just the read-write
partitions.
Thanks.Hi,
Improvements in Oracle 10g to maintain local-partitioned indexes when you use partition DDL commands:
add partition, split partition, merge partiton, move partition.
ALSO, the associated indexes NO LONGER have to be stored on the same tablespace as the table (i.e. answer to your question).
On Oracle 9i: Local indexes are recommended on data warehouse platforms. In an OLTP system, global indexes are more common. On a data data warehouse, problems can be isoloted to one partition, the partitions moved, made r/o (like yours), no local indexes need to be rebuilt
Regarding your issue:
We now have a change we need to make to one of the
fact tables - we need to add a new column AND add an
index to that columnTo maintain the simplicity + functionality of your DW configuration, I think you need to change the TS to R/W, update the objects, then alter to R/O.
fyi
http://www.oracle.com/technology/deploy/availability/htdocs/online_ops.html

Takes long time to drpo tables with large numbers of partitions

11.2.0.3
This is for a build. We are still in development. No risk of data loss. As part of the build, I drop the user,re-create it, re-create the objects. Allows us to test the build all the way through. Its our process.
This user has some tables with several 1000 partitions. I ran a 10046 trace and oracle is using pl/sql to do loops to do DML against the data dictionary. Anyway to speed this up? I am going to turn off the recyclebin during the build and turn it back on.
anything else I can do? Right now I just issue 'drop user cascade'. Part of is the weak hardware we have in the development/environment. Takes about 20 minutes just to run through this part of the script (the script has alot more pieces than this) and we do fairly frequent builds.
I can't change the build process. My only option is to try to make this run a little faster. I can't do anything about the hardware (lots of VMs crammed onto too few servers).
This is not a production issue. Its more of a hassle.

Support Note 798586.1 shows that DROP USER CASCADE was slower than dropping individual objects -- at least in 10.2 Not sure if it still the case in 11.2
Hemant K Chitale

How to Create a Table with Merge and partitions in HANA

Hi,
What is the best way to create a Table with MERGE and PARTITION and UNLOAD PRIORITIES.
Any body can you please give me some examples.
Regards,
Deva

Ok,
1) the UNLOAD PRIORITY has nothing to do with the order of data loads in your ETL process
2) Unloading of columns will happen automatically. Don't specify anything specific for the tables, then SAP HANA will take care about it
3) Not sure where you get your ideas from, but there is no need to manually "flush" tables or anything like that. SAP HANA will take care of memory housekeeping.
4) Partitioning and how to specify it for tables has been largely documented. Just read up on it.
5) Delta Merge will happen automatically, as long as you don't prevent it (e.g. by trying to outsmart the mergedog rules)
Seriously, I get the impressions that this list of requirements is based on some hear-say and lack of actual information and experience with SAP HANA. There are a couple of extensive discussions on data loading optimization available here in SCN and on SAPHANA.COM. Please read those first.
All this had been discussed broadly a couple of times.
- Lars

Table with BLOB column re-partitioning

Currently I have a table with a blob column Z partitioned on Column X I want to re-partition the table on Column Y is there a quick way of doing this.
INSERT INTO SELECT * has limitations on the blob size I guess.
Can someone explain this?
Edited by: user10229350 on Mar 1, 2010 7:36 AM

I am using hash partitioning looks like split partition doesn't apply for hash partition:
"The SPLIT PARTITION clause of the ALTER TABLE or ALTER INDEX statement is used to redistribute the contents of a partition into two new partitions. Consider doing this when a partition becomes too large and causes backup, recovery, or maintenance operations to take a long time to complete. You can also use the SPLIT PARTITION clause to redistribute the I/O load.
This clause cannot be used for hash partitions or subpartitions."

Table creation with partition

following is the table creation script with partition
CREATE TABLE customer_entity_temp (
BRANCH_ID NUMBER (4),
ACTIVE_FROM_YEAR VARCHAR2 (4),
ACTIVE_FROM_MONTH VARCHAR2 (3),
partition by range (ACTIVE_FROM_YEAR,ACTIVE_FROM_MONTH)
(partition yr7_1999 values less than ('1999',TO_DATE('Jul','Mon')),
partition yr12_1999 values less than ('1999',TO_DATE('Dec','Mon')),
it gives an error
ORA-14036: partition bound value too large for column
but if I increase the size of the ACTIVE_FROM_MONTH column to 9 , the script works and creates the table. Why is it so ?
Also, by creating a table in this way and populating the table data in their respective partitions, all rows with month less than "JULY" will go in yr7_1999 partition and all rows with month value between "JUL" and "DEC" will go in the second partition yr12_1999 , where will the data with month value equal to "DEC" go?
Plz help me in solving this problem
thanks n regards
Moloy

Hi,
You declared ACTIVE_FROM_MONTH VARCHAR2 (3) and you try to check it against a date in your partitionning clause:TO_DATE('Jul','Mon')so you should first check your data model and what you are trying to achieve exactly.
With such a partition decl, you will not be able to insert dates from december 1998 included and onward. The values are stricly less than (<) not less or equal(<=) hence such lines can't be inserted. I'd advise you to check the MAXVALUE value jocker and the ENABLE ROW MOVEMENT partitionning clause.
Regards,
Yoann.

Large partitioned tables with WM

Hello
I've got a few large tables (6-10GB+) that will have around 500k new rows added on a daily basis as part of an overnight batch job. No rows are ever updated, only inserted or deleted and then re-inserted. I want to stop the process that adds the new rows from being an overnight batch to being a near real time process i.e. a queue will be populated with requests to rebuild the content of these tables for specific parent ids, and a process will consume those requests throughout the day rather than going through the whole list in one go.
I need to provide views of the data asof a point in time i.e. what was the content of the tables at close of business yesterday, and for this I am considering using workspaces.
I need to keep at least 10 days worth of data and I was planning to partition the table and drop one partition every day. If I use workspaces, I can see that oracle creates a view in place of the original table and creates a versioned table with the LT suffix - this is the table name returned by DBMSMW.GetPhysicalTableName. Would it be considered bad practice to drop partitions from this physical table as I would do with a non version enabled table? If so, what would be the best method for dropping off old data?
Thanks in advance
David

Hello Ben
Thank you for your reply.
The table structure we have is like so:
CREATE TABLE hdr
(   pk_id               NUMBER PRIMARY KEY,
    customer_id         NUMBER FOREIGN KEY REFERENCES customer,
    entry_type          NUMBER NOT NULL
CREATE TABLE dtl_daily
(   pk_id               NUMBER PRIMARY KEY,
    hdr_id              NUMBER FOREIGN KEY REFERENCES hdr
    active_date         DATE NOT NULL,
    col1                NUMBER
    col2                NUMBER
PARTITION BY RANGE(active_date)
(   PARTITION ptn_200709
        VALUES LESS THAN (TO_DATE('200710','YYYYMM'))
        TABLESPACE x COMPRESS,
    PARTITION ptn_200710
        VALUES LESS THAN (TO_DATE('200711','YYYYMM'))
        TABLESPACE x COMPRESS
CREATE TABLE dtl_hourly
(   pk_id               NUMBER PRIMARY KEY,
    hdr_id              NUMBER FOREIGN KEY REFERENCES hdr
    active_date         DATE NOT NULL,
    active_hour         NUMBER NOT NULL,
    col1                NUMBER
    col2                NUMBER
PARTITION BY RANGE(active_date)
(   PARTITION ptn_20070901
        VALUES LESS THAN (TO_DATE('20070902','YYYYMMDD'))
        TABLESPACE x COMPRESS,
    PARTITION ptn_20070902
        VALUES LESS THAN (TO_DATE('20070903','YYYYMMDD'))
        TABLESPACE x COMPRESS
    PARTITION ptn_20070903
        VALUES LESS THAN (TO_DATE('20070904','YYYYMMDD'))
        TABLESPACE x COMPRESS
    ...For every day for 20 years
/The hdr table holds one or more rows for each customer and has it's own synthetic key generated for every entry as there can be multiple rows having the same entry_type for a customer. There are two detail tables, daily and hourly, which hold detail data at those two granularities. Some customers require hourly detail, in which case the hourly table is populated and the daily table is populated by aggregating the hourly data. Other customers require only daily data in which case the hourly table is not populated.
At the moment, changes to customer data require that the content of these tables are rebuilt for that customer. This rebuild is done every night for the changed customers and I want to change this to be a near real time rebuild. The rebuild involves deleteing all existing entries from the three tables for the customer and then re-inserting the new set using new synthetic keys. If we do make this near real time, we need to be able to provide a snapshot of the data asof close of business every day, and we need to be able to report as of a point of time up to 10 days in the past.
For any one customer, they may have rows in the hourly table that goes out 20 years at a hourly granularity, but once the active date has passed(by 10 days), we no longer need to keep it. This is why we were considering partitioning as it gives us a simple way of dropping off old data, and as a nice side effect, helps to improve performance of queries that are looking for active data between a range of dates (which is most of them).
I did have a look at the idea of save points but I wasn't sure it would be efficient. So in this case, would the idea be that we don't partition the table but instead at close of business every day, we create a savepoint like "savepoint_20070921" and instead of using dbms_wm.gotodate. we would use dbms_wm.gotosavepoint. Then every day we would do
DBMS_WM.DeleteSavepoint(
   workspace                   => 'LIVE',
   savepoint_name              => 'savepoint_20070910', --10 days ago
   compress_view_wo_overwrite => TRUE,
DBMS_WM.CompressWorkspace(
   workspace                   => 'LIVE,
   compress_view_wo_overwrite => TRUE,
   firstSP                     => 'savepoint_20070911', --the new oldest save point
   );Is my understanding correct?
David
Message was edited by:
fixed some formatting
David Tyler

JDeveloper, Table with Partitions

Similar Messages

Maybe you are looking for