Re: OPS$ Help

From: Pawel Kucharczyk <kuchar_at_kurdel.mimuw.edu.pl>
Date: 1996/02/16
Message-ID: <4g24m0$49s_at_parnas.mimuw.edu.pl>#1/1


 

|> >The setting of OS_AUTHENT_PREFIX will only define wich Oracle user will
|> >be implicitly connected when "connect /" is issued. For example:
 

|> >OS user OS_ATHENT_PREFIX Oracle user
|> >-------- ---------------- -----------
|> > SFA "" SFA
|> > SFA "OPS$" OPS$SFA
Yes I read it too.

|>
|> >I hope this helps
|> >Fernando Nantes. (nantes_at_amix.com.br)
|>
|> I too have problems with this parameter. I have a db user named 'CHA'.
|> It's the same as one of the Unix login names except in unix it's in
|> lower case. If I set OS_AUTHENT_PREFIX="" in my init.ora file, stop
|> and restart the database, I still can't use sqlplus / to log that user
|> in. I get "ERROR: ORA-01017: invalid username/password; logon denied".
|> Is there something else I neeed to set?
|>
|> --
|> Chuck Hamilton
|> chuckh_at_ix.netcom.com

  On HP-UX 9 with Oracle 7.1 I found that ANY attempt to define OS_ATHENT_PREFIX in init.ora produced this error. However after commenting OS_ATHENT_PREFIX line in init.ora it worked: OPS$XXX user in db for XXX OS user and xxx OS user. (The case didn't matter).

I didn't try Xxx, XxX and so on, but I guess it would work also. Seems like you can make a small OS workgroup to work with the single "/" login (?:).

If everything worked as it is written in documentation the DBAs wouldn't earn for living, eh;). If you don't have to fight with NLS you are lucky anyway.

Pawel Kucharczyk Received on Fri Feb 16 1996 - 00:00:00 CET

Original text of this message