1 The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
3
<Insert Picture Here>
Agenda
• Oracle Support• All about Patches • Current Releases Patch Sets • Extended Dates• Recent Alerts & Issues • Questions
4
Oracle Support
• GCS – Global Customer Support; the analysts within Oracle Support that own and work on Services Requests
• • BDE – Bug Detection and Escalation; also part of Oracle Support, these are engineers who have
access to the source code to check for or confirm the existence of a bug•
• Sustaining Engineering – formerly known as DDR; the team within Development that creates patches
• • Base Development – the developers who work on the current and future versions of the
software, owning a small section of code each
• Advance Customer Services- “On site” engineers for large customers
5
Terminology
• Interim Patch this is the official name for a one-off patch
• Conflict – two or more bugfixes which modify the same source code files; if this is the case then only one can be applied, otherwise the code for the fixes will need to be “merged” to produce a new label
• Merge – a combination of labels; if for example you have two bugfixes which touch the same files then you would need to have those fixes merged together, producing one new patch with a new label
• Backport – also known as an OOB or One-Off Backport, this is a change or fix in a later piece of code which is then retrospectively applied as a patch to an earlier level of the code e.g. a fix in 11.1.0.7 might then be backported on top of 10.2.0.5 and made available as an interim patch
• Patchset - A patchset is a tested and integrated set of product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the target system”…
but that has changed in 11.2.0.2 see later slides
6
Terminology
• CPU – a Critical Patch Update; in essence a CPU is a bundle which is released quarterly and only
includes security-related fixes. CPUs are cumulative, so a later CPU will contain all of the fixes from an earlier CPU for the same patchset. CPUs are “molecular” which means groups of related fixes (“molecules”) can be excluded if they conflict with existing patches.
• PSU – a Patch Set Update; another bundle released every quarter, the PSU contains critical bug fixes
for its intended patchset. Again they are cumulative, so they contain all fixes from previous PSUs for the same patchset – they also include the CPU released on the same date. So for example PSUApr2010 includes CPUApr2010. There are very specific rules about which fixes can be included in a PSU; nothing that affects optimizer query plans can be included, nor anything that requires a configuration change. Port-specific bugs also cannot be included. Application of a PSU will increment the last digit of the release
number, e.g. PSUApr2010 for 10.2.0.4 results in the version becoming 10.2.0.4.4 • Overlay Patch – when a one-off interim patch conflicts with a PSU, an overlay patch is
required. This is basically a merge of the patch you want and the PSU; Development aim to provide these automatically so they shouldn’t actually be as much work as they sound.
7
New RDBMS Releases
• Oracle 11gR2 (11.2.0.1.0)(11.2.0.2)– Linux X86, – Linux x86-64– Solaris(SPARC) 64-bit– Solaris (X86-64)– AIX(PPC64) – HP-UX Itanium– HP-UX PA-RISC– Microsoft Windows 32 bit– Microsoft Windows 64 bit
http://www.oracle.com/technology/software/products/database/index.html
8
New Releases
• Oracle 11gR2 (11.1.0.7)– Windows Server 2008 32 & 64 bit
• Oracle 11gR1 (11.1.0.6.0) – Linux X86– Linux X86-64– Windows 32-bit, 64-bit– Solaris(SPARC) 64-bit– AIX(PPC64) – HP-UX Itanium– HP-UX PA-RISC
http://www.oracle.com/technology/software/products/database/index.html
9
Enterprise Manager
• 11.1.0.1.0 Enterprise Manager 11g Grid Control – Linux x86, Linux x86-64, – Solaris Sparc(64 bit), – HP-UX PA-RISC, HP-UX Itanium– AIX 5L– Windows 32 bit
• 10.2.0.5 Enterprise Manager 10g Grid Control Release 5– Patch release on top of 10.2.0.X– Linux x86. X86-64– Windows 32 bit– Solaris(SPARC) 64-bit – HP-UX PA-RISC– HP-UX Itanium– AIX 5L
http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html
10
Patch Releases
• 11.2.0.2 Latest PSU 11.2.0.2.1
– Linux x86, x86-64– Solaris x86-64– Solaris(SPARC) 64-bit– AIX(PPC64) – HP-UX Itanium, HP-UX PA-RISC– Microsoft Windows 32 bit, 64 bit– Client only Solaris X86-32 Solaris Sparc 32 bit, HP-UX
Itanium 32 bit, AIX 32 bit• Patch 10098816 • Full install, does not require base release• Primary upgrade method out of place upgrade• 34 New features in 5 different product areas• Reference Note 1189783.1
11
Patch Releases
• Oracle 11g 11.1.0.7 is Terminal releaseLatest PSU 11.1.0.7.6
– HP-UX Itanium– MS Windows 32bit, 64 bit– Sun Sparc 64 bit– Linux x86– HP-UX PA-RISC – IBM AIX– Linux x86-64– Patch 6890831
12
Patch Releases
Oracle 10.2.0.5
Latest PSU 10.2.0.5.2
– Linux 32 Bit
– Linux 64 Bit
– Linux system z
– Solaris X86-64 bit
– Solaris (SPARC) 64 bit
– HP-UX Itanium, HP-UX PA-RISC(64 bit)
– IBM AIX on Power Systems ( 64 bit)
– Windows (32 bit) ( 64 bit)
– Fujitsu BS2000/OSD (SX Series)
• Patch 8202632
Oracle 9i Patches– 9.2.0.8 Patch 4547809
13
Life Time Support Policy
• Life Time Support Policy – 11.2 Premier: Jan 2015, Extended: Jan 2018– 11.1 Premier: Aug 2012, Extended: Aug 2015– 10.2.0 Premier: 31-Jul-2010,Extended: 31-Jul-2013
– Free Extended for first year
– 10.1.0.x Premier: 31-Jan-2009,Extended: 31-Jan-2012
– 9.2.0.x Premier: 31-Jul-2007,Extended: 31-Jul-2010
• Sustaining: Indefinite applies to all above
New Lifetime support policy
http://www.oracle.com/support/lifetime-support-policy.html
Note 9i P1 fixes til July2012
14
Support Update - Status Notes
• Generic Server Support Status Notes
– 11.2.0 Note 880782.1– 11.1.0 Note 454507.1– 10.2.0 Note:316900.1
– 10.1.0 Note:263719.1
– 9.2 Note:189908.1
15
Support Update - Recent Alerts
• Install and Upgrade
– 11.2.0.2 Rootas.pl or Rootcrs.pl fails Note 1268390.1
– 11.2.0.2 Patches not found upgrading Grid Infrastructure Bug 10036834
– 11.2.0.1 Startup upgrade turns off recyclebin with spfile Bug 9768907
– 11.2 .0.1 Ownership of crsd traces change after patching script Bug 9837321
16
Support Update - Recent Alerts
• Install and Upgrade
– 11.2.0.1 DBUA Shared_Pool Too Small ( Sun sparc) Bug 9406095
– 11.1.0.7 Ora-1578 Blocks misplaced in ASM..compatible.asm < 11 and resize Note 965751.1
– 11.1.0.7 ASM rolling upgrade to 11.1.0.7 fails on RAC Note 742647.1
– 11.1.0.6 Various ora-600 errors during upgrade to 11g Note 579523.1
– 10.2.0.5 Upgrade fails on catupgrd.sql when Intermedia installed Bug 10091698
17
Support Update - Recent Alerts
18
Support Update - Recent Alerts
• Database
– Dictionary corruption / OERI from merge of PARTITIONS with LOBS11.1.0.7 to 11.2.0.1 Bug 9165206
– Corrupt blocks in 11.2 table with unique.key ORA-600[kdblkcheckerror] _in_memory_undo = FALSE Fixed in 11.2.0.1.2
Note 1078406.1
– Array Update can corrupt a row [kghstack_free1] or [kddummy_blkchk]10.2.0.1 to 11.1.0.7 Note 784633.1
– Ora-600:[kddummy-blkchk] after alter table allocate extent10.2.0.1 to 11.1.0.6 Note 564788.1
19
Support Update - Recent Alerts
• Database
– Data Blocks Misplaced in5 Node RAC ENV (ASM) rebalance Note 8339404.8 10.2.0.2 Fixed in 10.2.0.5
– Linux: Random node reboots in RAC induced by OCSSD Note 731599.1 11.1.0.7, 10.2.0.4 glibc
– Block change tracking on physical standby can cause incorrect backups11.1.0.7 ALTER DATABASE DISABLE BLOCK CHANGE TRACKING
Note 756435.1
– Wrong results (Null) from Select on compressed table Bug 7123643.8 11.1.0.6, 10.2.0.4:- one off’s available
20
Critical Patch Update
• Critical Patch Update – New process overview Note 290738.1
• Documentation tree Note 294914.1• CPU Jul 2009 Note 835649.1 • CPU Oct 2009 Note 881382.1• CPU Jan 2010 Note 967472.1• CPU Apr 2010 Note 1060989.1• CPU Jul 2010 Note 1089044.1• CPU Oct 2010 Note 1159443.1• CPU Jan 2011 Note 1263374.1
http://www.oracle.com/technology/deploy/security/alerts.htm
21
Patch Set Updates availability
• Server Technologies Product Release Dates - Note 742060.1 10.2.0.4 patching support finishes April 2011
• PSU Patchset updates Note 854428.1
– 11.2.0.2.1 Patch 10248523
– 11.2.0.1.4 Patch 10248516
– 11.1.0.7.6 Patch 10248531
– 11.1.0.7.6 for CRS Patch 10248535
– 10.2.0.4.7 Patch 10248636
– 10.2.0.5.2 Patch 10248542
22
Enterprise Manager
Schedule of Current Grid Control Patch Sets Note 793512.1
Enterprise Manager recommended patches Note 822485.1
11.1.0.1.2 OMS Patch 10270073
11.1.0.1.2 Agent Patch 10273607
10.2.0.5.4 OMS Patch 9786002
10.2.0.5.3 Agent Patch 9282414
23
Oracle Real Application Testing( RAT and SPA )
Real application Testing overview PDF
Real Application Testing for Earlier Releases Note 560977.1
SQL Performance Impact of Oracle 9i/10g Release 1 10g Release 2 upgrade with SQL Performance Analyzer.
Workload Analyzer
24
`
•Questions ???
Related Documents
