Showing posts with label 1Z0-027 dumps. Show all posts
Showing posts with label 1Z0-027 dumps. Show all posts

Capacity On Demand In Exadata Database Machine

Oracle has introduced capacity on demand on Exadata Database Machine so let's understand what is capacity on demand?

General Definition of COD:

Capacity on demand (COD) is a purchasing option that allows companies to receive equipment with more computer processing, storage, or other capacity than the company needs at the time of purchase, and have that extra capacity remain unused and unpaid for until the company actually requires it.

The number of active cores can be increased when additional capacity required is called capacity on demand.

Additional cores can be increased in 2-cores increment in X4-2 and X5-2 where as in X4-8 it can be increased in 8-cores increment.

Advantage:

Let's take an Example of database machine. When customer buy Exadata 1/8th Rack, only half of the cores would be enabled and half of them would be disabled so when customer's business expands and they required more computing power than they don't required to look around to increase it as vendor has already provided additional capacity which can be enabled at any time so in this case customer do not required to pass from purchasing procedure or any other hazardous which are time consuming. 

Simply they can enable it themselves whenever required.

Comparison between Exadata X4-2 and X5-2

Obliviously ED X5 would be faster and flexible compare to earlier version of ED. Here we have given comparison between X5 and X4 full configuration ED rack based on datasheet provided by Oracle.



Now from X5-2 Oracle introduced Oracle Virtual Machine to do the virtualization on ED machine, if there is any requirement of hard limits on CPUs and memory or required independent OS/Admin than we can use this virtualization feature.

There is no licence cost for OVM , it's free of cost with ED X5-2.

From ED X5-2 High performance disk has been replaced with Extream Flash (EF).

Exadata Certification Sample Questions & Answers (1Z0-536)

I have given some sample questions for Exadata Certification. I hope it will help you to prepare for certification. 


When do you specify the type of interleaving for a grid disk?


A. When you create the cell disk

B. When you create the grid disk
C. Through ASM
D. When you create a tablespace
Answer: B

Why would you reduce the default disk_repair_time parameter?


A. To extend the availability of your ASM disk groups.

B. To reduce the need for high redundancy
C. To reduce the amount of data collected for a fast resynch
D. To increase performance of anExadata Storage Server.
Answer: C


What benefit is provided by column filtering?


A. The Exadata Storage Server can select rows based on column values listed in a SQL predicate

B. Storage indexes are built on columns for use in filtering
C. Only necessary columns are returned to the database server
D. Column filtering is a marketing term, not a real benefit
Answer: C

Which types of data are most likely to be cached In the Exadata SmartFlash Cache?


A. Results of random reads.

B. Results of table scans.
C. Write to a mirror
D. Redo data
E. All data is cached In the Flash Cache
Answer: A

What does the role attribute of a DB plan Indicate?


A. The role specified for the category

B. The role specified for the user
C. The role specified In a Data Guard environment
D. The role specified for the application
Answer: A


Your customer has designated a number of database objects to be kept persistently in the Exadata Smart Flash Cache. What happens if the total size of these objects is greater than 80% of the size of the available Exadata Smart Flash Cache?

A. Nothing

B. Exadata Smart Flash Cache expands the allocation to hold the objects.
C. Not all objects will be stored in Exadata Smart Flash Cache.
D. Overall performance is increased as more objects fit into Exadata Smart Flash Cache.
Answer: C

Which three attributes are likely to result in data being cached in the Exadata Smart Flash Cache?


A. CELL_FLASH_CACHE attribute on the data object

B. CACHE hint In the SQL statement
C. Data from a table scan
D. Small data less than 128 KBs
E. Control file I/Os
Answer: A,C,E

How many IP addresses you need to assign for each Exadata storage cell?

Exadata Installation Activities


Implementation of Exadata done by Oracle ACS team so many time we are curious to know that what exactly they are doing so here we have listed down the list of activities which can be done by Oracle in various phases.



1.  Configuration worksheet
2.  Pre-delivery Survey

(ACS Team Activity)

3.  Generic Config Files based on Configuration Worksheet
4.  Run checkip.sh

(Oracle H/W Team Activity)

5.  Power on and validate all the components
6.  Configure KVM
7.  Configure Infiniband Swithces
8.  Configure Cisco Switch
9.  Configure IP to PDUs
10. Storage Cell validation
11. Compute Node validation

(ACS Team Activity)



12. Transfer configuration files from USB to DB node

13. Execute firstboot and applyconfig.sh
14. Stage Oracle Software on Node 1
15. Run OneCommand

                                           ASR Installation

Location of Log files in Exadata

On the cell nodes
============

1. Cell alert.log file
/opt/oracle/cell/log/diag/asm/cell/{node name}/trace/alert.logorif the CELLTRACE parameter is set just do cd $CELLTRACE

2. MS logfile
/opt/oracle/cell/log/diag/asm/cell/{node name}/trace/ms-odl.log.
orif the CELLTRACE parameter is set just do cd $CELLTRACE

3. OS watcher output data
/opt/oracle.oswatcher/osw/archive/

To get OS watcher data of specific date :

#cd /opt/oracle.oswatcher/osw/archive
#find . -name '*12.01.13*' -print -exec zip /tmp/osw_`hostname`.zip {} ;
where 12- year 01- Month 13-day

4. Os message logfile
/var/log/messages

5. VM Core files
/var/log/oracle/crashfiles
More details can be found in the following note:
Where / How to find OS crashcore file in Exadata Systems [Linux] (Doc ID 1389225.1)

6. SunDiag output files.
/tmp/sundiag_.tar.bz2

7. Cell patching issues related logfiles:
/var/log/cellos
The major logfile of patch application output you will find in the db node from where you are patching in the location /tmp/<cell version>/patchmgr.stdout and patchmgr.err

8. Disk controller firmware logs:
/opt/MegaRAID/MegaCli/Megacli64 -fwtermlog -dsply -a0

================

1. Database alert.log
$ORACLE_BASE/diag/rdbms/{DBNAME}/{sid}/trace/alert_{sid}.log
Ex: /u01/app/oracle/diag/rdbms/dbfs/DBFS2/trace/alert_DBFS2.log

2. ASM alert.log
$ORACLE_BASE/diag/asm/+asm/+ASM{instance number}/trace/ alert_+ASM {instance number}.log
Ex: /u01/app/oracle/diag/asm/+asm/+ASM2/trace/alert_+ASM2.log

3. Clusterware CRS alert.log
$GRID_HOME/log/{node name}/alert{node name}.log
Ex: /u01/app/11.2.0/grid/log/dmorldb02/alertdmorldb02.log

4. Diskmon logfiles
$GRID_HOME/log/{node name}/diskmon/diskmon.lo*
Ex: /u01/app/11.2.0/grid/log/dmorldb02/diskmon/diskmon.log

5. OS Watcher output files
/opt/oracle.oswatcher/osw/archive/

To get OS watcher data of specific date :

#cd /opt/oracle.oswatcher/osw/archive
#find . -name '*12.01.13*' -print -exec zip /tmp/osw_`hostname`.zip {} ;
where 12- year 01- Month 13-day

6. Os message logfile
/var/log/messages

7. VM Core files for Linux

/u01/crashfiles

More details can be found in the following note:Where / How to find OS crashcore file in Exadata Systems [Linux] (Doc ID 1389225.1)

8. Disk controller firmware logs:
/opt/MegaRAID/MegaCli/Megacli64 -fwtermlog -dsply -a0


What are the Exadata Installation Activities ?

ASR Installation and Registration procedure with Oracle

Plateforms:

RHEL 3 or latter x86

SUSE Linux 9 or latter x86
OEL 4 or latter x86

Software Requirement (08/10/2013) :



  1. Oracle Automated Service Manager (OSAM) Package (Patch Number p17270592_150_Linux-x86-64.zip)
  2. Oracle Automated Service Request (ASR) Package (Patch Number p17199302_45_Linux-x86-64.zip)
  3. Service Tools Bundle (STB) (Patch Number p12757884_10000_Generic.zip)
Here we have taken rpm and patch for testing purpose, it's always best practice to use latest RPMs and patch.

All the installation must be done by super User

  1. Install STB on ASR Manager Server
          #rpm -i sun-hardware-reg-1.0.0-1.i386.rpm
          #rpm -i sun-servicetag-1.1.5-1.i386.rpm

   2. Verify created service tag execute below command


         #/opt/sun/servicetag/bin/stclient -x


  3. Install OSAM on ASR Manager Server


        #rpm -i SUNWsasm-1.5.0-112.rpm


  4. Install ASR Package on ASR Manager Server


       #rpm -ivh SUNWswasr-4.5-20130703104534.rpm


  5. Add asr path in .bash_profile file:


      PATH=$PATH:/opt/SUNWswasr/bin/asr

      export PATH

Register ASR Manager :

OEM11g / OMS Auto Start and Stop Script for Linux

After installation OEM 11g mostly we required is to start the OEM services even after server reboot so here you will see how to make a OEM start-up script and add into the OS start-up sequence.

This is purely to avoid manual operation of OEM start-up if in any case we reboot the server.


1. Create dbora (service name) file as below: 


 vi /etc/init.d/dbora



#Run-level Startup script for the Oracle Instance and Listener

#
# chkconfig: 345 91 19
# description: Startup/Shutdown Oracle listener and instance


ORACLE_HOME="/oem/oracle/app/oracle/product/11.2.0/dbhome_1/"

ORACLE_OWNR="oracle"
OMS_ORACLE_HOME="/oem/Middleware/oms11g/"
OEM_AGENT_HOME="/oem/Middleware/agent11g/"


# if the executables do not exist -- display error


Power Off Sequence for Exadata Stack


Poweroff Database Servers

For single server power off /Restart

1. First stop the oracle cluster with below command

#$GRID_HOME/grid/bin/crsctl stop cluster

2. If it fails to stop the cluster then use -f option to stop it forcefully.
Shutdown the server with below command

#shutdown -h -y now

To restart the server execute below command

#shutdown -r -y now      or      #reboot

3. Remove power cable from the server

For multiple servers poweroff/restart with dcli utility

1. First stop the oracle cluster with below command

#$GRID_HOME/grid/bin/crsctl stop cluster -all

2. Shutdown all the servers with dcli utility

#dcli -g dbs_group -l root shutdown -h -y now

---dbs_group is the file which contains the list of all the exadata servers.

To restart the server execute below command

#dcli -g dbs_group -l root shutdown -r -y now    or  #dcli -g dbs_group -l root reboot

----dbs_group is the file which contains the list of all the exadata servers.

3. Remove power cables from the servers

Poweroff Storage Servers

Reat the same procedure of server to power off the exadata storage servers except to stopping the crsctl.

Note: We have to use cell_group file instead of dbs_group file to shutdown the storage servers.

Poweroff Network Equipments

We can directly remove power cables from the network switches as network equipments don't have power switches.

How to find serial number of Exadata Server/Storage

Execute below command on operating system to find the serial number of DB node and Storage cell.

# ipmitool sunoem cli "show /SP system_identifier"



Example:


[root@db01 ~]#  ipmitool sunoem cli "show /SP system_identifier"

Connected. Use ^D to exit.
-> show /SP system_identifier

  /SP

    Properties:
        system_identifier = Exadata Database Machine X3-2 AK00097035


-> Session closed

Disconnected


You can follow our Exadata Certification Question Bank to achieve maximum success in your Exadata certification exam.

User Management in Exadata

User Management

#pam_tally2 -- Check the failed user login

#pam_tally2 -r -u username  ---Reset user user

######Check user pwd policy

#chage -l username

Cell Storage Processes

There are three processes will be running on the cell stoarge servers.

cellsrv - Cell Server

It is mutlithreaded process. The primary storage software components. Responsible for disk I/O with the use of iDB protocol.It communicates with Oracle Database to serve simple block requests like database buffer cache reads and Sart Scan requests like tablespaces with projections and filters. CELLSRV also implements I/ORM and collect statistics relating to its operation

MS - Management Server

This is the intermediater between command line interface and cell storage. It provide the interface of storage for configuration and administration purpose. It works with cellcli.It is also responsible to send alerts and collect statistics.

RS - Restart Server

Restart service will monitor the cellsrv and MS processes. It restarts them if necessary.

Exadata Operating System

Database Node:

Exadata DB node comes with 4 HDD (Hard Disk) with two OS. Two HDD Linux Configured and two HDD Solaris configured.

After Exadata comes to the floor, customer has to decide that which OS they will be required , accordingly Oracle ACS guy will configure single OS either Linux or Solaris on all four HDD with RAID 5 configuration.

Note: From X2-5, Solaris is no more available for Exadata machine.

Cell Storage:

Cell storage will be Linux configured. There is no second option for the storage cell.

Cellcli - Drop

CellCLI> drop cell --->> To reset the cell to its factory settings, removes the cell related properties of the server; it does not actually remove the physical server. 

CellCLI> drop cell force 
CellCLI> drop celldisk CD_01_cell05 
CellCLI> drop celldisk CD_00_cell09 force 
CellCLI> drop celldisk harddisk 
CellCLI> drop celldisk flashdisk 
CellCLI> drop celldisk all
CellCLI> drop celldisk all flashdisk force 
CellCLI> drop griddisk DBFS_DG_CD_02_cel14 
CellCLI> drop griddisk RECO_CD_11_cell01 force 
CellCLI> drop griddisk prefix=DBFS 
CellCLI> drop griddisk flashdisk 
CellCLI> drop griddisk harddisk 
CellCLI> drop griddisk all 
CellCLI> drop griddisk all prefix=temp_dg 
CellCLI> drop flashcache 
CellCLI> drop quarantine 
CellCLI> drop threshold DB_IO_RQ_SM_SEC.PRODB 
CellCLI> drop alerthistory

Cellcli - List

CellCLI> help list 


Enter HELP LIST <object_type> for specific help syntax. 

<object_type>: {ACTIVEREQUEST | ALERTDEFINITION | ALERTHISTORY | CELL | CELLDISK | FLASHCACHE | FLASHCACHECONTENT | GRIDDISK | IBPORT | IORMPLAN | KEY | LUN | METRICCURRENT | METRICDEFINITION | METRICHISTORY | PHYSICALDISK | QUARANTINE | THRESHOLD } 


CellCLI> list cell - Will display Oracle Exadata Storage Servers/Cells information 


CellCLI> list cell detail 
CellCLI> list cell attributes all 
CellCLI> list cell attributes rsStatus 
CellCLI> list physicaldisk - Will display physical disks information 
CellCLI> list physicaldisk detail 
CellCLI> list physicaldisk 34:5 
CellCLI> list physicaldisk 34:11 detail 
CellCLI> list physicaldisk attributes all 
CellCLI> list physicaldisk attributes name, id, slotnumber 

CellCLI> list physicaldisk attributes name, disktype, makemodel, physicalrpm, physicalport, status 

CellCLI> list physicaldisk attributes name, disktype, errCmdTimeoutCount, errHardReadCount, errHardWriteCount 

CellCLI> list physicaldisk where diskType='Flashdisk' 

CellCLI> list physicaldisk attributes name, id, slotnumber where disktype="flashdisk" and status != "not present" 

CellCLI> list physicaldisk attributes name, physicalInterface, physicalInsertTime where disktype = 'Harddisk'

CellCLI> list physicaldisk where diskType=flashdisk and status='poor performance' detail 

CellCLI> list lun  
CellCLI> list lun detail 
CellCLI> list lun 0_8 detail 
CellCLI> list lun attributes all 
CellCLI> list lun attributes name, cellDisk, raidLevel, status 
CellCLI> list lun where disktype=flashdisk 
CellCLI> list celldisk - Will display cell disks information 
CellCLI> list celldisk detail 
CellCLI> list celldisk FD_01_cell07 
CellCLI> list celldisk FD_01_cell13 detail 
CellCLI> list celldisk attributes all 
CellCLI> list celldisk attributes name, devicePartition 
CellCLI> list celldisk attributes name, devicePartition where size>20G
CellCLI> list celldisk attributes name,interleaving where disktype=harddisk 
CellCLI> list griddisk - Will display grid disks information 
CellCLI> list griddisk detail
CellCLI> list griddisk DG_01_cell03 detail 
CellCLI> list griddisk attributes all 
CellCLI> list griddisk attributes name, size
CellCLI> list griddisk attributes name, cellDisk, diskType 
CellCLI> list griddisk attributes name, ASMDeactivationOutcome, ASMModeStatus 

CellCLI> list griddisk attributes name,cellDisk,status where size=476.546875G
CellCLI> list griddisk attributes name where asmdeactivationoutcome != 'Yes' 
CellCLI> list flashcache - Will display flash cache information 
CellCLI> list flashcache detail 
CellCLI> list flashcache attributes all 
CellCLI> list flashcache attributes degradedCelldisks 
CellCLI> help list FLASHCACHECONTENT 

Usage: LIST FLASHCACHECONTENT [<filters>] [<attribute_list>] [DETAIL] 
Purpose: Displays specified attributes for flash cache entries. 
Arguments: 
<filters>: An expression which determines the entries to be displayed. 
<attribute_list>: The attributes that are to be displayed. ATTRIBUTES {ALL | attr1 [, attr2]... } 
[DETAIL]: Formats the display as an attribute on each line, with an attribute descriptor preceding each value. 


CellCLI> list flashcachecontent - Will display flash cache content information

CellCLI> list flashcachecontent detail 
CellCLI> list flashcachecontent where objectnumber=161441 detail

CellCLI> list flashcachecontent where dbUniqueName like 'EX.?.?' and hitcount > 100 attributes dbUniqueName, objectNumber, cachedKeepSize, cachedSize

CellCLI> list flashcachecontent where dbUniqueName like 'EX.?.?' and objectNumber like '.*007'

CellCLI> list flashcachecontent where dbUniqueName like '.*X.?.?' and objectNumber like '.*456' detail 

CellCLI> list metriccurrent - Will display metrics information 
CellCLI> list metriccurrent gd_io_rq_w_sm 
CellCLI> list metriccurrent n_nic_rcv_sec detail 
CellCLI> list metriccurrent attributes name,metricObjectName,metricType, metricValue,objectType where alertState != 'normal' 

CellCLI> list metriccurrent attributes name,metricObjectName,metricType, metricValue,alertState where objectType = 'HOST_INTERCONNECT' 

CellCLI> list metriccurrent attributes all where objectType = 'CELL'
CellCLI> list metriccurrent attributes all where objectType = 'GRIDDISK' - 
> and metricObjectName = 'DATA_CD_09_cell01' and metricValue > 0 

CellCLI> list metricdefinition 
CellCLI> list metricdefinition cl_cput detail 
CellCLI> list metricdefinition attributes all where objecttype='CELL' 
CellCLI> list metrichistory - Will display metric's history
CellCLI> list metrichistory cl_cput 
CellCLI> list metrichistory where objectType = 'CELL' 
CellCLI> list metrichistory where objectType = 'CELL' and name = 'CL_TEMP'

CellCLI> list metrichistory cl_cput where collectiontime > '*2011-10-15T22:56:04-04:00*' 

CellCLI> list alertdefinition detail - Will display alert's definitions 
CellCLI> list alertdefinition attributes all where alertSource!='Metric'


CellCLI> list alerthistory - Will display alert's history

CellCLI> list alerthistory detail
CellCLI> list alerthistory where notificationState like '[023]' and severity like '[warning|critical]' and examinedBy = NULL;


CellCLI> list activerequest 

CellCLI> list ibport - Will display InfiniBand configuration details
CellCLI> list ibport detail 
CellCLI> list iormplan - Will display IORM plan details 
CellCLI> list key
CellCLI> list quarantine 
CellCLI> list threshold - Will display threshold details

Cellcli - Describe

It Will display all attributes

CellCLI> describe cell
CellCLI> describe physicaldisk
CellCLI> describe lun
CellCLI> describe celldisk
CellCLI> describe griddisk
CellCLI> describe flashcache
CellCLI> describe flashcachecontent
CellCLI> describe metriccurrent
CellCLI> describe metricdefinition
CellCLI> describe metrichistory 

Cellcli - Help

CellCLI> help
HELP [topic]
    Available Topics:
        ALTER
        ALTER ALERTHISTORY
        ALTER CELL
        ALTER CELLDISK
        ALTER GRIDDISK
        ALTER IBPORT
        ALTER IORMPLAN
        ALTER LUN
        ALTER PHYSICALDISK
        ALTER QUARANTINE
        ALTER THRESHOLD
        ASSIGN KEY
        CALIBRATE
        CREATE
        CREATE CELL
        CREATE CELLDISK
        CREATE FLASHCACHE
        CREATE GRIDDISK
        CREATE KEY
        CREATE QUARANTINE
        CREATE THRESHOLD
        DESCRIBE
        DROP
        DROP ALERTHISTORY
        DROP CELL
        DROP CELLDISK
        DROP FLASHCACHE
        DROP GRIDDISK
        DROP QUARANTINE
        DROP THRESHOLD
        EXPORT CELLDISK
        IMPORT CELLDISK
        LIST
        LIST ACTIVEREQUEST
        LIST ALERTDEFINITION
        LIST ALERTHISTORY
        LIST CELL
        LIST CELLDISK
        LIST FLASHCACHE
        LIST FLASHCACHECONTENT
        LIST GRIDDISK
        LIST IBPORT
        LIST IORMPLAN
        LIST KEY
        LIST LUN
        LIST METRICCURRENT
        LIST METRICDEFINITION
        LIST METRICHISTORY
        LIST PHYSICALDISK
        LIST QUARANTINE
        LIST THRESHOLD
        SET
        SPOOL
        START

What is cellcli ?

What is cellcli utility?

Full form – Cell Command Line Interface

Cellcli used to manage the cell through the cell command line utility.

To invoke the cellcli utility, login to the cell storage through root, celladmin or cellmonitor and type cellcli.

Storage Indexes


-Storage Indexes provide the third level of optimization for Smart Scans. 
-Storage Indexes are in-memory structures on the storage cells that maintain a maximum and minimum value for each 1MB disk storage unit, for up to eight columns of a table. -Storage Indexes are a little different than most Smart Scan optimizations. 
-The goal of Storage Indexes is not to reduce the amount of data being transferred back to the database tier. In fact, whether they are used on a given query or not, the amount of data returned to the database tier remains constant. 
-On the contrary, Storage Indexes are designed to eliminate time spent reading data from disk on the storage servers themselves. Think of this feature as a  pre-filter.
-Since Smart Scans pass the query predicates to the storage servers, and Storage Indexes contain a map of values in each 1MB storage region, any region that can’t possibly contain a matching row can be eliminated without ever being read. 
-You can also think of Storage Indexes as an alternate partitioning mechanism. Disk I/O is eliminated in analogous fashion to partition elimination. If a partition can’t contain any records of interest, the partition’s blocks will not be read. 
-Similarly, if a storage region cannot contain any records of interest, that storage region need not be read. Storage Indexes cannot be used in all cases, and there is little that can be done to affect when or how they are used. But in the right situations, the results from this optimization technique can be astounding.

Exadata Offload Processing

Exadata offloading is to offload processing to the storage tier. Offloading and Smart Scan are two terms that are used somewhat interchangeably. Offloading is a more generic term that means doing work at the storage tier that would otherwise have to be done on the database tier (this can include work that is not related to executing queries such as optimization of incremental backups). Smart Scans on the other hand are the access mechanism used to offload query processing tasks. For example, storage servers can apply predicate filters at the storage layer, instead of shipping every possible block back to the database server(s). Another thing that happens with Smart Scans is that the volume of data returned can be further reduced by column projection (i.e. if you only select 1 column from a 100 column table, there is no need to return the other 99 columns). Offloading is geared to long running queries that access a large amount of data. Offloading only works if Oracle decides to use its direct path read mechanism.

There three primary goals to use the smart scan/Offloading.

• Reduce the volume of data transferred from disk systems to the database servers.
• Reduce CPU usage on database servers.
• Reduce disk access times at the storage layer.


Reducing the volume was the main focus and primary goal. The majority of the optimizations introduced by Offloading contribute to this goal. Reducing CPU load is important as well, but is not the primary benefit provided by Exadata and therefore takes a back seat to reducing the volume of data transferred. (As you’ll see, however, decompression is a notable exception to that generalization, as it is performed on the storage servers.) Several optimizations to reduce disk access time were also introduced, and while some of the results can be quite stunning, we don’t consider them to be the bread-and-butter optimizations of Exadata.

Exadata Components

Hardware Components

-Database Node (Database Server)
-Cell Storage (Storage Server)
-Infiniband switch
-Cisco network switch
-KVM
-PDU
-Rack
-Flash Cache


Software Components

-Storage Software
-Operating System (Linux/Solaris)
-Oracle Database Software