More Oracle TAR humor
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 1 of 1

Thread: More Oracle TAR humor

  1. #1
    Join Date
    Sep 2003
    Location
    over the hill and through the woods
    Posts
    995

    More Oracle TAR humor

    Thought I'd share some more Tar humor. I have not edited the
    conversation / spelling whatsoever.

    ENHANCEMENT REQUEST

    ### Reason current product functionality is insufficient. ###
    During the application of patch 4193299 when the catcpu.sql is ran it
    does the following.
    ALTER SYSTEM SET "_system_trig_enabled"=FALSE SCOPE=MEMORY;
    ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0 SCOPE=MEMORY;
    ALTER SYSTEM SET AQ_TM_PROCESSES=0 SCOPE=MEMORY;
    ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=BYTE SCOPE=MEMORY;
    At the end of the patch these parameters are not back to their orginal
    settings. In order for these settings to be put back to the orginal, the
    database must be bounced. No where in the read me does it specify that one
    should bounce the database after the patch has been successfully applied.

    ### Detailed description of the Enhancement Request. ###
    In the read me file specify that the database MUST be bounced.

    ### How the product can be changed to achieve the desired result. ###
    a simple one line sentence of. Bounce the database.

    ### Reasons to consider the Enhancement Request. ###
    Because if they don't they're going to have a bunch of databases out there not
    working correctly!

    ### Business impact if the Enhancement is not considered. ###
    You all should know this the best.

    10-MAY-05 07:11:00 GMT

    TAR has been assigned to an analyst -- Sending email.


    10-MAY-05 07:20:57 GMT

    Thank you for using MetaLink. We are currently
    reviewing/researching the situation and will update the SR /
    call you as soon as we have relevant information.
    Thank you for your patience.

    Best Regards,
    Oracle Support Services



    10-MAY-05 07:58:20 GMT

    Hi

    Question
    =============
    Where is the part of the paramter chaining during applying the
    CPU patch in documents

    Answer
    =========
    From the patch read me file there is a link to

    Note:301045.1 Subject: Oracle Critical Patch Update April 2005
    Pre-Installation Note for Oracle Database

    ======================================================
    12. After running catcpu.sql/catcpu_rollback.sql, the following
    parameters are set to a different value:

    _system_trig_enabled, JOB_QUEUE_PROCESSES, AQ_TM_PROCESSES

    and must be reset to their original values. This can be accomplished
    by simply restarting the database to have the parameters reloaded
    from the current parameter file. Alternatively, they can be reset
    by running the following SQL statements:

    PROMPT _system_trig_enabled;
    ALTER SYSTEM SET "_system_trig_enabled"=&TRUE_OR_FALSE SCOPE=MEMORY;
    PROMPT JOB_QUEUE_PROCESSES;
    ALTER SYSTEM SET JOB_QUEUE_PROCESSES=&X_JOB SCOPE=MEMORY;
    PROMPT AQ_TM_PROCESSES;
    ALTER SYSTEM SET AQ_TM_PROCESSES=&X_AQ SCOPE=MEMORY;
    ======================================================



    10-MAY-05 08:16:25 GMT

    New info: That's your solution to this? You're kidding right?
    That says KNOWN ISSUES... It says nothing about patching
    instructions. Don't you think that as a part of the patching
    proceedure that reloading the database should be included to bring
    the database back to the orginal state that it was
    before the patching process began?



    10-MAY-05 08:19:14 GMT

    yes i agree with you but this is document is considered
    to be read before patching and this is refrenced 3 times in the
    readme of the patch readme


    10-MAY-05 08:46:24 GMT

    New info : I still don't understand how reloading the database falls
    under "known issues" but, it looks like you're going to take the easy
    way out of this. So, let me make another "enhancement request". For
    future IAVI patches (and all others for that matter) if system
    parameters are dynamically changed during the patching process, can
    Oracle simply put "After patch has been sucessfully applied reload
    the database." at the end of the patch installation? After all
    isn't this good practice after a patch has been applied?

    With that in place it would ensure that the entire patching process
    was followed correctly according to the readme and Post Installation
    Instructions. It would also ensure without a doubt that any dynamic
    system alterations would
    be set back to orginal settings before the patching process started.
    Fair enough?


    10-MAY-05 10:58:11 GMT

    Hi

    Actually,that i happened normally in the patch installation procedure
    but your point of view is very logic and has to be taken into
    consideration please follow these notes for logging enhancemnet
    tar to address the issue as the procedure changed

    Note:214168.1 Subject: Logging an Enhancement Request

    Regards


    10-MAY-05 11:49:25 GMT

    New info : According to that note it says to open an ITAR and choose
    "Product Enhancement Request" but this is what this current ITAR is
    titled. Why would I have to open another ITAR if what we are
    discussing deals directly with what is at hand?

    10-MAY-05 12:28:34 GMT

    Hi

    I have opened an enhancemnet request for this issue it is :4360764
    please wait some times and folllow it from metalink as described
    from the note i already mentioned

    Reegards
    Last edited by gandolf989; 05-11-2005 at 10:27 AM.
    Oracle it's not just a database it's a lifestyle!
    --------------
    BTW....You need to get a girlfriend who's last name isn't .jpg

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width