<fitzjarrell_at_cox.net> wrote in message
news:1109492218.333765.217220_at_f14g2000cwb.googlegroups.com...
>
> Haximus wrote:
>> "Thomas Kyte" <tkyte_at_oracle.com> wrote in message
>> news:119453490.0000d577.094_at_drn.newsguy.com...
>> > In article <1109453060.818448.137070_at_l41g2000cwc.googlegroups.com>,
> G
>> > Quesnel
>> > says...
>> >>
>> >>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
>> >>
>> >
>> >
>> > In order to use the OS authentication:
>> >
>> > connect / as sysdba
>> >
>> > you must belong to the correct OS group, looks like the default dba
> is in
>> > place
>> > here.
>> >
>> > So, are you in the DBA group?
>>
>> He rebuilt the password file... if I'm correct this means the
> INTERNAL
>> account. If the password file is not successfully reset he's SOL!
> Try
>> re-create the password file with the utlity is the best bet, or copy
> a
>> working one...
>
> Interesting that no one has caught the fact he's trying to use NTS
> authentication on a Solaris box, other than myself. If this truly is
> on Solaris the following line in the sqlnet.ora file needs to be
> commented:
>
> SQLNET.AUTHENTICATION_SERVICES= (NTS)
>
> since NTS authentication is solely for Oracle on a Windows platform.
> Changing this one line could very well solve his problem.
That does make sense Fitzy... setting native NT authentication would be
pointless on Solaris. You'd think though, that Oracle would detect it's not
on a Windows host and barf when trying to use NTS with a log entry or
something... might require setting tracing options to see it ...
Received on Sun Feb 27 2005 - 10:05:36 CST
