Download Oracle.1z0-062.PassGuide.2018-11-15.217q.tqb
| Vendor: | Oracle |
| Exam Code: | 1z0-062 |
| Exam Name: | Oracle Database 12c: Installation and Administration |
| Date: | Nov 15, 2018 |
| File Size: | 3 MB |
| Downloads: | 1 |
Demo Questions
Question 1
Which three statements are true about Automatic Workload Repository (AWR)? (Choose three.)
- All AWR tables belong to the SYSTEM schema.
- The AWR data is stored in memory and in the database.
- The snapshots collected by AWR are used by the self-tuning components in the database
- AWR computes time model statistics based on time usage for activities, which are displayed in the v$SYS time model and V$SESS_TIME_MODEL views.
- AWR contains system wide tracing and logging information.
Correct answer: BCD
Question 2
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? (Choose two.)
- Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.
- Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.
- Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE argument set to No.
- Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE arguments set to Yes.
- Re-create the password file in the Oracle Database 12c format.
Correct answer: BD
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. * 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.
Question 3
An application accesses a small lookup table frequently. You notice that the required data blocks are getting aged out of the default buffer cache.
How would you guarantee that the blocks for the table never age out?
- Configure the KEEP buffer pool and alter the table with the corresponding storage clause.
- Increase the database buffer cache size.
- Configure the RECYCLE buffer pool and alter the table with the corresponding storage clause.
- Configure Automata Shared Memory Management.
- Configure Automatic Memory Management.
Correct answer: A
Explanation:
Schema objects are referenced with varying usage patterns; therefore, their cache behavior may be quite different. Multiple buffer pools enable you to address these differences. You can use a KEEP buffer pool to maintain objects in the buffer cache and a RECYCLE buffer pool to prevent objects from consuming unnecessary space in the cache. When an object is allocated to a cache, all blocks from that object are placed in that cache. Oracle maintains a DEFAULT buffer pool for objects that have not been assigned to one of the buffer pools. Schema objects are referenced with varying usage patterns; therefore, their cache behavior may be quite different. Multiple buffer pools enable you to address these differences. You can use a KEEP buffer pool to maintain objects in the buffer cache and a RECYCLE buffer pool to prevent objects from consuming unnecessary space in the cache. When an object is allocated to a cache, all blocks from that object are placed in that cache. Oracle maintains a DEFAULT buffer pool for objects that have not been assigned to one of the buffer pools.
