Hello Yasser,
The effect of turning of autoextend is more manual intervention/management of your tablespace freespace. Easily mitigated if you have good monitoring of your DB/Tablespaces.
Please try these queries.
1. List the state of the datafiles for PSAPSR3740 (pls post here)
select file_name, status from dba_data_files where tablespace_name = 'PSAPSR3740' ;
2. List all datafiles in sapdata2 that are autoextensible (pls post here).
select FILE_NAME, MAXBYTES/1024/1024, AUTOEXTENSIBLE from dba_data_files where file_name like '%sapdata2%' ;
3. The space required in the filesystem if all autoextensible datafiles grew to their maxsize.
select round(sum(MAXBYTES/1024/1024/1024)) as GB from dba_data_files where AUTOEXTENSIBLE = 'YES' and file_name like '%sapdata2%' ;
If the sum of the above statement is greater than the size of sapdata2 then you have overallocation.
4. Depending on the result of step (3), turn off autoextend for the datafiles found in sapdata2.
eg: alter database datafile '/oracle/EGD/sapdata2/sr3740_5/sr3740.data5' autoextend off ;
Repeat for all datafiles found in step (2)
5. Manually extend one datafile for PSAPSR3740
eg: alter database datafile '/oracle/EGD/sapdata2/sr3740_5/sr3740.data5' resize 30G ;
Additionally, I would suggest you run dbv for '/oracle/EGD/sapdata2/sr3740_5/sr3740.data5'
KR,
Amerjit