Re: svrmgrl's passwd

Hi

If you use the orapwd utility you can pass only one password to it, this is then used for SYS and INTERNAL. Also you cannot use sqlplus or svrmgrl to change the internal password as it then complains that the user does not exist.

Maybe i misunderstand you, how can you set the internal password different to the SYS password ?

Here is an interesting thought,

select username,password from dba_users;

the password hash does not appear for the user internal. But ensure you dont have a password file and use connect internal in sqlplus not as a dba of course and enter the password.

Oracle must either store the hash seperatly somewhere else, or it must check it by "munging" the password with SYS and check its hash, hence maybe why it has to be the same password ?

cheers

Pete

In article <uYEa7.23793$b_3.2047419_at_news0.telusplanet.net>, Dave Haas <davehaas_at_hotmail.com.com> writes
>Hi all.
>
>Just to clarify one thing. The SYS password and the INTERNAL password are
>usually not the same. Running an 'alter user sys identified by ...' command
>has the side effect of changing the internal password. However, to me it
>seems like a better security system to have the INTERNAL password and the
>SYS password different. The INTERNAL password should really be changed using
>the orapwd utility (except on WinNT systems where they seem to want to
>change the name of the utility every 5 minutes).
>
>Cheers,
>
>Dave Haas
>
>
>"Pete Finnigan" <pete_at_peterfinnigan.demon.co.uk> wrote in message
>news:1SklXmBl6wa7EwCG_at_peterfinnigan.demon.co.uk...
>> hi
>>
>> log into sqlplus and set the sys password to something new, this will
>> then be the same password required for the user "INTERNAL". The only
>> time its a different password to SYS is on install, when INTERNAL is
>> set to oracle and SYS is set to change_on_install.
>>
>> Else if you know the the SYS password run orapwd as follows
>> orapwd filename=[location] password=[sys password]
>>
>> cheers
>>
>> Pete Finnigan
>>
>> www.pentest-limited.com
>>
>>
>> In article <b5a20d6c.0108031046.32cc450c_at_posting.google.com>, Michel
>> Gauthier <michel_gaudu_at_hotmail.com> writes
>> >Hi,
>> >
>> >My hint might look a little bit simple, but here it is anyway:
>> >
>> >Did you set the ORACLE_SID environment variable prior to run svrmgrl?
>> >I don't know win 2000 yet, but on WinNT 4, if there is not a default
>> >value for this variable and if you omit to specify one, you obtain the
>> >same behavior you mentioned in you posting (since svrmgrl cannot
>> >identify which instance to connect to).
>>
>>
>> >
>> >HTH,
>> >
>> >Michel
>> >
>> >cljlk <cljlk_at_hotmail.com> wrote in message
 news:<3B6A6B44.AFC6C9EB_at_hotmail.com>.
>> >..
>> >> Hi,
>> >>
>> >> I ran svrmgrl on Windows 2000 and enter connect internal, it requests
 me
>> >>
>> >> to enter password. I enter passwd as xxxxxx.But I got insufficient
>> >> privileges.
>> >> When I first install the Oracle 8.1.7, it gave me the Internal passwd
 is
>> >> xxxxxx.
>> >> I thought it does not require to enter password for internal
 connection.
>> >>
>> >> Please give me a tip how to solve this issue.
>> >> Thanks
>>
>> --
>> Pete Finnigan
>
>
 

-- 
Pete Finnigan