You dont want to give them the sys password. A good "politically correct" way of saying it would be that you do not want any user to create user objects in the sys schema, thus, you cannot give it to them.
Better still, question them till they get fed up and stop asking for it.
Write a packaged procedure to do the job for them and grant execute access to them. The procedure will run with owner rights (by default) allowing them to perform the action as if they were SYS, but what they do will be limited by the procedure you code.
Mine being a small company i have faced this problem and finally gave up trying.
The reason given by my manager is that sometimes if i am not there the other developers might need to bounce the database for some reason or if the database crashes and if i am not there then how will they get oracle support if they dont have the passwords etc etc.
Originally posted by ronnie
Mine being a small company i have faced this problem and finally gave up trying.
The reason given by my manager is that sometimes if i am not there the other developers might need to bounce the database for some reason write some script so that you can start up and shutdown the database
or if the database crashes They cannot do anything about it
and if i am not there then how will they get oracle support if they dont have the passwords etc etc. What password ??
actually I REALLY WANT TO SHOOT THEM.
Last edited by adewri; 02-06-2003 at 11:42 AM.
Amar "There is a difference between knowing the path and walking the path."
I still recall when I was a DBA at this big company.. The development team lead is to climb and sh*t all over the dba's heads.. that is to put it mildly..
He used to page me at 8pm.. to do a production migration urgently.. and then I migrate a little pro*c program.. it does not work obviouly.. ok.. I migrate again.. it does not work.. this goes on till 3am..
Originally posted by ronnie The reason given by my manager is that sometimes if i am not there the other developers might need to bounce the database for some reason or if the database crashes and if i am not there then how will they get oracle support if they dont have the passwords etc etc.
Our solution was the password in a sealed envelope in the safe in the CEO's office and a signout procedure (make a BIG deal of it). Things have to get bad before they ask him . . .
Recommend NOT shooting them - it is impossible to get the blood out of the keyboard. Poison them, or better "Do it not with poison, strangle them, even on their own desks which they have contaminated" (appologies to WS).
"The power of instruction is seldom of much efficacy except in those happy dispositions where it is almost superfluous" - Gibbon, quoted by R.P.Feynman
Reply With Quote
Bookmarks