Oracle 11g New Features Out-of-the-Box by Alex Gorbachev (from Sydney Oracle Meetup #5)
30 likes2,538 views
The document discusses the new features and enhancements of Oracle 11g, including improvements in Automatic Storage Management (ASM), Recovery Manager (RMAN), and Data Guard. It highlights usability changes, such as enhanced backup performance, new commands, and advanced security features like tablespace encryption and password management. Overall, the presentation outlines significant upgrades aimed at boosting productivity and performance for database management.
Editor's Notes
- #3: Pythian provides database services and consulting for Oracle, MySQL and SQL Server as well as EBS support and SA services. I’m been with the company for almost 3 years - in Sydney since September 2008 heading our operations in East Asia Pacific. We are a global company with main offices in Canada, the US, Europe and Australia. Over 12 years of operations, we have served 400+ clients and currently we have 100+ active clients world-wide.
- #4: Ask your questions right away - too many different topics
- #5: Not finished
- #6: Not finished
- #7: Not finished
- #8: Association - warehouse Introduced in 10g and surprisingly stable Based on old technology
- #9: INTRO - ASM and RDBMS - for ASM instances and for DB compatible init.ora parameter. ASM compat - metadata format. RDBMS compat - files content format. Default 10.1 - no new features. Defined per disk group. Case study - upgrade to 11g & downgrade, smooth upgrade path, transportable tablespaces. select i.ksppinm, v.ksppstvl from x$ksppi i, x$ksppcv v where i.ksppinm in ('_rdbms_compatibility','_asm_compatibility') and i.indx=v.indx;
- #10: 1. start rolling migration 2. upgrade all instances one by one ASM provides limited services 3. stop rolling migration
- #11: AU - smallest chunk of space that Oracle can allocate; coarse stripe size problem - inflexible physical layout + high overhead for VLDB 10g - underscore parameter - instance-wide + undocumented/unsupported 11g - official way to change AU size per diskgroup. AU 1-8 MB - compat 10.1 but 6-64 MB - compat 11.1. Fine striping is not changed!
- #12: Fully automatic. Explain how it works. Main purpose - reduce overhead on disk mount and file open for huge files, sga overhead for extent maps.
- #13: 10g - disk failure -> BROKEN & rebalancing 11g FMR - disk failure -> OFFLINE -> wait for disk_repair_time (3.6h default) -> rebalancing if too log or ALTER DISKGROUP DISK ... ONLINE; * can do manual ALTER DISKGROUP DISK ... OFFLINE; FMR - case study SAN firmware update, FMR - case study extended clusters FB - case study - rebalancing takes days and impacts performance but night can be offline
- #14: Case study - extended clusters - in addition to Fast Mirror Resync
- #15: cp - doesn’t work for controlfiles but works for datafiles and spfle; strange path copying to ASM remap - ASM detects corruption on read and re-allocates extent. remap causes ASM to read blocks and repair if needed. md_backup/md_restore - can re-create DG on disks and directory structure
- #18: * lighter compression * multisection backup (max 256 sections) * UNDO backup optimization - CONFIGURE BACKUP UNDO OPTIMIZATION
- #19: Use case - recovery window of 7 days + monthly for one year KEEP FOREVER - requires catalog Deletion policy shipped is new in 11g DB_NIQUE_NAME - useful for standby
- #21: ADVISE - human language; REPAIR .. PREVIEW - script CHANGE - change priority, close
- #23: FROM ACTIVE DATABASE - no UNTIL clause - time is chosen automatically based on the last datafile copy completed PASSWORD FILE - by default for standby and optional for normal duplicate.
- #27: Use case for Active Data Guard - use DR for reporting without RTO impact, management is happy - DR hardware is utilized! RTO = Recovery Time Objective - how quick we can recover. Use case for snapshot - testing 1. convert to snapshot 2. test on it (database diverges) 3. convert to physical standby
- #28: DB_UNIQUE_NAME - unsure that no standby has the same DB_UNIQUE_NAME as primary
- #32: Invisible indexes are maintained as usual by all DML’s but not used by CBO by default.
- #33: Old way - add NULL column, updated NULLs, change to NOT NULL
- #34: Doc says 1000000=infinity. To test - wait 11+ days
- #36: Can also do FK Redesign physical data and keep referential integrity
- #37: I did a test in single process - no visible difference Behind the scene does the same!
- #49: Laurent Schneider has interesting blog post about case-sensitive passwords
- #50: Purge?