The document discusses edition-based redefinition in Oracle databases, enabling high availability and reducing downtime during upgrades and application maintenance. It outlines the process of managing editions, including creating new objects, modifying existing ones, and ensuring normal operations during cut-overs. Best practices for applications accessing tables and managing editions are also highlighted, emphasizing the benefits of fine-grained dependency tracking and uninterrupted operations.

2. Edition Based RedefinitionAlex Nuijten

3. High Availability

4. 24/7

7. Unplanned DownPlanned Down

8. High Availability

9. RACPhyiscal StandbyLogical StandbyImmunityHardware Failure

10. Logical StandbyStreamsOnline Database Upgrade

11. Online Table RedefinitionOnline Index RebuildOnline Application Maintenance

12. Edition Based RedefinitionOnline Application Upgrade

13. Application Upgrade

14. Application Upgrade

15. Application Upgrade

16. Application Upgrade

17. Application Upgrade

18. Application UpgradeCreation of New ObjectsChanging Existing ObjectsDrop Redundant ObjectsConvert / MigrateResume Normal Operation

21. Restructuring A12Build new road next to current one (A12-B)Same “functionality” as the old roadAt the cut-over momentOpen new A12-B: Newly arriving traffic travels on temporary roadClose A12 (original)Cars already on old road keep going

22. 11gR2 EBR is similarPrepare New ReleaseConstruct in ParallelOperations in Existing Application Continue NormallyFrom the cut-over point:New Sessions Operate on New ReleaseExisting Sessions continueon Existing Release

23. New DimensionBase ReleaseRelease 2

24. Base ReleaseRelease 1New Dimension

25. Parallel UniversesObject TypeObject NameSchemaEditionSession run in context of Edition

26. Editionable Objects

27. Non Editionable Objects

28. Application BApplication AEnameJobMgrSalCommHiredate

29. Application AApplication BEditioning ViewEnameJobMgrSalCommHiredate

30. preUpgradepostUpgradeEditioning View

31. “EditioningViews:the New Tables”

32. Application AApplication BEdition R1Edition R2EV EMPEV EMPEnameJobMgrSalCommHiredate

33. Application AApplication BEdition R1Edition R2EV EMPEV EMPEnameJobMgrSalCommHiredateLanguage

34. DMLEV EMPEdition R1Edition R2EV EMPEV EMP…* languageEnameJobMgrSalCommHiredateLanguage

35. DMLDMLEV EMP…- enameo first_name* last_nameEdition R1Edition R2Edition R3EV EMPEV EMP…* languageEnameJobMgrSalCommHiredateLanguageLast_nameFirst_name

36. DMLEV EMPForward CrossEdition Trigger…- enameo first_name* last_nameEdition R1Edition R3EV EMPEnameJobMgrSalCommHiredateLanguageLast_nameFirst_name

37. DMLEV EMPReverse CrossEdition Trigger…- enameo first_name* last_nameEdition R1Edition R3EV EMPEnameJobMgrSalCommHiredateLanguageLast_nameFirst_name

38. Parallel Application VersionsApplication XVERSION 1Application XVERSION 2Release 2Release 1Base Release

39. Version 1 on Base Edition

40. Upgrade Base to Release 2AuthorsNew columns COUNTRY and BIOGRAPHYBooksDrop column NUM_OF_PAGESModified column ISBN (10 to 20 characters)New columns LANGUAGE and PUBLICATION_YEAR

41. Version 2 on Edition Release 2

42. Version 1 on Edition Release 2

43. Version 2 on Base Edition

44. Preparing your ApplicationIn 6 easy steps

48. Oracle guarantees:The Execution Plan for a SQL query that uses an Editioning View is identical to that for the same query based directly on the table

49. PrivilegesCREATE ANY EDITIONALTER ANY EDITIONDROP ANY EDITIONALTER USER ENABLE EDITIONSGRANT USE ON <EDITON> TO <USER>ALTER DATABASE DEFAULT EDITION <edition>

50. Dictionary Views*_EDITIONS*_EDITION_COMMENTS*_VIEWS_AE*_SOURCE_AE*_OBJECTS_AE*_ERRORS_AE*_EDITIONING_VIEWS_AE*_EDITIONING_VIEW_COLS_AE

51. “Best Practices”Applications never access TablesApplication sets Edition

52. TidbitsDrop Object stops InheritanceEditions can have one childNo branching (yet)DBMS_SQL.PARSE in specific EditionOnline Table RedefinitionFine Grained Dependency Tracking