Long-lasting operations

Use the Database Troubleshooting dashboard to identify long-lasting operations, how long they have been running, and which users are performing them. A long-lasting operation is one that runs for more than 5 seconds. One example of a long-lasting operation is loading data.

The Start Time and Duration fields are filled for long-lasting operations. Otherwise, they are blank and the Long Lasting Operation field displays No Operation.

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

  • User for user name
  • User Id
  • Session for session ID
  • Database Worker

You can abort a long-lasting operation by clicking Stop operation 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.

These long-lasting operations can be aborted:

  • Load Cube
  • Data Area
  • Calculation
  • Accelerators
  • Splashing
  • Splash Undo
  • Load From Source
  • MDX Engine

These long-lasting operations cannot be aborted:

  • Save Cube
  • Backup
  • DB Schedule
  • Unload Idle DB
  • Optimization

You can end a session of a user by clicking End Session. If the user has one or more operations in the same session, these operations are aborted, and the session is ended. If the user has multiple sessions, the other sessions are not affected by ending one session.