Re: Oracle 7 logon
From: Hans Forbrich <fuzzy.graybeard_at_gmail.com>
Date: Tue, 19 Mar 2013 11:00:55 -0600
Message-ID: <514899C7.1010006_at_gmail.com>
On 19/03/2013 10:44 AM, Christopher.Taylor2_at_parallon.net wrote:
> using OS authentication it was
>
> sqlplus using the OS authentication prefix I think.
>
> I "think" you had to actually do sqlplus ops$username after setting oracle SID env variable on the server back on an AT&T NCR Unix box in 97 I believe (first Oracle database I had access to out of college so I'm probably wrong)
>
OS Authentication set up: You would normally create a user in Oracle using OPS$ as prefix to the OS username. (That prefix is now defined by an init parameter.) The Oracle username was in uppercase, and the connection method did the appropriate translation.
Date: Tue, 19 Mar 2013 11:00:55 -0600
Message-ID: <514899C7.1010006_at_gmail.com>
On 19/03/2013 10:44 AM, Christopher.Taylor2_at_parallon.net wrote:
> using OS authentication it was
>
> sqlplus using the OS authentication prefix I think.
>
> I "think" you had to actually do sqlplus ops$username after setting oracle SID env variable on the server back on an AT&T NCR Unix box in 97 I believe (first Oracle database I had access to out of college so I'm probably wrong)
>
OS Authentication set up: You would normally create a user in Oracle using OPS$ as prefix to the OS username. (That prefix is now defined by an init parameter.) The Oracle username was in uppercase, and the connection method did the appropriate translation.
Then you would use
sqlplus /
If you wanted to connect as sysdba, you would use
svrmgrl
and generally 'connect internal' once inside svrmgrl without the 'AS SYSDBA' notation that was required when they merged svrmgrl and sqlplus.
/Hans
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Mar 19 2013 - 18:00:55 CET