: create user ops$fred identified by wilma .... ;
I am not sure what you associate with "eating the cake" but for me the
best cake is not to have to mess with users' passwords. In UNIX, when
you set a new ID, you can leave it blank and make the account invalid,
then when the user is ready to log on, he phones you, you validate the
login, he rlogins and sets his own password, which he can change later
on. While this is happening, you watch the who, making sure that there
are no impostors, and also ask him whether he made it successfully.
Now, the question is, is something like this possible in
client-server? From your example above, I see that you have to type
this "wilma" thing -- this is what I am trying to avoid. If I had to
do it, then what's the point of having ops$ logins -- all users will
be connecting via sqlnet anyway, so what's the point?
Thank you.
