ITPub博客

首页 > Linux操作系统 > Linux操作系统 > Extract or Replicat Fail to Start (Don't Start) With No Error Messages

Extract or Replicat Fail to Start (Don't Start) With No Error Messages

原创 Linux操作系统 作者:尛样儿 时间:2012-11-09 11:41:48 0 删除 编辑

Extract or Replicat Fail to Start (Don't Start) With No Error Messages [ID 1338582.1]
修改时间:2011-7-22类型:PROBLEM状态:PUBLISHED优先级:3

In this Document
  Symptoms
  Cause
  Solution


Applies to:

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

Symptoms

Extract or Replicat cannot start and there is either 
no report file or the report file does not contain diagnostic/error messages and ends abruptly 
or there is no relevant message in GoldenGate error log (ggserr.log).  
How to proceed in such cases ?

Cause

Many factors can cause extract or replicat in being not able to display error messages in the normal way, that is writing them down in the report file or the GoldenGate error log. 
These factors are potential reasons for such failures:
1) system resource issues, such as disk full. 
2) access/security issues such as not able to access certain directories like dirrpt, dirchk etc. 
3) abnormal process condition where an existing component is stopped by GGSCI but remains running or GoldenGate system files, such as those in dirpcs, dirchk files are not properly cleaned up. Subsequent starts fail because the new process conflicts with the old process.
4) GoldenGate system files are corrupted. 

Solution

Run extract or replicat from the Unix or Windows shell, such as the example shown:
> replicat paramfile dirprm/myrep.prm

The process will run and display all relevant information on the screen. The significant display can be found at the end. These diagnostics that cannot be found in the report file will be displayed on the screen. 
An example of a replicat having an issue with one of its GoldenGate system files is shown below:

ggsadm@spy3db:/users/ggsadm/ggs$ ./replicat paramfile dirprm/rep2.prm

Source Context :
SourceModule : [ggapp.util.pcs]
SourceID : ......
.....................
2011-07-14 05:03:50 ERROR OGG-01454 Unable to lock file "/users/ggsadm/ggs/dirpcs/REP2.pcr" (error 11, Resource temporarily unavailable). Lock currently held by process id (PID) 2731.

2011-07-14 05:03:50 ERROR OGG-01668 PROCESS ABENDING.

In the above example, rep2.pcr already exist and an orphan process is still running. These diagnostics can now be seen and action taken (kill the orphan process id). 


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

请登录后发表评论 登录
全部评论
Oracle数据库管理员,Oracle数据库系统构架员;2012年7月出版《构建最高可用Oracle数据库系统:Oracle 11gR2 RAC管理、维护与性能优化》一书;Oracle 10g OCM。

注册时间:2010-01-05

  • 博文量
    483
  • 访问量
    5650544