I recently was preppring a database for decommissioning and discovered that
some application userids had restricted access. Putting the database in
restricted mode was ineffective in this instance. Spent almost a week
tracking down the someone who could move the application moved to the new
database. The person who "used to handle" the application had left the
company several months earlier. Just another detail you may want to look
at as you put the database in restricted mode.
Sandy
On Thu, Apr 14, 2016 at 7:25 AM, Mladen Gogala <gogala.mladen@xxxxxxxxx>
wrote:
On 04/13/2016 05:46 PM, Oracle DBA wrote:
Thanks everyone,restricted session mode and leave it like that for a while.
I won't do individual replies but some good info.,
Mladen, I had thought of your idea and I like it very much, but upper
management will take that as a cowboy tactic and in the event of actual
downtime if its still being used then they will get stoppy, its already
hard enough to promote IT as having good service, but that will give the
end users more ammo against IT. But yes switch off and wait for the screams.
Well, Mark Farnham actually has an excellent idea: put the instance into
--
Mladen Gogala
Oracle DBA
http://mgogala.freehostia.com
--
//www.freelists.org/webpage/oracle-l
