/***环境：***/
Oracle 9.2.0.8 on windows 64bit
Oracle goldengate 11.1.1.0.11
/**简单错误描述：**/
2012-10-21 07:58:15 WARNING OGG-00959 Oracle GoldenGate Manager for Oracle, MGR.prm: PURGEOLDEXTRACTS .
/dirdat/*,usecheckpoints, minkeepdays 7 (MINKEEPFILES option not used.).
对目标端ogg 重新初始化后，目标端mgr 进程会异常中断。复制进程正常
且手动重启，可以正常启动
Oracle 9.2.0.8 on windows 64bit
Oracle goldengate 11.1.1.0.11
/**简单错误描述：**/
2012-10-21 07:58:15 WARNING OGG-00959 Oracle GoldenGate Manager for Oracle, MGR.prm: PURGEOLDEXTRACTS .
/dirdat/*,usecheckpoints, minkeepdays 7 (MINKEEPFILES option not used.).
对目标端ogg 重新初始化后，目标端mgr 进程会异常中断。复制进程正常
且手动重启，可以正常启动
最终咨询原厂工程时候，发现这是一个在windows才会发生的bug，bug 号：13786241 （再次感谢oralce 刘相兵）
最终在mgr 进程参数中加入 nousethreads ，来尝试绕过该bug；
,(想来再windows 上oracle讲这个purge purgemarkhistory的任务交了不大靠谱的windows 线程来解决，因为thread 没有process这么耗资源，偏偏这线程不争气，最终无法完成purge，还导致mgr 进程 crash，所以 disable usethread后，oracle会去找一个相对安全但比较傻的进程做这个事情-----属个人猜想)
oracle bug 具体解释及解决方法如下：
RELEASE NOTES:
]]This is a manager bug that causes the manager to crash when the manager is ru
]]nning in threaded mode. The manager is running in threaded mode by default o
]]n Windows. On other platforms, the manager is in threaded mode if USETHREADS
]] is specified in the manager parameter. In addition to being in threaded mod
]]e, the manager has to have purge operations turned on such as purgemarkerhis
]]ink (i.e. userid scott@inst1). The symptom of the bug is that after a few ro
]]unds of purging of history (you can tell from the mgr report file), the manag
]]er will crash unexpectedly.
REDISCOVERY INFORMATION:
On Windows platform, or on other platforms and run manager with USETHREADS para
a system name, i.e. scott@inst1. In addition, the manager needs to specify pu
rging operations turned on such as purgemarkerhistory and pugeddlhistory. Once
the manager is up and running, after a few rounds of purging, the manager will
crash.
WORKAROUND:
Add 'NOUSETHREADS' in mgr parameter file to disable threading in mgr.
]]This is a manager bug that causes the manager to crash when the manager is ru
]]nning in threaded mode. The manager is running in threaded mode by default o
]]n Windows. On other platforms, the manager is in threaded mode if USETHREADS
]] is specified in the manager parameter. In addition to being in threaded mod
]]e, the manager has to have purge operations turned on such as purgemarkerhis
]]ink (i.e. userid scott@inst1). The symptom of the bug is that after a few ro
]]unds of purging of history (you can tell from the mgr report file), the manag
]]er will crash unexpectedly.
REDISCOVERY INFORMATION:
On Windows platform, or on other platforms and run manager with USETHREADS para
a system name, i.e. scott@inst1. In addition, the manager needs to specify pu
rging operations turned on such as purgemarkerhistory and pugeddlhistory. Once
the manager is up and running, after a few rounds of purging, the manager will
crash.
WORKAROUND:
Add 'NOUSETHREADS' in mgr parameter file to disable threading in mgr.
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/22907091/viewspace-746963/ ，如需转载，请注明出处，否则将追究法律责任。
请登录后发表评论
登录
全部评论
