RE: Best Practices for MultiTerrabyte TDW

Hey Gregory,

If you haven't checked or tested it already, you may want to validate TDW is supported for Oracle RAC.  I thought I remember a while back reading that it wasn't.  I couldn't find anything about it online.  Maybe IBM can chirp in.

Cheers,
Charlie

From: [email protected] [mailto:[email protected]] On Behalf Of Gregory Mendes
Sent: Thursday, January 24, 2013 5:38 PM
To: [email protected]
Subject: RE: [TME10] Best Practices for MultiTerrabyte TDW

Hey Charles,

Thanks for that information.  Great info, because the databases they are using for TDW is Oracle RAC v11.x.  They will definitely have tables that will probably meet that mark or beyond because it's for "the life of the mission" of the program without too much thought in the architecture on migrating or exporting data to other locations for efficient reporting capabilities, alone.

Thanks for the WPA and SPA suggestions, as well.

Regards,

Gregory R. Mendes
770-317-8593


________________________________
From: charles.a.wolfe-WvK1HsOUa2dWk0Htik3J/[email protected]<mailto:charles.a.wolfe-WvK1HsOUa2dWk0Htik3J/[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: RE: [TME10] Best Practices for MultiTerrabyte TDW
Date: Thu, 24 Jan 2013 18:27:29 +0000
The size of the total TDW is not as significant as the size of your largest tables.   I've found any table north of 100 million records can start to be a concern.   It depends a lot on what the settings for Summarization & Pruning are set for those tables too.   If you start to creep up to double digit S&P times for individual tables you may want to investigate partitioning those tables.   It won't help much with the summarization, but it will allow you to prune tables in seconds by just dropping the partition.

Both the WPA and SPA have some parameters you can tune to increase the memory and handle larger throughputs.

Other than that, be cautious of using Oracle's table compression as we ran into a bug which caused INSERT's to crawl to a halt on some very large tables with compression turned on.   This was on 11.1 and they might have fixed it, but caused massive problems for us for about a month so we have had it disabled ever since.

Charlie

From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gregory Mendes
Sent: Thursday, January 24, 2013 11:49 AM
To: [email protected]<mailto:[email protected]>
Subject: [TME10] Best Practices for MultiTerrabyte TDW

Hello All,

I have a TDW (Oracle) that will be over 25 TBs.  I have the white paper or best practices for TDW but it doesn't address handling these types of large databases.

I know about the TDW Load Projection spreadsheet but my customer refuses to use it.  So, they have calculated in their head what they think the size should be.

So, do you guys/gals have any suggestion or tips to give?

Regards,

Gregory R. Mendes
770-317-8593
This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

_______________________________________________ TME10 mailing list [email protected]<mailto:[email protected]> Unsubscribe:[email protected]

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]