We have a daily batch that alters a tablespace to read only, then takes backups and puts it back to read-write mode again.
The problem is, as long as there are users logged on to this database (even though they are simple select statements and accessing objects from other TBS), the alter tablespace waits. The weird thing is this that even if there are idle sessions in the DB, the "ALTER TBS read only" still waits.
Is there a way around this? Like, ending the sessions on the DB and making the alter TBS run immediately.
-Anukta
The problem is, as long as there are users logged on to this database (even though they are simple select statements and accessing objects from other TBS), the alter tablespace waits. The weird thing is this that even if there are idle sessions in the DB, the "ALTER TBS read only" still waits.
Is there a way around this? Like, ending the sessions on the DB and making the alter TBS run immediately.
-Anukta