Oracle 1Z0-083 - Questions & Answers
Free preview · every answer includes a full explanation
Product page: https://prepkeys.com/1z0-083.html
Which three are true about thresholds, metrics, and server-generated alerts? (Choose three.)
All metrics are instance related.
Cleared stateful alerts are displayed by querying DBA_ALERT_HISTORY.
A space usage management alert is automatically cleared after the underlying problem is resolved.
They are generated by SMON when a tablespace is 97% full.
Metrics are statistical counts for a specific unit.
STATISTICS_LEVEL must be set to ALL to generate alerts.
A. False. Tablespace Space Usage metris is database related
B. True. Stateful alerts appear in DBA_OUTSTANDING_ALERTS and, when cleared, go to
DBA_ALERT_HISTORY
C. True. Most alerts (such as "Out of space") are clared automatically when the cause of the problem
disappears.
D. False. They're generated by MMON
E. True
F. False. This parameter is not required to generate alerts
References:
Oracle Database 12c: Administration Wrokshop (https://docs.oracle.com/cd/E11882_01/server.112/e41573/autostat.htm#PFGRF027)
https://blogs.oracle.com/oem/how-to-clear-an-alert-v2
While backing up to an SBT channel, you determine that the read phase of your compressed Recovery Manager (RMAN) incremental level 0 backup is a bottleneck.
FORCE LOGGING is enabled for the database.
Which two could improve read performance? (Choose two.)
Increase the size of tape I/O buffers.
Disable FORCE LOGGING for the database.
Increase the size of the database buffer cache.
Enable asynchronous disk I/O.
Increase the level of RMAN multiplexing.
In RMAN operation, asynchronous Disk I/O is always better than synchronous I/O as a server process can begin an I/O and then perform other work while waiting for the I/O to complete.
On operating systems that do not support native asynchronous I/O, the database can simulate it with special I/O slave processes (DBWR_IO_SLAVES)
For which two requirements can you use the USER_TABLESPACE clause with the CREATE PLUGGABLE DATABASE command? (Choose two.)
to specify a default tablespace in a PDB cloned from another PDB in the same CDB.
to exclude all tablespaces except SYSTEM, SYSAUX, and TEMP when plugging in a PDB
to include specific user tablespaces only when relocating a PDB
to specify the list of user tablespaces to include when moving a non-CDB to a PDB
to exclude a temp tablespace when plugging in a PDB
to specify the list of tablespaces to include when creating a PDB from the CDB seed
Which three are true about requirements for various FLASHBACK operations? (Choose three.)
FLASHBACK transaction query requires undo to retrieve all versions of a row that existed between two points in time.
FLASHBACK drop requires that the RECYCLEBIN parameter be set to ON.
FLASHBACK version query requires that the RECYCLEBIN parameter be set to ON.
FLASHBACK DATA ARCHIVE requires undo to store all versions of all rows of a table being tracked.
FLASHBACK drop requires undo to retrieve all versions of a row that existed between two points in time.
FLASHBACK version query requires undo to retrieve all versions of a row that existed between two points in time.
A is incorrect. Although the statement "FLASHBACK transaction query requires undo" is true, it is asking to retrieve all versions of a row instead. The correct answer should be F which is FLASHBACK version query to retrieve versions between two point in time from undo.
A. FLASHBACK transaction query requires undo to retrieve all versions of a row that existed between two
points in time.
F. FLASHBACK version query requires undo to retrieve all versions of a row that existed between two
points in time.
References:
https://books.google.com.pk/books?id=0iwrL9P25Z0C&pg=PA35&lpg=PA35&dq=FLASHBACK
+transaction+query+requires+undo+to+retrieve+all+versions+of+a+row+that+existed+between+two +points+in +time&source=bl&ots=MJnYl5CZ1u&sig=ACfU3U0dWP-NPd- U8uu3zbaoi3YZzT0FTQ&hl=en&sa=X&ved=2ahUKEwigi5_Jl9joAhXzUBUIHUh4DksQ6AEwAnoECAsQJg #v=onepage&q=FLASHBACK%20transaction%20query%20requires%20undo%20to%20retrieve%20all% 20versions%20of%20a%20row%20that%20existed%20between%20two%20points%20in%20time&f=false (https://docs.oracle.com/cd/E18283_01/server.112/e17120/tables011.htm)
Which three actions are performed by the Oracle Preinstallation RPM, oracle-database-server-xxxx-preinstall, for Oracle Grid Infrastructure, where xxxx is the Oracle version and release? (Choose three.)
performing checks to ensure minimum configuration requirements for Oracle Grid Infrastructure are met
creating the oracle OS user
creating the OSDBA (dba) group
creating thte oraInventory (oinstall) group
creating the grid OS user
configuring the OS for Oracle Automatic Storage Management shared storage access
When installed, the Oracle Preinstallation RPM does the following:
Automatically downloads and installs any additional RPM packages needed for installing Oracle Grid Infrastructure and Oracle Database, and resolves any dependencies
Creates an oracle user, and creates the oraInventory (oinstall) and OSDBA (dba) groups for that user
As needed, sets sysctl.conf settings, system startup parameters, and driver parameters to values based on recommendations from the Oracle Preinstallation RPM program
Sets hard and soft resource limits
Sets other recommended parameters, depending on your kernel version
Sets numa=off in the kernel for Linux x86_64 machines.
References:
https://docs.oracle.com/cd/E11882_01/install.112/e41961/prelinux.htm#CWLIN2932
Which two are true about common objects? (Choose two.)
They can be created only in CDB$ROOT.
They can be only metadata-linked in an application container.
They can exist in user-defined schemas only in application containers.
They can exist in CDB$ROOT and an application root.
They can be extended data-linked in CDB$ROOT.
They can be created only in an application root.
A common object is defined in either the CDB root or an application root, and can be referenced using metadata links or object links. A local object is every object that is not a common object.
Database-supplied common objects are defined in CDB$ROOT and cannot be changed. Oracle Database does not support creation of common objects in CDB$ROOT.
You can create most schema objects-such as tables, views, PL/SQL and Java program units, sequences, and so on-as common objects in an application root. If the object exists in an application root, then it is called an application common object.
ACCORDING THE LECTURE, CORRECT ANSWERS ARE: DF
D: they can exist in CDB$ROOT and application root.
F: they can be created only in application root.
References:
https://blog.toadworld.com/2017/08/01/oracle-multi-tenant-application-containers-part-iii-sharing-of-data-in-application-common-objects
Which two are true about the Automatic Database Diasnostic Monitor (ADDM)? (Choose two.)
It analyzes a period of time corresponding to the 12 hours of activity.
It runs automatically after each AWR snapshot.
A DBA can run it manually.
Results are written to the alert log.
It analyzes a period of time corresponding to the last day of activity.
Results are written to the alert log. -Incorrect .. stores in AWR not in alert logfile.
Which two are true about server-generated alerts? (Choose two.)
Stateful alerts must be created by a DBA after resolving the problem.
Stateless alerts can be purged manually from the alert history.
Stateless alerts can be cleared manually.
Stateless alerts are automatically cleared.
Stateful alerts are purged automatically from the alert history.
Best to start with defining stateful/stateless: A stateful alert is a threshold based alert (ie, tablespace usage above 90%), a stateless alert is non-threshold based alert (ie, a capture aborted with an ORA-error).
A stateful alert first appears in DBA_OUTSTANDING_ALERTS. When cleared, it goes to DBA_ALERT_HISTORY.
A stateless alert goes straight to DBA_ALERT_HISTORY
A stateless alert can be considered as a "point in time" error, the DB tells you about it and then forgets that it ever spoke about it.
Therefore, each answer:
A: FALSE - the DB creates stateful alerts, not a DBA.
B: TRUE - a DBA can perform a purge to bulk remove alerts, perhaps based on date
C: TRUE - a DBA can clear individual alerts
D: FALSE - Stateless alerts are never checked again, by the DB, so cannot be automatically cleared
E: FALSE - Stateful alerts are purged from the "Outstanding Alerts" and put into the alert history, where they will remain.
Therefore, BC are correct
References:
https://jameshuangsj.wordpress.com/2019/12/01/clears-stateless-alerts-in-oem-by-using-emcli/
Which three are located by using environment variables? (Choose three.)
the Optimal Flexible Architecture (OFA) compliant path to store Oracle software and configuration files.
the location of Oracle Net Services configuration files
the list of a disk group names to be mounted by an Oracle Automatic Storage Management (ASM) instance at startup
default directories for temporary files used by temporary tablespaces
the temporary disk space used by Oracle Installer during installation
the maximum number of database files that can be opened by a database instance
A - ORACLE_BASE, ORACLE_HOME - correct
B - TNS_ADMIN, old TWO_TASK, etc - correct
C - spfile parameter ASM_DISKGROUPS, not env variable
D - [s]pfile parameter DB_CREATE_FILE_DEST, not env variable
E - TMP, TEMP - correct
F - [s]pfile parameter DB_FILES, not env variable
Which three are true about opatchauto? (Choose three.)
It performs a shutdown and then a restart of all processes in both Oracle Grid Infrastructure and Oracle Database home during the patching process.
It must be invoked by a user with root user privileges.
Patches are applied via opatchauto.
Users must always input patch plans to opatchauto.
It requires the Oracle Grid Infrastructure and Oracle Database instances to be shut down before being invoked.
It applies patches in nonrolling mode by default.
It is used to apply interim patches to Oracle Grid Infrastructure and Oracle Database home combinations.
A. It performs a shutdown and then a restart of all processes in both Oracle Grid Infrastructure and Oracle
Database home during the patching process. => True
B. It must be invoked by a user with root user privileges. => true
C. Patches are applied via opatchauto. => not always.
D. Users must always input patch plans to opatchauto. => false, patch plans is optional
E. It requires the Oracle Grid Infrastructure and Oracle Database instances to be shut down before being
invoked. => false
F. It applies patches in nonrolling mode by default. => false, default is rolling mode.
G. It is used to apply interim patches to Oracle Grid Infrastructure and Oracle Database home
combinations. => true
Correct: A,B,G
References:
https://docs.oracle.com/cd/E24628_01/doc.121/e39376/opatchauto_commands.htm#OPTCH585
https://docs.oracle.com/cd/E24628_01/doc.121/e39376/configuration_patching.htm#OPTCH149
Showing 10 of 273 questions · Unlock the full set