FAQ
Metalink Note: 1189783.1 speaks of out-of-place upgrading and patching.

I'm wonder if it might be a good idea to change the oracle home naming conventions to use four or five digits under product directory, out-of-place patching being a driving factor.

Examples:
/orasoft/app/oracle/product/11.2.0/dbhome_1
/orasoft/app/oracle/product/11.2.0.2/dbhome_1
/orasoft/app/oracle/product/11.2.0.2.1/dbhome_1

I was wondering what a sampling of opinions would produce from this list.

Five digits would represent PSU patching. In my case, once the oratab file is updated, everything else (scripts, etc), will set environment correctly, so no issues there.


Joel Patterson
Database Administrator
904 727-2546

Search Discussions

  • D'Hooge Freek at Oct 28, 2011 at 2:50 pm
    Since 11.2.0.2 I have started to use 4 digits for all 11.2 installations.
    PSU patches are done in place.


    Freek D'Hooge
    Uptime
    Oracle Database Administrator
    email: [email protected]
    tel +32(0)3 451 23 82
    http://www.uptime.be
    disclaimer: www.uptime.be/disclaimer

    -----Original Message-----
    From: oracle-[email protected] On Behalf Of [email protected]
    Sent: vrijdag 28 oktober 2011 16:30
    To: [email protected]
    Subject: Oracle Home naming (and out-of-place patching)

    Metalink Note: 1189783.1 speaks of out-of-place upgrading and patching.

    I'm wonder if it might be a good idea to change the oracle home naming conventions to use four or five digits under product directory, out-of-place patching being a driving factor.

    Examples:
    /orasoft/app/oracle/product/11.2.0/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2.1/dbhome_1

    I was wondering what a sampling of opinions would produce from this list.

    Five digits would represent PSU patching. In my case, once the oratab file is updated, everything else (scripts, etc), will set environment correctly, so no issues there.


    Joel Patterson
    Database Administrator
    904 727-2546



    --
    http://www.freelists.org/webpage/oracle-l


    --
    http://www.freelists.org/webpage/oracle-l
  • Guillermo Alan Bort at Oct 28, 2011 at 3:29 pm
    I use a different approach:
    /u00/app/<owner>/product/11.2.0/db11201
    /u00/app/<owner>/product/11.2.0/db11202
    so we have:

    /u00/app/<owner>/product/11.2.0/db11202
    /u00/app/<owner>/product/10.2.0/db10205
    /u00/app/<owner>/product/9.2.0/db9208

    in most of our servers (hopefully soon the 9.2 will be gone!)

    hth
    Alan.-

    On Fri, Oct 28, 2011 at 11:51 AM, D'Hooge Freek wrote:

    Since 11.2.0.2 I have started to use 4 digits for all 11.2 installations.
    PSU patches are done in place.


    Freek D'Hooge
    Uptime
    Oracle Database Administrator
    email: [email protected]
    tel +32(0)3 451 23 82
    http://www.uptime.be
    disclaimer: www.uptime.be/disclaimer

    -----Original Message-----
    From: [email protected]
    On Behalf Of [email protected]
    Sent: vrijdag 28 oktober 2011 16:30
    To: [email protected]
    Subject: Oracle Home naming (and out-of-place patching)

    Metalink Note: 1189783.1 speaks of out-of-place upgrading and patching.

    I'm wonder if it might be a good idea to change the oracle home naming
    conventions to use four or five digits under product directory, out-of-place
    patching being a driving factor.

    Examples:
    /orasoft/app/oracle/product/11.2.0/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2.1/dbhome_1

    I was wondering what a sampling of opinions would produce from this list.

    Five digits would represent PSU patching. In my case, once the oratab
    file is updated, everything else (scripts, etc), will set environment
    correctly, so no issues there.


    Joel Patterson
    Database Administrator
    904 727-2546



    --
    http://www.freelists.org/webpage/oracle-l


    --
    http://www.freelists.org/webpage/oracle-l


    --
    http://www.freelists.org/webpage/oracle-l
  • Bobak, Mark at Oct 28, 2011 at 2:54 pm
    I©ž…êÞý'§µúèšlŒ¢Ú+¢V€Mÿÿø‰ÀOôÿÿÿÿ:¸ Šv¥™ë,jÿÿÿÿº&ü?Ú¦‹ÿŠ xZÞzOÅ­ç¤ü1è¢ÿº›b™ïÛ{ôèÿòhz_ÏjÛ^®Ê'ýÊèÂW²ýÊ&ÿòhz_ÏjÛ^®Ê'ýÊèÂW²ýÊ&ÿÿè­§%{ùÿ~·ž–+-³ú+ƒÿè­§%{ùÿ~·ž–+-³ú+ƒôžžßÅ®/Îrݼÿm5×^ÿç_öØcûMÿÓD®n7œ·ôDüêÚrW‡¢g§jh§ƒö§v‹­þ‡ÿ¦Vœz–­r§ƒô¢Çµ×ýÿÓýˆ…«Þ²Ö«µçm¢ëáØ ŠÛ¢¶¥—]ÿÚ)쵩ejبžÏÏIJZµÈ^±ªÞv‰ÞŠzeiÇÿ·ž?Ç¢ˆR›b™ã«iÉ^
    «Zm«Ù¢ž+-­«h­éšŠ_ß­ç¤ýØh¢ÿº›b™ïÛz×¥û}ÿÓýøç]·óhm¶Ÿÿÿ 0þêmŠgÿmçb±ÉZŠg«ÿ 0þêmŠgÿmïÝŠÇ%j)ž¯øm¶Ÿÿÿ 0þêmŠgÿmïÝŠÇ%j)ž¯ÿÿÿÿή("©LzˁïÿÿÿÅ®‰ÿ¢¶œ•ïåýº.Çÿ~·ž–+-³ú+ƒùšŠ[hþŠÚrWÿ—öèºwýúÞzX¬¶Ïè®Μ¡jWÎ|š—óڶ׫²‰ÿrº0•ìÿr‰’z{ÿ¾¸£u¨6ò‰-¡·«ÛMuׯ÷Ñ:ÿ¢¶œ•ïåýúÞzX¬¶Ïè®®n7œ·ó«iÉ^‰ž©¢žڝÚ.·úþ™ZqêZµÈbžÌzÖ¥Šy
    ¢×ÿ×_=ïÍÿÖÊ^jK(~‹­þ‡ÿ¦Vœzê`­§bž§v–­r§ƒòÿ›
    'uêâ~+fŠmmæ ¢‡buæ­¡ÈZž­…ê+iÉ^†‰ž©¢ž(ž÷§¶*'²Ú.±ç躺+~+Þv("¶Ë§uê鮇nr×b­ç-¢¼ÿ¢ëÿ¡ÿé•§¥«\†)àm见§kŠø§öœ¶Šÿ¦¦W¬ÿú+jÊ·ö©§ú+iÉ^þšèvç-ÿ]ÿÛý?u¸h™ïõþŠÚ²‡íýªiþŠÚrW¿¦º¹Ë×_öÿOöýÖá¢gÿ×ú+jÊ·ö©§ú+iÉ^þšèvç-ÿ]ÿÛýÿÛýu¸h™ïõ#¬Â‰Ýz¸§ƒZµ«š™bž
    ¢˜§Š‰ì‹¥všèvç~º&¶¬–+-üX¯yØ ŠÛ0¢é]­êkzǧ´ô”¥«\†)àü‰æÉƬ{ú'qëazŠÚµ¦ßŠW¢²ê]jםýëÞ¯+aŠx–Çÿ±Êâ¦Ûÿz×ÿÿ¥–Ç­z{⮉æz{\¢ºÞrÙrþÊ'¢+,¹ë-…êÞüš”ö­µêì¢pÚµ¦Ú±àš)â²ÚÚ¶ŠýÓŽöïý¹ã¯ÿ†ÛiÿÿðÃ߭祊ËlþŠàÿ›¥¨þŠÚrWÿ—ÿá¶Úÿÿü0Ã÷ëyéb²Ûÿ¢¸?Áæéj¿¢¶œ•ïå
  • Jeremy Schneider at Oct 28, 2011 at 3:26 pm
    Personally, I've always found the top-level folder name sufficient for
    this (db_1, db_2, etc) - because ultimately it's very difficult to rely
    on the directory name to completely identify what software is in the
    home. Even if you do add forth or fifth digits, that still won't
    accommodate for multiple homes at the same PSU level with different
    combinations of one-off patches applied. Also, this doesn't work for
    any systems where you only do CPUs since they don't increment the
    version number.

    I was once in a position where we repackaged oracle binaries with
    various patchset & one-off combinations for internal distribution and I
    was looking for a good version numbering scheme for identifying these
    packages. You're trying to deal with the same core problem: coming up
    with a "name" (you're using directory instead of my version numbering)
    to intelligently and more easily identify the software installed on a
    system. I wrote a blog post with some thoughts; doesn't answer your
    question, but I think you might find it to be an interesting read -
    mainly the requirement list at the bottom of the post for a robust
    identification scheme.
    http://www.ardentperf.com/2008/12/05/robust-software-version-numbering/

    -Jeremy

    On 10/28/2011 9:30 AM, [email protected] wrote:
    Metalink Note: 1189783.1 speaks of out-of-place upgrading and patching.

    I'm wonder if it might be a good idea to change the oracle home naming conventions to use four or five digits under product directory, out-of-place patching being a driving factor.

    Examples:
    /orasoft/app/oracle/product/11.2.0/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2.1/dbhome_1

    I was wondering what a sampling of opinions would produce from this list.

    Five digits would represent PSU patching. In my case, once the oratab file is updated, everything else (scripts, etc), will set environment correctly, so no issues there.


    Joel Patterson
    Database Administrator
    904 727-2546



    --
    http://www.freelists.org/webpage/oracle-l


    --
    http://www.ardentperf.com
    +1 312-725-9249

    Jeremy Schneider
    Chicago

    --
    http://www.freelists.org/webpage/oracle-l
  • Michael Dinh at Oct 28, 2011 at 6:49 pm
    Shameless plug: http://mdinh.wordpress.com/2011/10/28/11-2-0-3-silent-install-and-database-creation-using-omf/

    Comments welcome.

    Michael Dinh

    Disparity Breaks Automation (DBA)

    Confidence comes not from always being right but from not fearing to be wrong - Peter T Mcintyre


    -----Original Message-----
    From: oracle-[email protected] On Behalf Of [email protected]
    Sent: Friday, October 28, 2011 7:30 AM
    To: [email protected]
    Subject: Oracle Home naming (and out-of-place patching)

    Metalink Note: 1189783.1 speaks of out-of-place upgrading and patching.

    I'm wonder if it might be a good idea to change the oracle home naming conventions to use four or five digits under product directory, out-of-place patching being a driving factor.

    Examples:
    /orasoft/app/oracle/product/11.2.0/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2.1/dbhome_1

    I was wondering what a sampling of opinions would produce from this list.

    Five digits would represent PSU patching. In my case, once the oratab file is updated, everything else (scripts, etc), will set environment correctly, so no issues there.


    Joel Patterson
    Database Administrator
    904 727-2546



    --
    http://www.freelists.org/webpage/oracle-l


    --
    http://www.freelists.org/webpage/oracle-l
  • Martin Berger at Oct 30, 2011 at 12:47 pm
    Joel,

    We changed the naming conversion slightly to something like
    ...../oracle/product/rdbms_112021_rel1
    ...../oracle/product/cman_112022_rely
    ...../oracle/product/agent_112030_relb

    ht's a prefix which defines it's general purpose, 6 digits for the
    version down to the PSU and a postfix. based on this full name we
    identify the O_H down to all one-off patches we apply.

    maybe this also applies to your needs.

    Martin
    On Fri, Oct 28, 2011 at 16:30, wrote:
    Metalink Note: 1189783.1 speaks of out-of-place upgrading and patching.

    I'm wonder if it might be a good idea to change the oracle home naming conventions to use four or five digits under product directory, out-of-place patching being a driving factor.

    Examples:
    /orasoft/app/oracle/product/11.2.0/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2/dbhome_1
    /orasoft/app/oracle/product/11.2.0.2.1/dbhome_1

    I was wondering what a sampling of opinions would produce from this list.

    Five digits would represent PSU patching.   In my case, once the oratab file is updated, everything else (scripts, etc), will set environment correctly, so no issues there.
    --
    http://www.freelists.org/webpage/oracle-l

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouporacle-l @
categoriesoracle
postedOct 28, '11 at 2:31p
activeOct 30, '11 at 12:47p
posts7
users7
websiteoracle.com

People

Translate

site design / logo © 2023 Grokbase