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

Free Oracle Tips

HTML Text

 Home
 E-mail Us
 Oracle Articles



 Oracle Training
 Oracle News

 Oracle Forum
 Class Catalog


 Our Staff
 Our Prices
 Help Wanted!

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


 SQL Tuning
 Security

 UNIX
 Oracle UNIX
 Linux
 Oracle Linux
 Monitoring
 Remote help

 Remote plans
 Remote
services
 Oracle C++
 Oracle Java
 Apache
 JDeveloper
 App Server

 Applications
 Oracle Forms
 Oracle Portal
 11i Upgrades
 SQL Server
 Oracle Concepts
 HTML-DB Tips
 Software Help

 Remote Help  
 Development  

 Implementation


 Financials Training
 Oracle 11i
 Oracle Apps 11i
 Oracle Workflow
 Oracle AR 11i Class
 Oracle AP 11i class
 Oracle GL 11i class
 Oracle HR 11i class
 Oracle FA 11i class
 11i Project Mgt
 11i procurement
 11i collections


 Oracle Posters
 Oracle Books

 Oracle Tuning Book
 Oracle RAC Book
 Oracle Security
 Easy Oracle Books
 Oracle Scripts
 SQL Server DBA
 SQL Design Patterns
 WISE
 Excel-DB   


 BC Oracle News


 Rednecks!
 Dress code
 Arabian Stallion

 Burleson Arabians
 Guide Horses
 Don Burleson Blog
 Golf & Travel


 Privacy Policy
 

 

 

 
 

LOB CLOB BLOB, undo and PCTVERSION

Oracle Tips by Burleson Consulting

Oracle handles large objects (LOB) different than text-based table data.  In a traditional table, Oracle stores the data for in-flight transactions (previous values) in the UNDO segment, so that the transaction can be rolled-back in case of failure.  A shortage of UNDO causes the ORA-01555 error, but with BLOB storage we see the error "ORA-22924 snapshot too old".

Using the PCTVERSION parameter

With tables containing LOB's (CLOB, BLOB), we see a different mechanism whereby the previous image is stored within the data block itself (to ensure read consistency), and the PCTVERSION parameter governs this mechanism.

The default value for PCTVERSION is 10, meaning that 10% of the LOB storage space is reserved for UNDO.  The docs note:

"Specify the maximum percentage of overall LOB storage space used for maintaining old versions of the LOB. The default value is 10, meaning that older versions of the LOB data are not overwritten until they consume 10% of the overall LOB storage space."

The Oracle "LOB" storage clause lets you specify the LOB tablespace, storage in row, CHUNK and PCTVERSION settings as well as CACHE status, and if NOCACHE is specified whether the LOB storage should be LOGGING or NOLOGGING.  For example:

An example creation of a table using a BLOB datatype is shown in Listing 1. It just as easily could have been a CLOB.

create table internal_graphics (
  graphic_id number,
    graphic_desc varchar2(30),
    graphic_blob blob,
    graphic_type VARCHAR2(4))
    lob (graphic_blob) store as glob_store (
    tablespace raw_data
    storage (initial 100k next 100k pctincrease 0)
    chunk 4
    pctversion 10
   INDEX glob_index (
   tablespace raw_index))
   TABLESPACE appl_data
  storage (initial 1m next 1m pctincrease 0);
 
You can also specify PCTVERSION in a TYPE definition:
 
SQL> CREATE OR REPLACE TYPE clob_demo (
  2  clob_id       NUMBER,
  3  clob_value CLOB
  4 );
 
SQL> CREATE TABLE clob_table OF clob_demo
  5  LOB (clob_value) STORE AS clob_store (
  6  TABLESPACE raw_data
  7  STORAGE (INITIAL 100K NEXT 100K PCTINCREASE 0)
  8  CHUNK 4
  9  PCTVERSION 10
 10  INDEX clob_index (
 11  TABLESPACE raw_index))
 12  TABLESPACE appl_data
 12* STORAGE (INITIAL 1M NEXT 1M PCTINCREASE 0)
 

Using the RETENTION parameter

The PCTVERSION and RETENTION parameters both govern LOB storage rules for tables, but they are mutually exclusive and you may not choose both.

If you like Oracle tuning, see my book "Oracle Tuning: The Definitive Reference", with 950 pages of tuning tips and scripts. 

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.


    Need an Oracle Health Check?
  • Do you have bad performance after an upgrade?
     
  • Need to certify that your database follows best practices?

BC Oracle performance gurus can quickly certify every aspect of your Oracle database and provide a complete verification that your database is fully optimized.

 

 

 

 
 
 

Oracle performance tuning book

 

 

Oracle performance tuning software

 
Oracle performance tuning software
 
SearchOracle web site
 
Oracle performance Tuning 10g reference poster
 
Oracle performance tuning webcast
 
Oracle training in Linux commands
 
Oracle training Excel
 
Oracle training & performance tuning books
 

 

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


 

Copyright © 1996 -  2007 by Burleson Enterprises, Inc. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.


Hit Counter