RE: Best Practices for MultiTerrabyte TDW

I wouldn't say definitively that the WPA and SPA have problems with Oracle,
just that they *may* have problems with some of the more esoteric features
simply because very few customers are using them. But they *do* normally
support all/most DB2 features and functions. So my suggestion is based on
the pragmatic goal of keeping you and the customer out of the kind of PMR
hell that can derail a project.

Definitely will see you at Pulse.

Frank - from my phone
On Jan 24, 2013 6:06 PM, "Gregory Mendes" <[email protected]>
wrote:

>
> Frank, that is another great solution.  Would I be correct to say, what
> I'm hearing about the WPA and SPA seems to be, they will most likely have
> issues with Oracle and this size of DB?    If so, then this is good to
> know because it could allow me to understandable future issues or problems
> with operations.  The main problem they have with TDW being on DB2 revolves
> around not having those resources.
>
> I need to think about how efficiently TCR can pull reports from a large
> database with this design.  They keep reminding me "life of the mission".
> :)  So, for me tuning the WPA and SPA and knowing the issues I can run in
> to with Oracle, is valualbe information.  If you know of any gotchas, let
> me know.
>
> I'll see you at Pulse.
>
> Thanks,
>
> Gregory R. Mendes
> 770-317-8593
>
>
> ------------------------------
> Date: Thu, 24 Jan 2013 16:46:10 -0500
> Subject: Re: [TME10] Best Practices for MultiTerrabyte TDW
> From: frank.tate-9LkaxTQlAnxWk0Htik3J/[email protected]
> To: [email protected]
>
> Ya know what? The entire datadase is flat, with absolutely NO
> relationships, so you *could* use the DB2 that you're licensed to use for
> the "live" TDW, then just copy whatever tables you want into Oracle. In
> this type of situation I've found that what the DBA and/or reporting group
> of the customer wants to do is something new/sexy/cool/experimental that
> the WPA and especially SPA have absolutely no chance of dealing with. So
> separating the live DB from the one they want to mess with can make a lot
> of sense. Just set up the documented maintenance scripts for db2 to run
> via.cron and it won't really need any other work.
>
> Just a thought.
>
> Frank - from my phone
> On Jan 24, 2013 11:54 AM, "Gregory Mendes" <[email protected]>
> wrote:
>
>  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
>
>
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
>
> _______________________________________________ TME10 mailing list
> [email protected] Unsubscribe:[email protected]
>
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
>

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