Skip to main content

SPACE IS NOT GETTING RELEASED AFTER DROPPING DATA FILES IN LINUX MACHINE.



Please see below ...


We have encountered the below situation many times.

The space is not getting released after dropping the data files in LINUX machine.

 SQL> drop user TMP561 cascade;

SQL> drop tablespace TMP561 including contents and datafiles;

Note: The schema size is around 300Gig. And its having 11 datafiles each  data-file 30G.

But after dropping the User/Tbs. Space is not reclaimed in the Server.

SOLUTION:

 After dropping the datafiles still one process is holding these files. Check like below
oracle@/oracle/tmp: /usr/sbin/lsof |grep deleted |grep TMP*

oracle    13683    oracle   17u      REG             253,16 33286004736   40550413 /user/TMP/TMP561_01.dbf (deleted)
oracle    13683    oracle   18u      REG             253,16 33286004736   40550414 /user/TMP/TMP561_02.dbf (deleted)
oracle    13683    oracle   20u      REG             253,16 32212262912  206487553 /user/TMP/TMP561_03.dbf (deleted)
oracle    13683    oracle   21u      REG             253,16 28183633920   40566785 /user/TMP/TMP561_04.dbf (deleted)
oracle    13683    oracle   22u      REG             253,16 24587214848  302956545 /user/TMP/TMP561_05.dbf (deleted)
oracle    25070    oracle   16u      REG             253,16 33286004736   40550413 /user/TMP/TMP561_06.dbf (deleted)
oracle    25070    oracle   17u      REG             253,16 33286004736   40550414 /user/TMP/TMP561_07.dbf (deleted)
oracle    25070    oracle   19u      REG             253,16 32212262912  206487553 /user/TMP/TMP561_08.dbf (deleted)
oracle    25070    oracle   20u      REG             253,16 28183633920   40566785 /user/TMP/TMP561_09.dbf (deleted)
oracle    25070    oracle   21u      REG             253,16 24587214848  302956545 /user/TMP/TMP561_10.dbf (deleted)

oracle    25070    oracle   21u      REG             253,16 24587214848  302956545 /user/TMP/TMP561_11.dbf (deleted)

 The marked processes are still holding these datafiles. 

 Kill those processes to re-claim the space in the server.

 oracle@kill -9  13683

 oracle@kill -9  25070

 Alert Log shows like below:

 oracle@ tail -f alert_HGU11.log
Immediate Kill Session: sess: 0x9ff8f060  OS pid: 13683
Thu Jan 15 22:51:11 PST 2015
Process OS id : 13683 alive after kill
Errors in file
Thu Jan 15 22:53:54 PST 2015
Immediate Kill Session#: 158, Serial#: 10
Immediate Kill Session: sess: 0x9ff8f060  OS pid: 13683
Thu Jan 15 22:53:55 PST 2015
Process OS id : 13683 alive after kill

 SOLUTION 2:
Another way is to RESTART the database. To reclaim the space in the server.
Thank You!





Comments

Post a Comment

Popular posts from this blog

Issues and Solutions for Oracle 19c Grid Infrastructure Installation

     Common Issues and Solutions for Oracle 19c Grid Infrastructure Installation •       Check Log Files for Details Oracle installation issues often provide valuable clues in the log files. If the installer seems stuck or fails, check the following logs: ▪ Install log : /u01/app/oraInventory/logs/installActions<date>.log •       ▪ Grid Infrastructure log : $ORACLE_BASE/cfgtoollogs/ •         •       These logs can provide error messages and help identify the exact issue. •         •        Check Permissions and Ownership Verify that the Oracle Grid Infrastructure installation directories have the correct ownership and permissions. •        For example: •        Make sure the grid user has permission to write to the directories where the i...
Post a Comment
Read more

How to Improve Oracle Data Pump Performance - IMPDP

  How to Improve Oracle Data Pump Performance:- Use Parallelism : Set the PARALLEL parameter to at least 2 * number of CPUs . This allows multiple worker processes to perform tasks simultaneously, speeding up both export and import processes. Example: PARALLEL=4 for a system with 2 CPUs. Perform Import Using NETWORK_LINK : Use the NETWORK_LINK parameter to import data directly from the source database. This method is particularly helpful when space is constrained, as it streams the data without needing to generate dump files on the source. It can also reduce time compared to exporting and then importing, as data is streamed directly from the source to the target database. Disable Archivelog Mode (Standalone Databases) : For standalone databases, temporarily disable archive logging during the import process. Import operations can generate a lot of redo logs, slowing down the import. Disabling...
Post a Comment
Read more

Difference between AWR, ADDM and ASH reports

AWR: Automatic Workload Repository gathers, processes and maintains performance stats used for problem detection and self-tuning the databases. Different Components that uses AWR are: Automatic Database Diagnostic Monitor Undo Advisor SQL Tuning Advisor Segment Advisor Different types of AWR Reports for different purposes: For Single Instance Environment: @$ORACLE_HOME/rdbms/admin/awrrpt.sql For Oracle RAC Environment : @$ORACLE_HOME/rdbms/admin/awrgrpt.sql For a particular SQL Statement : @$ORACLE_HOME/rdbms/admin/awrsqrpt.sql For Comparing the reports : @$ORACLE_HOME/rdbms/admin/awrddrpt.sql ADDM: Automatic Database Diagnostic Monitoring Report analyzes the AWR data on a regular basis, to give you overview of the root cause of the problem which is affecting your database’s performance. It also provides suggestions or recommendations for rectifying any problem identified and lists the areas which are having no issues. ADDM recommends multiple solutions for the DBA to choose from which...
Post a Comment
Read more