Oracle A423961 - Manual (Page 91)

4 – 7 Getting the Most out of Integration with Windows NT
Creating Password Files
You create password files with the Instance Manager, as part of the
process of creating an instance. The two essential elements of a
password file you specify with the Instance Manager are:
• the password for the INTERNAL account for that instance
• the maximum number of users to whom you wish to grant
SYSOPER or SYSDBA privileges
The Instance Manager creates (in \ORANT\DATABASE) a password
file with the name PWDsid.ORA, where sid is the system identifier (SID).
Later, you can add (or delete) user names, user passwords, and user
privileges in the password file, using Server Manager.
Warning: Do not move or copy password files on your own; do
so only with the Instance Manager. If you do, the Instance
Manager may not be able to find a password in order to start an
instance.
Starting Services Automatically
You can start Oracle7 Server for Windows NT automatically on restart
by setting the OracleStartORCL service to automatic in the Services
control panel.
Using Windows NT OS Authentication
When enrolling ORACLE users, you may optionally use the NT
username as the basis for ORACLE usernames. Users enrolled in this
way can connect to ORACLE7 Server faster and more conveniently.
When using the NT username for authentication, the database
administrator sets the OS_AUTHENT_PREFIX parameter in the
INITsid.ORA file. If this parameter is not set, the default value is OPS$.
The syntax for granting automatic logins when using the default value
of OS_AUTHENT_PREFIX is as follows:
SVRMGR> create user TO OPS$USERID IDENTIFIED EXTERNALLY;
where USERID is the user’s NT username.
Additional Information: For more information on operating
system authentication, see Oracle7 Server Administrator’s Guide.