Troubleshooting Transaction Surveillance

Cannot view rule definition

  • Check that the IRTSVCOL.ini* file exists

  • Check that the IRTSVCOL.ini* file is not already open

* IRTSVCOI for Transaction Surveillance on HPE NonStop

No exceptions get raised

  • Check WVLOG for errors.

  • Check the rules.

  • Check the TRANSACTION-LOG-LOCATION configurations in the IRTSVCOL* ini file.

  • Using Transaction Surveillance check back through all recent previous transactions and ensure the data is as expected.

  • Use IRTSVTST to offline process the data and debug the rules.

Some exceptions get raised

  • Check the rules.

  • Check the TRANSACTION-LOG-LOCATION configurations in the IRTSVCOL* ini file.

  • Check WVLOG for errors.

  • Using Transaction Surveillance check back through all recent previous transactions and ensure the data is as expected.

  • Use IRTSVTST to offline process the data and debug the rules.

No rules exist

  • Check that the IRTSVCOL* ini file exists in the Prognosis directory.

  • Check the IRTSVCOL* ini file rule definitions.

Rules give too many exceptions

  • Check the rules.

  • Use IRTSVTST to offline process the data and debug the rules.

  • Using Transaction Surveillancecheck back through all recent previous transactions and ensure the data is as expected.

  • Check the TRANSACTION-LOG-LOCATION configurations in the IRTSVCOL* ini file.

Busy CPU

  • Could indicate a Display containing WHERE ALL and no TOP N configured.

High memory usage

  • The NUMBER-OF-TRANSACTIONS is set to high, or,

  • A rule is capturing too many exceptions, or,

  • A rule is capturing too many exceptions and the rules KEEP option is too long. Reduce the KEEP option so that the exceptions expire and not as many are stored.

Windows Client disconnecting from server

  • A Display is requesting too much data, or,

  • There are too many Displays open that are collectively requesting too much data.

  • The default disconnect limit configured on the server is 10MB. If a Windows Client requesting too much data causes a queue to build up, when it reaches 10MB the connection is dropped by the server.

No Transaction/Error Starting Configuration for Connex

  • Check LGWARM location.

  • Check that Connex is running.

  • Check ircnxtlr and the collector object exist.

  • Check Security. Are the LGWARM and log files readable by the Prognosis User?


Provide feedback on this article