Its an application restriction. Due to this reason we are still running on DMT mode.

Also I heard that Oracle 92 has a bug related to DBA_SEGMENTS.
---------------------------------------------------------
So what I have done is, I ran the CATSPC2.sql

New views are created:
- SYS_DBA_SEGS_2
- DBA_SEGMENTS_2
- USER_SEGMENTS_2
- DBA_EXTENTS_2
- USER_EXTENTS_2
---------------------------------------------------------

and later on I ran the following sql statements:

---------------------------------------------------------
sqlplus /
create or replace synonym sys_dba_segs for sys.sys_dba_segs_2;
create or replace synonym dba_segments for sys.dba_segments_2;
create or replace synonym user_segments for sys.user_segments_2;
create or replace synonym dba_extents for sys.dba_extents_2;
create or replace synonym user_extents for sys.user_extents_2;
exit;

---------------------------------------------------------
Later on I ran the following sql command to see the results (As an example):

Examining Segments that CANNOT Allocate Next Extents
---------------------------------------------------------
SELECT
a.owner as "Owner", a.tablespace_name as "Tspace",
a.segment_name as "Segment", a.next_extent/1024 "Next(k)",
a.pct_increase "%inc" FROM sys.dba_segments a
WHERE
next_extent > (SELECT MAX(b.bytes)
FROM
sys.dba_free_space b
WHERE
a.tablespace_name = b.tablespace_name) ;
---------------------------------------------------------

Still I see the same old story. System is still processing the same statement.

Thanks,
Nikee