Database troubleshooting

The Database Troubleshooting dashboard has features to identify and, if necessary, disconnect individual users and to generate and download request log files.

Select Dashboards > OLAP > Database Troubleshooting.

The Connected Users widget lists all currently connected users of a selected database which is online. You can use these criteria to restrict the list:

  • User name
  • User ID
  • Session ID
  • Database Worker name

You can also select from a list of long-lasting operations, such as loading data, to identify when the operations started and which users are performing them. A long-lasting operation is one that runs for more than 5 seconds.

The Start Time and Duration fields are filled for long-lasting operations. Otherwise, they are blank and the Long Lasting Operation field displays No Task. In the Duration field, you can search for operations that have been running for longer or less than a specified number of seconds. If a load job, for example, consists of multiple tasks, those tasks can be canceled individually.

These long-lasting operations can be aborted:

  • Load cubes
  • Load from source jobs
  • DataArea operations
  • Calculation
  • Accelerator loading
  • Splashing
  • SplashUndo
  • MdxEngine

Click Stop in the Connected Users widget.

Note: Operations are not aborted immediately but only at certain points. The locations of these safe points depend on the specific software environment.

You can monitor requests to OLAP that may result in these types of issue:

  • Database crash
  • Reporting
  • Performance

If one of these types of issue occurs, you can record a log of the requests over a specified number of hours or minutes. You can download the results to a .zip file. The file can be used by Infor support to identify the specific requests that result in the issues.

Optionally the responses from OLAP can also be logged. Logging of responses from OLAP and the sizes of the request buffers are configured in the configuration database. The buffers determine the number of requests that are held in memory before being written to the log file.

This table shows whether responses are logged, and the size of the buffer, for each type of issue:

Issue type Responses logged Buffer size
Performance False 300
Reporting True 300
Crash False 1