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 [ID 1338582.1]
修改時間:2011-7-22型別:PROBLEM狀態:PUBLISHED優先順序:3

In this Document
  
  
  

---

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 

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:

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:


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).