Basic - Oracle Edition Based Redefinition Presentation

Oracle Edition Based
Redefinition

Presentation for

http://surachartopun.com

Introduction
• Surachart Opun
• Blog: surachartopun.com
• Oracle ACE
• OCP 10G/11G and OCE (RAC)
• Member: OUGTH, IOUG, UKOUG, RAC SIG
• Twitter: @surachart


Edition Based Redefinition (EBR)?
• New Feature on 11gR2
• Upgrade an application while it is in use
• Edition object types
– SYNONYM
– VIEW
– All PL/SQL object types:
(FUNCTION,LIBRARY,PACKAGE and PACKAGE
BODY,PROCEDURE,TRIGGER,TYPE and TYPE BODY)


Three New Object Types
• Edition
– Replacing Edition object types (PL/SQL, synonyms,
and views)
• Editioning View
– Table is not an edition type. If you change the
structure of one or more tables.
• Crossedtion trigger
– Other users must be able to change data in the
tables while you are changing their structure
– If the pre- and post-upgrade applications will be in
ordinary use at the same time

Dictionary Views
• Edition
– dba_editions
– dba_edition_comments
• Editioning View
– dba_editioning_views
– dba_editioning_views_ae (edition_name)
– dba_editioning_view_cols
• Crossedition Trigger
– dba_triggers (crossedition)

What is an Edition?
• A nonschema object type, uniquely identified,
therefore, by just its name.
• Be able to check in DBA_OBJECTS.

select * from dba_objects where object_type=
’EDITION’;

• Every database from 11.2 onwards - Least one
edition.
• The default edition name is ORA$BASE

• A new edition must be created as the child of an
existing one.

create edition version2 as child of ora$base;

• An edition may have no more than one child.

ORA$BASE <- VERSION2 <- VERSION3 <- VERSION4

create edition version2 as child of ora$base;
create edition version3 as child of version2;
create edition version4 as child of version3;

SQL> select * from dba_editions;
EDITION_NAME PARENT_EDITION_NAME USA
---------------------- ------------------------------ ---
ORA$BASE YES
VERSION4 VERSION3 YES
VERSION2 ORA$BASE YES
VERSION3 VERSION2 YES


• A new database property, DEFAULT_EDITION.

alter database default edition = Some_Edition

SQL> select PROPERTY_NAME, PROPERTY_VALUE
from database_properties
where PROPERTY_NAME='DEFAULT_EDITION';
PROPERTY_NAME PROPERTY_VALUE
------------------------------ --------------------
DEFAULT_EDITION ORA$BASE


• A new alter session command allows the edition that
a session is using to be changed.

alter session set edition = Some_Edition

SQL> alter session set edition=version3;
Session altered.
SQL> SELECT SYS_CONTEXT
('userenv','current_edition_name') ce FROM DUAL;
CE
----------
VERSION3

Edition Privileges
• System Privileges
– CREATE ANY EDITION
– ALTER ANY EDITION
– DROP ANY EDITION
• Object Privileges - USE (not granted by default)
GRANT USE ON <edition_name> TO <user_name>;

• Roles
system privileges are granted to the DBA role (only).
• Enable Editioning
ALTER USER <user_name> ENABLE EDITIONS;


Edition Enabled Data Dictionary
Views
• AUD$ (obj$edition)
• DBA_EDITIONS (edition_name,
parent_edition_name)
• DBA_OBJECTS (edition_name)
• DBA_OBJECTS_AE (edition_name)
• DBA_SOURCE_AE (edition_name)
• DBA_USERS (editions_enabled)

• AE = All Editions

Edition Enabled Data Dictionary
Views
• FGA_LOG$ (obj$edition)
• UTL_RECOMP_ALL_OBJECTS (edition_name)
• V$LOGMNR_CONTENTS (edition_name)
• V$SESSION (session_edition_id)



SQL> SELECT * FROM DBA_EDITIONS;
------------------------------ ------------------------------ ---
ORA$BASE YES

SQL> CREATE EDITION VERSION2 AS CHILD OF ORA$BASE;
Edition created.

SQL> SELECT * FROM DBA_EDITIONS;
------------------------------ ------------------------------ ---
ORA$BASE YES
VERSION2 ORA$BASE YES

SQL> ALTER USER DEMO ENABLE EDITIONS;

SQL> GRANT USE ON EDITION VERSION2 TO DEMO;

SQL> connect demo/demo
Connected.

SQL> SELECT SYS_CONTEXT ('userenv','current_edition_name') ce FROM DUAL;

CE
--------------------------------------------------------------------------------
ORA$BASE

SQL> create or replace procedure my_procedure
as
Begin
dbms_output.put_line ( 'I am version 1.0' );
end;
/


SQL> ALTER SESSION SET EDITION=VERSION2;
Session altered.

SQL> create or replace procedure my_procedure
as
Begin
dbms_output.put_line ( 'I am version 2.0' );
end;
/

SQL> SELECT SYS_CONTEXT ('userenv','current_edition_name') ce FROM
DUAL;
CE
--------------------------------------------------------------------------------
ORA$BASE


SQL> exec my_procedure;
I am version 1.0

SQL> ALTER SESSION SET EDITION=VERSION2;
Session altered.

SQL> SELECT SYS_CONTEXT ('userenv','current_edition_name') ce FROM
DUAL;
CE
--------------------------------------------------------------------------------
VERSION2

SQL> exec my_procedure;
I am version 2.0


What is an Editioning View?
• Editioning view selects a subset of the columns from
a single base table.
• Use the SQL statement CREATE VIEW with the OR
REPLACE clause and the keyword EDITIONING.

CREATE OR REPLACE EDITIONING VIEW …

• Partition-Extended Editioning View Names


Editioning View Related Data
Dictionary Views
• DBA_EDITIONING_VIEW_COLS
• DBA_EDITIONING_VIEW_COLS_AE
• DBA_EDITIONING_VIEWS
• DBA_EDITIONING_VIEWS_AE
• DBA_ERRORS_AE (editioning_name)
• DBA_OBJECTS_AE (editioning_name)
• DBA_VIEWS (editioning_view)



SQL> CREATE EDITIONING VIEW ed01_tab AS SELECT name, tel_num FROM
ed01_tab_tmp;

SQL> select * from ED01_TAB partition (par_1);
NAME TEL_NUM
------------------------------ ----------
TEST1 1234567
TEST5 1234567

SQL> CREATE TRIGGER ed01_tab_tri
BEFORE INSERT ON ed01_tab FOR EACH ROW
BEGIN
null;
END;
/
Trigger created.


What is a Crossedition Trigger?
• A new, and special type of trigger specific to
editioning
• Can only be created on a table (not on an editioning
view)
• Propagates transactions between editions
• Two types
– FORWARD
– REVERSE


• Crossedition triggers are always created in the child
• Crossedition triggers are temporary—drop them
after you have made the restructured tables
available to all users.


Crossedition Trigger Types
• Forward Crossedition Triggers
– Only fired by code running in the parent edition
– Transforms from the old representation to the
new
• Reverse Crossedition Triggers
– Only fired by code running in the child edition
– Transforms from the new representation to the
old


Crossedition Trigger Related Data
Dictionary Views
• DBA_TRIGGERS
• DBA_TRIGGER_ORDERING
• DBA_ERRORS_AE (editioning_name)
• DBA_OBJECTS_AE (editioning_name)



CREATE TABLE PERSONS (ID NUMBER(10) NOT NULL, FIRST_NAME VARCHAR2(100)
NOT NULL, LAST_NAME VARCHAR2(100) NOT NULL,EMAIL VARCHAR2(100) NOT
NULL)
/

RENAME persons TO persons_tab;

CREATE EDITIONING VIEW persons AS
SELECT id, first_name AS firstname, last_name AS lastname, email FROM persons_tab;

create sequence persons_seq;


CREATE OR REPLACE TRIGGER persons_bi_trg
BEFORE INSERT ON persons FOR EACH ROW
BEGIN
:new.id := persons_seq.nextval;
END;
/

insert into persons values (null,'Somchai','A.','somchai@test.com');
commit;

ALTER TABLE persons_tab ADD (email_recipient VARCHAR2(100),email_domain
VARCHAR2(100));

SQL> select * from persons;
ID FIRSTNAME LASTNAME EMAIL
---------- --------------- --------------- --------------------
1 Somchai A. somchai@test.com


alter session set edition=VERSION2;

CREATE TRIGGER persons_fc_trg
BEFORE INSERT OR UPDATE ON persons_tab FOR EACH ROW
FORWARD CROSSEDITION
DISABLE
BEGIN
:new.email_recipient :=
regexp_substr(:new.email,'(.*)@',1,1,NULL,1);
:new.email_domain :=
regexp_substr(:new.email,'@(.*)',1,1,NULL,1);
END;
/


column CE for a10
SELECT SYS_CONTEXT ('userenv','current_edition_name') ce FROM DUAL;

CREATE OR REPLACE EDITIONING VIEW persons AS
SELECT id, first_name AS firstname, last_name AS
lastname,email_recipient,email_domain FROM persons_tab;


ID FIRSTNAME LASTNAME EMAIL_RECIPIENT EMAIL_DOMAIN
---------- --------------- --------------- -------------------- --------------------
1 Somchai A.


ALTER TRIGGER persons_fc_trg ENABLE;

DECLARE
c INTEGER;
r INTEGER;
BEGIN
c := dbms_sql.open_cursor;
dbms_sql.parse(
c => c,
statement => 'UPDATE persons SET email_domain = email_domain',language_flag =>
dbms_sql.native,
apply_crossedition_trigger => 'persons_fc_trg');
r := dbms_sql.execute(c);
dbms_sql.close_cursor(c);
COMMIT;
END;
/


---------- --------------- --------------- -------------------- --------------------
1 Somchai A. somchai test.com

---TEST FORWARD ---

alter session set edition=ORA$BASE;

update persons set email='surachart@gmail.com' where id=1;
commit;

---------- --------------- --------------- -------------------------
1 Somchai A. surachart@gmail.com


alter session set edition=version2;

---------- --------------- --------------- -------------------- --------------------
1 Somchai A. surachart gmail.com


---TEST REVERSE---

alter session set edition=version2;

CREATE TRIGGER persons_rc_trg
BEFORE INSERT OR UPDATE ON persons_tab FOR EACH ROW
REVERSE CROSSEDITION
DISABLE
BEGIN
:new.email := :new.email_recipient || '@' || :new.email_domain;
END;
/

alter trigger persons_rc_trg enable;

insert into persons values (null,'Surachart','O.','surachart',‘test.com');
commit;


---------- --------------- --------------- -------------------- --------------------
1 Somchai A. surachart gmail.com
2 Surachart O. surachart test.com

alter session set edition=ORA$BASE;

---------- --------------- --------------- ------------------------------
1 Somchai A. surachart@gmail.com
2 Surachart O. surachart@test.com


Learn More…
• Oracle Documents (E11882_01)


Learn More..
• Tom Kyte on Edition Based Redefinition


Learn More…
• Bryn Llewellyn's White Paper


Learn More…
• Morgan Library www.morganslibrary.org


Learn More…
• IOUG – Select Journal


Q&A


THANK YOU


Basic - Oracle Edition Based Redefinition Presentation

More Related Content

What's hot

Viewers also liked

Similar to Basic - Oracle Edition Based Redefinition Presentation

Basic - Oracle Edition Based Redefinition Presentation