WARNING OGG-00952 Purging log history from OGG.GGS_DDL_HIST

最新推荐文章于 2022-03-17 18:13:19 发布
最新推荐文章于 2022-03-17 18:13:19 发布
阅读量4k 收藏 2
点赞数 1
分类专栏： GoldenGate Oracle TroubleShooting 文章标签： OGG-00952
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/zbdba/article/details/39313379
版权

经常在巡检OGG日志的时候发现如下警告：
2013-01-18 16:52:56  WARNING OGG-00952  Oracle GoldenGate Manager for Oracle, mgr.prm:  Purging log history from OGG.GGS_DDL_HIST older than 2013-01-13 15:52:56.084114: Could not delete rows from OGG.GGS_DDL_HIST, no database specified.
2013-01-18 16:52:56  WARNING OGG-00952  Oracle GoldenGate Manager for Oracle, mgr.prm:  Purging log history from OGG.GGS_DDL_HIST_ALT older than 2013-01-13 15:52:56.084261:Could not delete rows from OGG.GGS_DDL_HIST_ALT, no database specified.
2013-01-18 16:52:56  WARNING OGG-00952  Oracle GoldenGate Manager for Oracle, mgr.prm:  Purging log history from OGG.GGS_MARKER older than 2013-01-13 15:52:56.084448: Could not delete rows from OGG.GGS_MARKER, no database specified.

开始没有引起重视，后面发现OGG的表空间使用率渐渐升高。才觉得与这个有关系，于是上网查了资料。果然如此

引起这个警告的原因是，OGG做这个操作需要进入到数据库里面，所以我们需要在MANAGER里面加入如下参数：
USERID OGG,PASSWORD DFASDFASFASDADFAD,ENCRYPTKEY DEFAULT

MANAGER修改参数不需要重启进程，只用刷新进程即可：
refresh manager

重新监控OGG ggserr.log日志发现没有出现上述警告
WRH$_ACTIVE_SESSION_HISTORY未自动清理导致SYSAUX空间过度增长的处理方法
cpc84938的博客
02-25 1389
参考MOS文档： WRH$_ACTIVE_SESSION_HISTORY Does Not Get Purged Based Upon the Retention Policy (文档 ID 387914.1...
oracle wri$_adv_objects突增,Oracle19c手动清理PDB SYSAUX中的大对象如WRI$_ADV_OBJECTS (ORA-65040)...
weixin_42161450的博客
04-03 862
近期一客户19c RAC CDB数据库的SYSAUX表空间增长超大，分析原因为Optimizer statistics advisor特性导致的WRI$_ADV_OBJECTS对象记录数变多， 以下为清理方法。1, 找出最大对象SQL> set lines 120SQL> col occupant_name format a30SQL> select occupant_name,...
ORA-1653: unable to extend table GGS.GGS_DDL_HIST
charels
11-04 1296
1.表GGS_DDL_HIST由来 这张表是在GLOBALS里面参数DDLTABLE指定的，若是没有指定默认就是这个表名GGS_DDL_HIST 此表记录了被goldengate处理过的DDL，也就是通过goldengate同步到对端的DDL GGSCI (TEST)> EDIT PARAMS ./GLOBALS DDLTABLE GGS_DDL_HIST 2.定时清
OGG-00952---oracle goldengate无法purge历史表和mark表处理一例
01-18 382
今天观察oracle goldengate的errlog发现一直会有如下的告警信息： 2013-01-18 16:52:56 WARNING OGG-00952 Oracle GoldenGate Manager ...
oracle edit历史,OGG-00952---oracle goldengate无法purge历史表和mark表处理一例
weixin_40001967的博客
04-05 182
今天观察oracle goldengate的errlog发现一直会有如下的告警信息：2013-01-18 16:52:56 WARNING OGG-00952 Oracle GoldenGate Manager for Oracle, mgr.prm: Purging log history from OGG.GGS_DDL_HIST older than 2013-01-13 15:52...
OGG-00952 Could not delete rows from ogg.GGS_MARKER, no database specified.
zhuxiaoliao的专栏
01-28 1442
WARNING OGG-00952  Oracle GoldenGate Manager for Oracle, mgr.prm:  Purging log history from ogg.GGS_MARKER older than 2014-10-11 03:06:38.084645: Could not delete rows from ogg.GGS_MARKER, no database
OGG管理-清理ddl hist表
oradbm的博客
11-10 714
由于在11版本的ogg软件中ddl复制对hist表和mark表自动清理存在各种bug，取消对上述2个表的自动清理功能，使用如下脚本手工对数据进行清理。 sqlplus / as sysdba @ddl_disable.sql create table nm.histbak as select * from OGG.GGS_DDL_HIST where optime>to_char(sysdate- interval ‘2’ hour,‘yyyy-mm-dd hh24:MI:ss’); TRUNC
nextjs-cache-purging:通过设置自定义服务器来按需提供Next.js缓存无效的建议
05-09
Next.js缓存清除 介绍 ... 对于具有使用getStaticPaths预定义路由器的静态或静态生成的页面（在构建时），具有增量静态生成的页面（在首次请求时）或定义了revalidate参数的页面（在首次请求后，在后台，都会发生这种...
Laravel开发-attribute-purging
08-28
这就是“attribute purging”（属性清除）的概念，它允许开发者指定哪些模型属性在保存时应被忽略。本篇文章将深入探讨Laravel中的attribute purging特性，以及如何在实际开发中有效地运用这一功能。 首先，理解...
oracle重启后ogg不能同步了,OGG 状态正常但是数据不同步
weixin_35122994的博客
04-05 1493
补充extract信息> info allProgram Status Group Lag at ChkptTime Since ChkptMANAGER RUNNINGEXTRACT RUNNING DPE_SLSC 00:00:00 00:00:05EXTRACT RUNNING EXT_SLSC...
ggsa的自动释放历史垃圾日志
viviliving的专栏
08-03 284
$ more delggsa.sql delete from ggs_marker where sysdate - to_date(OPTIME, 'yyyy-mm-dd hh24:mi:ss') > 10; delete from GGS_DDL_HIST where sysdate - to_date(OPTIME, 'yyyy-mm-dd hh24:mi:ss') > 10; delete from GGS_DDL_HIST_ALT where sysdate - to_date(OP..
ERROR OGG-01232 Receive TCP params error: TCP/IP error 104 (Connection reset by peer), endpoint:
白元霞的博客
03-17 5259
解决办法1： 因源端与目的端的端口不一致导致， 源端的报错信息是 ERROR OGG-01232 Receive TCP params error: TCP/IP error 104 (Connection reset by peer), endpoint: 10.238.83.44:7847. 编辑进程，查看配置的端口 edit params 42P3 42P3是进程号 发现进程里配置的信息是rmthost 10.238.83.44 mgrport 7839,compress 与报错的端口不一致，修改
OGG-01232 问题解决
白及
05-22 4121
OGG-01232  Receive TCP params error: TCP/IP error 110 (Connection timed out). 2013-12-25 17:06:44  ERROR   OGG-01232  Receive TCP params error: TCP/IP error 113 (No route to host). 网
oracle ogg--ogg搭建过程中遇到的错误及处理
weixin_30856725的博客
06-21 2669
1 PRVF-0002 : Could not retrieve local nodename---# Begin Stacktrace #---------------------------ID: oracle.install.commons.util.exception.DefaultErrorAdvisor:37oracle.cluster.verification.Verificatio...
oracle goldengate报错解决之OGG-00446、OGG-00529、OGG-00014
weixin_34025051的博客
11-08 2132
OGG测试：无法启动ext进程，报错OGG-00446报错日志【截取重要部分】2016-10-2816:51:40ERROROGG-00446Missingfilenameopeningcheckpointfile. 2016-10-2816:51:40ERROROGG-01668PROCESSABENDING.日志意思很明显：在打开...
【OGG】OGG故障错误处理总结
小麦苗DBA宝典
07-23 7405
【OGG】OGG故障错误处理总结 第一章GoldenGate错误分析与处理 在维护GoldenGate过程中，由于各种意外情况，难免还...
Oracle To Mysql (Use Goldengate)
Database、Code
03-03 1782
安装环境： Source: OS:redhat 6.3 IP:192.168.56.60 DB:Oracle 11.2.0.4 Target: OS:redhat 6.3 IP:192.168.56.13 DB:Mysql 5.6.14 Goldengate for mysql： https://edelivery.oracle.com/EPD/Download/get_form?egr
OGG-01232 Receive TCP Params Error: TCP/IP Error 104 (Connection Reset By Peer).
woailyoo0000的博客
05-27 1466
ERROR OGG-01232 Receive TCP params error:TCP/IP error 104(Connection reset by peer),endpoint:192.168.247.16:7812 CASE： Extract/Pump uses STREAMING mode by default Most of the tcp-ip errors are treated fatal and results in an immediate abend. i.e. O...
oracle OGG-01232 Receive TCP params error:TCP/IP error 232(connection reset)
clm20482的博客
04-24 680
2018年4月24日，收到之前广州同事请求，说他们的源端库ogg的三个传输进程abend了，让协助排查下是什么原因。 环境信息： 源端操作系统：HPUNIX 源端数据库版本：oracle 11.2.0.4 rac ...
--set-gtid-purged
最新发布
03-31
SET GTID_PURGED is a MySQL system variable that is used to control the global transaction identifier (GTID) state of the server. It sets the list of purged transactions, which means that the server will not replicate any transactions that occurred before the specified GTID. When we set GTID_PURGED, we are telling MySQL that we are purging all transactions up to a certain point in time, and that all transactions before this point should not be replicated. This can be useful when we are setting up a new server and want to ensure that we only replicate data from a certain point forward. To set GTID_PURGED, we can use the following command: ``` SET GLOBAL gtid_purged='GTID1, GTID2, GTID3'; ``` Where GTID1, GTID2, GTID3 are the GTIDs that we want to purge up to. Note that setting GTID_PURGED incorrectly can cause replication issues, so it is important to ensure that we have the correct GTIDs before setting it.
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值