Page Comparison

If the Mine or Apply MINE or APPLY processes die for no apparent reason, then the following steps maybe able to assist in diagnosing the issue:

1. Check the log file for either Mine or Apply MINE or APPLY for appropriate messages
2. Check the memory usage for the Mine or Apply MINE or APPLY process. There maybe operating system limits in place and the operating system has killed the Mine or Apply MINE or APPLY process to enforce this. Example a watchdog process
3. Check APPLY (or MINE) cannot connect - connectivity issues
4. Check General Check
5. Restart the Mine or Apply MINE or APPLY process without the "–daemon" option so that all output is logged to the console. This can be done on Linux, Windows and Unix
6. Check operating system event logs or messages
7. Check temporary disk space
8. Check disks space used for the replication folder
9. Check Oracle alert log for any relevant messages
10. Ensure the Oracle archiver is not stuck (ORA-00257: archiver error)

If there is still no clear reason why the Mine or Apply MINE or APPLY process has died, then please contact Contact Dbvisit Support

The following information would assist Dbvisit support in trouble shooting the information:

• Support package for Mine or ApplyMINE or APPLY. See Contacting Support

• Trace file. Restart the process and create an Operating System trace file.

  This can be done with:

  On Linux and Unix:

  No Format
  kill -12 <process

  id> 

  id>

   

  On

  Linux and Unix 

  Windows:

  No Format
  dbvrep> DUMP MINE

  ALL 

  ALL

  On Windows

  No Format
  dbvrep> DUMP APPLY

  ALL 

  On Windows

...

• ALL