Things to consider before moving table

 The following thing can be potential problem for big size table move .

1. No transaction should access those tables which you are going to move otherwise there will be ORA error on application side .So better to use dbms_redifnation in this case.( dbms_redifnation is available only EE edition) .

2. Time estimation can be go wrong .It may be due to different storage type used ( some times in some scenario the moving table reside on attached hard disk level file system and target reside on NAS or SAN ). I have seen that even 100GB of table takes time around 4 hours although target tablesapce and source tablespace were on different mount point but on same storage ( it was SAN ) .

3. Always use DBverify command to check block level corruption on target datafile before moving large tables .Otherwise it stuck in the middle of operation and some times it gets failed .

4.you can not use index rebuild on BITMAP index on partition table , if it is invalid state , you have to drop and rebuild .

5. You can not move those table which LONG Rows .

6. Always take expdp of those tables which you going to move, so in the middle of operation , this activity failed , you can rolled back .

7. Always enable row movement for the table which is going to be move.

8. Move the table.

9. Disable row movement for the table .

Comments

Post a Comment

Popular posts from this blog

Installing DBMS_JAVA package in Oracle and calling UTL_DBWS web services through Oracle database

Installing DBMS_JAVA package in Oracle following  files need to be run:-  sql> select comp_name, version, status from dba_registry where comp_name like '%JAVA%'; @?/javavm/install/initjvm.sql; @?/xdk/admin/initxml.sql; @?/xdk/admin/xmlja.sql; @?/rdbms/admin/catjava.sql; @?/rdbms/admin/catexf.sql; and verify your java installation in Oracle Database  sql> select comp_name, version, status from dba_registry where comp_name like '%JAVA%'; sql> select dbms_java.longname(object_name), status, object_type from all_objects where       object_type = 'JAVA CLASS'; ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ calling  UTL_DBWS  web services through Oracle Database :-  set the follwing parameters in .bash_profile of oracle user  export JAVA_HOME=$ORACLE_HOME/jdk ORACLE_BASE=/opt/oracle/product; export ORACLE_BASE ORACLE_HOME=/opt/oracle/product/11.2.0/dbhome_1; export ORACLE_HOME PATH=$PATH:/opt/o
Read more

stick the job to the specific instance in Oracle RAC

First method ( and easy one too ) :- note:-  must perform this activity on each instance one by one. ......stop jobs which is assigning to the specific instance..... $ export ORACLE_SID=SID connect database using job owner .... $ sqlplus username/password list of jobs and its instance....  sql> select JOB,INSTANCE from user_jobs;        JOB   INSTANCE ---------- ----------       2510          0       2951          0       2992          0       3091          0       3111          0       1570          0       1567          0       1568          0       1569          0       1571          0       1572          0 stick the job to the specific instance..... Syntax DBMS_JOB.INSTANCE (    job        IN BINARY_INTEGER,    instance   IN BINARY_INTEGER,    force      IN BOOLEAN DEFAULT FALSE); sql>execute dbms_job.instance(job=>1571, instance=>2,force=>true); verify from the instance number........
Read more

Starting background process GTX4 and GLOBAL_TXN_PROCESSES

Starting background process GTX4 Tue Jan 01 15:51:12 2012 GTX4 started with pid=64, OS id=11122 Tue Jan 01 15:51:43 2012 Auto-tuning: Starting background process GTX5 and Auto-tuning: Shutting down background process GTXi Like messages in alert log in RAC database This event is recorded in RAC environment only, which is normal.    Its normal for the database to automatically tune the number of these processes based on the workload of XA global transactions. If any application which using XA transaction and connecting to oracle RAC database, is it required. This normal behavior and you do not have to worry about this error messages.  If you are sure that you are not using XA and want to stop these messages. You can disable the GTXn background processes, then you must set GLOBAL_TXN_PROCESSES to 0 in your parameter file. Setting this parameter to 0 will disable the XA support on an Oracle RAC database. GLOBAL_TXN_PROCESSES specifies the initial numb
Read more