Free and Premium Oracle 1z0-068 Dumps Questions Answers

Default data file templates are only created by ASM when a normal redundancy disk group is created.

Default template settings for redundancy depends on the disk group redundancy.

Default templates for a disk group can be modified.

Default template setting for striping depends on disk group redundancy.

Templates may be shared across disk groups.

They exist both in ASM and RDBMS instances, and display the same output.

Their names can be seen in dict when connected to an ASM instance.

Their names can be seen in vfixed_table when connected to an instance of any type that is started.

They exist in both in ASM and RDBSM instances, but they can display different outputs depending on the instance type.

gvasm_attribute can be used to display the ASM_POWER_LIMIT attribute of all ASM instances in the cluster.

Some grid infrastructure patchsets may not be installed in a rolling fashion.

They can be applied in-place.

When performing rolling patches, crsctl query crs softwareversion always displays the lowest version of the software running anywhere in the cluster

When performing rolling patches, the VIPs for the node being patched are relocated to another node.

ACFS auditing information is replicated from the primary file system to the standby file system.

One site of an ACFS replication configuration can be host both primary and standby file systems.

Replication is automatically terminated if the primary file system has less than 2GB free space.

Standby redo log files are required on the standby site for synchronous redo transport.

The privilege SYSREPL has been introduced for ACFS replication.

using Shared GNS for the leaf nodes and local GNS for the hub nodes in a Flex Cluster

using Shared GNS running on another cluster

using Shared GNS for the hub nodes and local GNS for the leaf nodes in a Flex Cluster

creation of a new GNS for this cluster

using DHCP to assign Node Virtual IP addresses for nodes in the cluster

It applies a patch to the Grid Infrastructure only on the first cluster node.

It applies a patch to the Grid Infrastructure on all cluster nodes.

It applies a patch to all database ORACLE_HOMEs, with the same release as the Grid Infrastructure, only on the first cluster node.

It applies a patch to all database ORACLE_HOMEs, with the same release as the Grid Infrastructure, on all cluster nodes.

It applies a patch to all database ORACLE_HOMEs of any version on the first cluster node.

It applies a patch to all database ORACLE_HOMEs of any version on all cluster nodes.

PDB_3 must be closed on all CDB1 instances.

Manually created services for PDB_3 are not removed automatically from the OCR when dropping PDB_3.

CDB1 must be open in restricted mode on all cluster nodes.

PDB_3 must be open READ ONLY in all CDB1 instances.

Manually created services for PDB_3 are removed automatically from the OCR when dropping PDB_3.

The Installer permits the creation of a disk group for use by the voting disks and OCR file.

If no ASM disk groups are specified during installation, then ASM instances are not started after the installation completes on any cluster node.

The Installer permits the creation of a disk group to be used for the Recovery Area for the ASM instance.

If ASM disk groups are configured for the Clusterware files, then ASM must be used for all databases on the cluster.

ASM disk groups used for voting files and OCR files require a quorum failgroup.

The application may use the JDBC thin driver.

The ons.jar file must be present in the CLASSPATH.

The ONS daemon must be started on the middle tier running the Java application.

You must configure TAF, either on the client or for the service.

The ONS daemon must be started on the middle tier and client machines to enable FCF.

1, 2, 3, 4, 5, 2, 10, 7

1, 3, 5, 7

1, 8, 6, 3, 5, 8, 9, 7

1, 8, 6, 3, 5, 2, 10, 7

One UNDO tablespace for each PDB is required.

One UNDO tablespace for each instance is required.

PDBs can have local temporary tablespaces.

All the containers share the same SYSTEM and SYSAUX tablespaces.

You can open one, several, or all PDBs on one, several, or all CDB instances.

an operating system version

a version of Oracle database server used in Real Application Cluster (RAC) databases

software required to configure nodes at startup

the GPnP software

a file system version used for the software to be installed

a version of Automatic Storage Management (ASM) used for the cluster

using DBCA to migrate the database to shared storage and then start one or more RAC database instances on the cluster

using DBCA to create a template from the single-instance database and then to create a RAC database on the cluster using that template

using the rconfig utility to create a template from the single-instance database and then using DBCA to create a RAC database on the cluster using that template

using the rconfig utility to migrate the database to shared storage and then using DBCA to start one or more RAC database instances on the cluster.

Update the PATH environment variable on each cluster node to point to the $ORACLE_HOME/OPatch directory.

Stage the patch on the cluster node where the OPatch utility will be executed.

Update the PATH environment variable on the node where will run the OPatch utility to point to the $ORACLE_HOME/OPatch directory.

Stage the patch on the cluster nodes.

An ASM instance must store its SPFILE in ASM.

The ASM passwordfile can be stored in $GRID_HOME/dbs on local storage of a cluster node.

The ASM passwordfile can be stored in a diskgroup that is accessible to all ASM instances.

The SPFILE must be stored in $GRID_HOME/dbs on local storage of a cluster node.

The SPFILE must be stored in a diskgroup that is accessible to all ASM instances.

PARALLEL_MIN_SERVERS will be 200 for all instances of PROD.

PARALLEL_MIN_SERVERS will be 100 for all instances of PROD.

The second statement returns an error because this parameter must be identical for all instances.

PARALLEL_MIN_SERVERS will be 200 for PROD2 and PROD3 and 100 for PROD1.

Pluggable Databases (PDBs)

administrator-defined resources

local resources

database transactions

cluster resources

All node evictions require that the evicted node or nodes be rebooted.

A node whose performance is severely degraded can be evicted.

The OCSSD process may evict a node after an escalation request from a database instance LMON process.

The CSSDMONITOR process can request a node eviction.

The OCLSKD process is used for node eviction requests originating on the node to be evicted.

The reboot advisory broadcasts reboot decisions only over the interconnect.

Run ocrconfig –repair on another node in the cluster to repair the ocr.loc file on host01

Stop the clusterware stack on host01 only.

Stop the clusterware stack on all cluster nodes.

Run ocrconfig –repair on host01.

Stop the clusterware stack on host01 and on the node used to issue the ocrconfig –repair command.

The Clusterware binaries may be installed without installing ASM binaries.

The Grid Infrastructure Management Repository is only required when using ASM.

Specifying the use of Grid Naming Service is optional.

Normal Redundancy ASM Disk Groups used for Clusterware flies will contain three voting files regardless of the number of failgroups.

High Redundancy ASM Disk Groups used for Clusterware files will contain two OCRs.

It always requires a Flex cluster.

Only three ASM instances are supported in Flex ASM.

The SPFILE and password file for ASM are stored by default in an ASM disk group.

An ASM instance can run on a leaf node.

A designated network is used for communication between ASM instances and theirclients.

ASM clients can fail over to other ASM instances.

A server pool directive override can be used to modify the database parameter CPU_COUNT for all databases within one server pool.

It requires a resource manager plan to be active on databases managed by QoS.

It supports RAC One Node databases if they are assigned to server pools with a maximum size of one server.

One QoS policy can span multiple clusters if they contain server pools, assigned to be managed by QoS.

The command-line utility qosct1 can be used to change the password of the internal user QOSADMIN.