How to resolve a Lost Connection alert

February 12th, 2025

0 min read

A Lost Connection exception means some type of connection failure occurred between the enterprise server and the database server. This can lead to jobs starting in error, failed transactions, or even a JDE system shutdown.

The good news is that a Lost Connection may correct itself. Run a few tests by submitting jobs and pulling back data to see if this is the case. If your tests are unsuccessful, you can restart services to re-establish the connection.

Topics:

ERP Suites Clarity 23A

How to resolve a Lost Connection alert

Related Articles

How to resolve a Java Out of Memory alert

Clarity Dashboard

Log Monitor stopped collecting

Application Monitor

How to resolve a Server CPU Utilized per Instance alert

Log Monitor

Reinstalling/Updating the Clarity Collector

How to resolve a JDE Net Invalid Request Exception

Database Monitor stopped collecting

Batch Monitor stopped collecting

How to resolve an ORA-03113 alert

Installing the Clarity Collector

How to resolve a KNT000086 alert

How to resolve a Manual Open JDB Transactions alert

Exporting Reports in Clarity

Batch Monitor

Application Analytics

Finding expensive database queries

How to resolve a OCI0000064 alert

Maintenance Windows

Finding your slowest applications

How to resolve an ODB0000162 alert

How to resolve an ORA-03114 alert

How to resolve an OALL8 alert

How to resolve a [COULD NOT START SCHEDULER] alert