READ Free Dumps For Oracle- 1z0-062
| Question ID 21743 | 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?
|
| Option A | Configure the KEEP buffer pool and alter the table with the corresponding storage clause.
|
| Option B | Increase the database buffer cache size.
|
| Option C | Configure the RECYCLE buffer pool and alter the table with the corresponding storage clause.
|
| Option D | Configure Automata Shared Memory Management.
|
| Option E | Configure Automatic Memory Management
|
| Correct Answer | A |
Explanation 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.
| Question ID 21744 | You conned using SQL Plus to the root container of a multitenant container database (CDB) with SYSDBA privilege.
The CDB has several pluggable databases (PDBs) open in the read/write mode.
There are ongoing transactions in both the CDB and PDBs.
What happens alter issuing the SHUTDOWN TRANSACTIONAL statement?
|
| Option A | The shutdown proceeds immediately.
The shutdown proceeds as soon as all transactions in the PDBs are either committed or rolled hack.
|
| Option B | The shutdown proceeds as soon as all transactions in the CDB are either committed or rolled back.
|
| Option C | The shutdown proceeds as soon as all transactions in both the CDB and PDBs are either committed or rolled back.
|
| Option D | The statement results in an error because there are open PDBs.
|
| Correct Answer | B |
Explanation Explanation: * SHUTDOWN [ABORT | IMMEDIATE | NORMAL | TRANSACTIONAL [LOCAL]] Shuts down a currently running Oracle Database instance, optionally closing and dismounting a database. If the current database is a pluggable database, only the pluggable database is closed. The consolidated instance continues to run. Shutdown commands that wait for current calls to complete or users to disconnect such as SHUTDOWN NORMAL and SHUTDOWN TRANSACTIONAL have a time limit that the SHUTDOWN command will wait. If all events blocking the shutdown have not occurred within the time limit, the shutdown command cancels with the following message: ORA-01013: user requested cancel of current operation * If logged into a CDB, shutdown closes the CDB instance. To shutdown a CDB or non CDB, you must be connected to the CDB or non CDB instance that you want to close, and then enter SHUTDOWN Database closed. Database dismounted. Oracle instance shut down. To shutdown a PDB, you must log into the PDB to issue the SHUTDOWN command. SHUTDOWN Pluggable Database closed. Note: * Prerequisites for PDB Shutdown When the current container is a pluggable database (PDB), the SHUTDOWN command can only be used if: The current user has SYSDBA, SYSOPER, SYSBACKUP, or SYSDG system privilege. The privilege is either commonly granted or locally granted in the PDB. The current user exercises the privilege using AS SYSDBA, AS SYSOPER, AS SYSBACKUP, or AS SYSDG at connect time. To close a PDB, the PDB must be open.