DB2BP Warehouse HPU Recovery 1111 (2)

8/10/2019 DB2BP Warehouse HPU Recovery 1111 (2)

1/32

IBMSmartAnalyticsSystem

Best

Practices

Using

IBM

InfoSphere

Optim

High

Performance

Unload

as

part

of

a

RecoveryStrategy

GarrettFitzsimons

IBMDataWarehouseBestPracticesSpecialist

KonradEmanowicz

IBMDB2DataWarehouseQASpecialist

RichardLubell

IBM

Information

Development

Specialist

Issued

November

2011


2/32

ExecutiveSummary..................................................................................................................... 3

Introduction.................................................................................................................................. 4

IncorporatingHPUintoyourrecoverystrategy..................................................................... 5

When

to

use

HPU.............................................................................................................

5

HPUandbackupimages................................................................................................ 6

UsingHPU.................................................................................................................................... 8

UsingHPUwithoutputfilesornamedpipes............................................................. 8

ControllingparallelismwiththeMAXSELECTSparameter.....................................8

Controllingprocessorresourceswiththenbcpuconfigurationfileparameter......9

Howthedb2hpucommandworks......................................................................................... 10

UsingHPUcontrolfiles................................................................................................ 10

Creatingacontrolfile.................................................................................................... 12

Issuingthedb2hpucommand..................................................................................... 13

InstallingandconfiguringHPUinanIBMSmartAnalyticsSystem.................................14

InstallingHPUinanIBMSmartAnalyticsSystem..................................................14

ConfiguringHPUinanIBMSmartAnalyticsSystem.............................................14

HPUdiskrequirements................................................................................................. 16

Conclusion.................................................................................................................................. 17

Appendix

A.

Configuration

of

test

system

used...................................................................

18

AppendixB.Recoveryscenariocontrolfileexamples.........................................................20

RecoverdroppedpartitionedtablesusingbackupimagesonTSM.......................20

Recoverexistingpartitionedtablesusingbackupimagesondisk.........................22

RecoverdroppedpartitionedtableusingbackupimagesonTSMandnamedpipes................................................................................................................................. 23

RecoverdroppedtablespaceusingbackupimagesonTSM..................................25

RecoverdatausingnonproductionsystemandbackupimagesonTSM............26

Appendix

C.

LOB

and

XML

objects

........................................................................................

28

Furtherreading........................................................................................................................... 29

Contributors................................................................................................................................ 29

Notices......................................................................................................................................... 30

Trademarks..................................................................................................................... 31


3/32

HPUaspartofarecoverystrategyinanIBMSmartAnalyticsSystem

Executive

Summary

Thispaperistargetedatthoseinvolvedinplanning,configuring,designing,implementing,or

administeringadatawarehousebasedonDB2DatabaseforLinux,UNIX,andWindowssoftware.

The

examples

in

this

paper

apply

generally

but

are

focused

on

the

IBM

Smart

Analytics

System

based

on

SystemxandPowerSystemsservers.

IBMInfoSphereOptimHighPerformanceUnload(HPU)forDB2forLinux,UNIX,andWindowsV4.2is

ahighspeedtoolforunloading,extracting,andrepartitioningdatainDB2forLinux,UNIX,and

Windowsdatabases.HPUisdesignedtoextractdatafromDB2incrementalanddeltabackupimagesand

fromDB2tablespacecontainers.HPUhasadditionalusesindatamigrationandrepartitioningthatwill

bedealtwithinfuturepaper.

Thefocusofadatabasebackupandrecoverystrategyshouldbetherecoveryplan.ThepaperBuildinga

Recovery

Strategy

for

an

IBM

Smart

Analytics

Systemdiscussesbestpracticerecommendationsforbackup

and

recovery

using

the

native

DB2

software

commands.

Although

not

recommended

for

full

database

recovery,HPUcanbeeffectiveinspeedilyrecoveringdiscretepiecesofdatafromtablesandtablespaces.

ThedatabaseisnotaffectedbytheHPUprocessandtablespacesdonotneedtobeplacedinanoffline

state.HPUcanthereforeofferadvantagesoverotherrecoverymethodsindataavailabilityand

processingspeed.IncorporatingHPUintoyourrecoverystrategyforscenariosinvolvingdatalossor

corruptioncanhelpachieveservicelevelobjectivesfordataavailabilityanddatarecovery.

UsingtherecommendationsinthispapercanhelpyoudevelopastrategythatusesHPUtocomplement

yourexistingrecoverystrategy.

Page:3


4/32


Introduction

ThispaperdescribesbestpracticesforincorporatingtheuseofHPUintoyourrecoverystrategyand

implementingHPUforanIBMSmartAnalyticsSystemdatawarehouse.Thepapercovershowtounload

datafrombackupimages.

Tousethispaper,youshouldhaveabasicknowledgeofHPUsoftwareaswellasDB2softwareas

implementedinanIBMSmartAnalyticsSystem.Thefurtherreadingsectioninthispapercontainslinks

toproductdocumentationandpapersreferencedthroughoutthepaper.

ThefirstsectionofthepaperdiscusseshowtoincorporateHPUintoarecoverystrategyandwhentouse

HPUtomeetyourrecoveryobjectives.

Thesecondsectioncontraststheuseofoutputfilesandnamedpipesanddiscussesintroducing

parallelism.

ThethirdsectionreviewstheHPUcommandandcontrolfileandrecommendsbestpracticesforcreating

control

files.

ThefourthsectionofthepaperdetailshowtoinstallandconfigureHPUinanIBMSmartAnalytics

System.

Theappendixesoutlinetheconfigurationofthetestsystemusedindevelopingthispaperandalso

containexamplesofusingHPUincommonrecoveryscenarios.

ThispaperbuildsonandcomplementsaseriesofbestpracticespapersthatdiscussaspectsofaDB2data

warehouse.Refertothesepapersforfurtherinformation.

Page:4


5/32


Incorporating

HPU

into

your

recovery

strategy

HPUisahighspeedstandaloneutilityforunloading,extracting,andrepartitioningdatainDB2for

Linux,UNIX,andWindowsdatabases.HPUunloadslargevolumesofdataquicklybyreadingdirectly

fromfull,incremental,anddeltabackupimagesortablespacecontainersratherthanthroughtheDB2

software

layer.

HPU

does

not

replace

other

recovery

tools

in

your

recovery

strategy,

but

can

have

significantadvantagesinrecoveringdiscretevolumesofdata.

IncorporateHPUintoyourrecoverystrategytoprovide:

Reducedrecoverytimesthroughtargeteddatarecovery

UsetheWHEREclausewhenselectingdatafrombackupimagestotargetonlythedatathatwas

lost,compromised,orcorrupted,reducingrecoverytime.

Increaseddataavailabilityandreducedresourceusageduringrecoveryscenarios

Unloaddatafromabackupimageandoptionallyprocessthisdataonanonproductionsystem,

maintaining

availability

of

the

query

workload

and

reducing

the

effect

on

the

production

system.

IntegrationwithDB2andTivoliStorageManagersoftware

QueryTSMtounloaddatafromfull,incremental,anddeltabackupimagesarchivedtoTSMby

theDB2BACKUPcommand,reducingerrorsandfacilitatingoutsiderecovery.

InstallHPUonlyonthephysicalserverswhereyouintendtorunHPUtounloaddata.

HPUwouldbeuseful,forexample,inarecoveryscenariowhereanETLapplicationchangehas

compromiseddatasuchasacustomerZIPcode.InsteadofusingtheRESTOREcommandandaffecting

dataavailability,HPUcouldbeusedtounloadthecustomer idandzip codecolumnsfroma

backup

image.

The

unloaded

data

would

then

be

loaded

into

a

temporary

table

and

the

customers

ZIP

codecorrectedbyusingasimpleUPDATEstatement.

WhentouseHPUHPUcancomplementyourexistingrecoverystrategywhere:

TheRecoveryTimeObjective(RTO)isaggressive.

HPUdoesnotneedtoconnectthroughtheDB2softwarelayerbutinsteadreadsdatadirectly

fromthebackupimage,increasingthespeedofunloadingdata.UseHPUtounloaddatafroma

backupimagetomultipleoutputfilesinparallelforoneormoretables.UsetheDB2Loadutility

tocompletetherecoveryofthedroppedtable.

Forexample,themethodofrecoveringeachdroppedtableinseparatesequentialrestore

operationsisnotcompatiblewithsomerecoverytimeobjectives(RTO).HPUcanperformdata

unloadfrommultipletablesinparallelanddoesnotneedtoperformaROLLFORWARDtoendof

logs,helpingtoensurefasterdatarecoverytimes.

Thedatabaseneedstobeavailabletoqueriesduringtherecoveryprocess.

HPUunloadsdatadirectlyfrombackupimagesinsteadofthroughthedatabaseengine.Youcan

therebyrecoverdataforatablewithouttheneedtoputatablespaceordatabaseoffline.

Page:5


6/32


HPUcanunloaddataforindividualtableorforalltables.Bydefault,HPUunloadsdataforall

tablesinthetablespaceinparallel,reducingtheeffectonqueryworkloadbyminimizing

networktraffic.Thisapproachhelpsensurethatbackupimagesarereadaminimumnumberof

times.HPUusessystemresourcesbutwillnotneedtoconnecttotheproductiondatabase.

DatacanberestoredbyusingtheLOADcommandwithanINSERTwithSELECTstatement.

Alternatively,

the

ALTER

TABLE

DETACH

and

ATTACH

command

can

be

used

to

switch

the

recovereddatapartitionwiththecorrupteddatapartition.Theseoperationsdonottakethe

systemofflineasisrequiredwhenusingtheRestorecommand.

Therecoveryprocessneedstotakeplaceawayfromtheproductionsystem.

Whendataneedstoberestoredandvalidatedoutsideoftheproductionsystem,youcanunload

datafordroppedorcorruptedtablesintoanonproductionsystem.Thisactionallowsyouto

cleanseandpreparedataforloadintotheproductionsystem.Usethisapproachtominimizethe

effectontheproductionsystem.HPUsupportsDB2softwareintegrationwithIBMTivoliStorage

Manager(TSM);usethistooltorecoverandvalidatedataonanonproductionsystem.Thistopic

isdiscussedfurtherinAppendixB.

For

example,

HPU

can

be

used

to

recover

specific

pieces

of

data

to

a

nonproduction

system.

Whenusedinthisway,HPUmustbeinstalledonthenonproductionsystemandacopyofthe

databasecatalogbackupimagemustbeaccessible.Ifonlyasinglecolumnthathasbeen

compromised,useHPUtounloadjusttheprimarykeyandthecontentsoftheaffectedcolumn.

Retainacopyofthemostrecentdatabasecatalogbackupimageondisktohelpincreaserecovery

speedwhenusingHPU.

HPUandbackupimagesSeveralfactorsrestrictthevolumeofdatathatcanbeunloadedandthenumberofbackupimagesthat

canbeaccessedinparallel,Thefactorsincludethenumberoftapedrivesavailable,theresources

assigned,andthebackupstrategychosen.

HPUdirectlyreadsbackupimagescreatedbyDB2.Thefollowingisrecommended:

Useofflinebackupimageswhereavailabletohelpensuretheintegrityandconsistencyofdata

unloaded.

Useonlinebackupimagesonlywhenyouarecertainthatnotransactionstookplaceagainstthe

objectsyouareunloadingduringthemostrecentonlinebackup.

Usetablespacebackupsinsteadoffulldatabasebackupswhenpossibletoreducethesizeofthe

backup

image

you

are

reading

and

therefore

enable

faster

data

unload

times.

Includethecaptureoftablecreatestatementsinyourbackupstrategy.Whenatableisdroppedit

needstoberecreatedbeforerecoveryviaaLOADcommand.

Useofflinebackupimagesorconsistentonlinebackupimagestohelpensuretheintegrityofthe

dataunloaded.

Page:6


7/32


Yourbackupstrategyshouldallowforthenumberoftapedrivesavailableperdatanode.Inapartitioned

databaseitisrecommendedthatyoubackuponedatabasepartitionperdatanodeinparallelacrossall

datanodes. Thisrecommendation assumesonetapedriveperdatanode.Iftwotapedrivesareavailable,

thentwodatabasepartitionsperdatanodecanbebackedupinparallel.Throughthisstrategy,a

databasebackupconsistsofmultiplebackupimageswithdifferenttimestamps.HPUcanuseapartial

timestampparametertoreferenceallofthesebackupimages.

IfnobackupimagetimestampisspecifiedthenHPUdeterminesthemostrecentfullbackuptakenand

alsoidentifiesincrementalanddeltabackupimagescreatedsincethefullbackup.HPUtemporarily

stagesdatafromthefulldatabasebackupandthenappliesanychangestothedatafoundinthe

incrementalordeltabackupimagesbeforecreatingthefinaloutputfile.Notethatadditionalstaging

spaceisrequiredwhendataisunloadedfromincrementalbackupimages.

AccesstoacopyofthedatabasecatalogisneededbyHPUtodeterminethecharacteristicsofthetables

forwhichdataisbeingunloaded.ToavoidanydatabaseconnectionswhenusingHPU,itis

recommendedthatyouretainabackupofthedatabasecatalogondiskforusewithHPU.HPUcanrefer

toadatabasethatcontainsthedatabasecatalogortoanindividualbackupimageofthedatabasecatalog

itself.

Page:7


8/32


Using

HPU

WhenusingHPUtorecoverdataconsiderthediskandserverresourcesavailableandyouruseofthese

resources.

Using

HPU

with

output

files

or

named

pipes

HPUusesastagingareatostagedatapagesreadfromthebackupimage.Dataisthenwrittentooutput

filesintheoutputarea.

Unloadingdatatooutputfilesallowsthisprocesstobeseparatedfromtheprocessofloadingdata,

allowingforvalidationorpostponementoftheloadoperation.Usingnamedpipesallowsdatatobe

unloadedfromabackupimageandloadedtothetargetdatabasetableconcurrentlyanduseslessdisk

spacetoperformtherestoreoperation.

Choose

your

recovery

method

based

on

your

resource

priority:

use

named

pipes

where

there

is

insufficientdiskspaceonthedatanodes,orunloadtooutputfileswhereprocessorusageis

limited.

Tofacilitateparallelunloadandloadoperations,createacontrolfiletounloaddataforeachdatabase

partitiontoindividualoutputfilesontheappropriatenode.ThenusetheDB2Loadutilitytoloaddatain

parallelacrossallthedatabasepartitions,avoidingunnecessarynetworktrafficbetweendatanodes

duringtherecoveryprocess.ThesyntaxoruseoftheDB2LoadutilityisnotalteredbyHPUandall

featuresandparametersoperatenormally.

When

using

the

DB2

Load

utility

to

complete

a

recovery

scenario

it

is

recommended

that

you

perform

a

backupoftherecovereddatainlinewithyourservicelevelobjectivesforbackupandrecovery.When

usingtheLOADcommanditisrecommendedthatyouusetheLOAD_ONLY_VERIFY_PARTmode. HPU

doesnotgeneratepartitionheaderdatainoutputfiles.UseLOAD_ONLY_VERIFY_PARTratherthanthe

LOAD_ONLYmodetoindicatetotheLOADutilitythatthedataisalreadypartitionedbutdoesnotcontain

apartitionheader.

ControllingparallelismwiththeMAXSELECTSparameterTheMAXSELECTSparameterdeterminesthenumberofSELECTstatementsandthereforethenumberof

tablestobeprocessedinparallelwhenunloadingdatafrombackupimages.UsingMAXSELECTSinthis

wayminimizesthenumberoftimesthebackupimageisreadbutincreasestheresourcesrequiredbythe

HPU

process.

IfavalueforMAXSELECTSisnotspecified,HPUattemptstoprocessallselectstatementintheunload

block,oralltablesinaspecifiedtablespace.

ItisrecommendedthatyouincludeaMAXSELECTSentryinthedb2hpu.cfgconfigurationfileand

associateavalueof1.ThisactionpreventsanHPUprocessfromconsumingmoreresourcesthan

intended.Thisdefaultvaluecanthenbeoverriddeninanindividualcontrolfilewhereneeded.Usethe

Page:8


9/32


MAXSELECTScontrolfileconfigurationparametertorestrictthenumberoftablestobeunloadedfrom

inparallelwhereyouwanttoreducetheresourcesconsumed.

UsetheconfigurationandcontrolfileparameterstothrottleHPUusageofprocessorresources.

Controllingprocessorresourceswiththenbcpuconfigurationfile

parameterThenbcpuconfigurationparameterspecifiesthemaximumnumberofthreadsallowedwhenunloading

data.Defaultbehavioristostartaworkunitforeachprocessorcore.Thisparameterissetinthe

db2hpu.cfgconfigurationfileandcannotbeoverriddeninthecontrolfile.

Inascenarioinvolvingadatabaseoutage,youmightwanttoallowHPUtouseallavailableprocessor

resourcesinordertounloaddataasquicklyaspossible.Inanenvironmentwherequeriesarerunning

duringrecovery,configureHPUtorestricttheresourcesconsumed,reducingtheamountofprocessor

used.

Page:9


10/32


How

the

db2hpucommand

works

TheHPUutilityusesacommandlineinterfacewithacontrolfiletoperformthedataunloadoperation.

DataunloadsfromthebackupimagetostagingfilesandthenwritestooutputfilesforusewiththeDB2

Load

utility.

Employing

a

separate

staging

directory

and

output

file

directory

is

recommended

to

separatefilesandinputandoutputoperationsduringunloadprocessing.HPUprocessesonesingle

databasepartitionpernodeinsequenceoneachdatanodeinparallel.Allthetablesinthetablespace

unloadoneachdatanodeinthefollowingformat:file.NNN___

whereNNNisdatabasepartitionandandaretheschemaandtablesnames.

Avoidcontentionwhenunloadingdatafromtapebyensuringthatthesequenceofdatabase

partitionsreferencedintheunloadblocksmirrorsthebackupsequence.

ThesetopicsarediscussedinthefollowingsectionswithdetailedexamplesinappendixB:

UsingHPUcontrolfiles

Creatingacontrolfile

Issuingthedb2hpucommand

UsingHPUcontrolfilesThestructureofthecontrolfileconsistsoftwotypesofcontrolblocks:

GlobalBlock

UnloadBlocks

GlobalBlock

TheglobalcontrolblockcontainsconfigurationdatathatiscommontoallunloadblocksintheHPU

controlfile.Thereisonlyoneglobalblockpercontrolfileandtheglobalblockmustbethefirstblockin

thecontrolfile.

Thedb2hpucommandreferencesadatabasecatalogtogatherdetailsonthetablestobeunloaded.

SpecifytheUSINGBACKUPCATALOGclausewhentheobjectsbeingrecoveredarenotavailableonthe

existingdatabasecatalogcontainedinthedatabasereferenced.Scenariosforthisactionincludewhere

objectsweredropped,thecatalogiscorruptedoryouareexecutingthedb2hpucommandonanon

productionsystemwhereDB2softwareisnotinstalled.

Thefollowingexampleillustratesthecontentofacontrolblockwherethedatabasecatalogbackupimage

forthedatabaseTPCDSistobeused.Thebackupimageforthedatabasecatalogtobeusedislocatedon

diskand thebackup image tousehasallorpartial timestamp2011033108.A semicolon isused to

terminatethestatementandtheblock.

Page:10


11/32


-- Global Block specifies disk location for the database catalog

GLOBAL USING BACKUP CATALOG TPCDS from "/work0/HPU/catalog_BACKUP"

TAKEN AT 2011033108;

;

Unload

Blocks

Theunloadblockspecifiesthetablespace,tables,andSELECTstatementforthedatatobeunloaded.

Multipleunloadblockscanbeusedinasinglecontrolfiletoperformasequenceofunloadoperations.

Scenariosforthisusageincludewhenunloadingfrommultipletablespacesorfrommultipletablespace

backupimages.

HPUattemptstoreadthebackupimageonceperunloadblock.MultipleSELECTstatementsinasingle

unloadblockareprocessedinparallelsubjecttotheMAXSELECTSparametervalue.

WhencreatingacontrolfileinanIBMSmartAnalyticsSystem:

SpecifytheUSINGBACKUPDATABASEclauseasthelastoneintheUNLOADTABLESPACE

command

when

unloading

the

whole

table

space

or

the

HPU

command

will

fail

with

incorrect

syntax.

Useaperiodafterthefilenameinthecontrolfile;thisnotationisrequiredfortheDB2Load

utilitytoloadthedatasuccessfully.

UsetheOUTFILEclauseinpreferencetotheOUTPUTclause.

Unloaddataforalltablesneeded;HPUdoesnotsupportJOINS.

Thefollowingexampleillustrateshowanunloadblockwouldbecreatedtounloaddatafromatable

spacebackupimagefromdatabasepartitions1and9inparallel:

-- Unload Block specifies backup image for partitions 1 and 9

-- A table space backup is used.

UNLOAD TABLESPACE

PART(1,9)

USING BACKUP DATABASE TPCDS TABLESPACE ("HASHTS") USE TSM ON SOURCE

HOST TAKEN AT 20110331080240;

-- Select statement specifies customer table

SELECT * FROM BCUAIX.CUSTOMER;

OUTFILE("%{source_host}:/work%{source_node}/HPU/bcuaix.customer.file.%{s

ource node}") FORMAT DEL

;

-- Select statement specifies customer_demographics table

SELECT * FROM BCUAIX.CUSTOMER_DEMOGRAPHICS;

OUTFILE("%{source_host}:/work%{source_node}/HPU/bcuaix.demographics.file

.%{source_node}") FORMAT DEL

;

Theprecedingexampleincorporatestheserecommendations:

TAKENAT

Page:11


12/32


Usethisparametertospecifyapartialbackupimagetimestamptoreferencemultiplebackup

images,includingincrementalanddeltabackupimages.

Forexample,atimestampof20110630willinstructthedb2hpucommandtolookforallbackup

imagesonJune30th2011.Wheremultiplefullbackupimagescontainthepartialtimestamp,HPU

terminatesandoutputsamessagetothatmultiplebackupimageswiththesamepartial

timestamp

were

found.

To

allow

HPU

to

determine

the

most

recent

backup

images

to

use,

omit

theTAKENATclause.

ONSOURCEHOST

UsethisparametertoinstructHPUtounloaddatainparalleltoindividualoutputfilesoneach

databasepartitioninsteadofcreatingasinglelargefileontheadministrationnode.

Thisactionincreasesparallelisminasharednothingarchitecturesinceeachoutputfileiscreated

locallyoneachdatanode.EachdatanodeinvolvedrecoversthedataforitslocalDB2database

partitionstoitslocaloutputpathwiththecorrectfilepernodespecifiedbytheOUTFILEkey.

OUTFILEwith{source_host}and{source_node}keywords

Use

the

OUTFILE(%{source_host}:/OUTPUTPATH/FILE.%{source_node}

)

keywords

to

generatetheoutputfileonthecorrectfilesystemassociatedwitheachdatabasepartition.

Eachdatabasepartitionhasaseparateoutputfilecreatedwiththedatabasepartitionnumber

appendedtothenameofthefile.

Creating

a

control

file

Followtheserecommendationswhencreatingacontrolfileforanunloadoperation:

Identifytheportionofdatathatneedstoberecovered.Thisactionspeedsuptherecoveryby

limitingtheamountofdatatobeunloadedtotheoutputpaths.

Specify

the

data

to

be

recovered

in

the

control

file

by

using

the

WHERE

clause

to

specify

the

rangeofvaluesfromcolumns,DATAPARTITIONIDtoreferenceparticulartablerange,PART

clausetoreferenceparticulardatabasepartitions.Thismethodissuitableforascenariowhere

corruptiononanindividualdatabasehasoccurred.

Referenceadatabasecatalogbackupimagethatisconsistentwiththebackupimage.For

example,ifyouareunloadingdataforadroppedtableyouneedtoreferenceadatabasecatalog

thathasthedefinitionofthatdroppedtable.

Verifythattheoutputpathsspecifiedinthecontrolfileforthestagingandoutputfileareasexist

andareaccessibletotheDB2instanceuserid.

Throttle

the

resources

used

by

HPU

using

the

nbcpu

configuration

parameter

to

reduce

the

numberofthreadscreatedtomitigatetheeffectofdb2hpuonotherworkloads.

ControltheamountofmemorytobeusedbyHPUbyusingthebufsizeparameter.

Page:12


13/32


Issuingthedb2hpucommandThedb2hpucommandisissuedasshowninthisexamplewhereiisthedb2instancenameandf

specifiesthecontrolfiletobeused:

db2hpu -i instname -f controlfile

Thecontrolfilesettingsoverridethedefaultssetintheproductconfigurationfile,db2hpu.cfg,whichis

locatedintheinstallationdirectory,typically/opt.

Ensurethatanybackup,ingest,orotheroperationsscheduledthatmightaffecttheunload

processhavebeenalteredforthedurationoftheunloadexercise.Avoidcontentionfortape

drivesandTSMresourcesbyensuringthatnootheroperationsareactiveatthetimeofrunning

HPU.

Ensurethatyoualwayshavethelatestbackupofthedatabasecatalogreflectinganychanges

availableondisk.UsinganuptodatecatalogreducestheneedforHPUtoaccessthebackup

image

via

tape.

Unloaddatafrombackupimagesbyfollowingthesamepatternthatwasusedtocreatethe

backupimages.

Page:13


14/32


Installing

and

configuring

HPU

in

an

IBM

Smart

Analytics

System

HPUishighlyscalableandcanemployallprocessorandnetworkresourcesmadeavailabletounload

data

at

high

speeds.

Assess

the

effect

on

your

test

environment

before

implementing

HPU

in

aproductionenvironment.

ConfigureyouroutputdirectoriestoallowHPUtounloaddatawithasinglecommandin

parallelacrossmultipledatabasepartitions.

Installing

HPU

in

an

IBM

Smart

Analytics

System

InstallandconfigureHPUoneachnodewhereyouintendtousetheproduct.Avoidcopyingthe

installationpackagetoeachindividualnodebylocatingitontheshared/db2homefilesystem.

There

are

no

additional

installation

requirements

outside

the

standard

product

installation

instructions.

WheninstalledinaDB2V9.7environment,HPUcanunloaddatafromaDB2v9.5backupimage.

Configuring

HPU

in

an

IBM

Smart

Analytics

System

ConfigurationofHPUconsistsofthreetasks:

Creatingandsharingasingleconfigurationfileacrossallnodes

CreatingadirectorystructureforHPUstagingandoutputfiles

Settingconfigurationfileparameters

Creatingandsharingasingleconfigurationfileacrossallnodes

Minimizeadministrationofconfigurationfilesbycreatingasharedconfigurationfileonthe

administrationnodeandmodifyingthelocalconfigurationfileoneachnodetoreferenceit.Tocreatea

singleconfigurationfilethatissharedacrossallnodesonwhichHPUisinstalled:

1. Makeacopyofthedefaultconfigurationfile,customizeitasrequiredandsaveitonafile

systemthatisaccessibleacrossallnodes;/db2homeisrecommended.

2. Addthedir_cfgparametertothedefaultHPUconfigurationfileoneachdatanodewhere

HPUisinstalledtoreferencethesharedHPUconfigurationfile.

3. Makefurthercustomizationstothereferencedconfigurationfileonly.

ConfigureandshareasingleHPUconfigurationfileacrossallnodestoavoidconfusionwhen

operatingHPU.

CreatingadirectorystructureforHPUstagingandoutputfiles

Atableinatablespacethatis100GBinsizerequiresupto100GBofdiskspaceforstagingdata,

Additionaldiskspaceisrequiredforstagingdataifincrementalbackupimagesarereferenced.

Page:14


15/32


StagingArea

Youcanspecifyonlyonedirectoryforthestagingarea.Itisrecommendedthatyoucreatethesame

directorystructureoneachdatanodetoaccommodatestagingofdata.Wherepossible,locatetheoutput

andstagingdirectoriesforeachnodeonaseparatefilesystemonseparatelogicalunitnumber(LUNs).

Sizethestagingareatoaccommodatethelargesttablespaceinyourdatabaseandalsotakeintoaccount

your

incremental

and

delta

backup

policy.

OutputArea

ToenableparallelismwhenusingHPU,itisrecommendedthatyoucreateanoutputdirectoryforeach

databasepartition.AppendixAshowshowtousesymboliclinkstosimplifytheuseofHPUwiththe

LOADutility.Sizetheoutputareatoaccommodatethelargesttablespaceinyourdatabase.

OnanIBMSmartAnalyticsSystem,theuseofthe/db2fsfilesystemisnotrecommendedforHPU

outputandstagingareasasitmightcompromisethedatabasecontainers.Theoptionsavailableonan

IBMSmartAnalyticsSystemdependonthemodelinstalled(refertoyourdocumentationforfurther

information):

The

IBM

Smart

Analytics

System

5600

can

be

configured

during

the

build

phase

to

assign

a

pre

determinedamountofdiskspacetoa/bkpfs/bculinux/NODE$N filesystem.Thisfilesystem

isconfiguredtobeonaseparatelogicalunitnumber(LUN)fromthe/db2fsfilesystem.

TheIBMSmartAnalyticsSystem7700R1.1and7600canbeconfiguredduringthebuildphaseto

assignapredeterminedamountofdiskspacetoa/workNfilesystemwhereNisthedatabase

partitionnumber.Thisspaceisreallocatedfromthe/db2fsfilesystem.

A/stagefilesystemisavailableontheadminnodeandcanbemountedviaNFSorGPFS

acrossthedatanodes.Thistacticissuitableforsmallersystemsonlyastheamountofspaceis

limitedandthenetworktrafficgeneratedinarecoverysituationcouldbeprohibitiveinlarger

environments.

Where

the

system

is

already

installed

and

space

is

available,

consider

reconfiguring

the

storage

to

facilitatethecreationofafilesystemforHPUuse.Theconfigurationofthetestsystemuseisoutlinedin

AppendixAandsymboliclinksarerecommendedtoaccommodateamoreelegantsolution.

Settingconfigurationfileparameters

Theproduct configuration fileholdsdefaultparametervalues that are referenced each time theHPU

utilityisused.

Recommendationsapplytotheseparameters:

nbcpu

Determine

the

number

of

work

threads

to

be

initiated

by

assessing

the

recovery

time

objective

requiredandtheresourcesavailable.Changetheconfigurationparameterasrequiredbefore

runningthedb2hpucommand.

stagedir

Useseparatedirectoriesforthestagingareaandoutputareawheretheloadformattedoutput

filesarewritten.Thestagedirparameterinthedb2hpu.cfgconfigurationfileissetto/tmpby

Page:15


16/32


default.Changethisentrytoreferenceadirectorythatexistsoneachdatanodeandhasenough

diskspacetoaccommodateyourHPUusagestrategy.

bufsize

Defaultmemoryusageof8MBperdatabasepartitionisrecommendedformost

implementations,

which

is

calculated

as

4

MB

for

each

HPU

bufferpool.

Increasing

this

configurationparametervalueincreasestheamountofmemoryreservedbyHPUwithonlya

marginalincreaseinthroughputandisnotrecommended.

maxselects

Determinethenumberoftablestoprocessinparallelbasedontestingandtheamountof

resourcesallocatedtorecovery.

HPU

disk

requirements

Thestagingareamustbesizedtoaccommodatethetemporaryfilescreatedwhendataisunloaded.The

minimumsizeneededforthestagingareadependson:

TheDB2softwareversion.InDB2V9.7theentiretablespaceisstageduptotheHighWaterMark

(HWM)forDMStablespaces.Usethe"ALTER TABLESPACE REDUCE"command

inDB2V9.7toavoidunnecessarylargeHWMonDMStablespaces.

Thetablespacetype.SMStablespacesdonotrequiretheentiretabletobestaged,stagingis

completewhenalltableinitializationdatahasbeenfound.

Itisrecommendedthatyouallocatespaceequivalenttothesizeofthetablespace.

Whenmultipletablesareunloadedinparallel,theHPUutilityattemptstominimizethenumberoftimes

thebackupimageisaccessed.AdditionalprocessingisrequiredforobjectsincludingLOB,XML,LONG,

LONGVARCHAR,andLONGVARGRAPHICandisdiscussedinAppendixE.

Page:16


17/32


Conclusion

UseIBMInfoSphereOptimHighPerformanceUnloadasatooltoaddressrecoveryscenarioswhere

traditionalrestoreandrebuildoptionsarenotviable.

ThefollowingrecommendationsshouldbetakenintoaccountwhenusingHPUinyourenvironment:

InstallHPUonlyonthephysicalserverswhereyouintendtorunHPUtounloaddata.

Retainacopyofthemostrecentdatabasecatalogbackupimageondisktohelpincreaserecovery

speedwhenusingHPU.

Useofflinebackupimagesorconsistentonlinebackupimagestohelpensuretheintegrityofthe

dataunloaded.

Chooseyourrecoverymethodbasedonyourresourcepriority:usenamedpipeswherethereis

insufficient

disk

space

on

the

data

nodes,

or

unload

to

output

files

where

processor

usage

islimited.

UsetheconfigurationandcontrolfileparameterstothrottleHPUusageofprocessorresources.

Avoidcontentionwhenunloadingdatafromtapebyensuringthatthesequenceofdatabase

partitionsreferencedintheunloadblocksmirrorsthebackupsequence.

Unloaddatafrombackupimagesbyfollowingthesamepatternthatwasusedtocreatethe

backupimages.

ConfigureyouroutputdirectoriestoallowHPUtounloaddatawithasinglecommandin

parallel

across

multiple

database

partitions.

ConfigureandshareasingleHPUconfigurationfileacrossallnodestoavoidconfusionwhen

operatingHPU.

Page:17


18/32


AppendixA.ConfigurationoftestsystemusedThetestsystemusedforthispaperwasanIBMSmartAnalyticsSystemE7100thatconsistedofthree

servers;anadministrationmoduleandtwodatamodules.Theadministrationmodulehadasingle

database

partition

that

supported

the

catalog

function,

the

coordinator

function

and

nonpartitioned

metadata,staginganddatawarehousetables.Eachdatamodulehadeightdatabasepartitionsthat

containedpartitioneddatawarehousetables.

InfoSphereOptimHighPerformanceUnloadforDB2forLinux,UNIX,andWindowsversion32

bits04.01.003.01(100929)

DB2version:DB2V9.7withFixPack3installed.

AIXversion:6.1.0.0

TwotapedriveswereavailableontheTSMserver.Foronlinetablespacebackups,2databasepartitions

werebackedupatatime;startingwith1and9followedby2and10andcontinuinginthissequence.

Onlinetablesspacebackupswerecoordinatedwiththedataingestapplicationsothatnotransactions

occurred

on

the

tables

during

the

online

backup.

StagingArea

Thedirectory/work1/hpu/stagewassetintheconfigurationfile.Symboliclinkswereusedtoensure

thatthisdirectorywasavailableoneachdatanodesothatdatabothunloadedandstagedoneachdata

node.ThestagingareaisatemporaryareaandHPUremovestemporaryfilesoncetheunloadoperation

finished.Theexamplebelowshowsthecommandsusedtocreatethesymboliclinksonthe

administrationnodeandtheseconddatanode.Thefirstdatanodealreadycontainedthedirectories

/work1through/work8.Notethatthesecommandswereusedforalldatabasepartitionsoneachnode.

ln s /work0 /work1

ln s /work9 /work1

mkdir /work1/hpu

mkdir /work1/hpu/stage

OutputArea

The/workNfilesystemwasusedtocontainHPUoutputfileslocaltoeachdatabasepartition.Because

theHPU %{source_node}parameterdenotesadatabasepartitionnumberasNODE0000,symboliclinks

werecreatedtoreferencethe/workNdirectorystructure. Directorieswerecreatedasfollows:

ln s /work1 /work001

mkdir /work1/HPU


mkdir /work2/HPU


mkdir /work3/HPU

Page:18


19/32


..


mkdir /work9/HPU


mkdir /work16/HPU

Tofacilitateparallelloadoftheoutputfilescreatedinthedirectoriesshownabovethefollowingsymbolic

linkswerecreatedontheseconddatanodesothateachdatanodehas/work1through/work8:

ln s /work9 /work1

ln s /work10 /work2

ln s /work11 /work3

..

ln s /work16 /work8

Tofacilitatetheunloadingofdatafrombackupimagesondiskthefollowingdirectorystructurewas

createdtocontainthebackupimages.

mkdir /work1/backup

mkdir /work2/backup

mkdir /work3/backup

..

The

backup

strategy

in

place

was

to

back

up

a

table

space

on

one

database

partition

per

node

in

parallel

untilalldatabasepartitionsonwhichthetablespaceresidedwerebackedup.

TheHPUconfigurationfileonthetestsystemusedwasasfollows:

# HPU default configuration

bufsize=4194304

db2dbdft=TPCDS

db2instance=BCUAIX

doubledelim=binary

netservice=db2hpudm412

#stagedir=/tmp

stagedir=/work1/hpu/stage

nbcpu=8

maxselects=10

Page:19


20/32


Appendix

B.

Recovery

scenario

control

file

examples

ThescenariosandexamplecontrolfilesinthissectionillustratehowHPUcanformapartofyour

recoverystrategyusingtherecommendationsmadeinthispaper.Theexamplesillustratetherecoveryof

partitioned

tables

through

backup

images

stored

on

TSM.

These

examples

cover:

RecoverdroppedpartitionedtableusingbackupimagesonTSM

Recoverexistingpartitionedtableusingbackupimagesondisk

RecoverdroppedpartitionedtableusingbackupimagesonTSMandnamedpipes

RecoverdroppedtablespaceusingbackupimagesonTSM

RecoverdatausingnonproductionsystemandbackupimagesonTSM

Thebackupstrategyforeachtablespacewastobackuponedatabasepartitionpernodeinparalleluntil

thetablespaceresidedwasbackedup.Intheexamplesbelowthesamesequencewasappliedwhen

unloading

data.

Recover

dropped

partitioned

tables

using

backup

images

on

TSM

ThisscenariousedHPUtorecovertwopartitionedtables,CUSTOMERandCUSTOMER_DEMOGRAPHICS

fromonlinetablespacebackupimagesstoredonTSM.Thedatawasunloadedtooutputfilesoneach

datanodeandthentheDB2Loadutilitywascalledasaseparatesteptoloadthedataintothetarget

table.

Theoutputlocationondiskforeachdatabasepartitionwasspecifiedas/workN/HPU. Anexcerptfrom

thecontrolfileusedinthisscenariofollows:

-- Global Block specifying backup image on disk where catalog resides

GLOBAL USING BACKUP CATALOG TPCDS FROM "/work0/HPU/catalog_BACKUP"

TAKEN AT 2011033108;

;


UNLOAD TABLESPACE

PART(1,9)


HOST TAKEN AT 20110331080240;

-- Select Blocks specifies customer table and output files


OUTFILE("%{source_host}:/work%{source_node}/HPU/bcuaix.customer.file.%{

source_node}") FORMAT DEL

-- Select Blocks specifies customer_demographics table and output files

Page:20


21/32



OUTFILE("%{source_host}:/work%{source_node}/HPU/bcuaix.demographics.fil

e.%{source_node}") FORMAT DEL

;


UNLOAD TABLESPACE

PART(2,10)


HOST TAKEN AT 20110331084220;





OUTFILE("%{source_host}:/work%{source_node}/HPU/bcuaix.demographics.fil

e.%{source_node}") FORMAT DEL

;

-- NB: Repeat sequence for database partitions 3 & 11 and on to 8 & 16.

Thedatawasunloadedinsequenceaccordingtothephysicaltapedrivesavailable.ThefollowingLOAD

commandswereusedtoloadthedatafilescreatedbytheHPUprocessintothetargetpartitionedtablein

parallelwithnonetworktrafficgenerated.Notalldatabasepartitionsareincludedintheexample:

db2 "LOAD from bcuaix.customer.file OF DEL INSERT

INTO BCUAIX.CUSTOMER PARTITIONED DB CONFIG MODE

LOAD_ONLY_VERIFY_PART PART_FILE_LOCATION /work1/HPU

OUTPUT_DBPARTNUMS(1,9)"

db2 "LOAD from bcuaix.customer.file OF DEL INSERT

INTO BCUAIX.CUSTOMER PARTITIONED DB CONFIG MODE



-- Issue LOAD commands for all database partitions to be recovered

db2 "LOAD from bcuaix.demographics.file OF DEL INSERT INTO

bcuaix.customer_demographics PARTITIONED DB CONFIG MODE



db2 "LOAD from bcuaix.demographics.file OF DEL INSERT INTO

bcuaix.customer_demographics PARTITIONED DB CONFIG MODE




Page:21


22/32


UsetheLOAD_ONLY_VERIFY_PART modeinsteadofLOAD_ONLYmodeasHPUdoesnotgenerate

theheaderswithpartitionnumber,partitionmap,andpartitioningkeycolumnswhichLOAD_ONLY

moderequires.TheappropriateheadersweregeneratedonlyforHPUrepartitioningandHPUmigration.

Recoverexistingpartitionedtablesusingbackupimagesondisk

ThisscenariousedHPUtorecoverapartitionedtablefromonlinetablespacebackupimagesstoredon

disk.Thisscenarioapplieswherethetableexistsinthedatabasebutthecontentshavebeencompromised

orcorruptionhasoccurred.

Theunloadblockspecifiedeachpathwherebackupimagesfilesexist.Becausethetabletoberecovered

existedinthedatabase,thedatabasecatalogisreferencedintheglobalcontrolblockratherthanacatalog

associatedwithabackupimage.Thisactionreducedthenumberofbackupimagestobereadand

thereforeincreasedthespeedoftheHPUoperation.Thecontrolfileusedinthisscenariowas:

-- Global Block uses local database catalog

GLOBAL CONNECT TO TPCDS;

-- Unload Block specifies backup images for partitions 1 - 16

UNLOAD TABLESPACE

PART(1:16)

USING BACKUP DATABASE TPCDS TABLESPACE ("HASHTS") FROM

"/work1/backup","/work2/backup","/work3/backup","/work4/backup",

"/work5/backup","/work6/backup","/work7/backup","/work8/backup"

ON SOURCE HOST TAKEN AT 2011033108;





;

TheLOADcommandissued:

db2 "LOAD from bcuaix.customer.file OF DEL INSERT INTO BCUAIX.CUSTOMER

PARTITIONED DB CONFIG MODE LOAD_ONLY_VERIFY_PART

PART_FILE_LOCATION /work1/HPU OUTPUT_DBPARTNUMS(1,9)"

db2 "LOAD from bcuaix.customer.file OF DEL INSERT INTO BCUAIX.CUSTOMER

PARTITIONED DB CONFIG MODE LOAD_ONLY_VERIFY_PART

PART_FILE_LOCATION /work2/HPU OUTPUT_DBPARTNUMS(2,10)"


Page:22


23/32


Recover

dropped

partitioned

table

using

backup

images

on

TSM

and

namedpipes

ThisscenariousedHPUtorecoverpartitionedtablesfromonlinetablespacebackupimagesstoredon

TSMand,byusingnamedpipes,simultaneouslyloadedthedataintothetargetdatabasetable.

ThefollowingcontrolfilewascreatedtouseinunloadingthetablefrombackupimagesonTSMfor

databasepartitions1and9whichwerethefirstdatabasepartitionsoneachdatanodeinthetest

environment.Asthetablehadbeendroppedontheproductiondatabasethecatalogonthecatalog

backupimagewasreferenced.

1. Thecontrolfilewascreated.Eachunloadblockprocessedtwodatabasepartitions.Thefollowing

exampleshowsthefirsttwounloadblocksfordatabasepartitions1,9and2,10.Thepattern

continueduntilalldatabasepartitionswereprocessed.

-- Global block uses backup image of catalog on disk


TAKEN AT 2011033108;

;

-- 1,9 specifies partitions 1 and 9

UNLOAD TABLESPACE PART(1,9)


HOST TAKEN AT 20110331080240;


OUTFILE("%{source_host}:/work%{source_node}/HPU/pipe.%{source_node}")

FORMAT DEL

;

-- 2,10 specifies partitions 2 and 10 (continues to 8 and 16)

UNLOAD TABLESPACE PART(2,10)


HOST TAKEN AT 20110331084220;


OUTFILE("%{source_host}:/work%{source_node}/HPU/pipe.%{source_node}")

FORMAT DEL

;

2. Thenamedpipeswerecreatedoneachdatanodeasspecifiedinthecontrolfile.Thenamesin

this

example

have

the

format:

/workN/HPU/pipe.XXX

where

XXX

is

the

appropriate

database

logicalnodenumber.

Thenamedpipeswerecreatedforthedatabasepartitionstobeprocessedbytheunloadblockin

thecontrolfile.Thecommandsusedtocreatethenamedpipesinthetestenvironmentare

illustratedasfollows:

Page:23


24/32


-- Data Node 1

mkfifo /work1/HPU/pipe.001








-- Data Node 2 (Symbolic links for /work1 to /work8 created)









3. TheHPUcommandspecifyingtherequiredcontrolfilewasexecuted:

db2hpu -f CUSTOMER_disk_pipes.ctl

4. DB2Loadoperationwasstarted:


Page:24

db2 "LOAD from pipe OF DEL INSERT INTO BCUAIX.CUSTOMER PARTITIONED DB

CONFIG MODE LOAD_ONLY_VERIFY_PART PART_FILE_LOCATION /work1/HPU


db2 "LOAD from pipe OF DEL INSERT INTO BCUAIX.CUSTOMER PARTITIONED DB

CONFIG MODE LOAD_ONLY_VERIFY_PART PART_FILE_LOCATION /work2/HPU



25/32


RecoverdroppedtablespaceusingbackupimagesonTSM

ThisscenariousedHPUtorecoverallthetablesinatablespacefrombackupimagesonTSM.Thetarget

tablesdidnothavetousethesametablespacename.

ThefollowingcontrolfileunloadsallthetablesinthetablespaceHASHTS.ItalsoinstructstheHPU

processtousetablespacebackupimages.TheUSING BACKUP CATALOGkeywordisneededasinthis

scenariothetablespacewasdroppedandsonotvisibleinthedatabasecataloganymore.

-- Global Block


TAKEN AT 20111117094257;

;

-- Unload Block 1,9

UNLOAD TABLESPACE HASHTS PART(1,9)

OUTFILE("%{source_host}:/work%{source_node}/HPU/file.%{source_node}")

FORMAT DEL


HOST TAKEN AT 20111117105244;

;

-- Unload Block (2,10)

UNLOAD TABLESPACE HASHTS PART(2,10)

OUTFILE("%{source_host}:/work%{source_node}/HPU/file.%{source_node}")

FORMAT DEL


HOST TAKEN AT 20111117105244;

;

-- continue process for other database partitions

Page:25


26/32


Recover

data

using

nonproductionsystemandbackupimagesonTSM

Inthisscenario,thecontentsofacolumninaproductiontablehadbeencompromised.Backupimagesof

theproductiondatabasewerelocatedontheTSMserver.Anonproductionsystemwasusedtorecover

andpreparethedatabeforeitwasreappliedtotheproductionsystem.

The

production

environment

contained

two

data

nodes

and

a

total

of

16

database

partitions.

The

non

productionsystemcontainedonedatanodeandeightdatabasepartitions.Thereweretwotapedrives

available.

HPUwasinstalledandconfiguredonthenonproductionsystemonlyandthenonproductionsystem

wasconfiguredtouseTSM.Acopyofthebackupimageforthecatalogpartitionontheproduction

systemwasmadeavailableonthenonproductionsystem.Becauseonlyasinglecolumnwas

compromised,HPUwasusedtounloadjusttheprimarykeyandthecontentsoftheaffectedcolumn.

Thecontrolfileforthisscenariounloadeddatafromeachbackupimageinsequence.TheTSMNODE

parameterinthecontrolfilewasusedtoidentifythecorrectTSMnodewherethebackupimagefile

exists.

TheTARGETENVIRONMENTandTARGETKEYScontrolfileparametersdirectoutputdataforeach

targetdatabasepartitiontoaseparatefile.TheTARGETENVIRONMENTparametervaluespecifiesthe

instancename,databasename,andtheservernamewherethedatabasecatalogresidesonthenon

productionsystem.TheTARGETKEYSparametervaluespecifiesthedatabasepartitionsonwhichthe

tableexistsinthenonproductionsystem.

Eachdatanodeonthenonproductionsystemused/workN/HPUdirectoryfortheoutputfiles.The

APPENDparameterintheOUTFILEclauseensuredthateachsubsequentunloadblockdidnotoverwrite

theoutputdatafilealreadycreated.

-- Global Block specifying catalog partition backup image on disk

GLOBAL USING BACKUP CATALOG TPCDS from "/work0/HPU/catalog_BACKUP"

TAKEN AT 2011033108;

;

-- Unload Block specifies backup image for database partition 1 and 2 -

-- from TSMNODE tsm_datanode1

UNLOAD TABLESPACE

PART(1,2)

USING BACKUP DATABASE TPCDS TABLESPACE ("HASHTS") USE TSM TSMNODE

"tsm_datanode1" TAKEN AT 2011033109;



TARGET ENVIRONMENT (INSTANCE "bcuaix" ON "perfbwadm_test" IN TPCDS)

TARGET KEYS(CURRENT PARTS(1:8))

OUTFILE

Page:26


27/32


("%{target_host}:/work%{target_node}/HPU/BCUAIX.CUSTOMER.file.%{target_

node}") FORMAT DEL

;

-- Unload Block specifies backup image for database partitions 9 and 10

-- from TSMNODE tsm_datanode2

UNLOAD TABLESPACE

PART(9,10)

USING BACKUP DATABASE TPCDS TABLESPACE ("HASHTS") USE TSM TSMNODE

"tsm_datanode2" TAKEN AT 2011033109;



TARGET ENVIRONMENT (INSTANCE "bcuaix" ON "perfbwadm_test" IN TPCDS)

TARGET KEYS(CURRENT PARTS(1:8))

OUTFILE

("%{target_host}:/work%{target_node}/HPU/BCUAIX.CUSTOMER.file.%{target_

node}" APPEND) FORMAT DEL

;

Datawasloadedintononproductionsystem:

db2 "LOAD from BCUAIX.CUSTOMER.file OF DEL INSERT INTO BCUAIX.CUSTOMER

PARTITIONED DB CONFIG MODE LOAD_ONLY_VERIFY_PART PART_FILE_LOCATION

/work1/HPU OUTPUT_DBPARTNUMS(1)"

db2 "LOAD from BCUAIX.CUSTOMER.file OF DEL INSERT INTO BCUAIX.CUSTOMER

PARTITIONED DB CONFIG MODE LOAD_ONLY_VERIFY_PART PART_FILE_LOCATION

/work2/HPU OUTPUT_DBPARTNUMS(2)"


Datawasunloadedfromnonproductionsystemtofilesinpreparationfortransfertotheproduction

system.Onlythecolumntoberecoveredisspecifiedintheselectblock.

GLOBAL CONNECT TO TPCDS;

UNLOAD TABLESPACE

PART(1:8)

select customer_address_id,ca_zip FROM BCUAIX.CUSTOMER where ca_zip

like 'NA%4';

OUTFILE("/work1/HPU/customer_recovered_data.csv") FORMAT DEL

;

Thedatawasappliedtotheproductionsystembyfirstbeingloadedintoatemporarytableandthen

appliedtothetargettablethroughanUPDATEstatement.

Page:27


28/32


Appendix

C.

LOB

and

XML

objects

HPUsupportsLargeObjects(LOB)andXMLdatathroughanintermediatestepintheunload/load

process.

If

the

table

is

located

in

an

SMS

table

space,

the

data

files

containing

the

externalized

data

(LOB

and

XML

orboth)areentirelystagedwhilereadingthebackupafirsttime.Thebackupisreadasecondtimebythe

HPUoperationtoprocessthemaindatapagesofthetable,containingreferencestoLOBandXMLor

bothdatastorage.Duringthissecondpass,thismaindatafilecanbepartiallystaged,untiltheinternal

recordsdescribingthetablehavebeenfound.

IfthetableislocatedinaDMStablespace,themaindataandtheexternalizedonesareentirelystaged

whilereadingthebackup.Thisactioncanresultinseveraltablespacesbeingstaged,iftheLOBorXML

dataisstoredinaseparatetablespace.Theunloadprocedureisstartedagainstthestagedfiles.

Page:28


29/32


Further

reading

VisitthebestpracticespageondeveloperWorksforpapersonphysicaldatabasedesign,datalifecycle

management,databasebackup,compression,andmanyothertopics:

http://www.ibm.com/developerworks/data/bestpractices/

Refertothefollowinglinksforadditionalinformationabouttopicsdiscussedinthispaper:

IBMInfoSphereOptimHighPerformanceUnload

http://www01.ibm.com/software/data/optim/highperformanceunloaddb2luw/

DB2LoadUtility

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.

dm.doc/doc/c0004616.html

BuildingarecoverystrategyforanIBMSmartAnalyticsSystemDataWarehouse

http://www.ibm.com/developerworks/data/bestpractices/isasrecovery/index.html

Traditionaldroppedtablerecoverymethod

(http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin

.ha.doc/doc/t0006318.htmlFirefoxHTML\Shell\Open\Command

Contributors

AliceMa

Client

Technical

Professional,

Enterprise

Content

Management,

IBM

AustinClifford

DB2DataWarehouseQASpecialist,IBM

BillMinor

InformationManagementTooling&Development,IBM

DaleMcInnis

DB2AvailabilityArchitect&SeniorTechnicalStaffMember,IBM

JaimeBotellaOrdinas

ITSpecialist&AcceleratedValueLeader,SoftwareGroup,IBM

VincentArrat

HPUDevelopmentTeam

Page:29
http://www.ibm.com/developerworks/data/bestpractices/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dm.doc/doc/c0004616.htmlhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dm.doc/doc/c0004616.htmlhttp://www.ibm.com/developerworks/data/bestpractices/isasrecovery/index.htmlhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.ha.doc/doc/t0006318.htmlFirefoxHTML\Shell\Open\Commandhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.ha.doc/doc/t0006318.htmlFirefoxHTML\Shell\Open\Commandhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.ha.doc/doc/t0006318.htmlFirefoxHTML\Shell\Open\Commandhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.ha.doc/doc/t0006318.htmlFirefoxHTML\Shell\Open\Commandhttp://www.ibm.com/developerworks/data/bestpractices/isasrecovery/index.htmlhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dm.doc/doc/c0004616.htmlhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dm.doc/doc/c0004616.htmlhttp://www-01.ibm.com/software/data/optim/high-performance-unload-db2-luw/http://www.ibm.com/developerworks/data/bestpractices/


30/32


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the produc ts, services, or features discussed in this doc ument in other

countries. Consult your local IBM representative for information on the produc ts and services

currently available in your area. Any reference to an IBM product, program, or service is not

intended to state or imply that only that IBM product, program, or service may be used. Any

functiona lly equivalent product, program, or service that does not infringe any IBM

intellectual property right may be used instead. However, it is the user's responsibility to

evaluate and verify the operation of any non-IBM produc t, program, or service.

IBM may have patents or pending patent applications covering subject matter described in

this document. The furnishing of this document does not grant you any license to these

patents. You can send license inquiries, in writing, to:

IBM Direc tor of LicensingIBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where

such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES

CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON

INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do

not a llow disclaimer of express or implied warranties in certain transac tions, therefore, thisstatement may not apply to you.

Without limiting the above disclaimers, IBM provides no representations or warranties

regarding the accuracy, reliab ility or serviceability of any information or recommendations

provided in this publication, or with respect to any results that may be obtained by the use of

the information or observance of any rec ommendations provided herein. The information

contained in this document has not been submitted to any formal IBM test and is distributed

AS IS. The use of this information or the implementation of any recommendations or

techniques herein is a customer responsibility and depends on the customers ability to

evaluate and integrate them into the customers operational environment. While each item

may have been reviewed by IBM for accurac y in a specific situation, there is no guarantee

that the same or similar results will be obtained elsewhere. Anyone attempting to adapt

these techniques to their own environment do so a t their own risk.

This document and the information contained herein may be used solely in connec tion with

the IBM products discussed in this document.

This information could include technica l inac curac ies or typographica l errors. Changes are

periodically made to the information herein; these changes will be incorporated in new

Page:30


31/32


editions of the publication. IBM may make improvements and/or changes in the product(s)

and /or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only

and do not in any manner serve as an endorsement of those Web sites. The materials at

those Web sites are not part of the materials for this IBM product and use of those Web sites is

at your own risk.

IBM may use or distribute any of the information you supply in any way it believes

appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a c ontrolled environment.

Therefore, the results obtained in other operating environments may vary significantly. Some

measurements may have been made on development-level systems and there is no

guarantee that these measurements will be the same on generally available systems.

Furthermore, some measurements may have been estimated through extrapolation. Ac tual

results may vary. Users of this document should verify the applica ble data for their specific

environment.

Information conc erning non-IBM produc ts was obtained from the suppliers of those produc ts,

their published announcements or other publicly available sources. IBM has not tested those

products and cannot confirm the accurac y of performance, compatibility or any other

claims related to non-IBM produc ts. Questions on the capabilities of non-IBM products should

be addressed to the suppliers of those products.

All statements regarding IBM's future direc tion or intent are subject to change or withdrawal

without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To

illustrate them as completely as possible, the examples include the names of individua ls,

companies, brands, and products. All of these names are fictitious and any similarity to the

names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate

programming tec hniques on various operating platforms. You may copy, modify, and

distribute these sample programs in any form without payment to IBM, for the purposes of

developing, using, marketing or distributing application programs conforming to the

application p rogramming interfac e for the operating platform for which the sample

programs are written. These examples have not been thoroughly tested under all conditions.

IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these

programs.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International

Business Mac hines Corporation in the United States, other countries, or both. If these and

Page:31


32/32


other IBM trademarked terms are marked on their first oc currence in this information with a

trademark symbol (or ), these symbols indica te U.S. registered or common law

trademarks owned by IBM at the time this information was published. Such trademarks may

also be registered or common law trademarks in other countries. A current list of IBM

trademarks is ava ilab le on the Web a t Copyright and trademark information at

www.ibm.com/legal/copytrade.shtml

UNIX is a registered trademark of The O pen Group in the United States and other countries.

Linux is a registered tradema rk of Linus Torvalds in the United States, other countries, or both.

Other company, produc t, or service names may be trademarks or service marks of others.
http://www.ibm.com/legal/copytrade.shtmlhttp://www.ibm.com/legal/copytrade.shtml

Documents

DB2BP Warehouse HPU Recovery 1111 (2)