Re: CONNECT INTERNAL ASKS FOR PASSWORD

Check your ORACLE_SID. Then check that there is a password file of the name orapw<SID> in the ORACLE_HOME/dbs directory (or at least a symbolic link to wherever the password file actually resides). Might just want to check that the permissions on that file have not been altered by someone, and that Oracle has full read/write access to it.

Use the orapwd utility to construct a new password file (in the appropriate location) if the original has gone walkabout.

(And, PS, cross-posting is usually not a good idea. The server group would have been fine on its own)

Regards
HJR "Dennis Chebotarev" <dddennn_at_pacbell.net> wrote in message news:fbha8.3033$662.2034080877_at_newssvr21.news.prodigy.com...
> Connect internal stopped working for some reason. It used to work before.
> I'm doing everything as oracle software owner.
>
> Here's what i got:
>
> $ id
> uid=105(oracle) gid=100(dba)
> $ uname -a
> SunOS daemos 5.8 Generic_108528-11 sun4u sparc SUNW,Ultra-4
> $ svrmgrl
>
> Oracle Server Manager Release 3.1.6.0.0 - Production
>
> Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
>
> Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
> With the Partitioning option
> JServer Release 8.1.6.0.0 - Production
>
> SVRMGR> connect internal
> Password:
> Password:
> ORA-01031: insufficient privileges
> SVRMGR> exit
> Server Manager complete.
> $
>
> Any ideas why?
>
>
Received on Tue Feb 12 2002 - 21:38:50 CST