CONNECT INTERNAL Prompting for Password

[Scott Buckingham]

Sounds simple enough, but all attempts to fix have failed. Please read on.

Yesterday, our database server went down and a cold reboot was the result (HP-9000, K360, HP-UX 11.00). We have both Oracle 7 and 8 on this box and the one instance of 7 came back and our test instance of Oracle 8.1.7 did too. However, our production instance (also 8.1.7) did not. In fact, we cannot do a CONNECT INTERNAL as we are prompted for a password. We enter the SYS password, but when a STARTUP is issued, we get 'insufficient privileges'. I suspected a bad password file so I thought I would rebuild it using orapwd. However, when I execute this command, I get: 'opw-00001 unable to open password file'. Any ideas?

[Steve Steel]

Hi


check

$ORACLE_HOME/dbs/orapw$ORACLE_SID


Permissions on the orapwd command


Steve Steel

[Scott Buckingham]

That's part of the problem; I'm trying to recreate the password file and I can't. The original file had permission settings of (I've sinced renamed it):

-rwSr----- oracle dba orapwSID

The SQLNET.ORA file contains the line:

SQLNET.AUTHENTICATION_SERVICES=(NTS)

and my initSID.ora file contains:

remote_login_passwordfile = EXCLUSIVE

[Massimo Bianchi · Accepted solution]

Try commenting the entry of sqlnet.authentication.

NTS should be for use on WINDOWS, afaik....

Are you sure you are logging in as the owner of the oracle executable ? It is the onle one allowed to login with internal, without password...

Massimo

[Scott Buckingham]

Thank you! That was it! I forgot that I added the authentication line to the sqlnet.ora file a while back for "preferred credentials". I only applied this for one user and not the other.