best practices for upgrade february 23, 2012-1

Upload: rajiv272799

Post on 04-Jun-2018

216 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    1/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    2/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    3/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    4/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    5/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    6/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    7/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    8/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    9/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    10/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    11/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    12/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    13/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    14/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    15/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    16/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    17/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    18/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    19/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    20/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    21/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    22/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    23/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    24/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    25/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    26/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    27/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    28/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    29/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    30/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    31/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    32/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    33/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    34/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    35/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    36/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    37/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    38/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    39/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    40/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    41/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    42/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    43/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    44/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    45/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    46/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    47/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    48/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    49/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    50/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    51/71

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    52/71

    2012 Oracle Corporation 2

    allbac- (trateg (n an! case/

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    53/71

    2012 Oracle Corporation 33

    Best Practice #11 $5ter t'e upgrade

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    54/71

    2012 Oracle Corporation ..

    Post Upgrade Create s!stem statistics during a regular Aor;load period -

    ot'erAise non-appropriate alues 5or t'e C"O Aill be used/

    ()L* select &name A!E; &7al$ >ALUE; &7al% I ?O 4rom au: stats@

    A!E >ALUE I ?O-------------------- ---------- ------------------------------(

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    55/71

    2012 Oracle Corporation

    Post Upgrade )?ample/ customer O+

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    56/71

    2012 Oracle Corporation 66

    Post Upgrade Create 5i?ed table statistics

    Directl! a5tercatup rd.s3l

    'as been completed

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    57/71

    2012 Oracle Corporation 8

    Post Upgrade 6 (P I $lAa!s create an editable init ora 5rom t'e current

    #P (+) a5ter t'e upgrade 'as been 5inis'ed Pre ents reArite in case o5 setting Arong parameters or

    5orced edit Geep in mind/

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    58/71

    2012 Oracle Corporation 99

    Agenda

    "est Practices

    #ummar!

    $%

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    59/71

    2012 Oracle Corporation 77

    t 2 + + B

    2 + + /

    2 + + 3

    2 + + ;

    2 + + =

    2 + + ,

    2 + + 2

    2 + + D

    2 + 1 +

    toda!

    ifeti e (upport Polic

    2 + 1 1

    2 + 1 2

    2 + 1 /

    2 + 1 3

    Sustaining Support Premier Support

    R2 #$%y 2&&'

    Extended Support #$%y 2&(&

    #an$ary 2&&) #an$ary 2&(2

    R2 #$%y 2&(& #$%y 2&(*

    2 + 1 ;

    2 + 1 =

    A$g$+t 2&(2 A$g$+t 2&(

    #$%y 2&&-

    #$%y 2&((

    R2

    2 + 1 ,

    2 + 1 B

    #an$ary 2&( #an$ary 2&(-

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    60/71

    2012 Oracle Corporation 6060

    Upgrade to Oracle Database 11 g Release2

    R2

    R2

    10.2.0.2

    10.1.0.

    R2

    !.3."

    #.0.$

    #.1.!."

    %.0.1."

    %.2.0.#

    %.2.0."

    E/0ty arrow+ /ean1 no +0ecific 0atc! re%ea+e re $ire

    $

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    61/71

    2012 Oracle Corporation 61

    AF$ Ho' long 'ill t.e upgrade ta-e7

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    62/71

    2012 Oracle Corporation 62

    Upgrade engt. oA long Aill t'e upgrade ta;e

    to complete (ndependent o5/

    #i@e o5 t'e database Used data t!pes

    Dependent mainl! on/

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    63/71

    2012 Oracle Corporation 63

    Ga ple$ Database Upgrade !i e Usuall! betAeen W30 and W70 minutes

    Dependent mainl! on installed options and components X$ctual times ma! ar!Y

    (omponent ,,: :++

    %racle +erver 00:1T:1#

    F+erver F'H' Hirtual achine 00:05:19

    %racle @orkspace ana er 00:01:01

    %racle Enterprise ana er 00:10:1"

    %racle C D 00:00:68

    %racle e!t 00:00:58

    %racle C ) atabase 00:06:09

    %racle atabase Fava 7acka es 00:00:""

    %racle ultimedia 00:0#:6"

    %racle E!pression Ailter 00:00:18

    %racle &ule ana er 00:00:12

    Latherin +tatistics 00:06:5"

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    64/71

    2012 Oracle Corporation 6.

    Upgrade engt. #peed up !our upgrade per5ormance b!/

    Possibl! sAitc' o55 arc'i ing Ma;e sure t'is Aill compl! Ait' !our business rules Do *O< do t'is i5 !ou are using #tandb! Database or :olden :ate

    Creating dictionar! statistics t'e nig't be5ore t'e upgrade Oracle 7 i/

    Oracle 10 g =11g /

    +

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    65/71

    2012 Oracle Corporation 66

    AF$ C.ic. )et.od (.ould I Use7

    #ta! on same O#*

    UP: $D)

    )?port=(mport

    C

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    66/71

    2012 Oracle Corporation 66

    C.en to &.oose t.e DBUA Can a55ord 30 H 70 minutes a erage doAntime

    Operating s!stem remains t'e same :U( is pre5erred o er manual command line inter5ace

    $utomaticall! per5orms use5ul pre-upgrade c'ec;s +ess error-prone = less manual e55ort

    )?isting database is at least 7 2 0 9 *ote/ especiall! use5ul 5or $C databases Consideration/

    #ource and target Oracle omes must be on t'e same s!stem Cannot be re-run i5 an error is encountered mid-upgrade

    C & & d6 i ()L* s&ool u&grade.log

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    67/71

    2012 Oracle Corporation 68

    C.en to &.oose &o and6 ine Can a55ord 30-70 minutes a erage doAntime

    Manual command-line inter5ace is pre5erred o er :U( )?isting database is at least 7 2 0 9 Migrating to a neA 'ardAare plat5orm Ait' same O#

    Consideration Cannot upgrade to a s!stem Ait' a di55erent operating s!stem

    arc'itecture More manual steps reNuired Potential 5or errors due to t!pos, missed details

    () g g()L* catu&grd.s'l

    C & Al i?

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    68/71

    2012 Oracle Corporation 69

    C.en to &.oose an Alternati?e)et.od $lternati e met'ods include

    Original e?p=imp or Data Pump e?pdp=impdp Oracle #treams or Oracle :olden :ate Data :uard B#%+ $ppl!

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    69/71

    2012 Oracle Corporation 6767

    Agenda

    "est Practices

    #ummar!

    $%

    (

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    70/71

    2012 Oracle Corporation 80

    (u ar

    Preparation and planning are t'e! ;e!s to a success5ulupgrade

  • 8/13/2019 Best Practices for Upgrade February 23, 2012-1

    71/71