We have users requesting access to SYS.
Even though it is on a development database, we think users should not be allowed to log in as SYS.
Can anybody give me valid reasons why users should not have SYS access so I can present them with this?
If I am wrong, and you think this is OK, please let me know.
We have users requesting access to SYS.
Even though it is on a development database, we think users should not be allowed to log in as SYS.
Can anybody give me valid reasons why users should not have SYS access so I can present them with this?
If I am wrong, and you think this is OK, please let me know.
Thanks for your help
I guess you want to practice your recovery techniques!!
Ask them exactly what they want to do and then decide if it is do-able. Why even let them get used to having the keys to the castle if it is NEVER going to happen in production.
Remember the horse goes before the cart,
The lunatics should not run the asylem,
USER is a 4 letter word, ect...
Users should never need the sys or system passwords. If the database is setup properly (Permissions/synonyms, etc...), they should never need or ask for that access...
What's next - User's requesting root(Unix) or Administrator (Windows)?
I had this problem from developers who wanted to install something from a CD that required a sys password. For example, if they working on an application called RMS 9.0 and would like to apply the latest patch.
The solution is - either the DBA installs the application patch
or he changes the sys password TEMPORARILY for their install to go through and change it back once the install is complete.
For example change sys password to kris and change it back after an hour or so.
Remember the Golden Rule - He who has the gold makes the rules!
===================
Kris109
Ph.D., OCP 8i, 9i, 10g DBA
Bookmarks