Advanced compression for OLTP

If a new insert takes place on a compressed table will it go to the end of the table or to a new block.
Edited by: ahmed on Sep 21, 2010 12:20 PM

If you use DIRECT LOAD then it will, by definition, be placed above the high-water mark.
Probably not something you want to do one row at a time.

Similar Messages

  • How to specify COMPRESS FOR OLTP on a table in physical model?

    Hi,
    we have licensed Oracle's Advanced Compression and want to use the OLTP compression on some tables. I am looking for a way to specify COMPRESS FOR OLTP on a table in the physical model. So far, I can only set "Data Compression" to YES or NO.
    Are you going to add the "new" compression modes in the next release?
    Thanks,
    Frank
    Version of SQL Developer Data Modeler is 3.1.3.709

    Hi Frank,
    Are you going to add the "new" compression modes in the next release?There is support for compression type (including OLTP) in DM 3.3 EA and you can download it from OTN.
    Philip

  • Create Table with Compress for OLTP and error ORA-14464

    Hello,
    i have a Oracle-DB 11.2 and want to use Advanced Compression.
    I want to create a table:
    CREATE TABLE TD_GE_1990
    ( "name_id" NUMBER(1,0),
    "name_txt" VARCHAR2(100 BYTE)
    ) COMPRESS FOR OLTP;
    But i get:
    SQL-Fehler: ORA-14464: Kompressionstyp nicht angegeben
    The "compatible"-Parameter is set to 11.1:
    SELECT value
    FROM gv$parameter
    WHERE name LIKE '%compatible%';
    11.1.0.0.0
    Do i have to change something in the database?
    Best regards
    Heidi

    14464, 00000, "Compression Type not specified"
    // *Cause: Compression Type was not specified in the Compression Clause.
    // *Action: specify Compression Type in the Compression Clause.                                                                                                                                                                                                                                                                                                                                                                                   

  • Compress for OLTP and ORA-14464

    Hello,
    i have a Oracle-DB 11.2 and want to use Advanced Compression.
    I want to create a table:
    CREATE TABLE TD_GE_1990
    (     "name_id" NUMBER(1,0),
         "name_txt" VARCHAR2(100 BYTE)
    ) COMPRESS FOR OLTP;
    But i get:
    SQL-Fehler: ORA-14464: Kompressionstyp nicht angegeben
    The "compatible"-Parameter is set to 11.1:
    SELECT value
    FROM gv$parameter
    WHERE name LIKE '%compatible%';
    11.1.0.0.0
    Do i have to change something in the database?
    Best regards
    Heidi

    This post is related to following thread and got resolved by changing compatible parameter to 11.2.0:
    http://translate.google.co.in/translate?hl=en&sl=ko&u=http://kr.forums.oracle.com/forums/thread.jspa%3FthreadID%3D1594232%26tstart%3D345&ei=_u7QTKCwKIOfcbqxqdgL&sa=X&oi=translate&ct=result&resnum=2&ved=0CCMQ7gEwAQ&prev=/search%3Fq%3DORA-14464:%2BKompressionstyp%2Bnicht%2Bangegeben%26hl%3Den%26client%3Dsafari%26rls%3Den

  • HOW to enable oracle advance compression for EXIST partitioned table

    Hi All,
    I have to enable oracle advance compression for existing table which PARTITION BY RANGE then SUBPARTITION BY HASH.
    ORacle version: 11.2.0.2.0
    Please provide me any relevant doc or any exp.
    Thanks in advance.

    could not see any text for how to enable oracle advance compression for EXIST partitioned table.RTFM.
    From the resource above:
    How do I compress an existing table?
    There are multiple options available to compress existing tables. For offline compression, one could use ALTER TABLE Table_Name MOVE COMPRESS statement. A compressed copy of an existing table can be created by using CREATE TABLE Table_Name COMPRESS FOR ALL OPERATIONS AS SELECT *. For online compression, Oracle’s online redefinition utility can be used. More details for online redefinition are available here.
    "

  • Comparision of Advanced compression for DG with WAN optimization solutions

    Has anyone compared the compression ratio that Oracle's advance compression (for Data Guard) provides with a WAN optimization solution from CISCO or BIGIP (f5) - I will appreciate if you could share your results.

    I have not. That said Oracle compression and WAN optimization both use on data patterns for their compression. These algorithms are mature at this point and
    I don't believe either has an advantage.
    The rumor is Oracle is going to do more with Hardware Compression in the near future as the bottleneck appears to be brown round.
    Best Regards
    mseberg

  • Difference between " COMPRESS FOR ALL OPERATIONS" and "COMPRESS FOR OLTP"?

    I was looking through Oracle's OLTP Table Compression (11g onwards) documentation as well as online resources to find the syntax and came across two different versions:
    COMPRESS FOR ALL OPERATIONS
    and
    COMPRESS FOR OLTP
    The documentation I looked through didn't mention any alternative syntax, so i was wondering if anyone here might know the difference.
    Thank you!

    Table Compression Enhancements in Oracle Database 11G Rel1 as as follows:
    The compression clause can be specified at the tablespace, table or partition level with the following options:
    •NOCOMPRESS - The table or partition is not compressed. This is the default action when no compression clause is specified.
    •COMPRESS - This option is considered suitable for data warehouse systems. Compression is enabled on the table or partition during direct-path inserts only.
    •COMPRESS FOR DIRECT_LOAD OPERATIONS - This option has the same affect as the simple COMPRESS keyword.
    •COMPRESS FOR ALL OPERATIONS - This option is considered suitable for OLTP systems. As the name implies, this option enables compression for all operations, including regular DML statements. This option requires the COMPATIBLE initialization parameter to be set to 11.1.0 or higher.

  • Oracle compress with option FOR OLTP

    Hi
    I'm trying out compression on oracle but for unknown reason i cant use option "for oltp" (se below)
    any ideas  ?
    SQL> create table ct(x int) compr for oltp
      2  ;
    create table ct(x int) compr for oltp
    ERROR at line 1:
    ORA-00922: missing or invalid option
    SQL> create table ct(x int) compress;
    Table created.
    SQL> drop table ct
      2  ;
    Table dropped.

    There is no compr keyword, it's compress
    SQL> create table ct(x int) compr for oltp;
    create table ct(x int) compr for oltp
    ERROR at line 1:
    ORA-00922: missing or invalid option
    SQL> create table ct(x int) compress for oltp;
    Table created.
    Cheers Michael

  • Question about advance compression in Oracle 11gR2

    Hi,
    I am on Oracle 11gR2 on Solaris 10. I want to run the oracle advance compression advisor for my database and get compression ratios for the tables, how can I do it? I am looking for a sample command to run this advisor package (dbms_compression) from sqlplus.
    Can someone please suggest.
    Thanks,
    Nirav

    Thanks SriniChavali and Stefan. I can't make more answer "Helpful' so I couldn't do that for your answers! Here is my point. In Jonathan's blog i see this remarks:
    "Sadly it seems that “compress for OLTP” (formerly “compress for all operations”) doesn’t compress for all operations, it compresses only for inserts, and the benefits it has over basic compression are that (a) it leaves 10% of the block free for updates, and (b) it doesn’t require direct path inserts to trigger compression. Given the limitations on how it works you may find that the problems it brings might make it something you want to avoid.... this is at this link: http://allthingsoracle.com/compression-in-oracle-part-3-oltp-compression/
    To date I’ve only heard complaints about OLTP compression (there’s an element of self-selection there as no-one ever calls me to look at their system because it’s running so well and has no problems). A common thread in the complaints I have heard, though, is about the significant amount of row migration (once it has been noticed), the extra CPU, and ”buffer busy waits”.
    Compression for OLTP is (according to the manuals) supposed to be able to compress during updates – but it doesn’t (at least, as far as I can tell); this means that you can easily end up suffering a large number of row migrations on updates, which can result in extra random I/Os, buffer busy waits, and increased CPU and latch activity.
    If you can work out a good strategy for using OLTP compression, though, think carefully about making a choice between freelist management and ASSM – there seem to be some undesirable side effects that appear when you mix OLTP compression with ASSM."
    Note that I am not that technical and I hope I have not mis-quoted. I am trying to figure out if this is a good option or not and seeing some findings that it may not be so good and seeing at some other places notes that it is indeed very good.
    Best regards

  • Moving to advanced compression (11gR2)

    Hi all!
    I'm planning to migrate some schemas from a 10.2.0.4 database to an 11.2 database using datapump.
    At the same time i want to store the data in compressed format (compress for oltp - using advanced compression).
    What is the best way to achive this?
    I have tried a couple of different ways...
    1) Pre-create all tablespaces with compress.
    and then import with transform=segment_attribute:n:table
    Then all tables are imported with compression, but all objects ends up in the default tablespace for that schema, since the attribute removes the "tablespace" clause from the export file. This is not feasible since i have many partitions in different tablespaces.
    2) Pre-create all tablespaces with compress.
    and then import with transform=storage:n:table
    Then the tablespace clause is included but so is the NOCOMPRESS clause... so all tables are uncompressed after import.
    3) Pre-create all tablespaces with compress.
    Create a sqlfile with content=metadata_only and then edit the sqlfile replacing NOCOMPRESS with COMPRESS FOR OLTP.
    Then do an import with content=data_only
    This will give me the result i want, but is quite time consumuing..
    Is there another way i can do this, by just pre-creating tablespaces with compression and do regular import?
    Thank you very much in advance!

    that is pretty much option 3 you are suggesting, no?
    i'm creating a sqlfile with metadata only, but i have to remove the uncompress keyword from that file since table properties overrides the tablespace properties.
    I was looking for an easier way, but maybe i just have to do it that way.

  • Compressed table using oracle advanced compression but space is not release

    Dear Experts,
    I am using oracle 11.2.0.2 with sap as application
    I have compressed one of my largest indetified table "SWWCNTP0" as per below statement
    Alter table sapsr3.SWWCNTP0 compress for oltp;
    After this i have performed reorg for the above table but it doesnt released the space
    before reorg 39gb
    after reorg 39g
    Please advice
    Regards
    Navin Somal

    906078 wrote:
    Dear Experts,
    I am using oracle 11.2.0.2 with sap as application
    I have compressed one of my largest indetified table "SWWCNTP0" as per below statement
    Alter table sapsr3.SWWCNTP0 compress for oltp;
    After this i have performed reorg for the above table but it doesnt released the space
    before reorg 39gb
    after reorg 39g
    Please advice
    Regards
    Navin SomalHow did you go about doing the reorg?
    He's a simple working example ...
    ME_ORCL?create table to_compress as
      2  select * from all_objects
      3  union all
      4  select * from all_objects
      5  union all
      6  select * from all_objects
      7  union all
      8  select * from all_objects
      9  union all
    10  select * from all_objects;
    Table created.
    Elapsed: 00:00:16.74
    ME_ORCL?select bytes
      2  from dba_segments
      3  where segment_name = 'TO_COMPRESS';
                 BYTES
              44040192
    1 row selected.
    Elapsed: 00:00:00.06
    ME_ORCL?alter table to_compress compress for oltp;
    Table altered.
    Elapsed: 00:00:00.09
    --we don't expect any change here, because this only affects subsequent operations on the table, we need to MOVE the table to see any benefits in the existing data
    ME_ORCL?select bytes
      2  from dba_segments
      3  where segment_name = 'TO_COMPRESS';
                 BYTES
              44040192
    1 row selected.
    Elapsed: 00:00:00.08
    ME_ORCL?alter table to_compress move compress for oltp;
    Table altered.
    Elapsed: 00:00:01.08
    ME_ORCL?select bytes
      2  from dba_segments
      3  where segment_name = 'TO_COMPRESS';
                 BYTES
              14680064
    1 row selected.
    Elapsed: 00:00:00.02
    ME_ORCL?

  • 11.2 new features for OLTP compression, datapump compression

    Hi All,
    I am working related to datawarehouse and i am looking forward to impliment 11.2 new OLTP compression features. When i am reading some articles its telling me that i need seperate license for that. What about datapump compression and do i need license for that as well?
    Appriciate if some one can share any experience/links about this feature.
    I did some testing and it reduced the space nearly 50%. Hope this would be a great feature to look at.
    Karunika

    If you are working with a data warehouse, why do you want to use the new OLTP compression features? Normally, the older (and free) table compression functionality worked perfectly well for data warehouses.
    I believe that DataPump compression is part of the Advanced Compression Option which does require additional licensing. Straight table compression has been available for a while, though, does not require an additional license (beyond the enterprise edition, not sure if it's available in standard) and is generally ideal for data warehouses.
    Justin

  • Which tables are suitable for advanced compression in R12.1.1 vision db

    I want to use advanced compression in our R12.1.1 test env and I want to know which R12 tables are suitable for that?(I want make a script for compressing our VISION DB automatically)
    for example, table like GL% and ... ?
    some table contain long/long raw data_type ,so if I compress all tables in a tablespace(like APPS_TS_TX_DATA) ,filter long/long raw table will became a time-cosuming job..
    thanks

    Hi,
    for example, table like GL% and ... ?I believe this is no direct answer to your question as this depends on the number/type of records you have in your tables, and this varies from one organization/environment to another. You could calculate the size of the tables and decide which tables need compression by yourself.
    some table contain long/long raw data_type ,so if I compress all tables in a tablespace(like APPS_TS_TX_DATA) ,filter long/long raw table will became a time-cosuming job..Please see if these links help.
    Early Benchmarks: Using Advanced Compression with Apps 12
    http://blogs.oracle.com/stevenChan/2008/11/early_benchmarks_using_advanced_compression_with_ebs.html
    Using Advanced Compression with E-Business Suite Databases
    http://blogs.oracle.com/stevenChan/2008/10/using_advanced_compression_with_e-business_suite.html
    New Whitepaper: Options for Reducing E-Business Suite Database Sizes
    http://blogs.oracle.com/stevenChan/2008/12/whitepaper_options_for_reducing_ebs_database_size.html
    Regards,
    Hussein

  • Oracle Advanced Compression Option - Effect On RMAN Backup

    My client is interested in introducing Oracle's Advanced Compression capabilities into their 11g landscape. My questions are related to the effects RMAN Compression has on backup infrastructures. I need to understand the impact/reduction in Data Domain or tape that can be expected.
    1. What has been the experience with implementing RMAN Compression? Are there any lessons learned you can share?
    2. There are three levels of compression -- LOW, MEDIUM & HIGH. What compression ratios have you seen for any/all of these levels?
    3. Have you experienced any effects on server performance or any impact on database and backup functionality, when RMAN Compression is running?
    I would appreciate any insights you can share.

    Our main purpose for buying this option was OLTP compression. Just by this you can save tons of space(ofcourse it depends upon the type of data).
    With RMAN , in maximum compression mode ,your CPU usage will go high so make sure not to schedule the backup with heavy activities on the database.
    Page 10- 14 will help.
    http://www.oracle.com/technetwork/database/performance/global500acotwp0511final-396808.pdf

  • Basic vs Advanced Compression in Oracle 11g

    Hi,
    We are going to install Oracle 11gR2 in one new database server. Since the database will be used for Data Warehouse purposes and our company has rejected to pay licenses for "Oracle Advanced Compression", I wanted to know which options of "Basic Compression" are suitable for us, if we want to compress the biggest tables in our environment.
    Thanks in advance for your feedback.
    Regards,
    Rubén

    Hi;
    OAC mean you need to pay extra money to oracle. We are using basic compression in our env. Please check this search. Check first 4 links which is explain already how&what basic compress
    PS: This is installation related forum site. For your similar issue please use Oracle Discussion Forums » Oracle Database » General Questions forum part
    Regard
    Helios

Maybe you are looking for