<Insert Picture Here>

Oracle Support Update UKOUG AIM SIG 27th March 2012

Antony Higginson

2

<Insert Picture Here>

Agenda

•Oracle Support•New Releases

– Oracle Database– Enterprise Manager

•Patch Set Releases•Life Time Support Policy

– Extended Dates•Recent Alerts & Issues •Questions•Appendix

– Patch terminology

3

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.

4

Who Am I

•eSSC Engineer for Advanced Customer Services– Flagship of ACS Services in terms of services ACS offer– Reducing cost, risk and complexity of change, 24*7 support

• (Tech Lead) Financial, Central Government, Telco’s • Information Systems Engineering Background

– Internal Oracle tools to help deliver services that ACS Offer for RDBMS/Exadata/FMW

– Patching– Configuration – Performance

•First Time speaker at UKOUG DBMS SIGs

5

Oracle Support

• GCS – Global Customer Support; the analysts within Oracle Support that own and work on Service 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, each owning a small section of code

• ACS - Advanced Customer Services; mission critical support services for complex IT environments to help maximize performance, achieve higher availability and reduce risk

6

New RDBMS Releases

•Oracle 11gR2 (11.2.0.1)– 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– zLinux64 (11.2.0.2 full release)

http://www.oracle.com/technology/software/products/database/index.html

7

New RDBMS Releases

•Oracle 11gR1 (11.1.0.7)– Windows Server 2008 32 & 64 bit

•Oracle 11gR1 (11.1.0.6) – 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

8

New Enterprise Manager Releases•12.1.0.1 Cloud Control

Important: Please refer to My Oracle Support Note 1395505.1 for instructions on How to install Bundle Patch1 and update to 12.1.0.2 Plug-ins. This is a must-read note.

– for Linux x86 (32-bit) (With Bundle Patch 1)– for Linux x86-64 (64-bit) (With Bundle Patch 1)– for Solaris Operating System (SPARC) – for Solaris Operating System (x86-64) – for IBM AIX on POWER Systems (64-bit)

•11.1.0.1.0 Grid Control – Linux x86, Linux x86-64, – Solaris Sparc(64 bit), – HP-UX PA-RISC, HP-UX Itanium– AIX 5L– Windows 32 bit

http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html

9

RDBMS Patch Set Releases

•11gR2 11.2.0.3– 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– Linux on System z– S/390 based Linux– Client only Solaris x86-32 Solaris Sparc 32 bit, HP-UX

Itanium 32 bit, AIX 32 bit• Patch 10404530• Full install, does not require base release Note 1189783.1

10

RDBMS Patch Set Releases

•11gR1 11.1.0.7 (Terminal release)

– HP-UX Itanium– HP-UX PA-RISC – MS Windows 32bit, 64 bit– Sun Sparc 64 bit– Linux x86– Linux x86-64– IBM AIX

• Patch 6890831

11

RDBMS Patch Set Releases

•10gR2 10.2.0.5 (Terminal release)

– 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) + Itanium –Fujitsu BS2000/OSD (SX Series)

• Patch 8202632

12

Enterprise Manager Patch Set Releases

Release Schedule of EM Releases / Patch Sets Note 793512.1

Enterprise Manager recommended patches Note 822485.1

12.1.0.1 BP1 OMS - see Note 1395505.1 Unix Agent - see Note 1395505.1

11.1.0.1 PSU6 OMS Patch 13248190 Unix Agent Patch 9346243

13

Patch Set Update (PSU) Availability

• Oracle Database Support Newsletter - Issue March, 2012 Volume 14 Note 230.1

• Quick Reference to Patchset / PSU Numbers Note 753736.1

• Reference List of Critical Patch Update Availability(CPU) and Patch Set Update (PSU) Documents For Oracle Database and Fusion Middleware Product

Note 783141.1

• PSU Patchset updates Note 854428.1

• Oracle Recommended Patches -- Oracle Database Note 756671.1

• Database PSU-CPU Cross-Reference List Note 1119703.1

14

Life Time Support Policy

•RDBMS 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 Support ended July 2011– 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/us/support/lifetime-support/index.htmlNote 9i P1 fixes until July2012

15

Itanium Processor and Oracle Database Software

• After multiple conversations with Intel senior management Oracle has decided to discontinue all software development on the Intel Itanium microprocessor. Intel management made it clear that their strategic focus is on their x86 microprocessor and that Itanium was nearing the end of its life.

• Press Release• Oracle Software and Support for Itanium-Based Servers

Note 1313431.1

16

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

17

Critical Patch Update (CPU)

•Critical Patch Update – New process overview Note 290738.1

• Documentation tree Note 294914.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 • CPU Apr 2011 Note 1291877.1 • CPU Jul 2011 Note 1323616.1 • CPU Oct 2011 Note 1346104.1 • CPU Jan 2012 Note 1374524.1

http://www.oracle.com/technology/deploy/security/alerts.htm

18

Support Update - Recent Alerts

• Install and Upgrade

– Essential Steps to take before Upgrading to 11.2.0.3 Grid Infrastructure/ASM/Exadata Note 1363369.1

– ORA-600 [KKPO_RCINFO_DEFSTG:OBJNOTFOUND] On 11.2 Databases After Upgrade Note 1308400.1

– 11.2.0.2 Roothas.pl or Rootcrs.pl fails Note 1268390.1

– 11.2.0.2 Patches not found upgrading Grid Infrastructure Bug 10036834

– MRP0 ORA-328 on switchover to standby after upgrade to 11.2.0.2 Fixed in 11.2.0.2.3 Note 11664046.8

19

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 existing datafile resized

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

20

Support Update - Recent Alerts

•Database– Join of temp and permanent tables in RAC might cause corruption of

permanent table11.2.0.3 Note 13467683.8

– ORA-604 ORA-959 on object with Deferred Segment Creation11.2.0.3 Note 1390632.1

– ORA-600 or Data Corruption possible during shutdown normal/transactional/immediate of RAC instances in a rolling fashion 11.2.0.2 Note 1318986.1

– ORA-600 [2015] during transaction rollback in undo block for COMPRESS table11.1.0.6 to 11.2.0.2Note 1191474.1

21

Support Update - Recent Alerts

•Database

– Logical corruption of LOB data during recovery 10.1 to 11.2 Fixed in 11.2.0.2 Note 1206814.1

– Segment header corruption if extent allocation operation is interrupted 9.2 to 11.2 Fixed in 11.2.0.2 Note 1229669.1

– ORA-25027 ORA-4097 in plugged datafile after CREATE CONTROLFILE in 11g 11.1.0.6 to 11.2.0.1 Fixed in 11.2.0.2 Note 1066229.1

– RFS in standby with a wrong location for archive log corruption/overwriting datafiles when max_connections > 1

10.2 to 11.2 Fixed in 11.2.0.2 Note 1081961.1

22

Support Update - Recent Alerts

•Database

– Dictionary corruption / OERI from merge of PARTITIONS with LOBS11.1.0.7 to 11.2.0.1 Fixed in 11.2.0.2

Bug 9165206

– Corrupt blocks in 11.2 table with unique.key ORA-600[kdblkcheckerror] _in_memory_undo = FALSE Fixed in 11.2.0.1.3

Note 1078406.1

– Array Update can corrupt a row [kghstack_free1] or [kddummy_blkchk]10.2.0.1 to 11.1.0.7 Fixed in 11.2.0.1Note 861965.1

– ORA-1578 - Blocks can be misplaced in ASM during a REBALANCE 10.2.0.2 Fixed in 10.2.0.5

Note 8339404.8

23

Other notes

• System Change Number (SCN), Headroom, Security and Patch Information Note 1376995.1

• Pre 11.2 Database Issues in 11gR2 Grid Infrastructure Environment Note

948456.1

24

Q&A

&Q U E S T I O N SA N S W E R S

25

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

26

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.