Hi,
It looks as though the Mysource database tables are all defined with the same user-default storage defaults. Would it better to separate the indexes from the data, and the rollback data from the rest of the data? Also would it be better having the tablespace usage more closely aligned with the anticipated table volumes?
In summary of those questions: Would it be possible to add a storage clause defining tablespace name and extent size for all of the tables so that it is done during the initial install? Would this be recommended?
Cheers.
Just re-prompting these questions?
I guess no one is very inspired by those questions… 
What our DBA was suggesting was to proceed with the intall (up to step 2), restructure the tablespace and then populate the table (which occurs in step 3 right?). Does that sound ok?
[quote]Would it better to separate the indexes from the data, and the rollback data from the rest of the data? Also would it be better having the tablespace usage more closely aligned with the anticipated table volumes?
[right][post=“7660”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yes. 
To be clearer: I know a few Oracle DBAs that are monitoring the tablespace usage of Matrix and will be moving indexes and rollback tables to different tablespaces over time. Thankfully, you can move these things around in Oracle at any point, so there’s really no requirement to do it during installation.
Your DBAs should monitor the table usage and then plan/move accordingly.
[quote]Yes. 
To be clearer: I know a few Oracle DBAs that are monitoring the tablespace usage of Matrix and will be moving indexes and rollback tables to different tablespaces over time. Thankfully, you can move these things around in Oracle at any point, so there’s really no requirement to do it during installation.
Your DBAs should monitor the table usage and then plan/move accordingly.
[right][post=“8626”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yes but he was keener to do it when there was little data. From what I understand (very little regarding tablespace) it would be better (as in take less time).
Thanks Avi.
What’s the best way to keep in touch with the monitoring results of other Oracle DBAs? Or is that a silly question because it will depend on the type and amount of data for each instance?
[quote]Or is that a silly question because it will depend on the type and amount of data for each instance?
[right][post=“8628”]<{POST_SNAPBACK}>[/post][/right][/quote]
IANAOracleDBA, but I suspect this is true: You’d have to monitor your own instance and make changes as appropriate for your hardware. I know that the Oracle DBAs I’m referring to have various SANs and Fibre Channel drives that they’re going to be moving data and indexes to, but I’m not sure which way round, or anything like that until after the fact.
Also, on newer hardware (like SANs), moving tables between tablespaces is pretty quick. Matrix’s database doesn’t really get that big. 