The quickest way to do is to make the tablespaces read only
In this example below, I have RMANNI schema and my database is ORCLDB11G
Login as SYS or SYSTEM
1) Find all the tablespaces used by the RMANNI schema
select distinct tablespace_name from dba_tables where owner ='RMANNI';
select distinct tablespace_name from dba_indexes where owner ='RMANNI';
2) Change tablespace to Read Only ( Make sure that you have no transactions pending a commit or rollback)
alter tablespace rmanni_data read only;
alter tablespace rmanni_indx read only;
3) Now when you query dba_tablespaces and check the status column, they will show as READ ONLY instead of ONLINE
4) If you try make any modification to the schema, you will get a error message now
5) To make the tablespaces back to read write,
you can see the status changed from READ ONLY to ONLINE
***Only issue/bug I noticed is, even if the tablespace is read only, Oralce allows me to create empty tables.