You upgraded your database from pre-12c to a multitenant container database (CDB) containing
pluggable databases (PDBs).
Examine the query and its output:
Which two tasks must you perform to add users with SYSBACKUP, SYSDG, and SYSKM privilege
to the password file?
A.
Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.
B.
Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.
C.
Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE
argument set to No.
D.
Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE
arguments set to Yes.
E.
Re-create the password file in the Oracle Database 12c format.
Explanation:
* orapwd
/ You can create a database password file using the password file creation utility, ORAPWD.
The syntax of the ORAPWD command is as follows:
orapwd FILE=filename [ENTRIES=numusers] [FORCE={y|n}] [ASM={y|n}]
[DBUNIQUENAME=dbname] [FORMAT={12|legacy}] [SYSBACKUP={y|n}] [SYSDG={y|n}]
[SYSKM={y|n}] [DELETE={y|n}] [INPUT_FILE=input-fname]
force – whether to overwrite existing file (optional),
* v$PWFILE_users
/ 12c: V$PWFILE_USERS lists all users in the password file, and indicates whether the user has
been granted the SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, and SYSKM privileges.
/ 10c: sts users who have been granted SYSDBA and SYSOPER privileges as derived from the
password file.
ColumnDatatypeDescription
USERNAMEVARCHAR2(30)The name of the user that is contained in the password file
SYSDBAVARCHAR2(5)If TRUE, the user can connect with SYSDBA privileges
SYSOPERVARCHAR2(5)If TRUE, the user can connect with SYSOPER privileges
Incorrect:
not E: The format of the v$PWFILE_users file is already in 12c format.
I would go with DE
http://docs.oracle.com/database/121/ADMIN/dba.htm#ADMIN11059
B,D : D implied E too but with the flag FORCE
As you link say:
“The following command migrates a database password file in legacy format to Oracle Database 12c format. The password file is named orapworcl, and it is located in an operating system file system. The new database password file replaces the existing database password file. Therefore, FORCE must be set to y.”
I think is B&D. I we grant a user with the privilege of SYSBACKUP…..The username and password will be save as a new entry in the pwd file.
B and E
E
The administrative privileges SYSBACKUP, SYSDG, and SYSKM are supported in the password file only when the file is created created with the FORMAT=12 argument. 12 is the default for the FORMAT command-line argument.
B
Grant the SYSDBA, SYSOPER, SYSBACKUP, SYSDG, or SYSKM administrative privilege to the user. For example:
GRANT SYSDBA to mydba;
This statement adds the user to the password file, thereby enabling connection AS SYSDBA, AS SYSOPER, AS SYSBACKUP, AS SYSDG, or AS SYSKM.
B and D, file now in 12c Format => not E
B D
BD
B E
http://docs.oracle.com/database/121/ADMIN/dba.htm#ADMIN11059
FORMAT
If this argument is set to 12, the default, then ORAPWD creates a database password file in Oracle Database 12c format. Oracle Database 12c format is required for the password file to support SYSBACKUP, SYSDG, and SYSKM administrative privileges.
If this argument is set to legacy, then ORAPWD creates a database password file that is in the format before Oracle Database 12c. The password file supports SYSDBA and SYSOPER administrative privileges, but it does not support SYSBACKUP, SYSDG, and SYSKM administrative privileges.