RE: password for internal

From: Mark Leith <mark_at_cool-tools.co.uk>
Date: Fri, 3 Nov 2000 14:23:48 -0000
Message-Id: <10669.121059@fatcity.com>

Hold on, first of all you need to set REMOTE_LOGIN_PASSWORDFILE to either SHARED or EXCLUSIVE, the other option is NONE but you don't need that. the value is *not* TRUE.

Straight from a document:

---

EXCLUSIVE Specifies that only one instance can use the password file and that the password file contains names other than SYS and INTERNAL. Oracle8i looks in the registry for the value of the ORA_SID_PWFILE parameter. If a value is unspecified, it looks in the registry for the value of the ORA_PWFILE parameter, which points to a file containing the INTERNAL password as well as user names, passwords, and privileges. If that is not set, it uses the default of
ORACLE_BASE\ORACLE_HOME\DATABASE\PWDSID.ORA. SHARED Specifies that multiple instances can use the password file (for example, a parallel server environment). However, the only users recognized by the password file are SYS and INTERNAL. You cannot log in with SYSOPER or SYSDBA privileges even if those privileges are granted in the password file. The SHARED value of this parameter affords backward compatibility with earlier releases. The Oracle8i database looks for the same files as it does when the value is EXCLUSIVE, but only the INTERNAL account is available for privileged access. This is the default value.

NONE Specifies that the Oracle8i database ignores the password file and that privileged users are authenticated by the operating system. NONE is the default setting.

---

You will need to check if a password file already exists - Check this by going to ORACLE_HOME/DATABASE, the file would be PWDsid.ora, if one does already exists. If there is one you will already have a password set for INTERNAL, so you may want to dig a little more in to finding what it is.

If you want to continue to change the password, you can change it with ORADIM, but I don't think anybody can be connected at the time? List?

To do this with ORADIM get to a command prompt and input:

ORADIM -DELETE -SID SID then

ORADIM -NEW -SID <sid> -INTPWD <new_password> - STARTMODE AUTO - MAXUSERS <n>
-PFILE <\path\init{sid}.ora>

Where sid is the sid you just deleted, new_password explains itself, and n is the maximum number of user allowed to connect as either SYS or INTERNAL at any one time. pfile is the path to your init.ora file.

Please remember that this should only be done in a maintenance window!

Alternatively you can *delete the existing* and/or create a new PWDsid.ora file, with PWDORA. Once again get to a command prompt and input:

ORAPWD FILE=PWD<sid>.ORA PASSWORD=<password> ENTRIES= <max_users>

Once you have done this you should be able to connect with INTERNAL. You will also then be able to connect as SYSOPER/SYSDBA aswell. To do this:

grant SYSDBA to user

connect user/password as SYSDBA

You may also want to try just try changing it through SQL*Plus, connect as SYS and execute:

alter user SYS identified by new_password; as INTERNAL is essentialy just a SYS alias..

HTH Mark

----snip----
Sorry, I didn't reply sooner.
I have other problems which require my immediate attention. I do have REMOTE_LOGIN_PASSWORDFILE =TRUE Do I have to shutdown database to run that script (usually not)? Small problem is that I can't shutdown my database now ;users are connected (how dare they). As soon as I try I'll tell you. Does this script enable profile limits for me or I have to do it manualy through user profiles? Thanks for your help.

    Sonja

----snip----
>
> are you sure that you have the parameter REMOTE_LOGIN_PASSWORDFILE to
Received on Fri Nov 03 2000 - 08:23:48 CST