Monday Jun 16, 2014

DBUA can ignore Underscores with "keepHiddenParams"

The Database Upgrade Assistant (DBUA) by default will remove all underscores and events before actually doing an upgrade. This is expected behaviour as we believe that underscores or events were meant to treat misbehaviour of the database just in a specific release only. And in our experience a nice collection of underscores will at least make your upgrades run slower.

Now with Oracle Database 11.2.0.4 and Oracle Database 12.1.0.1 the DBUA has a new parameter which can be used during startup:

$> dbua -keepHiddenParams

Then it will keep the hidden/underscore parameters during and after the upgrade.

-Mike 

PS: Many thanks to Mr. Frank Becker for highlighting this to myself - I wasn't aware of it - screenshot is courtesy from Mr Becker as well 

Friday Jun 13, 2014

Upgrade Workshops in Bucharest, Athens and Warsaw

Finally travel time is not over yet. There are 3 more workshops Upgrade, Migrate & Consolidate to Oracle Database 12c due to happen within the next few weeks:
.

Friday Jun 06, 2014

Save Upgrade downtime: Upgrade APEX upfront

With almost every patch or release upgrade of the Oracle Database a new version of Oracle Application Express (APEX) will be installed. And as APEX is part of the database installation it will be upgraded as part of the component upgrades after the ORACLE SERVER component has been successfully upgraded to the new releases.

APEXBut the APEX upgrade can take a bit (several minutes or even more in some cases). Therefore it is a common advice to upgrade APEX upfront before upgrading the database as this can be done online while the database is in production (unless your databases serves just as an APEX application backend - in this case upgrading APEX upfront won't save you anything).

To upgrade Oracle APEX upfront you'll have to follow
MOS Note:1088970.1.

It explains that you'll have to:

  1. Determine the installation type by running this query:
    select count(*) from <SCHEMA>.WWV_FLOWS where id = 4000;
    whereas <SCHEMA> can be one of the following:
    FLOWS_010500 1.5.X 
    FLOWS_010600 1.6.X 
    FLOWS_020000 2.0.X 
    FLOWS_020100 2.1.X 
    FLOWS_020200 2.2.X 
    FLOWS_030000 3.0.X 
    FLOWS_030100 3.1.X  
    APEX_030200 3.2.X 
    APEX_040000 4.0.X
    APEX_040100 4.1.X
    APEX_040200 4.2.X

    If the query returns 0 then you'll need to run apxrtins.sql
    If the query returns 1 then you'll need to execute apexins.sql

  2. Download the newest APEX package and install it.

-Mike

About

Mike Dietrich - Oracle Mike Dietrich
Master Product Manager - Database Upgrade & Migrations - Oracle Corp

Based near Munich/Germany and spending plenty of time in airplanes to run either upgrade workshops or work onsite or remotely with reference customers. Acting as interlink between customers/partners and the Upgrade Development.

Follow me on TWITTER

Contact me via LinkedIn or XING

Search

Archives
« June 2014 »
SunMonTueWedThuFriSat
1
2
3
4
5
7
8
9
10
11
12
14
15
17
18
19
20
21
22
23
24
25
26
27
28
29
30
     
       
Today
Oracle related Tech Blogs
Slides Download Center
Visitors since 17-OCT-2011
White Paper and Docs
Workshops
Viewlets and Videos
This week on my Rega/iPod/CD
Workshop Map
Upgrade Reference Papers