Skip to main content

Reorg Script for Oracle Tables Within the Same Tablespace

 -- Ensure you're logged in as the appropriate user


-- 1. Define variables for schema and table names

DEFINE schema_name = 'YOUR_SCHEMA_NAME';

DEFINE table_name = 'YOUR_TABLE_NAME';


-- 2. Check the status and size of the table before reorganization

SELECT table_name, num_rows, blocks, empty_blocks, avg_row_len

FROM dba_tables

WHERE owner = '&schema_name'

AND table_name = '&table_name';


-- 3. Move the table within the same tablespace to reorganize it

-- No tablespace specified, it will remain in the same tablespace

ALTER TABLE &schema_name..&table_name MOVE;


-- 4. Rebuild indexes associated with the table

-- Get all indexes associated with the table

SELECT 'ALTER INDEX ' || index_name || ' REBUILD;' 

FROM dba_indexes 

WHERE owner = '&schema_name'

AND table_name = '&table_name';


-- 5. Gather statistics for the table after reorganization

EXEC DBMS_STATS.GATHER_TABLE_STATS('&schema_name', '&table_name');


-- 6. Check the table status and size after reorganization

SELECT table_name, num_rows, blocks, empty_blocks, avg_row_len

FROM dba_tables

WHERE owner = '&schema_name'

AND table_name = '&table_name';


-- 7. Optionally, shrink the table space after reorganization (use with caution)

ALTER TABLE &schema_name..&table_name SHRINK SPACE CASCADE;


-- 8. If partitioned, handle partitions separately

-- ALTER TABLE &schema_name..&table_name MOVE PARTITION partition_name;


Comments

Post a Comment

Popular posts from this blog

ORA-28007: THE PASSWORD CANNOT NE REUSED

             - Here will see how to deal with  => ORA-28007: the password cannot be reused -  I got a request from client user, stating his account has been locked. When I check the status of the account I found the below. connect to SYS user & execute the below query of that database. SQL> select password,username,account_status,profile from dba_users where username='TEST'; PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE ------------------             ----------------  -------------------------------           -------------------- AB2Aa8AC9971521e3     TEST       EXPIRED(GRACE)&LOCKED    NONAPP_USERS So, then I have unlocked the account and checked the same again & I found the below results. ...
Post a Comment
Read more

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG...
Post a Comment
Read more