Re: Connect / as sysdba = insufficient privileges

"Rick Wessman" <Rick.WessmanNO_SPAM_at_NoOrSaPcAlMe.com> wrote in message news:cvv4tg0j91_at_drn.newsguy.com...
> In article <119515402.0000a8e5.095_at_drn.newsguy.com>, Thomas Kyte says...
>>
>>In article <1109466467.879849.188260_at_o13g2000cwo.googlegroups.com>,
>>fitzjarrell_at_cox.net says...
>>>
>>>
>>>G Quesnel wrote:
>>>> I have ...
>>>> Oracle 10.1.0.2.0 on Solaris 64bits
>>>> sqlnet.ora > SQLNET.AUTHENTICATION_SERVICES= (NTS)
>>>> sqlnet.ora > NAMES.DIRECTORY_PATH= (TNSNAMES)
>>>> sqlnet.ora > NAMES.DEFAULT_DOMAIN = world
>>>> id> uid=1100(oracle) gid=200(dba)
>>>> init...ora > remote_login_passwordfile = exclusive
>>>>
>>>> orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=abcdef1
>>>>
>>>> I can connect with sqlplus /nolog ...
>>>> connect sys/abcdef1 as sysdba
>>>> But the following wont work
>>>> SQL> connect / as sysdba
>>>> ERROR:
>>>> ORA-01031: insufficient privileges
>>>>
>>>> I've even rebuilt the password file by
>>>> 1.Shutdown immediate
>>>> 2.issue the orapwd to build a new password file
>>>> 3.startup the database (after connecting sys/abcdef1 as sysdba)
>>>> 4.issue alter user sys identified by abcdef1;
>>>> 5.issue grant sysdba to sys;
>>>> and the connect / as sysdba still generates the ORA-1031
>>>>
>>>> How can I fix this problem ?
>>>> (or determine that I must re-install the Oracle software)
>>>>
>>>> TIA
>>>>
>>>> Note: This is the information in $ORACLE_HOME/root.sh ...
>>>> ORACLE_USER=oracle
>>>> DBA_GROUP=dba
>>>> CHGRP=/bin/chgrp
>>>> ORACLE_HOME=/u01/app/oracle/product/10g
>>>
>>>If this is truly 64-bit Solaris WHY on earth are you using NTS
>>>authentication? Such authentication service is reserved for the
>>>Windows operating system, certainly NOT Solaris.
>>>
>>>I'd change that immediately and reap the benefits.
>>>
>>>
>>>David Fitzjarrell
>>>
>>
>>
>>good eye, that would do it.....
>>
>>
>
> Yep.
>
> Another poster asked why Oracle wasn't smart enough to know that NTS was
> not a
> valid authentication mechanism on a non-Windows platform. Basically, it's
> because to do so would have made the code more complex and harder to
> support.
> The assumption was made that the installer would set the parameter
> properly.

Yep, and Oracle makes a lot of assumptions - that's why 3'rd party installation supports sites such as Werner Puschitz' got two million+ hits.

Three, four lines of code to test for host OS, added to the millions of lines? Screening for valid configurations would have eliminated the cause of this support issue altogether. Received on Mon Feb 28 2005 - 10:00:26 CST