1Z0-338 Exadata Certification Exam Guide

Finally the wait is over...!!!

In recent days, we have received lots of inquiry for 1Z0-338 certification preparation guide. Today we have launched the guide in QUESTION BANK section. (Buy Now)

1Z0-338Oracle Exadata Database Machine and Cloud Service 2017 Implementation Essentials


You will surprise to know the story behind how we have prepared this guide to make sure that whatever we are providing is the best.

Before releasing this question bank we have carried one exercise where we have given this guide to 10 readers of our website which were selected randomly based on the willingness to appear into the exam. 

We have provided this guide without any cost to prepare for the certification exam. However individual member has to bare the exam cost.

Believe us all of them cleared the exam with more than 95% score. We have carried this exercise to make sure whatever material we are providing here is 100% accurate.

Hope this guide will help you to beat the market competition and will add unique and beautiful feather in your career.

Don't hesitate to contact us any time even if you don't buy our product we will try our best to help you.

Best of luck for the certification and happy Exadating...!!!

1Z0-338 Oracle Exadata Certification Exam Dumps Download

Managing OS Statistics On Oracle Database Server

Operating system performance issues commonly involve process management, memory management, scheduling and storage management. 


Many times we get into the performance issue if we don't follow the common Oracle best practice like system parameters, improper swap allocation, hard/soft limit, not configuring hugepages wherever it requires.

If you have tuned the Oracle database instance and still need to improve performance, tune the OS, network and storage part.


Well, here we have given some of the basic statistics management which can help to boost the performance in your environment.

CPU Statistics: 

  • Doesn't exceed 95% in total
  • Check DB share on CPU 

Virtual Memory Statistics: 

  • Validate that memory usage does not increase after the system has reached a steady state after startup

Disk I/O Statistics: 

  • Current response time should be between 5 to 20 ms for a single block IO the length of the disk queues shouldn't exceed two

Network Statistics: 

  • Look at the network round-trip ping time and the number of collisions
  • Investigate it, if the network is causing large delays in response time

Reducing Disk Contention: 

  • Increase the number of disks in the storage system 
  • Separate the database and the redo log files 
  • For a large table, use partitions to reduce I/O 
  • Stripe the data either manually or by using a RAID disk-striping system 
  • Invest in cutting-edge technology, such as file caching, to avoid I/O bottlenecks 
  • Consider using ASM 

Top 10 Facts About Oracle Exadata Cloud Machine

This post is about the top facts about Oracle Exadata Cloud Machine from technical and business perspective.

                   YOU MUST SPEND MONEY TO MAKE MONEY



1. On-premise licenses cannot be transferred to ExaCM.

2. The minimum commitment to both the ExaCM and OCM is 4 years and the minimum configuration is Eighth Rack.

3. The subscription price for Oracle Database Exadata Cloud Machine X6 Eighth Rack is $40,000 per month (= $2,500 X 16) and that includes all DB options/features, Exadata Software and OEM DB Packs.

4. Standalone products such as Oracle Secure Backup and Oracle GoldenGate are not included in the ExaCM subscription. 

Only the database options (such as RAC, In-Memory, Partitioning, Active Data Guard, etc.), the database OEM packs and the Exadata storage server software are included.

5. ExaCM requires Oracle Cloud Machine to deploy Exadata Cloud Control Plane (separate subscription). OCM subscription requires similar minimum term commitment as ExaCM. 

If a customer already has an OCM, that can be leveraged to deploy Exadata Control Plane at no extra cost. One OCM Model 288 can manage 6 ExaCM Full Racks (i.e. 24 ExaCM Quarter Racks or 12 ExaCM Half Racks). 

Theoretically one OCM can support a much larger number of ExaCM full racks: about 50.

6. The 1/8th rack SKU is very similar to the on-premises 1/8th rack – i.e. minimum configuration of 16 OCPUs (cores), 240 GB RAM per database server, 144 TB raw storage (42 TB usable), 19.2TB of Flash. 

Compared to the Quarter Rack, it ships with less RAM, disk storage and flash. Those will be field installed if the customer chooses to go for the 1/8th to Quarter Rack upgrade. 

Note that this 1/8th rack enables customers to have an entry level configuration that is similar to what exists in Exadata Cloud Service.

7. Hourly Online Compute Bursting is supported with ExaCM. The commercial terms are the same as in Exadata Cloud Service – i.e. 25% premium over the Metered rate, calculated on an hourly basis. 

Customers can scale up or down, dynamically. Bursting does not kick in automatically based on load. Bursting of OCPUs needs to be configured by customers as needed. 

Once customer initiates bursting, the OCPU update is done dynamically without downtime. Customers will be billed later on the hours of bursting usage. Price: $8.401 per OCPU per hour.

8. If Cloud Control Plane is down, it doesn’t affect the availability of steady state runtime operations. However, cloud-based management (e.g. selfservice UI and REST API access) will be impacted.

9. Access: the Exadata Cloud Machine compute nodes are each configured with a Virtual Machine (VM). You have root privilege for the Exadata compute node VMs, so you can load and run additional software on the Exadata compute nodes. 

However, you do not have administrative access to the Exadata infrastructure components, including the physical compute node hardware, network switches, power distribution units (PDUs), integrated lights-out management (ILOM) interfaces, or the Exadata Storage Servers, which are all administered by Oracle.

10. Patching and backups: you can produce a list of available patches using the exadbcpatchmulti command as follows

# /var/opt/oracle/exapatch/exadbcpatchmulti -list_patches 
-sshkey=/home/opc/.ssh/id_rsa 
-oh=hostname1:/u01/app/oracle/product/12.2.0.1/dbhome_1

When you create a database deployment on Exadata Cloud Machine, you must choose from the following automatic backup configuration options:

– Remote Storage Only: uses remote NFS storage to store periodic full (RMAN level 0) backups and daily incremental backups, with a seven day cycle between full backups and an overall retention period of thirty days.

– None: no automatic backups are configured. Automatic backups cannot be configured later if you select the None option when you create a database deployment.

Oracle Exadata Cloud Administrator and Implementation Certification Exam Available

1Z0-485   Oracle Exadata Database Machine 2014 Implementation Essentials
1Z0-027   Oracle Exadata X3 and X4 Administration

1Z0-338 Oracle Exadata Database Machine and Cloud Service 2017 Implementation Essentials
1Z0-070   Oracle Exadata X5 Administration



Top Two Parameters in Oracle Exadata

You must have question in your mind that why only two parameters as there are n number of parameters related Exadata and all have it's own importance.

Well, we have choose these two because exadata performance more over dependent on these parameters and major two functionality works on these parameters.

These two parameters are:

_KCFIS_STORAGEIDX_DISABLED
CELL_OFFLOAD_PROCESSING


_KCFIS_STORAGEIDX_DISABLED

- There is not much you can do to control storage index behavior. However, the developers have built in a few hidden parameters that provide some flexibility.

- Above parameter is one of them to control the storage index functionality on exadata.

- This is undocumented and hidden parameter which is used to control the storage index function. It is highly recommended to check with the Oracle support before using it. 

- This parameter tells oracle storage if storage index need to be used while performing query execution. 

- It is used to enable and disable the usage of storage index when exadata is used for the database. 

- By default it is FLASE means storage index is enabled. If you need to disable the usage of storage index than make the value of this parameter TRUE.

Disable storage index:

SQL>alter system set _KCFIS_STORAGEIDX_DISABLED=TRUE;

Enable storage index:

SQL>alter system set _KCFIS_STORAGEIDX_DISABLED=FALSE;

You can also test this on session level.


CELL_OFFLOAD_PROCESSING

- Second parameter is related to the smart scan function of exadata. There are several parameters that apply to offloading. 

- The main one is CELL_OFFLOAD_PROCESSING, which turns offloading on and off.

- By default the value of this parameter is TRUE which means smart scan is enabled. In case if you want to test measure the performance of database using or without smart scan , you can use this parameter. 

- If it is disabled, it means that predicate filtering and storage indexes cannot be used to cut down the volume of data.

Disable smartscan:

SQL>alter system set CELL_OFFLOAD_PROCESSING=FALSE;

Enable smartscan:

SQL>alter system set CELL_OFFLOAD_PROCESSING=TRUE;

This parameter also can be tested on session level.

Why Exadata for Oracle Databases?

Many time it comes in our mind that why we should go for Exadata, what benefits we can get if we go for Exadata so here we have given some views based on the Exadata architecture, experience and features. This is the most common question in interview.



No doubt there can be many more advantages than what we have given below as we have only given high level views.

  • Exadata is high performance and high available pre-configured device.
  • It consists of servers,storage networking and software in single pre-configured box which is massively scalable, secure and redundant.
  • Multiple compression tiers are available on Exadata which can help customer to compress data as per business requirement to save storage space.
  • Implementation time is very less compare to non-Exadata systems as it's comes as pre-configured and pre-tested.
  • In case on any issue with the Exadata than we need to communicate with only single vendor which doesn't required to contact multiple vendor like non-Exadata setup so solution of issue could be done quicker.
  • Only DMA (Database Machine Administrator) would be required to manage the Exadata so it can manage with lower TCO which reduce the huge cost of manageability.
  • Exadata provides extreme performance for both DW and OLTP databases which is making it and ideal platform for database consolidation.

Top 14 Commands for Exadata Health Check

There are multiple ways, utilities or commands to monitor Exadata machine. Here we have mentioned the list of dcli commands which can help to get the list of cell alerts, resource consumption details and configuration details in shortest time.


Exadata alert

dcli -l root -g ~/cell_group "cellcli -e list metriccurrent where alertState!=\'Normal\'"

Exadata cell CPU utilization

dcli -l root -g ~/cell_group "cellcli -e list metriccurrent CL_CPUT"

Exadata cells flashdisk with status NOT present

dcli -l root -g ~/cell_group "cellcli -e list physicaldisk attributes name, id, slotnumber where disktype=\"flashdisk\" and status=\'not present\'"

Exadata cell current temperature

dcli -l root -g ~/cell_group 'cellcli -e list cell detail' | egrep temperature 

Exadata alert history

dcli -l root -g ~/cell_group "cellcli -e list metrichistory where alertState!=\'Normal\'" 

Exadata cells battery replacement checks

dcli -l root -g ~/cell_group '/opt/MegaRAID/MegaCli/MegaCli64 -adpbbucmd -aALL' |grep replaced

Exadata cells harddisk with status NOT present

dcli -l root -g ~/cell_group "cellcli -e list physicaldisk attributes name, id, slotnumber where disktype=\"harddisk\" and status=\'not present\'" 

Exadata cells services checks

dcli -l root -g ~/cell_group 'cellcli -e list cell detail' | egrep '(cellsrvStatus)|(msStatus)|(rsStatus)'

Exadata cells memory checks

dcli -l root -g ~/cell_group --vmstat="-a 3 2"

Exadata physical memory checks

dcli -g ~/all_group -l root "cat /proc/meminfo | egrep '^MemTotal:|^MemFree:|^Cached:

Exadata physical disk checks

dcli -g ~/all_group -l root /opt/MegaRAID/MegaCli/MegaCli64 AdpAllInfo -aALL | grep "Device Present" -A 8

Exadata cell fan status

dcli -l root -g ~/cell_group 'cellcli -e list cell detail' | egrep fan 

Exadata storage cell model detail

dcli -l root -g ~/cell_group 'cellcli -e list cell detail' | egrep makeModel -- For cell

dcli -l root -g ~/dbs_group 'dmidecode -s system-product-name'  -- For DB node

Exadata cells power status

dcli -l root -g ~/cell_group 'cellcli -e list cell detail' | egrep power


You can follow our Oracle Exadata Exam Certification Materials  to achieve the maximum success in your Oracle Exadata Certification Exam.



Top 7 Database Views To Monitor Exadata

There are multiple ways to monitor the Exadata. Below 7 views will help to monitor Exadata in terms of history and current statistic of Exadata.


V$CELL—provides information about cell IP addresses mentioned in the cellip.ora file


CELL_PATH - IP addresses of the cell.
CELL_HASHVAL - A numeric hash value for the cell.

V$CELL_STATE—provides information about all the cells accessible from the database client


CELL_NAME - IP addresses of the cell.
STATISTICS_TYPE - statistics type, such as thread_stats.
OBJECT_NAME - key for a specific statistics type, such as the thread ID if STATISTICS_TYPE is thread_stats.
STATISTICS_VALUE - statistic values in an XML document with attribute and value pairs.


V$CELL_THREAD_HISTORY—contains samples of threads in the cell collected by the cell server


CELL_NAME - IP addresses of the cell.
SNAPSHOT_ID - ID of the snapshot(NUMBER).
SNAPSHOT_TIME - date and time of the snapshot.
THREAD_ID - thread ID (NUMBER).
JOB_TYPE - job that the thread was running when the snapshot was taken.
WAIT_STATE - A unique state that identifies the location of the wait, if any exists.
WAIT_OBJECT_NAME - Object being waited on, if any exists. For example, the mutex name.
SQL_ID - The identifier of the SQL command that the client was processing for the job that is running.
DATABASE_ID - ID of the database (NUMBER).
INSTANCE_ID - ID of the instance (NUMBER).
SESSION_ID - ID of the session (NUMBER).
SESSION_SERIAL_NUM - session serial number (NUMBER).


V$CELL_REQUEST_TOTALS—contains historical samples of requests run by the cell


CELL_NAME - IP addresses of the cell.
SNAPSHOT_ID -ID of the snapshot(NUMBER).
SNAPSHOT_TIME - date and time of the snapshot.
STATISTICS_NAME - name of the statistic.
STATISTICS_VALUE - value of the statistic.

V$SYSSTAT - This is view what we often use for monitoring database and be able to use monitoring Exadata also.

V$SQL family of views contain columns that define the volume of data that may be saved by offloading (IO_CELL_OFFLOAD_ELIGIBLE_BYTES) and the volume of data that was actually returned by the storage servers (IO_INTERCONNECT_BYTES, IO_CELL_OFFLOAD_RETURNED_BYTES).

V$CELL_OFL_THREAD_HISTORY 


This interesting view records a ten-minute history of what cellsrv threads were doing, conceptually something like ASH for storage cells.