1z0-078 Oracle Database 19c: RAC, ASM, and Grid Infrastructure Administration Questions and Answers

Use the crsct1 set trace res "resource_name=debugging_level" command.

Use the crsct1 set log res "resource_name=debugging_level2" command.

Set the environment variable _USR_ORA_DEBUG=1 and then stop and restart the resource that requires resource debugging data to be collected.

Use the cluvfy comp command for the specific resource within a component.

The clusterware log files are stored inside the Grid Infrastructure Management Repository database used by the cluster health monitor

The diagcolleccion.pl script must be run from the Grid home directory as the arid infrastructure owner.

There is one ologgerd service for the cluster health monitor (CHM) on each cluster node regardless of cluster size.

The oclumon utility may be used to get and set parameters for the cluster health monitor (CHM) repository.

There is one osysmond service for the cluster health monitor (CHM) on each cluster node regardless of cluster size.

Cluster resources

Database transactions

Local resources

Administrator-defined resources

Pluggable Databases (PDBs)

Any database instance with the COMPATIBLE parameter set to 12.2 or later can access it.

It can contain ASM Dynamic Volume Manager (ADVM) volumes.

Each disk in each of the three fail groups is a mirror of the corresponding disk of the other two failure groups.

The ASM compatible attributes can be changed to 12. l for this disk group.

Files created in this disk group always have two copies for each allocation unit: one primary and one secondary.

The DB_CREATE_FILE_DEST parameter must be set to +DATA(newtemplate).

newtemplate must be defined for the +DATA disk group.

Existing data files in TBS1 must also use the same template.

User-defined subdirectories ORCL and USERS must already exist.

The +DATA disk group should not be part of Flex ASM.

Create the current yr directory in the root directory (+).

Create the current yr directory in the +data disk group.

Add the DATAFILE '+DATA/CURRENT YR/sales.dbf clause to the command.

Add the autoextend on clause to the command.

lAdd the DATAFILE '/CURRENT YR/sales.dbf clause to the command.

Each cluster node must have at least two network interface cards.

You must enable the Name Server Cache Daemon

A DHCP service on the private network for the cluster is required to allocate virtual IP addresses for HAIP.

A DHCP service on the public network for the cluster is required to allocate virtual IP addresses as required by the cluster.

DNS must be configured to delegate name resolution for the cluster subdomain to the cluster.

You must create a Grid Management Repository database.

Different nodes in a cluster may belong to separate administrator-defined categories.

All nodes in a cluster belong to the same Oracle-supplied category.

A server may be added to only one category using the crsctl utility.

All server attributes that may be used to determine the server category are discovered automatically by Oracle Clusterware.

All server attributes used for categorization are administrator modifiable.

Server categories can only be used for nodes running an application server.

They listen only for database instances on the same node.

They listen on behalf of any ASM instance and all database instances on the same node.

They listen only for the ASM instance on the same node.

There can be only one node listener per node.

They run from the Grid Infrastructure home by default.

It fails because the ASM instance has not been shut down first on HOST03.

It succeeds and starts an ASM instance on HOST02 but the ASM instance on HOST03 is not shut down until all connected clients disconnect.

It succeeds and starts an ASM instance on HOST02 and shuts down the ASM instance on HOST03.

It succeeds and 19c database instances connected to the ASM instance on HOST03 can be reconnected to the ASM instance on HOST02.

It succeeds and 19c database instances connected to the ASM instance on HOST03 can be reconnected to the ASM instance on HOST01.

It fails because an ASM instance is not configured to run on HOST02.

They can be created only if OMF is enabled.

They are system Generated at the time of ASM file creation.

They can be used to reference existing ASM files.

They are the only valid form that can be used for single file creation of a control file.

An alias may be created for an existing file by referring to the fully qualified file name.

SSH user equivalence for the Oracle user can be set up before the software installation.

Fix-up scripts generated during the installation must be run as root on UNIX platforms.

The software must be installed into a local file system on each node.

The software must be installed into a cluster file system.

RAC installations require Oracle Enterprise Edition.

The software can be installed into an ACFS file system.

The software must be installed on all nodes in the cluster.

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

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

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 dbca to create a template from the single-instance database and then to create a RAC database on the cluster using that template

Use srvctl start vip to start the VIP on host01.

Use oifcfg setif to start the VIP on host01.

Use oifcfg setif to stop the VIP on host01.

Use srvctl modify nodeapps to change the VIP on host01.

Use srvctl stop vip to stop the VIP on host01.

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

Their names can be seen inv$fixed_tablewhen connected to an instance of any type that is started.

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

gv$asm_attribute can be used to display the ASM_POWER_LIMIT attribute of all ASM instances in the cluster.

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

It can analyze performance over any given time period.

It can diagnose skew in response time.

It can analyze performance using data captured on all instances.

It can only analyze performance on the instance running the ADDM job.

It can diagnose latency problems in the Cluster Interconnect.

It runs automatically in Instance ADDM mode after each AWR snapshot is created.

A server pool must be created with srvct1 before creating a policy-managed RAC database that uses that server pool for a service.

They can be policy managed for a multitenant database.

Policy-managed services specified for a database allow the creation of a new server pool using dbca.

They can be administrator managed for a multitenant database.

Singleton services are not permitted for multitenant databases.

ssh user equivalence for the Oracle software owner must be configured on all cluster nodes where the Database software will be installed.

Grid Infrastructure must be installed on all cluster nodes.

The Clusterware stack must be up on all cluster nodes.

The Clusterware stack must be up on all cluster nodes where the Database software will be installed.

SSH user equivalence for the Oracle software owner must be configured on all cluster nodes.

Grid Infrastructure must be installed on all cluster nodes where the Database software will be installed.

They can be applied in-place.

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

Some Grid Infrastructure patchsets may not be intalled in a rolling fashion.

When performing rolling patches,crsctl query crs softwareversionalways displays the earliest version of the software running anywhere in the cluster.

Transparent Application Continuity is automatically enabled for a session when a database session reaches a safe place (such as a connection test or a known recoverable point) and the transactions are drained at the database.

Transparent Application Continuity is enabled when failover type=auto.

Recovery of the user database session is done safely and with no need for a DBA to have any knowledge of the application or make application code changes.

Recovery of the user database session is done safely by enabling auto recover within the user database session.

Transparent Application Continuity is enabled when failover type=All