Oracle 1z0-485 Dumps

database size, full/incremental cycle, RPO (Recovery Point Objective), and RTO (Recovery Time Objective)

database size, retention period, RPO (Recovery Point Objective), and compression

database size, full/incremental cycle, compression, and retention period

database size, compression, and backup window

full/incremental cycle, retention period, and ZFS Backup Appliance model

Transformations can be applied directly on the file data using SQL or PL/SQLconstructions.

External tables allow transparent parallelization inside the database.

Parallelizing loads with external tables enables more efficient space management.

External tables can take advantage of storage indexes to speed up data loads.

Instance caging is the right approach to make sure that database instances are not stealing memory from each other.

The CPU Resource Manager and IORM need to be enabled to make instance caging to work as expected.

Database instances need to be restarted to make changes to cpu_count effective.

For a system with 16 threads, the sum of cpu_count for all databases should notbe higher than 32 to prevent oversubscribing

The init.org parameter resource_manager_plan should be set.

Backing up database servers and storage cells is not recommended before performing plannedmaintenance.

Database server updates can be rolled back using the the “yum downgrade"procedure.

Bundle patches do not require testing before being installed on a production system.

It is recommended that Exadata systems with Data Guard configured use the"Standby First" patching approach.

Patching should never be interrupted due to a connection drop. It is therefore recommended that you use VNC or the screen utility.

Before patching cells in a rolling manner, you must check asmdeactivationoutcome amModestatus and make sure that cells on all disks are online and that disks can be deactivated.

High redundancy provides more usable storage.

Normal redundancy provides more usable storage.

High redundancy gives you better I/O performance.

High redundancy provides High Availability (HA) during disk failure and rolling Storage Server patching

Normal redundancy provides HA during rolling Storage Server patching.

Remove the doors of the 1/8th rack.

Add the new servers.

Cable the Database Servers in the rack.

Cable the Exadata Storage Servers in the rack.

Close the rack.

Activate all cores by using a software command.

Activate allhard drives and flash drives.

Create the grid disks.

Expand the Oracle ASM diskgroups.

Review the new configuration.

Remove the doors of the 1/8th rack.

Add an additional Sun Datacenter InfiniBand Switch.

Add the new servers.

Cable the Database Serversin the rack.

Cable the Exadata Storage Servers in the rack.

Close the rack.

Configure the new hardware.

Activate all cores by using a software command.

Activate all hard drives and flash drives.

Based on the priority of the user

Immediately

Based on the resource group of the user

Based on the intradatabase resource plan

adding a High Capacity Storage expansion rack

expanding the Exadata rack from a Half Rack to a Full Rack

moving underutilized grid disks fromthe RECO diskgroup to DATA

adding a ZFS storage appliance

adding a High Performance Storage expansion rack

COMPRESS

COMPRESS BASIC

COMPRESS FOR OLTP

COMPRESS FOR QUERY

COMPRESS FOR ARCHIVE

The Oracle Database patchset software (for example, 11.2.0.3) requires the Exadata-specific version.

Rolling patching is faster than non-rolling patching, but database down time is longer.

The Oracle Database software on Exadata is updated using standard OPatch and the Oracle Universal Installer.

Running Exadata with different storage server software versions is supported, but should be minimized to rolling patching scenarios.

The database server operating system software (other than kernel and OFED) may be installed or updated from non-Exadata sources

Storage server updates require access to an Unbreakable Linux Network (ULN) based repository.