I will never understand airline pricing

Thanks to everybody who attended the upgrade workshop in Santa Clara, CA today. You were a very attentive audience and I got some great questions (especially during the breaks). As always, you can download the slide set here:

500+ Slide Set “Upgrade to Oracle Database 11g: The Whole Story”
Keyword (Schluesselwort): upgrade112

As a complete non sequitur, I have to say that I will never understand airline pricing. I arrived at SJC airport for my 6:50 PM flight to Burbank, and found that a 5:30 PM flight was boarding. The flight was clearly less than half full, so I inquired with the Southwest agent as to whether I could take the earlier flight.

The answer of course was that I could…for an additional fee. Somehow that empty seat at 5:30 PM would cost me more than my empty seat at 6:50 PM. And this was Southwest, an airline that likes to advertise its lack of additional fees! I guess they love my bags, but they don’t love me?

Share this:

7 thoughts on “I will never understand airline pricing

  1. Hi Roy,
    I went through your powerpoint presentation of 11g upgrade. Very good seminar, thanks! I have one question though –
    On page 74 for installation sequence, you mention the steps as Install oracle 11g software -> apply PSU and other patches -> Start the database upgrade? Do I still need to run catbundle.sql after Database upgrade step complete (catupgrd.sql)? If so, what is benefit of install PSU patch right after 11g software installation? Should I take same sequence for CPU? we are not planning to switch to PSU at this point as E-Business and other tech stack still using CPU.

  2. Thanks for coming to CA and giving your presentation. I am in the midst of an upgrade/migration. Last summer I started researching techniques I could use; and you covered them all.
    In your slides, you’ve included the metalink id’s and various schema tables. I appreciate the references since most of my time is spent looking for information. IE Upgrade Preparation.
    Best wishes for your return flight.
    -gerald asp.

  3. That’s a great question, Vivian. You do actually need to run catbundle.sql after the database upgrade. The reason for this is that this script updates dba_registry_history to properly reflect the patch information. Otherwise your registry won’t necessarily reflect the true state of patches applied to your system.
    There is still a benefit to having a fully patched Oracle Home before upgrading. By doing this you incur just a single downtime for your upgrade/patching. If you upgrade first and then apply the PSU later, then you’ll be bringing your database down to apply the PSU. And, the downtime in this case will be shorter than if you upgrade first, then install the PSU, and then apply the PSU later.
    Finally, applying the PSU to the Oracle Home before you upgrade will allow you to apply any other one-off patches you might need, ensuring that there aren’t any conflicts. It’s just easier to prepare the home first and upgrade/patch once, instead of stringing it out of separate upgrade, PSU, and patching sessions.

  4. Well, just when you think you know it all and it’s so simple, here’s a more detailed answer from our global technical support lead. The bottom line is: read the REAME for the PSU.
    Actually it depends on the PSU patch and is documented in the specific readme.
    Per the October PSU readme for
    2.3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of PSU in the Oracle Home
    These instructions are for a database that is created or upgraded after the installation of PSU
    You must execute the steps in Section, “Loading Modified SQL Files into the Database” for any new database only if it was created by any of the following methods:
    Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)
    Using a script that was created by DBCA that creates a database from a sample database
    So for upgrades and instances created via command line, no action is needed.
    For instances created using DBCA Templates you must run the following:
    ============================================================================================================= Loading Modified SQL Files into the Database
    The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
    1. For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows:
    cd $ORACLE_HOME/rdbms/admin
    sqlplus /nolog
    SQL> @catbundle.sql psu apply
    The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series PSU.
    For information about the catbundle.sql script, see My Oracle Support Note 605795.1 Introduction to Oracle Database catbundle.sql.
    2. Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors:
    where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 3, “Known Issues”.
    This has been known to change per PSU released so the readme is the source of truth in this case.
    And as always, it will not hurt to run these commands, but they are not needed in an upgrade.

  5. Great presentation, Roy. Thanks for coming out to California to do it.
    Unfortunately, the link takes me to a page “Dateien ansehen”, with one ghosted-out APEX 3.0 logo and link.
    The rest of the page is blank. No 11g presentation.
    Scott Brainerd
    Sr. Oracle Apps DBA
    Arbonne International, LLC

Leave a Reply

Your email address will not be published. Required fields are marked *

* Checkbox to comply with GDPR is required


I agree

This site uses Akismet to reduce spam. Learn how your comment data is processed.