| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Convert to Locally-Managed Tablespaces
Hi
Obviously I'm not Tanel, but we have a similar situation where we don't actually need to keep segments in specifically named tablespaces - but we do need when upgrading all of the specifically named tablespaces to exist, and have sufficient free speace for the upgrade. The app is cross-dbplatform and hardcodes at least some of the tablespace names (on mssql some of the database names) in the upgrade scripts. Frustratingly the tablespace names <app>static, <app>histr,<app>transactional etc suggest an attempt to maintain segments in sappropriate tablespaces. Unfortunately the static segments change, the historic sgements contain current data, the transactional tables might be lookups....
My *impression* is that this sort of setup is actually quite common.
Niall
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Niall Litchfield
INET: niall.litchfield_at_dial.pipex.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services ---------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Tue Jan 06 2004 - 15:04:51 CST
 |
 |