Oracle GoldenGate and compressed tables [ID 1266389.1]

Oracle GoldenGate and compressed tables [ID 1266389.1]
		修改时间 17-JUN-2011 类型 HOWTO 状态 PUBLISHED

In this Document
Goal
Solution
References

---

Applies to:

Oracle GoldenGate - Version: 11.1.1.0.0 and later [Release: 11.1.1 and later ]
Information in this document applies to any platform.

Goal

Oracle GoldenGate and compressed tables

Solution

OGG does not support compressed tables or partitions, neither does it handle it well with proper error messages until OGG v10.4. We have several cases reported by customers when it deals with compressed tables. Sometimes it abends without any error message and sometimes with wrong messages. (ex: BugDB 10267584)

From V11.1.1.0.0, we enhanced the error handling part in BugDB 9425542, which gives meaningful error message on the compressed record before Extract abend. It will list out the table name, rowid and etc

Example :
ERROR OGG-01028 Record on table QATEST1.TAB1 with rowid AAM4EkAAEAACBguAAA from transaction 5.24.270123 (0x0005.018.00041f2b) is compressed. Compression is not supported.

However, due to bug 10063108, sometimes the error message on compressed tables are not entirely correct. This problem has been fixed in 11.1.1.0.3 and above

A table created as compressed will cause all of the DMLâs to go into compressed blocks on disk. If the user does an "alter table nocompress", every DML that goes into the table AFTER that point in time will be uncompressed. The query for compression will return "nocompress" now, but that simple "alter" does not change the already existing compressed blocks on disk that were created before the "alter". So to capture the records from a table which was compressed we need to do the following

SQL> alter table move nocompress;

This will touch every single block on disk and will uncompress everything and so OGG should be all good.

Sometimes customer has partitioned tables, even though they have un-compressed partitions, as long as there is any partition that is compressed, we canât support that. This could be verified by getting the full DDL for the table by running DBMS_METADATA.GET_DDL package. KM 965696.1.In case table partitions are compressed, Please run the below query and get the partition names & tablespace names.

SQL> SELECT partition_name, subpartition_name, tablespace_name, high_value FROM user_tab_subpartitions WHERE table_name = 'table_name';

Alter statement for partition to move nocompress.

SQL> ALTER TABLE MOVE PARTITION NOCOMPRESS TABLESPACE ;

Please ensure that you are having enough disk space within tablespaces before running the ALTER statement.

We will be adding full support of compressed tables in future release, however, in current V10.4 and V11.1.1.x, the only option is to comment the compressed table or exclude them in Extract(if you canât do a "move nocompress").

Listing some scenarios in which we have seen similar errors for compression --------------------------------------------------------------------------------------

1) The extract abends with the following error

GGS ERROR ZZ-0QY Failed to validate table .

However, if the table has been dropped immediately after creation, the Extract will only give out the object ID of the "compressed" table. To find out exactly what was the compressed table name, you could query GGS_DDL_HIST table if DDL replication is enabled. A sample query

select OBJECTID, OBJECTNAME, METADATA_TEXT FROM GGS_DDL_HIST WHERE OBJECTID = xxxxx

Once you find the table name, you have to exclude this table from both DDL and DML in Extract parameter file by using DDL EXCLUDE and TABLEEXCLUDE. Example

DDL EXCLUDE OBJNAME "TEST.DBMS_TABCOMP_TEMP_CMP"

TABLEEXCLUDE TEST.DBMS_TABCOMP_TEMP_CMP

Reference bugdb -- 10377296

3) There is another false positive warning in version V11.1.1.x. When we process regular table update followed immediately by a clustering table update. A bug in the code set the wrong flag for compressed table warning. This bug is being fixed in v11_1_1_0_11 and above.

Reference bugdb â 10308511

4) The extract getting abended with the following error when processing a cluster table.

ERROR OGG-01028 Record on table SCHEMA.TABLENAME with rowid AACprtAAIAAPPOYAB4 from transaction 50.5.8703098 (0x0032.005.0084cc7a) is compressed. Compression is not supported

The issue was resolved when doing a âalter grant any cluster to â

The issue is fixed in v11.1.1.0.29 (bug-12322319)

References

BUG:10063075 - EXTRACT ABENDS AS A TABLE IS CONSIDERED AS COMPRESSED WITH DDL PARAMETER
BUG:10063108 - V11.1.1.0 EXTRACT ABEND "RECORD ON TABLE IS COMPRESSED. COMPRESSION IS NOT SUPPO
BUG:10267584 - EXTRACT ABENDS WITH OUT OF ORDER SCN IN RAC ENVIRONMENT IN ORACLE 11G
BUG:10279456 - EXTRACT: OGG-01028 COMPRESSED TABLES ARE NOT SUPPORTED
BUG:10308511 - UNCOMPRESSED TABLE FAILS WITH A COMPRESSION ERROR
BUG:10377296 - EXTRACT FAILS ON COMPRESSED TABLES
BUG:12322319 - EXTRACT ABEND WITH COMPRESSION ERROR ON A CLUSTER TABLE

相关的 产品 Middleware > Data Integration > GoldenGate > Oracle GoldenGate 关键字 CLUSTER; COMPRESSION; GOLDENGATE; PARTITION; PARTITIONED TABLES; TABLESPACE 错误 ERROR HANDLING; 308511 ERROR; 26 ERROR

返回页首

[@more@]

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/161195/viewspace-1051581/，如需转载，请注明出处，否则将追究法律责任。

0

0

分享到：

上一篇： Oracle GoldenGate - Heartbeat process to monitor lag and performance in GoldenGate [ID 1299679.1]

下一篇： 检查asm磁盘组状态的视图v$asm_diskgroup

请登录后发表评论 登录

全部评论

<%=items[i].createtime%>

<%=items[i].content%>

<%if(items[i].items.items.length) { %>

<%for(var j=0;j

<%=items[i].items.items[j].createtime%> 回复

<%=items[i].items.items[j].username%>   回复   <%=items[i].items.items[j].tousername%>： <%=items[i].items.items[j].content%>

<%}%> <%if(items[i].items.total > 5) { %>

还有<%=items[i].items.total-5%>条评论 ) data-count=1 data-flag=true>点击查看

<%}%>

<%}%> <%}%>

msdnchina

注册时间：2008-07-30

• 博文量
  498
• 访问量
  1394645

最新文章

• 今天是邓世昌牺牲118周年纪念日，先发个帖子纪念下
• 今天是邓世昌牺牲118周年纪念日，特发本帖以示纪念
• 参数LOG_ARCHIVE_MIN_SUCCEED_DEST
• v$bgprocess --解释oracle db 后台进程作用的视图
• goldengate 认证矩阵matrix
• 日志挖掘是看不到谁在尝试密码的
• 各种*nix操作系统下查看网卡带宽 .
• Using Diagwait as a diagnostic to get more information for diagnosing Oracle Clusterware Node evicti
• 64bit client 与 32bit plsqldev是不兼容的
• Data Guard Switchover and Failover Best Practices

支持我们 作者招募 用户协议 FAQ Contact Us

北京盛拓优讯信息技术有限公司. 版权所有  京ICP备09055130号-4  北京市公安局海淀分局网监中心备案编号：11010802021510

广播电视节目制作经营许可证(京) 字第1234号 中国互联网协会会员

转载于:http://blog.itpub.net/161195/viewspace-1051581/