Is partitioning the ra_customer_trx_lines_all table by time as well as safe

Hi We're using Oracle Applications 11.5.10.2
Is partitioning the ra_customer_trx_lines_all table by time as well as its indexes safe?
It's getting huge and we wanted to cut down on query time. Someone here told me that partitioning it could be bad because Applications doesn't expect that table or its indexes to be partitioned and had queries tuned to query that table as a non-partitioned table with non-partitioned indexes.
Is this true?

Hi,
Please also see this related thread.
Partitioning GL_BALANCES
Partitioning GL_BALANCES
Please note that using partitioning requires extra license.
Thanks,
Hussein

Similar Messages

Partitioning the fact table

Hi Gurus,
I have a question regarding partitioning the cube. When you partition the cube from the Extras menu, will it partition the F table or is it the E table or both.
Second question: After partitioning, how will i know the newly created table names.
Thanks,
ANU

Hi Anu,
Partition Need and its definition
Infocube contains huge amount of data n the table size of the cube increases regularly. so
when a query is executed on cube then it has to check entire table to get the records for
example Sales in Jan08.
Advantage of Partition
so we can partition the cube so that smaller tables are formed .so that report performance
will increase bcoz the query hits that particular partition.
Steps for Partition
1.To partiotion a cube, it must not contain data.
2. Partition can be done using time characteristics 0CALMONTH and fiscalperiod.
steps:
1. in change of the cube, select extras menu and Partioning option.
2. select calmonth time characteristic.
3. it will ask for the time period to partiotion and no. of partiotions. give them
4. activate the cube.
In BI 7 we can partition the cube even if it contains data.
select the cube, right click , select repartitioning.
1. we can delete existing partitions
2. create new ones
3. merge partitions.
Partitioning of the Cube
http://help.sap.com/saphelp_nw04s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Partitioning Fields and Values
partition of Infocube
Partitioning of cube using Fiscal period
Infocube Partition
After Partition
You can find the Partition in the following tables in SE11 >
E tables /BIC/E* or /BIC/E(cube name)
Please also go through the following links
Partioning of Cube
partioning
Partioning of ODS object
/thread/733456 [original link is broken]
Hope i had answered your question
Assign points if helpful,
Thanks and regards
Bala

Partitioning the OKL_STRM_ELEMENTS table

I am looking for someone with experience with partitioning the OKL_STRM_ELEMENTS table. I would like to know what you partitioned on and if you had any problems once you implemented the partitions. Besides the OKL_STRM_ELEMENTS table are there any other Lease Management table that should be partitioned.
BLC

This is documentation of the Partitioning the OKL_STRM_ELEMENTS table
You should made a proposal to partition the table based on STREAM_ELEMENT_DATE Performance team however suggested creating a larger number of partitions using a smaller range (MMYYYY vs YYYY) rather than using a subpartition by hash(ID).
Performance benefits may be seen in SQL statements that take advantage of the partioning scheme resulting in partition elimination (i.e. the sqls actually scan less data), this happens for sqls that have the partition key in the WHERE clause.
Partitioning a table can actually degrade overall performance if the SQL statements referencing this table do not include the partition key in the WHERE clause as a filter. The performance degradation is caused by the fact that the query has to scan several partitions as opposed to a single segment in the non-partitioned case.
The majority of select statements on OKL_STRM_ELEMENTS in OKL do include STREAM_ELEMENT_DATE in the where clause, so overall benefit should be positive.
Moreover, ranges should be based on analysis of your data distribution

Partitioning a fact table

I am curious to hear techniques for partitioning a fact table with OWB. I know HOW to setup the partitioning for the table, but what I am curious about is what type of partitioning everyone is suggesting. Take the following example...Lets say we have a sales transaction fact table. It has dimensions of Date, Product, and Store. An immediate partitioning idea is to partition the table by month. But my curiosity arises in the method used to partition the fact table. There is no longer a true date field in the fact table to do range partitioning on. And hash partitioning will not distribute the records by month.
One example I found was to "code" the surrogate key in the date dimension so that it was created in the following manner "YYYYMMDD". Then you could use the range partitioning based on values of the key in the fact table less than 20040200 for Jan. 2004, less than 20040300 for Feb. 2004, and so on.
Is this a good idea?

Jason,
In general, obviously, query performance and scaleability benefit from partitioning. Rather than hitting the entire table upon retrieving data, you would only hit a part of the table. There are two main strategies to identify what partitioning strategy to choose:
1) Users always query specific parts of the data (e.g. data from a particular month) in which case it makes sense for the part to be the size of the partition. If your end users often query by month or compare data on a month-by-month basis, then partitioning by month may well be the right strategy.
2) Improve data loading speed by creating partitions. The database supports partion exchange loading, supported by Warehouse Builder as well, which enables you to swap out a temporary table and a partition at once. In general, your load frequency then decides your partitioning strategy: if you load on a daily basis, perhaps you want daily partions. Beware that for Warehouse Builder to use the partition exchange loading feature you will have to have a date field in the fact table, so you would change the time dimension.
In general, your suggestion for the generated surrogate key would work.
Thanks,
Mark.

Opinion needed on best way to map multiple table joins (of the same table)

Hi all
I have a query of the format:
select A.col1, B.col1,C.col1
FROM
MASTER_TABLE A, ATTRIBUTE_TABLE B, ATTRIBUTE_TABLE C
WHERE
A.key1 = B.key1 (+)
AND
A.key1 = C.key1(+)
AND
B.key2(+) = 100001
AND
C.key2(+) = 100002
As you can see, I am joining the master table to the attribute table MANY times over, (over 30 attributes in my actual query) and I am struggling to find the best way to map this efficiently as the comparison for script vs. mapping is 1:10 in execution time.
I would appreciate the opinion of experienced OWB users as to how they would tackle this in a mapping and to see if they use the same approach as I have done.
Many thanks
Adi

SELECT external_reference, b.attribute_value AS req_date,
c.attribute_value AS network, d.attribute_value AS spid,
e.attribute_value AS username, f.attribute_value AS ctype,
g.attribute_value AS airtimecredit, h.attribute_value AS simnum,
i.attribute_value AS lrcredit, j.attribute_value AS airlimitbar,
k.attribute_value AS simtype, l.attribute_value AS vt,
m.attribute_value AS gt, n.attribute_value AS dt,
o.attribute_value AS datanum, p.attribute_value AS srtype,
q.attribute_value AS faxnum,
R.ATTRIBUTE_VALUE AS FAXSRTYPE,
s.attribute_value AS extno,
t.attribute_value AS tb, u.attribute_value AS gb
v.attribute_value AS mb, w.attribute_value AS stolenbar,
x.attribute_value AS hcredit, y.attribute_value AS adminbar,
z.attribute_value AS portdate
FROM csi_item_instances a,
csi_iea_values b,
csi_iea_values c,
csi_iea_values d,
csi_iea_values e,
csi_iea_values f,
csi_iea_values g,
csi_iea_values h,
csi_iea_values i,
csi_iea_values j,
csi_iea_values k,
csi_iea_values l,
csi_iea_values m,
csi_iea_values n,
csi_iea_values o,
csi_iea_values p,
csi_iea_values q,
CSI_IEA_VALUES R,
csi_iea_values s,
csi_iea_values t,
csi_iea_values u,
csi_iea_values v,
csi_iea_values w,
csi_iea_values x,
csi_iea_values y,
csi_iea_values z
WHERE a.instance_id = b.instance_id(+)
AND a.instance_id = c.instance_id(+)
AND a.instance_id = d.instance_id(+)
AND a.instance_id = e.instance_id(+)
AND a.instance_id = f.instance_id(+)
AND A.INSTANCE_ID = G.INSTANCE_ID(+)
AND a.instance_id = h.instance_id(+)
AND a.instance_id = i.instance_id(+)
AND a.instance_id = j.instance_id(+)
AND a.instance_id = k.instance_id(+)
AND a.instance_id = l.instance_id(+)
AND a.instance_id = m.instance_id(+)
AND a.instance_id = n.instance_id(+)
AND a.instance_id = o.instance_id(+)
AND a.instance_id = p.instance_id(+)
AND a.instance_id = q.instance_id(+)
AND A.INSTANCE_ID = R.INSTANCE_ID(+)
AND a.instance_id = s.instance_id(+)
AND a.instance_id = t.instance_id(+)
AND a.instance_id = u.instance_id(+)
AND a.instance_id = v.instance_id(+)
AND a.instance_id = w.instance_id(+)
AND a.instance_id = x.instance_id(+)
AND a.instance_id = y.instance_id(+)
AND a.instance_id = z.instance_id(+)
AND b.attribute_id(+) = 10000
AND c.attribute_id(+) = 10214
AND d.attribute_id(+) = 10132
AND e.attribute_id(+) = 10148
AND f.attribute_id(+) = 10019
AND g.attribute_id(+) = 10010
AND h.attribute_id(+) = 10129
AND i.attribute_id(+) = 10198
AND j.attribute_id(+) = 10009
AND k.attribute_id(+) = 10267
AND l.attribute_id(+) = 10171
AND m.attribute_id(+) = 10184
AND n.attribute_id(+) = 10060
AND o.attribute_id(+) = 10027
AND p.attribute_id(+) = 10049
AND q.attribute_id(+) = 10066
AND R.ATTRIBUTE_ID(+) = 10068
AND s.attribute_id(+) = 10065
AND t.attribute_id(+) = 10141
AND u.attribute_id(+) = 10072
AND v.attribute_id(+) = 10207
AND w.attribute_id(+) = 10135
AND x.attribute_id(+) = 10107
AND y.attribute_id(+) = 10008
AND z.attribute_id(+) = 10103
AND external_reference ='07920490103'
If I run this it takes less than a second in TOAD, when mapped in OWB it takes ages. 10:1 is a conservative estimate. In reality it takes 15-20 minutes. CSI_IEA_VALUES has 30 million rows CSI_ITEM_INSTANCES has 500,000 rows.
Hope that helps. I would love to know how others would tackle this query.

Cloning TC backups to external HD with data on it already - should i partition the HD? How to do this safely?

hi. i found a discussion directing how to clone backups onto a HD for proper backup transfer. what it didn't anwer for me, was something else. i have data on the HD i am trying to use as a temp destination for my TC backups. Should i partition the destination drive and have my old data on one volume - TC backup on the other? please help if you could with instructions on how to do it safely without distroying my data! THANKS A BUNCH!
OS mountain lion, 1st gen TC, 500gb, destination HD - WD passport for mac, 1tb.

Yes. Time Machine works better if it is in total control of its storage space.
Of course partitioning the drive in a Time Capsule is only possible by removing it and doing the partitioning on another computer.
If this were mine I would get another external drive and connect that to the Time Capsule. Move your data to the new external and allow Time Machine to use the whole internal drive in the Time Capsule instead.
Allan

Partitioning on a table on the field TIMESTAMP WITH TIME ZONE

Hi I have a very large size table which has grown to a size that we are not able to query it efficiently. We have decided to partition the table. But the issue is the table has a TIMESTAMP WITH TIME ZONE field and not DATE. I have found some links on the web which state this might cause an error. I am planning to create a temp table with the partition rules and at the same time copy data from the original one.
using CREATE TABLE XYZ PARTITION BY RANGE (ABC) ( ---- Partition rules ------) NOLOGGING AS SELECT * FROM XYZ_ACTUAL where 1 = 2;
Then if it works fine, I would rename the table with partitions to the actual name.
Should all this be fine?
The database is very critical. Hence the dilemma.

Have you tried converting the timestamp with time zone to a character string as a partition key, possibly using an edit mask to control the timestamp components used?
Your plan sounds OK to me - if you can get the partitioned table created - but I would test in a development first o see where the lLw of Unintended Consequences might decide to manifest itself.
Edited by: riedelme on Dec 8, 2009 9:13 AM

I have partitioned my time capsule, but I can't get it to work as a Time Machine back up and permanent media server for both mac and PC. What format do I need to partition the drive to so that it works for both mac and windows and so that it will be visab

I have partitioned my time capsule, as I want part of it to act as a media server for both mac and windows. However I don't know what format that I need to partition it to. I also can't make it a permanently accesible drive. I want to restore the drive to the original format (which I don't know) and start again and re-partition the drive in a format that can be used for media by both mac and PC and for time machine back-ups and make the media part of it permanetly accesible so I can add and acccess my files.
Thanks

You are mixing up a couple of things here.
The TC drive cannot be partitioned without removing it.. did you do that?
If you partition it you must use a Mac disk utility and use the HFS+ ie standard Mac format. And GUID partition table not windows type.
You can select erase disk in the airport utility.. that will take the disk back to original format. No partitions. TC is deliberately not partitioned as it is not a media server.. it is a backup device for TM. Over time .. the disk will be filled with TM backups so you have a long history of file changes to your computer.
There is no media server in the TC.. it is merely disk storage.. you can serve files from it to a media device.. but the TC itself is dumb as dumb.
Now the actual format of the drive is irrelevant to the PC.. The TC offers SMB file services to the network. You can copy files to and from the TC as if it was a local disk without caring one iota about the format. The TC handles that .. it is not a local disk .. it is a network drive.
Although you cannot partition the TC. you can still copy files to it.. this does have implications for TM.. but as long as there is plenty of free space should not be a major issue.
You can create a disk image via the disk utility in a Mac.. and as stated you can create partitions if you do it on a Mac with the disk directly connected which means breaking warranty if any exists on the TC.

I am setting up a time machine backup to a external Hard drive. I want to backup by Mac book Pro running OSX 10.8.5. I would like to Partition the disk and use one partition for Time machine backups and the other for my Lightroom backups. How to do this?

I want to create a two partition disk. One partition for time machine, the other for Lightroom backup. Currently Time Machine is using the entire drive and it is doing the intial encryption and is about 29% complete after two days. I've decided that I want to turn encryption off and partition the disk. So I do I start over?

With the external drive attached, open Finder>Applications>Utilities>Disk Utility. Select the external drive from the list in the left side panel of the DU window. In the main window panel, click Partition in the buttons top center of that panel.
Select the number of partitions you want and adjust their sizes.
For the first partition, click to highlight the partition, then select the format, Mac OS Extended (Journaled) and then the partition table as GUID [both of those are the defaults]. Click Apply and it will ask to confirm and erase and format that partion...oh, give the partition a name, like Backup.
Then repeat those steps for the second partition..and remember to name it...something like Lightroom.
Close Disk Utilitty and you are ready to send TM to the one partition, and do your backup of Lightroom to the second partition.

How to choose the partition in oracle tables?

Dear all,
i m in need to create the partitions on prod.db tables since i m not aware of creating partitions?i just go through some theroy concepts and understood the range and list partitions (i.e)Range is normally used for values less than like jan,feb,march or values less than 50,000 values less than 1,00,000 like that each partition is having separate tablespaces to increase the performance. and for list is used to denoting the directions like west,east,north,south like that.
Now what i want to know is ?
1.)when will i can go ahead with partitions?
2.)before creating partitions is it advise to create index or not needed?
3.)if i started to create partition what is the leading column have to create partition and which partition has to choose?
pls let me know and pardon me if i did any mistakes.
thanks in advance..

I had to research on same topic. One of my teammates suggested few points that might help you also.
Advantages of partitioning:
1) Partitioning enables data management operations such data loads, index creation and rebuilding, and backup/recovery at the partition level, rather than on the entire table. This results in significantly reduced times for these operations.
2) Partitioning improves query performance. In some cases, the results of a query can be achieved by accessing a subset of partitions, rather than the entire table. Parallel queries/DML and Partition-wise Joins are also got benefited much.
3) Partitioning increases the availability of mission-critical databases if critical tables and indexes are divided into partitions to reduce the maintenance windows, recovery times, and impact of failures. (Each partition can have separate physical attributes such as pctfree, pctused, and tablespaces.)
Partitioning can be implemented without requiring any modifications to your applications. For example, you could convert a nonpartitioned table to a partitioned table without needing to modify any of the SELECT statements or DML statements which access that table. You do not need to rewrite your application code to take advantage of partitioning.
Disadvantages of partitioning:-
1) Advantages of partition nullified when you use bind variables.
Additional administration tasks to manage partitions viz. If situation arises for rebuilding of index then rebuilding should to be done for each individual partition.
2) Need more space to implement partitioning objects.
3) More time for some tasks, such as create non-partitioning indexes, collection of “global" statistics (dbms_stat’s granularity parameter to be set to GLOBAL. if sub partition are used then we have to set it to ALL).
4) Partition would implies a modification (of explain plan) for ALL the queries against the partitioned tables. So, if some queries use the choosing partition key and may greatly improve, some other queries not use the partition key and are dramatically bad impact by the partitioning.
5) To get the full advantage of partitioning (partition pruning, partition-wise joins, and so on), you must use the Cost Based Optimizer (CBO). If you use the RBO, and a table in the query is partitioned, Oracle kicks in the CBO while optimizing it. But because the statistics are not present, the CBO makes up the statistics, and this could lead to severely expensive optimization plans and extremely poor performance.
Message was edited by:
Abou

Partitioning the tables

i have a table that logs an actigtivity
it has activity date time
its a very large table...which i havnt partitioned.
because i havnt got the archiving requirements.
my questions is .. should i blindly create a monthly partition based on date key or should i wait for the archiving requirements?
what is the criteria to partition the table?
is it the amount of data ... or the archiving strategy. which one of these two should i take as the deciding factor to create partitions
regards
raj

my problem is that
i have two tables A and B
A has a column called activity date time and B is the child table for A.
i did not create partitions on both the tables because... i did not know the online data requirement.
now for a code move people are complaining that i did not create monthly partitions before...
my quesitioon is that...
shouldnt we wait for the online data requirement to come then think of partitioning the table?
or rather than waiting
should we blindly create the monthly partitions on activity date time?
regards
raj

Partitioning the table ...

I have procedure which inserts the data based on sysdate (everyday). I have partitioned the table using partition by list i have created 31 partitions on this table.
say for example if tis 8th of sep then the partition will be xyz_08 and tommorow will be xyz_09 similarly i have 31 partitions.
I was trying to insert manually by changing sys dates for example like sysdate -1, sysdate -2, sysdate -3 and so on. And it worked absolutely fine
My requirement :- is once its reaches to 31st partition then it has to drop the 1st partition and so on it continues by droping old partitions everyday once its inserted with the latest partition.
my questions
- how do incorporate a logic of adding partitions everyday ?
- how to drop the oldest partition(1st partition ) when it reaches the 31 partition ?
- do i need to use cursors and for loop to archive this both above tasks ?
Any logic with example would be great. Sample code will be wonderful ??
Thank you so much i appreciate it. !!!

user642297 wrote:
let me share my code how i am implementing the partition by list ...Please use the *\* tag before and after a sample code block (or database output) that you post. This formats the code properly (as predefined text output) and is a lot easier on the eye to read. (yes - copy the tag exactly as you see it here and paste it into your posting).
In my previous posting i mentioned about the droping the partition. But thats not the right way i guess. Because if i drop the partition then the data will not be loaded in the same partition next time since that partition will be dropped.
The best way would be truncating the partition i guess. so next time we can load the data in the same partition ....
Correct. You can simply truncate the partition to empty it and ready if for a new data set. However, as already mentioned, a range partition and not a list partition may be more suitable.
One of the great features of partitioning is called +partition pruning+. This means Oracle, at run-time, figures out what partitions to use, and what partitions to ignore, for a specific SQL query. As the data is date based. it makes more sense to use a date range partition - this allows pruning to happen when you look for data for a specific date or date range. With a list partition, you need to use the list column as is as a predicate... and it will be unusual to construct queries that only look at the day number and not as the date as a whole.
few more questions
- if i drop the table, will partitions will also be dropped automatically ? or do i need to explicitly drop the partitions before dropping the table ?
Yes. Partitions is part of the table (these are physical storage containers for the data). Drop the table. Partitions gone.
- how would i drop all the partitions at once ???
By dropping the table. You cannot drop all partitions either - at least one partition must remain behind as a table needs a "+storage container+". It cannot be a table without a means of storing the data inserted into the table somewhere.
i know i can use ALTER TABLE TABLE_NAME DROP PARTITION PARTITION_NAME. This only drops the particular partition but not all the partitions right????
Correct.

Calculating average time from two records from the same table.

Hi all
I need to calculate the average time between two events that are recorded in the same table.
The table is TMS_MESSAGE_AUDIT_LOG
MESSAGE_ID VARCHAR2(16 BYTE) NOT NULL,
MESSAGE_VERSION NUMBER(2) NOT NULL,
CREATE_TM VARCHAR2(18 BYTE) NOT NULL,
MESSAGE_STATUS VARCHAR2(30 BYTE),
TRANSACTION_TYPE_NM VARCHAR2(30 BYTE),
MESSAGE_TP VARCHAR2(3 BYTE),
WORKFLOW_OBJECT VARCHAR2(30 BYTE) NOT NULL,
WORKFLOW_REQUEST VARCHAR2(30 BYTE) NOT NULL,
WORKFLOW_RETURN_CD VARCHAR2(30 BYTE) NOT NULL,
AUDIT_ACTION VARCHAR2(255 BYTE),
LAST_UPDATE_USER_LOGON_ID VARCHAR2(12 BYTE),
LOCAL_TM VARCHAR2(18 BYTE) NOT NULL,
LOCAL_TIME_ZN_NM VARCHAR2(70 BYTE) NOT NULL,
LOCAL_DAYLIGHT_IN CHAR(1 BYTE) NOT NULL,
FPRINT VARCHAR2(30 BYTE)
What i now need is
When the MESSAGE_ID is the same i need have the average time between when the MESSAGE_STATUS is AA and BB ( I need the time out of the CREATE_TM field )
And this for every 15 minutes interval.
Because this table will become BIG millions and millions of records it needs to be fast.
Can anybody help me.
Marcel

Something like this?
CREATE TABLE wr_test
( message_id                 VARCHAR2(16 BYTE) NOT NULL
, message_version            NUMBER(2) NOT NULL -- Assumption: Acknowledged ver > Received ver
, create_tm                  VARCHAR2(18 BYTE) NOT NULL
, message_status             VARCHAR2(30 BYTE)
, transaction_type_nm        VARCHAR2(30 BYTE)
, workflow_object            VARCHAR2(30 BYTE) DEFAULT 'x' NOT NULL
, workflow_request           VARCHAR2(30 BYTE) DEFAULT 'x' NOT NULL
, workflow_return_cd         VARCHAR2(30 BYTE) DEFAULT 'x' NOT NULL
, audit_action               VARCHAR2(255 BYTE)
, last_update_user_logon_id VARCHAR2(12 BYTE)
, local_tm                   VARCHAR2(18 BYTE) NOT NULL
, local_time_zn_nm           VARCHAR2(70 BYTE) DEFAULT 'GMT' NOT NULL
, local_daylight_in          CHAR(1 BYTE) DEFAULT 'x' NOT NULL );
INSERT ALL
INTO   wr_test
       ( message_id
       , message_version
       , create_tm
       , message_status
       , local_tm )
VALUES ( message_id
       , 1
       , create_tm
       , '(Receive)'
       , TO_CHAR(local_tm,'YYYYMMDD HH24:MI:SS') )
INTO   wr_test
       ( message_id
       , message_version
       , create_tm
       , message_status
       , local_tm )
VALUES ( message_id
       , 2
       , create_tm
       , 'Wait CLSB Ack'
     , TO_CHAR
       ( local_tm + NUMTODSINTERVAL(DBMS_RANDOM.VALUE(0,2e5),'SECOND')
       , 'YYYYMMDD HH24:MI:SS' ) )
SELECT ROWNUM AS message_id
     , TO_CHAR(SYSDATE,'YYYYMMDD HH24:MI:SS') AS create_tm
     , DATE '2000-01-01' + DBMS_RANDOM.VALUE(0,3) AS local_tm
FROM dual CONNECT BY ROWNUM < 100000;
WITH src AS
     ( SELECT message_id
            , message_status
            , message_version
            , TO_DATE(SUBSTR(local_tm,1,17),'YYYYMMDD HH24:MI:SS') AS dt
            , TO_DATE(SUBSTR(local_tm,1,8),'YYYYMMDD') AS dt_day
            , TO_CHAR(TO_DATE(SUBSTR(local_tm,10,8),'HH24:MI:SS'),'SSSSS') AS dt_sec
       FROM   wr_test
       WHERE message_status IN ('(Receive)','Wait CLSB Ack') )
SELECT dt_day + NUMTODSINTERVAL(period,'SECOND') AS dt
     , NUMTODSINTERVAL(AVG(elapsed),'DAY') AS avg_elapsed
     , NUMTODSINTERVAL(MIN(elapsed),'DAY') AS min_elapsed
     , NUMTODSINTERVAL(MAX(elapsed),'DAY') AS max_elapsed
     , COUNT(*)
FROM   ( SELECT message_id
              , message_status
              , dt_day
              , TRUNC(dt_sec/300)*300 AS period
              , LEAD(dt) OVER (PARTITION BY message_id ORDER BY message_version) AS ack_dt
              , LEAD(dt) OVER (PARTITION BY message_id ORDER BY message_version) - dt AS elapsed
         FROM   src ) cal
WHERE cal.message_status = '(Receive)'
GROUP BY dt_day, period
ORDER BY 1;Replace "wr_test" with "tms_message_audit_log" in the WITH subquery to test on your data.

Best way of partitioning the huge size table in oracle 11gr2

hi,
OS: linux
DB: oracle 11gR2
table size is about 2T and single table space with multiple dbf files in ASM,
table partition with dbms.redefinition is running past 2 days (range partition).. its running but not that fast..
note: exchange partition is too slow.. hence not used..
what is the best way of doing the huge size table partition. please suggest, thanks.

>
what is the best way of doing the huge size table partition
>
A few questions
1. Is that an OLTP or OLAP table?
2. Is all of the data still needed online or is some of it archivable?
3. What type of partitiioning are you doing? RANGE? LIST? COMPOSITE?
4. Why do you you say 'exchange partition is too slow' - did you do a test?
For example if data will be partitioned by create date then one stragety is to initially put all existing data into the root partition of a range partitioned table. Then you can start using new partitions for new incoming data and take your time to partition the current data.

Pondini, I beseech thee....Time Machine won't back up external drive partitions

Pondini (or anyone else that would like to help),
I am running Mac OS X 10.7.5. At my edit bay, we utilize a Facilis Terrablock 24D for storage, which connects to our system via fibre cables. Before upgrading to 10.7.5, Time Machine would back up all of our drive partitions on the Terrablock. Since the upgrade, Time Machine still recognizes the drives, we can add or subtract files from the drives, and it appears to make and save the changes, but when Time Machine backs up, it will only back up the local hard drive. No error messages come up. It just does its thing but only for the local HD.
All of the drive partitions are Mac OS Extended Journaled. All of the permissions seem to be in order.
I have contacted Facilis and their technical support claims that they never tested their products with Time Machine (as they sell their own backup equipment) but in theory that it should work.
I'm not sure what other information you might need but please let me know and I'll do my best. I was wondering if anyone else has come across an issue like this? Thank you for your time.

LALB wrote:
Upon including this partition and all of its contents, it disappears from the exclusion list as it should AND its size is reflected in the Estimated size of full backup. But this is the kicker! Upon clicking "Save" and starting Time Machine's backup, I receive the error "Time Machine could not complete the backup. There are no disks available to be backed up." Upon going back into TM Preferences > Options, I find that the external drive / partition has been put back on the Exclusion list. It's like it is automatically rejecting the partition after I have saved my exclusion list.
That's quite strange.
TM does that if you try to back up a USB Thumb drive (I've filed a bug report), but this is the first I've heard of it under any other circumstances. Then again, I don't recall a post by anyone trying to back up from a drive connected this way.
If a drive isn't formatted for a Mac (ie, FAT32, ExFat, NTFS, etc), Time Machine cannot back it up, and will list it in gray on the exclusion list (same as the backup drive), and won't let you remove it from the list, so it's clear.
This sounds like a "cousin" of the way it treats a thumb drive, so sure seems like a bug. TM will back up USB, FireWire, and Thunderbolt drives without a problem, if they're formatted right.
If you have any Macs under 90 days old, or covered by AppleCare, a call to them is free, and the best way to get a quick answer (you may have to escalate to a "specialist" however, and it still may take a few days for something unusual). Otherwise it's $50 U.S.
An alternative is to file a Bug Report, per the green box in Reporting a Problem to Apple. That most likely won't get a response for quite a while, though.
Sorry, wish I had a fix!
Let us know what, if anything, you find out.

Is partitioning the ra_customer_trx_lines_all table by time as well as safe

Similar Messages

Maybe you are looking for