Hi
Tims ideas are good but also take a cold backup of the database before
the read only period starts so that even if someone manages to alter
data it can be restored back to its previous state. By the way when you
say read only does that apply to batch processes and general system
ageing? - if
We are in the process of upgrading our peoplesoft app, using an oracle
database of
8.0.5 to 9i. During the upgrade we still need access to the old 8.0.5
database as readonly.
I have read all the doc's but it appears I cannot open the database as
read only. Looks like
I could if the version was
Darren,
Couldn't you just open the database with a user that has all the
necessary privileges revoked?
-Original Message-
Browett, Darren
Sent: Wednesday, November 26, 2003 3:44 PM
To: Multiple recipients of list ORACLE-L
We are in the process of upgrading our peoplesoft app, using an
You can't.
Even if you were to set all possible tablespaces to READ ONLY, you'll find
that it doesn't prevent folks from dropping objects.
All you can do is restrict people to schemas/accounts which do not own any
objects and do not have permissions to create any. That way, you can
restrict
Looks like that is what we will be doing, basically creating
a generic user with read-only privileges. All the current
users will have their password changed so they cannot access the
system.
Darren
-Original Message-
Sent: Wednesday, November 26, 2003 4:04 PM
To: Multiple recipients
Consider also using ALTER USER xxx ACCOUNT LOCK instead of changing the
passwords...
on 11/26/03 6:49 PM, Browett, Darren at [EMAIL PROTECTED] wrote:
Looks like that is what we will be doing, basically creating
a generic user with read-only privileges. All the current
users will have their
