1 may 2012 oracle spatial user conference. january 29, 2013 oracle, blythe valley park, solihull...
TRANSCRIPT
1
May 2012Oracle Spatial User Conference
January 29, 2013Oracle, Blythe Valley Park, Solihull
Presented by Rich Pitts - Senior Principal Support EngineerOracle Support
The Oracle bug life cycle and support process
This talk came from “Making the most of a Spatial upgrade(The bug Life Cycle)”
Ronald Reagan Building and International Trade Center Washington, DC USA
Program Agenda
• Oracle Support Overview
• Support Process – Bug Life Cycle
• A Quick look at Patch sets
• 11.2.0.3 interesting points to note & RAT
• Where to find help….
5
Oracle Premier SupportComprehensive Coverage for Your Oracle Database and other Oracle Products
Service and Support
Quickly diagnose and resolve issues
Tools and Resources
Get the most of your Oracle products with proactive services
Product Innovation
Keep pace with change and capitalize on new opportunities
6
My Oracle Support provides access to 30+ Database Communities
• A real-time multi-channel personalized support environment to share ideas, connect with peers and Oracle experts
• Rich Content:
• Best Practices
• Tips and tricks
• Whitepapers,
• Live and archived Webcasts and much more
• Anyone with access to My Oracle Support portal is automatically a community member
• Spatial
• Database Administration
• Database Backup and Recovery
• Database Install Unix and Linux
• Database Security Products
• Oracle Multimedia
• Oracle Text
• Patch Reviews - DB
• PL/SQL
• Pre-compilers and OCI
• Scalability RAC
• SQL Language
• Managing DB Memory & 4030/4031
• Storage Management
• Windows Oracle Data Access Components
• XML Database
7
Lifetime Support Policy – Database
Premier Support
Extended Support
Sustaining Support
R2
10.2
11.1
9.2
July 2010
July 2013
August 2012
August 2015
January 2015
January 2018
July 2007
July 2010
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
11.2
10.1
January 2009
January 2012
Indefinite
Indefinite
Indefinite
Indefinite
Indefinite
Open World 2011
May 2012 Location Intelligence Conference
Jan2013 RDBMS OUG Conference
8
Program Agenda
• Oracle Support Overview
• Support Process – Bug Life Cycle
• A Quick look at Patch sets
• 11.2.0.3 interesting points to note & RAT
• Where to find help….
• What BDE does…- Bug triage- Bug escalations & Technical
Management - Backport requests- Forum Participation
- Requests For Assistance (RFAs) for Service Requests (SRs)
- Knowledge Engineering- Severity 1 (P1) bug screening –
always someone on duty 24x7 days a week
Customer> Support> BDE> Development
In Server Technology BDE team - Senior Principal Support Engineer
Core RDBMS, Optimizer, RAC, ASM, Spatial began with MultiDimension at 8.1.7
Currently Global BDE Lead For Oracle Spatial and other complex content...
17 yrs
(Bug Diagnosis & Escalation)
10
Where are you ? Where should you be aiming?
Premier Support
Extended Support
Sustaining Support
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
R2
10.2
11.1
9.2
July 2010
July 2013
August 2012
August 2015
January 2015
January 2018
July 2007
July 2010
11.2
10.1
January 2009
January 2012
Indefinite
Indefinite
Indefinite
Indefinite
Indefinite
Spatial User Group 2012
11.2.0.4 Terminal due ?2013?
History (we hope)
**** Are you here? ****
Hopefully you’re HERE! 11.2.0.3.x
Jan2013 RDBMS OUG Conference
Open World 2012 -> Is the Future too cloudy?
11
The Bug Life Cycle – Fix in Main
Customer has a problem with
10.2.0.5
Opens a Service Request via MOS
(Which patch are you on)
Problem defined Support Tests 10.2.0.5 & 11.2.0.3BDE Tests
12.1.0.0 – Reviews
Passes to Development
Bug Visible on MOS
Fixed on Main
(Job Done)
12
When a bug does not reproduce
More work for BDE
Problem at 11.2.0.3
12.1.0.0 Does not reproduce...
Start to find the Fix
Diagnosis……
Many spatial bugs are tagged to aid rediscovery.
STACK Trace
Searching knowledge base, You can do this as well...
14
Bug Process: RFI’s, BLR’s & PSE’s
• In order to obtain a fix in the earlier release, i.e. 11.2.0.2
– BDE files a Base Label Request (BLR) for 11.2.0.2
• For the Version the customer has requested
– Automatically a Request For Inclusion (RFI) IE 11.2.0.4 is produced, (IF 12.1 was also production it would do a 12.1 RFI as well, we don't know where you will go next....
– A Merge Label Request (MLR) may be required once the BLR is produced.... ”opatch lsinventory –detail”
– FINALLY, a Patch Set Exception (PSE) for Customer’s platform is produced....
Terms and definitions
15
The Bug Life Cycle – Getting the fix
Patch produced
Customer Requests Patch for 11.2.0.2
BDE Files BLR For 11.2.0.2
&
RFI For 11.2.0.4
BDE Files PSE for Customer Platform
Development produce fixes
Fixed on Main
(Job Done)
16
An MLR example….
A requested fix plus a fix applied affecting the same modules.
Bug 5611025 is a
MLR of bug 5380055 4883174 4953737 5098050 4967266 4395779 5001975
1. rdbms/notes/backport.txt
2. rdbms/src/server/rcv/if/kcrr.h
3. rdbms/src/server/rcv/kcrf.c
4. rdbms/src/server/rcv/kcrfr.c
5. rdbms/src/server/rcv/kcrr.c
6. rdbms/src/server/rcv/krsf.c
7. rdbms/src/server/sqllang/parse/dbsdrv.c
8. rdbms/src/server/txn/if/ktucts.h
9. rdbms/src/server/txn/lcltx/ktb.c
Bug 5448688 is a MLR of bug 5181800
& bug 5191972
1. rdbms/notes/backport.txt
2. rdbms/src/server/rcv/if/kcrr.h
3. rdbms/src/server/rcv/kcrf.c
4. rdbms/src/server/rcv/krsl.c
5. rdbms/src/server/rcv/kcrr.c
6. rdbms/src/server/rcv/krsf.c
7. rdbms/src/server/rcv/if/krsf.h
8. rdbms/src/server/rcv/if/krsl.h
Green is No Clash
17
MLR to PSE
Finally PSE Filed to obtain a one-off fix for
Customer’s version on their particular platform.
Bug 5611025 is a MLR of bugs 5380055 4883174 4953737 5098050 4967266 4395779 5001975
Bug 5448688 is a MLR of bug 5181800
& bug 5191972
Bug 5616780 is a MERGE OF THESE MERGES! FINISHED status 35
1. rdbms/notes/backport.txt
2. rdbms/src/server/rcv/if/kcrr.h
3. rdbms/src/server/rcv/if/krsf.h
4. rdbms/src/server/rcv/if/krsl.h
5. rdbms/src/server/rcv/kcrf.c
6. rdbms/src/server/rcv/kcrfr.c
7. rdbms/src/server/rcv/kcrr.c
8. rdbms/src/server/rcv/krsf.c
9. rdbms/src/server/rcv/krsl.c
10.rdbms/src/server/sqllang/parse/dbsdrv.c
11.rdbms/src/server/txn/if/ktucts.h
12.rdbms/src/server/txn/lcltx/ktb.c
PSE BUG 5616781 filed ended at status 93
Should be status 90
18
Composite Patching
– Prevention of requesting unnecessary BLR/MLR/PSE’s due to fact that there is NO conflict at all towards the PSU in question
– The composite patch approach introduced starting from 11.2.0.2.7 + 11.2.0.3.2
– Conflict checking towards composite patchesAttempting a more automated apporachMake supports life easy opatch lsinventory –detail
19
Why are we introducing Composite Patches?
Currently Cumulative patches have several deficiencies.• Installing a new version of the patch requires a rollback of the currently
installed cumulative patch• All overlay patches must be rolled back when a new version is installed• Any overlay patches not included in the new cumulative patch must be
reapplied after they are recreated• It’s expensive and time consuming to recreate all the patches • Applying Cumulative patches is slow
20
When to use a base patch xx.x.0.x.0
• A PSU specific PSE (patch) should only be installed/made/ requested in case there is a conflict towards the PSU.
• In case of no PSU conflict at all the base version of the patch should be installed/used (11.2.0.3.0/11.2.0.2.0/…).
• KEEP IT SIMPLE
21
What are Composite Patches?
• A packaging format used for Cumulative patches
• A model to distinguish each new layer of a Cumulative patch• Replace only the parts of the patch that have changed and are not
currently installed on the system• Rollback only the parts of the patch that were previously installed• Reduce the need to roll back overlay patches• Improve patch apply performance
22
Life gets complex
11.2.0.2.1
11.2.0.2.2
11.2.0.2.3
11.2.0.2.4
23
Complexity
PSE A not conflicting with any PSU# => so base version of PSE 11.2.0.3.0MLR BC for which B conflicts with C and both not conflicting with any PSU# => so base version of MLR 11.2.0.3.0PSE D conflicting with PSU#1 => so PSU 11.2.0.3.1 neededPSE E conflicting with PSU#2 => so PSU 11.2.0.3.2 neededMLR FG for which F conflicts with G and G conflicts with PSU#4 implying that a FG MLR is needed on top of PSU#4 (which requires a PSU#4 BLR of F and G) => so PSU 11.2.0.3.4 version neededPSE H is an incorrect PSE, there is only a conflict with PSU 11.2.0.3.1 and no conflict with higher PSU’s, the correct version to install/request/… for this patch is a PSU 11.2.0.3.1 version
24
Windows does it differently
But can be as complex
11.2.0.2.1
11.2.0.2.2
11.2.0.2.4
11.2.0.2.3
Note 161549.1
25
Program Agenda
• Oracle Support Overview
• Support Process – Bug Life Cycle
• Quick look at Patch sets
• 11.2.0.3 interesting points to note & RAT
• Where to find help….
26
Terminal release of 10.2.0.5.x
• Fixes many of the 10.2.0.4 issues• If your on 10.2 STILL then you need to be on 10.2.0.5
Bug 8202632 - 10.2.0.5.0 See – Note 161818.1
R2
July 2010
July 2013
Indefinite
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
Premier Support
Extended Support
Sustaining Support
10.2
May 2012 Location Intelligence Conference
27
Terminal release of 11.1.0.7.x
• Architecture changes in 11.2 make back ports tricky if not impossible [SDO_ANYINTERACT fixes wont backport....]
A COMPLEX SDO_ANYINTERACT query performance
• 11.1.0.7 Elapsed: 00:41:43.74
• 11.2.0.2, 16 times faster! Elapsed: 00:02:30.27
Strongly advise move to 11.2.0.3 ASAP201
8
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
11.1August 2015
Indefinite
Premier Support
Extended Support
Sustaining Support
August 2012
May 2012 Location Intelligence Conference
Jan2013 RDBMS OUG Conference
28
Current Release of 11.2.0.3.X
•Fixes much of the 10.2, 11.1, 11.2.0.1 and 11.2.0.2 issues….•sdo_anyinteract 43 secs at 11.1.0.7 to 0.7 of a second•There are some important changes to Oracle Database Patch Sets starting with 11.2.0.2 (refer to Note 1189783.1 for details)•11.2.0.4 or 12.1 where will you go?
To infinity and beyond?201
8
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
Premier Support
Extended Support
Sustaining Support
January 2015
11.2
Indefinite
May 2012 Location Intelligence Conference
Jan2013 RDBMS OUG Conference
29
Optimizer!!! Constantly evolving…. Mass of fixes each release.
• Issues 10.2.0.5 and beyond testing will show• Slow Performance when using SDO_RELATE / SDO_FILTER (Doc ID 1268383.1)• Execution plans involving "bitmap conversion to rowids" and "table access full".• Cause Optimizer is not selecting the optimal plan.
This is being addressed in a future release
There is a workaround…
30
SDO_RELATE / SDO_FILTER (Doc ID 1268383.1) Workaround…
SQL> connect /as sysdba
SQL> alter session set current_schema=MDSYS;
SQL> DISASSOCIATE STATISTICS FROM INDEXTYPES spatial_index FORCE;
SQL> DISASSOCIATE STATISTICS FROM PACKAGES sdo_3gl FORCE;
SQL> DISASSOCIATE STATISTICS FROM PACKAGES prvt_idx FORCE;
Then be sure either flush the shared pool or bounce the database for the effects to take place
31
Consider Rapid Application Testing
• Been around a while – mature enough to use….
• “Record” production system as it runs…
• Great for peak loads… etc.
• Replay on test/upgraded system
• Patch, change statistics/base lines
• Replay again and again….
Difficult to test spatial systems….
32
Test results
Exadata 11.2 Exadata 11.2 (HCC) GDMS 11.2 PROD 11.1 -
100.00
200.00
300.00
400.00
500.00
600.00
700.00
800.00
36.86 37.53
81.19
674.55
Comparison of DB Time by Platform
DB Time (hrs)
33
Test results
Exadata 11.2 Exadata 11.2 (HCC) GDMS 11.2 PROD 11.1 -
10.00
20.00
30.00
40.00
50.00
60.00
70.00
80.00
90.00
100.00
14.66 18.18 18.04
85.73
Redo Generation by Platform
Redo Size (GB)
34
Program Agenda
• Oracle Support Overview
• Support Process – Bug Life Cycle
• Quick look at Patch sets
• 11.2.0.3 interesting points to note & RAT
• Where to find help….
IF you do nothing you might end up here.....
35
We don’t want you coming for an ORA-paddle
**** Use the MOS store ***
36
USEFUL Notes See – Note 161818.1
Oracle 11gR2 Upgrade Companion - 785351.1
37
THANK YOU
Q&A