The orapwd command will create a password file with a single entry for the SYS user and other
options, as noted, when you run the orapwd command without any options:
[oracle@dw ~]$ orapwd
Usage: orapwd file=
password=
entries= force= ignorecase= nosysdba=
where
file - name of password file (required),
password - password for SYS (optional),
entries - maximum number of distinct DBA (required),
force - whether to overwrite existing file (optional),
ignorecase - passwords are case-insensitive (optional),
nosysdba - whether to shut out the SYSDBA logon
(optional Database Vault only).
There must be no spaces around the equal-to (=) character.
[oracle@dw ~]$
Once you re-create the password file, you will have to grant the SYSDBA and SYSOPER
privileges to those database users who previously had those privileges. In addition, if the password
you provided in the orapwd command is not the same password that the SYS account has in the
database, this is not a problem: when you connect using connect / as sysdba, you??™re using operating
system authentication, and if you use connect sys/syspassword as sysdba, the password syspassword
is the password for SYS in the database. And just to reiterate, if the database is down or in MOUNT
mode, you must use operating system authentication or the password file. Also worth noting is
that operating system authentication takes precedence over password file authentication, so as
long as you fulfill the requirements for operating system authentication, the password file will
not be used for authentication if it exists.
Pages:
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477