Tablespace Size ISSUE.....OS is FULL almost....Urgent Help...

Question

Hi All,
I have a database 9i 9.2.0.4 on Sun Solaris 5.9.
- We have many permanent tablespaces and has "autoextend ON" and "maxsize UNLIMITED". Let call is TS1.
- We have different users and each user is exclusively assigned the above tablespace as default storage. No other is user is having any privilege to use anybody's else tablespace. Let call this user as U1.
"One User - One Tablespace" that is, U1 is using TS1.
Let call the user
ISSUES
======
1. The datafile of the tablespace TS1 shows the SIZE of 4.3 GB on OS. The Database file on FileSystem is 4.5 GB
2. And when i take the EXPORT of the above User Schema i.e. User U1, it shows me very less SIZE i.e. 388 MB approx. This is a BIG Surprise to me. I take EXPORT like this:
$exp system/<password> file=TS1.dmp log=TS1.log owner=U1
3. I also tried to check the Tablespace Used Space and TableSpace Free Space and it shows me the statistics like this:
+
The Query to see Used Space (For all Tablespaces of my DB Instance):
select b.name, (sum(bytes)/1024)/1024
from v$datafile a, v$tablespace b
where a.ts# = b.ts#
group by b.name;
[For TS1, it is: 4.512 GB]
+
The Query to see Free Space (For all Tablespaces of my DB Instance):
select tablespace_name, (SUM(bytes)/1024)/1024
from dba_FREE_SPACE
group by tablespace_name;
[For TS1, it is: 4.188 GB]
+=================
+ Due to the Whopping Size of TS1, it is threat to my File System Space management as my Unix Slice is 93% Full.
+ How Can i understand this Phenomenon...Is is OK in Database or We might be missing some configuraiton / settign etc. Why is this great diff. between datafile size & export size.
+ And what is the best way i can reduce / shrink the TabaseSpace Datafile Size almost equal to the EXPORT SIZE..
Please help on priority pls. I look forward to some tips / help.
Regards,
Kamesh Rastogi

Answer 1

Hi,
It is quite clear to me it may be because of EXTENT allocated but not being used...something like all records of a particular extent might have been deleted...
As Ankit needed for better analysis, i am providing the details....but does all that information needed for analysis....Anyhow i am providing all needed....
1. 9iDB 9.2.0.4
2. Sun Solaris 5.9 SUN SPARC box
3. select sum(bytes)/1024/1024 from dba_segments
where tablespace_name='SHARES' and owner='SHARES' and segment_type <>'INDEX'
4. exp system/<password> file=shares.dmp log=shares.log owner=shares
5. I feel you wanted segment_name & its bytes. Because there is no column object_name in table dba_segments.
I have fired following query....Hope you will get the output proper format...
select segment_name,segment_type,bytes
from dba_segments
where tablespace_name='SHARES' and bytes > 1048576
SEGMENT_NAME SEGMENT_TY BYTES
CLEAR_TRIAL TABLE 2097152
FOLIO_LNK TABLE 2097152
DATA_FILE TABLE 5242880
SURNAME TABLE 8388608
DEPECS_BNKACNO TABLE 5242880
BNKACNO TABLE 3145728
DIVIDEND TABLE 5242880
BENPOS_DTL TABLE 75497472
CDSL_DTL TABLE 2097152
ECS_CREDIT TABLE 3145728
CERT TABLE 3145728
SEGMENT_NAME SEGMENT_TY BYTES
CERT_DEMAT TABLE 2097152
CDSLDIVD_MEMBER TABLE 2097152
ENVELOP_NO TABLE 2097152
ANN_TMP TABLE 3145728
JTMEMBER TABLE 4194304
MANDATE TABLE 2097152
MEMBER TABLE 24117248
SIGNATURE_OLD TABLE 27262976
STRIP_ADDRESS TABLE 19922944
SIGNATURE TABLE 7340032
SHARE_MERGED_REP TABLE 40894464
SEGMENT_NAME SEGMENT_TY BYTES
ZZ_INWHDR TABLE 4194304
BAR_STATUS TABLE 2097152
DR_REQ TABLE 2097152
INWHDR TABLE 5242880
TFERHDR TABLE 2097152
ZZ_MEMBER TABLE 2097152
ZZ_CERT TABLE 2097152
DIVIDEND_HIST TABLE 17825792
DEPDIVD_MEMBER_HIST TABLE 57671680
CDSLDIVD_MEMBER_HIST TABLE 3145728
DEPDIVD_MEMBER TABLE 75497472
SEGMENT_NAME SEGMENT_TY BYTES
DIVD_TMP TABLE 2097152
SYS_IL0000026149C00002$$ LOBINDEX 2097152
STRIP_ADDRESS_IND1 INDEX 4194304
STRIP_ADDRESS_IND2 INDEX 7340032
ZZ_MEMBER_FOLIO_IND1 INDEX 2097152
DIVD_TMP_IND_1 INDEX 3145728
SYS_LOB0000026149C00002$$ LOBSEGMENT 653262848
SYS_LOB0000127124C00002$$ LOBSEGMENT 1207959552
6. The table was exported it it shows the size: 813642752 Bytes. (800 MB).
7. Since it is our production database and hence trying anything just l ike this might trouble us...& that's why i am trying to get each & every bit & bytes before i may proceed...
Thanks.
Regards,
Kamesh Rastogi