KB-1530 How to kill queries initiated from phpMyAdmin

Elly Meng — Wed, 22 Jun 2022 14:23:11 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 6/22/2022 2:23:11 PM

Purpose

Long-running queries initiated from the phpMyAdmin interface and the Appian application may cause database performance issues. This article outlines how to kill such offending queries.

Instructions

Open the phpMyAdmin interface. If the interface is unresponsive, try opening it in a new browser type (e.g. Edge, Firefox, etc) or Chrome Incognito. If the interface is still unresponsive, create a case with Appian Technical Support.
Execute the following command from the SQL tab of phpMyAdmin.
1. Appian 21.4 and later: CALL AppianProcess.getFullProcessList();
2. Appian 21.3 and earlier: CALL AppianProcess.getMyProcessList();
A list of processes initiated by the Appian application, phpMyAdmin interface and Stored Procedures will be displayed. The 'Time' column will display how long (in seconds) a particular query has been running in the system. Copy the ID of the offending process.
Kill the offending process using the process ID and the following command.
1. Appian 21.4 and later: CALL AppianProcess.killProcess(<ID>);
2. Appian 21.3 and earlier: kill "<ID>";

Note: In Appian 21.3 and earlier, these instructions will only show the database processes that were started from within phpMyAdmin by the same user for that session. It will not show any hung processes started from within Appian, such as those initiated via a!query() or the Query Database smart service, as well as processes that were started during a previous session.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2022

Tags: phpmyadmin, database, Performance, infrastructure

KB-1530 How to kill queries initiated from phpMyAdmin

Parmida Borhani — Wed, 23 Mar 2022 02:39:18 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 3/23/2022 2:39:18 AM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill any offending queries, follow the steps below.

Instructions

Open a new tab in the phpMyAdmin interface.
Execute the following command from the SQL tab of phpMyAdmin: CALL AppianProcess.getMyProcessList();.
A list of processes belonging to the current user will be displayed. The 'Time' column will display how long a particular query has been running in the system in seconds. Copy the ID of the offending process that should be killed.
Kill the offending process using the process ID and kill process command, like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Note: These instructions will only show the database processes that are started from within phpMyAdmin by the same user for that session. It will not show any hung up processes started from within Appian, such as those initiated via a!query() or the Query Database smart service, as well as processes that were started during a previous session.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: March 2022

Tags: phpmyadmin, database, Performance, infrastructure

KB-1530 How to kill queries initiated from phpMyAdmin

Parmida Borhani — Wed, 26 May 2021 00:05:43 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 5/26/2021 12:05:43 AM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill any offending queries, follow the steps below.

Instructions

Open a new tab in the phpMyAdmin interface.
Execute the following command from the SQL tab of phpMyAdmin: CALL AppianProcess.getMyProcessList();.
A list of processes belonging to the current user will be displayed. The 'Time' column will display how long a particular query has been running in the system in seconds. Copy the ID of the offending process that should be killed.
Kill the offending process using the process ID and kill process command, like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Note: These instructions will only show the MySQL process that are started from within phpMyAdmin by the same user for that session. It will not show any hung up processes started from within Appian, such as those initiated via a!query() or the Query Database smart service, as well as processes that were started during a previous session.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: May 2021

Tags: phpmyadmin, database, Performance, infrastructure

KB-1530 How to kill queries initiated from phpMyAdmin

Jordan Horwat — Mon, 23 Jul 2018 12:51:41 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 12:51:41 PM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill any offending queries, follow the steps below.

Instructions

Open a new tab in the phpMyAdmin interface.
Execute the following command from the SQL tab of phpMyAdmin: CALL AppianProcess.getMyProcessList();.
A list of processes belonging to the current user will be displayed. The 'Time' column will display how long a particular query has been running in the system in seconds. Copy the ID of the offending process that should be killed.
Kill the offending process using the process ID and kill process command, like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Note: These instructions will only show the MySQL process that are started from within phpMyAdmin by the same user. It will not show any hung up processes started from within Appian, such as those initiated via a!query() or the Query Database smart service.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: March 2018

Tags: phpmyadmin, database, Performance, infrastructure

KB-1530 How to kill queries initiated from phpMyAdmin

Parmida Borhani — Mon, 26 Mar 2018 00:59:42 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 3/26/2018 12:59:42 AM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill any offending queries, follow the steps below.

Instructions

Open a new tab in the phpMyAdmin interface.
Execute the following command from the SQL tab of phpMyAdmin: CALL AppianProcess.getMyProcessList();.
A list of processes belonging to the current user will be displayed. The 'Time' column will display how long a particular query has been running in the system in seconds. Copy the ID of the offending process that should be killed.
Kill the offending process using the process ID and kill process command, like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: March 2018

Tags: phpmyadmin, database, Performance

KB-1530 How to kill queries initiated from phpMyAdmin

Parmida Borhani — Sun, 25 Mar 2018 20:58:14 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 3/25/2018 8:58:14 PM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill any offending queries, follow the steps below.

Instructions

Open a new tab in the phpMyAdmin interface.
Execute the following command from the SQL tab of phpMyAdmin: CALL AppianProcess.getMyProcessList();.
A list of processes belonging to the current user will be displayed. The 'Time' column will display how long a particular query has been running in the system in seconds. Copy the ID of the offending process that should be killed.
Kill the offending process using the process ID and kill process command, like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: March 2018

Tags: phpmyadmin, database, performance

DRAFT KB-XXXX How to kill processes initiated from phpMyAdmin

Parmida Borhani — Tue, 20 Mar 2018 04:01:23 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 3/20/2018 4:01:23 AM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill any offending queries, follow the steps below.

Instructions

Open a new tab in the phpMyAdmin interface.
Execute the following command from the SQL tab of phpMyAdmin: CALL AppianProcess.getMyProcessList();.
A list of processes belonging to the current user will be displayed. The 'Time' column will display how long a particular query has been running in the system in seconds. Copy the ID of the offending process that should be killed.
Kill the offending process using the process ID and kill process command, like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: March 2018

Tags: phpmyadmin, database, performance

DRAFT KB-XXXX How to kill processes initiated from phpMyAdmin

Parmida Borhani — Mon, 19 Mar 2018 01:40:13 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 3/19/2018 1:40:13 AM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill any offending queries, follow the steps below.

Instructions

Open a new tab in the phpMyAdmin interface.
Execute the following command from the SQL tab of phpMyAdmin: CALL AppianProcess.getMyProcessList();.
A list of processes belonging to the current user will be displayed. Copy the ID of the offending process that should be killed.
Kill the offending process using the process ID and kill process command, like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: March 2018

Tags: phpmyadmin, database, performance

DRAFT KB-XXXX How to kill processes initiated from phpMyAdmin

Nick Vigilante — Wed, 07 Feb 2018 09:14:59 GMT

Revision 3 posted to Appian Knowledge Base by Nick Vigilante on 2/7/2018 9:14:59 AM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill any offending queries, follow the steps below.

Instructions

Execute the following command from phpMyAdmin: CALL AppianProcess.list();.
A list of processes belonging to the current user will be displayed. Kill the process using the process ID and kill process command like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Note: This will only show the MySQL process that are started from within phpMyAdmin by the same user.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: February 2018

Tags: phpmyadmin, database, performance

DRAFT KB-XXXX How to kill processes initiated from phpMyAdmin

Parmida Borhani — Wed, 07 Feb 2018 06:11:14 GMT

Revision 1 posted to Appian Knowledge Base by Parmida Borhani on 2/7/2018 6:11:14 AM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill the offending query, follow the steps below.

Instructions

Execute the following command from phpMyAdmin: CALL AppianProcess.list();.
A list of processes belonging to the current user will be displayed. Kill the process using the process ID and kill process command like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Note: This will only show the MySQL process that are started from within phpMyAdmin by the same user.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: February 2018

Tags: phpmyadmin, database, performance

DRAFT KB-XXXX How to kill processes initiated from phpMyAdmin

Parmida Borhani — Wed, 07 Feb 2018 01:11:43 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 2/7/2018 1:11:43 AM

Purpose

Long running queries initiated from phpMyAdmin may cause database performance issues. To kill the offending query, follow the steps below.

Instructions

Execute the following command from phpMyAdmin: CALL AppianProcess.list();.
A list of processes belonging to the current user will be displayed. Kill the process using the process ID and kill process command like so: kill "processID";.
If phpMyAdmin is unresponsive, create a case with Appian Technical Support.

Note: This will only show the MySQL process that are started from within phpMyAdmin by the same user.

Affected Versions

This article applies to Appian Cloud 18.1 and later.

Last Reviewed: February 2018

Tags: phpmyadmin, database, performance