Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

Oracle versioning tips

Oracle Database Tips by Donald BurlesonFebruary 1,  2015

 

One nice feature of pre-relational databases (IDMS) was the ability to create versions of data dictionary entities.  You could create versions of table definitions, table columns, as well as code versions, all managed and controlled within the database.

The lack of version support has been sorely missed, and it looks like Oracle 11g may be posturing themselves to implement versioning in Oracle 12g:

See editionable object tips

The Oracle 11g documentation notes that versioning may be called "edition-based" redefinition:

"Edition-based redefinition is not available in Oracle Database 11g Release 1 (11.1).

You cannot create an edition, an editioning view, or a cross-edition trigger; nor can you use the ENABLE EDITIONS clause in the CREATE USER and ALTER USER commands. "

Alex Fatkulin (the Oracle internals guru and heir-apparent to Steve Adams) has noted some preliminary internals for this edition-based Oracle versioning, and notes that there is a new object_type called "_current_edition_obj":

select
   object_type
from
   dba_objects
where
   object_name='_CURRENT_EDITION_OBJ';
 
OBJECT_TYPE
-------------------
VIEW

At this time, it appears that critical objects for versioning (table columns, tables) are not supported and that versionable objects only include assembly, function, library, package, package body, procedure, synonym, trigger, type, type body and views.

The ability to do version control within the Oracle database will bring them into the technology of the 1980's, and finally allow Oracle DBA to manage and control versions of schema objects, just like we did with IDMS back in the 1980's.


 

   

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.