Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

If the MINE or Apply 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 APPLY for appropriate messages
  2. Check the memory usage for the MINE or Apply APPLY process. There maybe operating system limits in place and the operating system has killed the MINE or Apply 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 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 APPLY process has died, then please contact Contact Dbvisit Support

...

  • Support package for MINE or ApplyAPPLY. See Contacting Support
  • Trace file. Restart the process and create an Operating System trace file. This can be done with:

    No Format
    kill -12 <process id>

    On Linux and Unix



    No Format
    dbvrep> DUMP MINE ALL
    No Format
    dbvrep> DUMP APPLY ALL

    On Windows

...