Move indexes to a different tablespace

What is the best and easiest method to move all indexes/constraints to a different tablespace. I have 2 tablespaces one for data and the other for the indexes. At present, I have all data and indexes all in one tablespace. I would like to separate the indexes to another tablespace(which is reserved specifically for the indexes)
Thanks

You do not move constraints.
You can use the command:
ALTER INDEX index_name REBUILD TABLESPACE new_tablespace;

Similar Messages

Move index to a different tablespace using dbms_redefinition?

Hi all, I am trying to move indexes to new tablespaces. Can I use oracle built-in package DBMS_REDEFINITION for this? As far as I know dbms_redefinitoin only works for tables rebuilt online? I am running 10.2.0.5 on linux red hat, and the index sizes from 100MB to 10gb. Thank you in advance all.

Since one can seamlessly move an index from one tablespace to another by simply doing:
SQL> alter index <index_name> rebuild tablespace <tablespace_name>;even considering DBMS_REDEFINITION for this makes no sense at all.
If your boss has any further questions, show him the Oracle documentation:
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_redefi.htm
Quote from that page:
"The DBMS_REDEFINITION package provides an interface to perform an *online redefinition of tables*."
(Emphasis added by me.)
Hope that helps,
-Mark

Moving indexes to a different tablespace in siebel.

Hi,
While installation we gave same SIEBEL tablespace as default tablespace for indexes also , now I would like to move all indexes to a different tablespace. Is there any specifis utility / procedure available to move (or) recreate indexes .. or can we do it in Database using alter index <index_name> command...
Thank You,
Sunil.

You do not move constraints.
You can use the command:
ALTER INDEX index_name REBUILD TABLESPACE new_tablespace;

How to move lobsegment and lobindex to a different Tablespace

Oracle Version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit
Os: Solaris 10
Hello Everybody,
I want to move a lobsegment and a lobindex to a differrent tablespace.
But when i am executing the following statement in order to move the LOBINDEX I am getting the errors listed below:
SQL> ALTER INDEX SYS_IL0000012358C00008$$ REBUILD TABLESPACE INDX;
ALTER INDEX SYS_IL0000012358C00008$$ REBUILD TABLESPACE INDX
ERROR at line 1:
ORA-02327: cannot create index on expression with datatype LOB
Is there any differrent commands/methods of moving the LOBSEGMENT/LOBINDEX to a differrent tablespace.
Any help Appreciated..
Regards,
Prosenjit Mukherjee.

Hi,
Assuming that I have table "TEST" in USERS TableSpace
CREATE TABLE TEST
TEST_ID NUMBER NOT NULL,
TEST_NAME CLOB,
CONSTRAINT PK_TEST PRIMARY KEY(TEST_ID)
SQL> ALTER TABLE TEST MOVE TABLESPACE EXAMPLE;
Above command will move the table to new tablespace but will not move the CLOB segment and it will still be in original tablespace. This is because LOB data is stored outside of the table.
Check the tablespace of the CLOB column by issuing following sql.
SQL> SELECT index_name, tablespace_name
FROM user_indexes WHERE table_name = ‘TEST’;
INDEX_NAME TABLESPACE_NAME
SYS_IL0000073575C00002$$ USERS
In order to move CLOB column to different tablespace, we have to issue following command.
SQL> ALTER TABLE TEST MOVE LOB(TEST_NAME) STORE AS (TABLESPACE EXAMPLE);
In above example, TEST_NAME is the CLOB column which we want to move to new tablespace and EXAMPLE is target tablespace. Above command will successfully move LOB segments to the new tablespace. We can verify it by issuing same sql again.
SQL> SELECT index_name, tablespace_name
FROM user_indexes WHERE table_name = ‘TEST’;
INDEX_NAME TABLESPACE_NAME
SYS_IL0000073575C00002$$ EXAMPLE
- Pavan Kumar N

Index on different tablespaces

I need to move some indexes on a different tablespace. How can I complete this task ? I'm not a dba..

Have a look at these links:
http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_1010.htm#SQLRF00805
http://docs.oracle.com/cd/E11882_01/server.112/e25494/indexes004.htm#ADMIN11732
ALTER INDEX YOUR_INDX REBUILD TABLESPACE YOUR_TBS;

Table and index in the same tablespace

I have a table and its associated indexes all in one tablespace. Now, will creating a separate tablespace just for the indexes and drop and recreating the indexes the table has in the new tablespace help ???
Thanks

In all probability, no. This may have some housekeeping/ recovery benefits but it is very unlikely to have performance benefits. Most modern disk arrays are configured so that data access is spread pretty evenly across all the spindles. If your disk is configured such that you have "hot" and "cold" disks, and if you can move the index to a different tablespace that can be placed on one of the "cold" disks, this will tend to balance out disk I/O and may improve performance.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

How to move indexes to another tablespace through script

Hi Dear,
How i can move indexes to another tablespace through a script which just gets new tablespace name, owner name and move and rebuild indexes in one go.
Thank u for your prompt Help.
Regards

Hi,
alter session set sort_area_size = 15000000;
spool index.sql
select 'alter index '||owner||'.'||index_name||' rebuild tablespace TARGET_TBS;'
from dba_indexes
where tablespace_name = 'INIT_TBS'
@index.sql
This script move and rebuild index from one tablespace INIT_TBS to an other tablespace TARGET_TBS
Hope this help you
Nicolas.

How to move partitions/sub-partitions into a different tablespace?

Hi Uisng oracle 1..20.3 and have a range-hash partitioned table using interval partitioning - code below.
Works fine just one problem.
we wish to move the system geneerated partitions to different tablespaces later and also rename th epartitions.
When try assign partition to a different tablespace get the folloiwng message
alter table por_rt move partition SYS_P2283 tablespace bi_dw_data
get message ora-14257 - cannot move partition other than range,list, system or hash partition.
How can we avoid this.
We we need to move all the subpartitions first?
Tried this
alter table move subpartition SYS_SUBP2269 tablespace bi_dw_data;
but get message ora-01735 message invalid statement
-- Create table
create table POR_RT
plant_issue_id    NUMBER not null,
pf_run_num        NUMBER,
partitioning_date DATE
partition by range (PARTITIONING_DATE)
subpartition by hash (PLANT_ISSUE_ID)
partition PART_200912 values less than (TO_DATE(' 2010-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2261 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2262 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2263 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2264 tablespace BI_SUPPORT_DATA
partition PART_201001 values less than (TO_DATE(' 2010-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2265 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2266 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2267 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2268 tablespace BI_SUPPORT_DATA
partition SYS_P2273 values less than (TO_DATE(' 2010-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2269 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2270 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2271 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2272 tablespace BI_SUPPORT_DATA
partition SYS_P2283 values less than (TO_DATE(' 2010-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2279 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2280 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2281 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2282 tablespace BI_SUPPORT_DATA
partition SYS_P2278 values less than (TO_DATE(' 2010-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2274 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2275 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2276 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2277 tablespace BI_SUPPORT_DATA
);Edited by: user5716448 on 22-Mar-2013 04:49

you can not move composite parition directly you need to move subpartition using this statments
alter table <tablename> move subpartition <sub partition name > tablespace <tablespace name>;
than change partition tablespace using
ALTER TABLE <table name> MODIFY DEFAULT ATTRIBUTES FOR PARTITION      <partition name> TABLESPACE <tablespace name>;

Moving partioned tables to different tablespaces in oracle 11g.

Dear All,
I need to move the partitioned table to different tablespace. I moved all the partitions individually and also the index.
however i have a issue now, when i check the view user_tables or dba_tables, i see null tablespaces correspomding to the table in the tablespace_name column.
how can i see the tablespace name in these views.

Even thouh Sb has given you the correct answer, I am just showing you below cut and paste sqlplus screen of 11.2.0.1 :
test1@ORCL> create table t (x number)
2    partition by list (x)
3    (partition p1 values (10),
4    partition p2 values (20));
Table created.
test1@ORCL> select table_name,tablespace_name from user_tables;
TABLE_NAME                     TABLESPACE_NAME
T
1 row selected.
---Means tablespace_name.user_tables is always null for partition table(s).
---Ok, then how do I see the tablespace name?
test1@ORCL> select table_name, partition_name,tablespace_name
2 from user_tab_partitions
3 where table_name = 'T';
TABLE_NAME                     PARTITION_NAME                 TABLESPACE_NAME
T                              P1                             USERS
T                              P2                             USERS
2 rows selected.
test1@ORCL> ALTER TABLE T MOVE PARTITION P1 TABLESPACE EXAMPLE;
Table altered.
test1@ORCL> select table_name, partition_name,tablespace_name
2 from user_tab_partitions
3 where table_name = 'T';
TABLE_NAME                     PARTITION_NAME                 TABLESPACE_NAME
T                              P1                             EXAMPLE
T                              P2                             USERS
2 rows selected.
test1@ORCL> select table_name,tablespace_name from user_tables;
TABLE_NAME                     TABLESPACE_NAME
T
1 row selected.Just for your information please.
Regards
Girish Sharma

User_lobs and user_segments view shows different tablespace for lob segment

Hi,
I am trying to move lob in different tablespace for partitioned table.
I used
alter table <table_name> move partition <partition_name> lob(lob_column) store as (tablespace <tablespace_name>);
alter index <index_name> rebuild partition <partition_name> tablespace <tablespace_name>
ALTER TABLE <table_name> MODIFY DEFAULT ATTRIBUTES TABLESPACE <tablespace_name>
ALTER INDEX <index_name> modify default ATTRIBUTES TABLESPACE <tablespace_name>
Database - 10.2.0.5
OS- HP Itanium 11.31
I can see in user_lob_partitions, user_segments and user_part_tables shows me new tablespace information
whereas user_lobs and user_part_indexes shows me different information regarding tablespace.
I checked some documents in metalink but didnt help me.
I think that I am missing something or doing some step wrong.
Please help.
SQL> select partition_name, lob_partition_name, tablespace_name from user_lob_partitions where table_name in ('TRB1_PUB_LOG','TRB1_SUB_ERRS','TRB1_PUB_LOG') ;
PARTITION_NAME                 LOB_PARTITION_NAME             TABLESPACE_NAME
S2000                          SYS_LOB_P8585                  USAGE_REORG_TBS
S2001                          SYS_LOB_P8587                  USAGE_REORG_TBS
S2003                          SYS_LOB_P8589                  USAGE_REORG_TBS
S2004                          SYS_LOB_P8591                  USAGE_REORG_TBS
S2005                          SYS_LOB_P8593                  USAGE_REORG_TBS
S2006                          SYS_LOB_P8595                  USAGE_REORG_TBS
S2007                          SYS_LOB_P8597                  USAGE_REORG_TBS
S2008                          SYS_LOB_P8599                  USAGE_REORG_TBS
S2010                          SYS_LOB_P8601                  USAGE_REORG_TBS
S2011                          SYS_LOB_P8603                  USAGE_REORG_TBS
S2012                          SYS_LOB_P8605                  USAGE_REORG_TBS
S2013                          SYS_LOB_P8607                  USAGE_REORG_TBS
S2014                          SYS_LOB_P8609                  USAGE_REORG_TBS
S2015                          SYS_LOB_P8611                  USAGE_REORG_TBS
S2888                          SYS_LOB_P8613                  USAGE_REORG_TBS
S2999                          SYS_LOB_P8615                  USAGE_REORG_TBS
S3000                          SYS_LOB_P8617                  USAGE_REORG_TBS
S3001                          SYS_LOB_P8619                  USAGE_REORG_TBS
S3004                          SYS_LOB_P8621                  USAGE_REORG_TBS
S3005                          SYS_LOB_P8623                  USAGE_REORG_TBS
S3006                          SYS_LOB_P8625                  USAGE_REORG_TBS
S3007                          SYS_LOB_P8627                  USAGE_REORG_TBS
S3008                          SYS_LOB_P8629                  USAGE_REORG_TBS
S3009                          SYS_LOB_P8631                  USAGE_REORG_TBS
S3010                          SYS_LOB_P8633                  USAGE_REORG_TBS
S3011                          SYS_LOB_P8635                  USAGE_REORG_TBS
S3012                          SYS_LOB_P8637                  USAGE_REORG_TBS
S3013                          SYS_LOB_P8639                  USAGE_REORG_TBS
S3014                          SYS_LOB_P8641                  USAGE_REORG_TBS
S3015                          SYS_LOB_P8643                  USAGE_REORG_TBS
S3050                          SYS_LOB_P8645                  USAGE_REORG_TBS
SMAXVALUE                      SYS_LOB_P8647                  USAGE_REORG_TBS
32 rows selected.
SQL> select TABLE_NAME,COLUMN_NAME,SEGMENT_NAME,TABLESPACE_NAME,INDEX_NAME,PARTITIONED from user_lobs where TABLE_NAME in ('TRB1_PUB_LOG','TRB1_SUB_ERRS','TRB1_SUB_LOG') ;
TABLE_NAME                     COLUMN_NAME                    SEGMENT_NAME                   TABLESPACE_NAME                INDEX_NAME                     PAR
TRB1_SUB_ERRS                  GENERAL_DATA_C                 SYS_LOB0006703055C00017$$      TRBDBUS1LNN1                   SYS_IL0006703055C00017$$       YES
TRB1_SUB_LOG                   GENERAL_DATA_C                 SYS_LOB0006703157C00017$$      TRBDBUS1LNN1                   SYS_IL0006703157C00017$$       YES
TRB1_PUB_LOG                   GENERAL_DATA_C                 SYS_LOB0006702987C00014$$      TRBDBUS1LNN1                   SYS_IL0006702987C00014$$       YES
SQL> SQL> select unique segment_name ,tablespace_name from user_Segments where segment_name in (select SEGMENT_NAME from user_lobs where TABLE_NAME in('TRB1_PUB_LOG','TRB1_SUB_ERRS','TRB1_SUB_LOG') );
SEGMENT_NAME                                                                      TABLESPACE_NAME
SYS_LOB0006702987C00014$$                                                         USAGE_REORG_TBS
SYS_LOB0006703055C00017$$                                                         USAGE_REORG_TBS
SYS_LOB0006703157C00017$$                                                         USAGE_REORG_TBS
SQL> select unique segment_name ,tablespace_name from user_Segments where segment_name in (select INDEX_NAME from user_lobs where TABLE_NAME in('TRB1_PUB_LOG','TRB1_SUB_ERRS','TRB1_SUB_LOG') );
SEGMENT_NAME                                                                      TABLESPACE_NAME
SYS_IL0006702987C00014$$                                                          USAGE_REORG_TBS
SYS_IL0006703055C00017$$                                                          USAGE_REORG_TBS
SYS_IL0006703157C00017$$                                                          USAGE_REORG_TBS
SQL> select unique index_name,def_tablespace_name from user_part_indexes where table_name in ('TRB1_PUB_LOG','TRB1_SUB_ERRS','TRB1_SUB_LOG');
INDEX_NAME                     DEF_TABLESPACE_NAME
SYS_IL0006702987C00014$$       TRBDBUS1LNN1
SYS_IL0006703055C00017$$       TRBDBUS1LNN1
SYS_IL0006703157C00017$$       TRBDBUS1LNN1
TRB1_PUB_LOG_PK                USAGE_REORG_IX_TBS
TRB1_SUB_ERRS_1IX              USAGE_REORG_IX_TBS
TRB1_SUB_ERRS_1UQ              USAGE_REORG_IX_TBS
TRB1_SUB_ERRS_2IX              USAGE_REORG_IX_TBS
TRB1_SUB_LOG_1IX               USAGE_REORG_IX_TBS
TRB1_SUB_LOG_PK                USAGE_REORG_IX_TBS
SQL> select unique def_tablespace_name from user_part_tables where table_name in ('TRB1_PUB_LOG','TRB1_SUB_ERRS','TRB1_SUB_LOG');
DEF_TABLESPACE_NAME
USAGE_REORG_TBS
Please let me know if some more details required.

>whereas user_lobs and user_part_indexes shows me different information regarding tablespace.
do you see different results after starting a new session after the ALTER statements were issued?

IMPORT INTO A DIFFERENT TABLESPACE

Hi All,
When attempting to import a .dmp file into a user with different default tablespace errors IMP-00003 and ORA-00922 was raised, some objects were imported but the problem seems to arise when importing tables. Help will be greatly appreciated.

Quote: apart from that you have to realize if the definition of your tables are poiting to a specific tablespace because if that is your case. You have to create that tablespace with quota for the new user and after move your tables from that tablespace.
Not true, Import first attempts to create an object in it's specified tablespace. If it is unable to then it will create the object in the owners default tablespace.
So buy changing a users default tablespace (with a quota) and removing the users quota from the old tablespace, you can actually change tablespaces on import.

Moving sys.aud$ to a different tablespace other than system

Hi,
I have a 10g RAC database system with a high volume of activity and would like to monitor a large slice of it using audit.
I have reviewed all options of audit trails and chose db, extended to be the most suitable for my purposes!
Ive noticed that all audit data goes to sys.aud$ table in system tablespace.
I have 3 questions:
1. What is the logic behind putting this table in systems tablespace and not sysaux (10g)?
2. Can I move sys.aud$ table to a different tablespace (should I expect trouble for doing so)?
3. Is there any RAC implication if I move sys.aud$ table to a different tablespace?
Regards,
Tal Olier
[email protected]

That's true, it's not recommanded to move a sys table... but we can find some good explanation for this one for aud$ table.<br>
See Metalink Note 72460.1 : Moving AUD$ to another tablespace and adding triggers to AUD$<br>
Or google search give some good results.<br>
Nicolas.

Assign AW to a different tablespace

Hello all,
We would like to move an analytical workspace (Oracle 10.2.0.1) to a different tablespace. The owner user was originally assigned to a shared tablespace; however, it was changed to use a dedicated tablespace. I have attempted to export / import the AW upon the change, but it is still assigned to the original shared tablespace. Could you please let me know how to change the tablespace, so I don't have to recreate the AW from scratch.
Many thanks!

If I read this correctly, you have an existing AW that you want to move to a different tablespace. If so, you will need to recreate your AW. The easiest way to do this is as follows:
1. Save dimensions and cubes to XML templates. (Save them independantly, don't just save the AW to a template.)
2. Create a new AW, using the tablespace option. (I recall that there was a bug in 10.x where the tablespace option got ignored. After you create your AW with the spacespace option, check to see which tablespace the AW$ table is in. If it's in the default tablespace, not the tablespace you have chosen, you probably need a patch or upgrade.)
3. Create your dimensions and then cubes from the templates in the new AW.

How to upgrade AND move between platforms with different Endians...?

Hi, all,
I have two databases - one of 500Gb and one of 50Gb - that are currently running on 10.2.0.4 on AIX 64-bit. They are Production systems.
I have to move them to a brand new Linux (RHEL 5.6 - 64-bit) server that will be running 11.2.0.2.
For test, I'm OK with this being done with Data Pump. But for the eventual move to 'New Prod', this will result in hours' worth of downtime and it's a business-critical system, so I'm trying to mitigate that as much as I can.
I was, naively, hoping to use RMAN to both move the databases from one box to the other, but also to upgrade them. I figure I would do the following (as per Metalink 369644.1) as I have a Recovery Catalog, etc, etc:
Install the binaries on the New Prod server
Connect to the RCAT and restore the database and recovery to a PiT
Manually upgrade the database by putting the DB into STARTUP UPGRADE and running the catupgrd.sql
Unfortunately, I didn't realise the Endian was different between AIX and RHEL (as per 1079563.1). Oops.
It doesn't look like I'll be able to use Transportable Tablespaces (as per 243304.1) either without first having to migrate the data across as a 10g DB and then upgrading.
So my options appear to be:
a) Data Pump and suck the outage up
b) Move the data using Transportable Tablespaces to 10.2.0.4 and then upgrade to 11.2.0.2.
Are there any other options? I have hopes that a logical standby would work in this instance a la rolling upgrade, but suspect that the different O/S AND the different Endian would scupper that idea...
Mark

Perhaps, I have more experience using concurrent exports/imports using the traditional exp/imp utility than using the parallel option on expdp/impdp. One thing you can do with exp/imp that you cannot do with expdp/impdp is export into a named pipe, start a remove copy of the named pipe to the new server, and then start importing from the named pipe on the new server so that you are importing while still exporting the same objects. We use tables= exports when we did this back when the tables= parameter could only handle 99 tables. We had a separate export for every large table and then a set of exports for 99 tables for each of the other tasks ran 6 to 12 concurrent processes.
One thing to look at is historic data. Potentially some tables can be moved in advance of the majority of the application objects and replaced with synonym to remote objects.
Truely static tables could also potentially be moved in advance even if only a day or two before to reduce the number of objects to be moved.
Build the new database in noarchive log mode to save some processing and switch it over and immediately back it up when you migrate.
And Yes, if the two platforms appear in the view name I gave you then you can use transportable tablespaces with the rman conversion step. Instructions for using rman to do the conversion are in the rman manual.
HTH -- Mark D Powell --

Moving objects into different tablespaces

Hi Gurus,
Here is my query .
I have 40gb space to have dataset from production database.
Test enviornment will be refreshed with production database.
From testing enviornment development will be refreshed to aviod any connections to production.
As part of data copying to dev env is depending on the conditions given by business.
So my question comes here
Initially I will be dumpring all the data to one tablespace in one tablespace of development environment.
It could take 39 to 40GB.
Now i want to move objects into different tablespaces accoring to storage clause and no of records .
New tablespaces will be created in development enviornment and will be created in same 40GB.
Space is constraint in dev env and cann't be extended.
How can i create tablespaces into the dev env and move objects into them?
I hope you understood my queries ...
In simple
TESTING ENV - - - -- - - - > DEV ENV(Initially one tablespace for all tables/objects) - - -- -- ---- >DEV ENV(Objects in diiferent tablespaces )

You say:
While creating scripts of tables we are removing all tablespace names as we will be having 3 tablespaces at target that is also after loading the data into them.Don't remove the TS clause, but replace the TS so-and-so with TS that-and-that.
Or replace tablespaces a, b and c with x+, and d* and e with y*+.
This can be automated, but you will have to write some logic for that.
Because ... we will be having only 3 tablespaces in DEV. ex NEWYORK tablespace is in production but it won't be created in DEv , istead all the objects into that tablespace will be moved to large table space.
As I said: You will need a code which greps for TS NEWYORK* and replaces it with +<your_big_TS>+.
So once again: Where is the problem?
It's just a question of coding.

Move indexes to a different tablespace

Similar Messages

Maybe you are looking for