[Syteline] Syteline ERP System "zombie" processing mode

In the process of running the backstage task of sytelineerp system, the phenomenon of zombie is occasionally produced
There is no tool to kill this process, in Oracle JDE, there is the concept of queues, one of the dead will cause blocking, you can adjust the priority!
However, there is no work in the syteline that can only be deleted in the database.
The method is as follows:
Another solution about kill a process in SQL is as below:

Kill a Process in SQL Server

Symptom:

Kill a Process in SQL Server

System is hanging

Clarifying Fact:

Product:sltech

SL7 XX

Sql

Resolution:

Open Query Analyzer
Type Sp_who2 and Run query (F5)
When results appear, view the ' BLK by ' column
And make a note of the Spid causing locking/blocking EG 20

Then Type
Kill 20
and run (F5)

Legacy ID:

2003syteline49999

Doris

The following is a Primus (R) eserver solution:

id:2003syteline45313
Domain:syteline
Solution Class:syteline

Goal identify and kill A, this is accidentally submited with no starting and ending parameters ng SQL Server Resources

Fact syteline 7-all Versions

Fact SQL

[NOT] Fact Progress

Symptom performance across the Syteline application is slow due to SQL Server resources being tied up in a ' bad ' Process

Symptom SQL tempdb grows quickly and does not shrink once the ' offending process is terminated.

Cause a user accidentally submitted a Background Task History with no starting and/or ending parameters and The process is consuming SQL Server resources, or causing SQL locking and blocking

Cause with reports this use temporary tables in the SQL tempdb for workspace (e.g. Itemwhereusedbom), an open  Ended cause the tempdb to grow very quickly. Since the ' tempdb is ' just like no other SQL database, which is won't be automatically reclaimed once the ' is CA  Ncelled and the transaction is rolled. SQL would however flag the space as available for the other programs.

Fix There is no quick way to identify such a process automatically, however, the following recommendations May assist and getting the information required to kill the SQL Server process associated and the ' bad '.

Firstly, log into syteline and open the Background Task History form and review recent tasks this are currently in a Runni ng status. For each running task, review the parameter detail information searching for the "the" or utility that is submitted with  No starting and/or ending data parameters. Parameters are not labeled, so you could need to look at the the the the the the the the the on screen to the the What options are available and compare the m to the parameters listed the Background Task History form.

Once you know the syteline which are suspected of consuming of SQL Server resources, open Query Analyzer on your SQL Se RVer, select the APP database from which the "is submitted", and run the following query:

SELECT SCN. Contextname, SCN. ProcessID, Ci. UserName
From Sessioncontextnames SCN (readuncommitted)
Left OUTER JOIN connectioninformation ci (readuncommitted)
On SCN. SessionID = ci. ConnectionID
WHERE CI. ConnectionID is not NULL

The above query would return a list of SQL Server processes and the associated syteline information.  The column contextname should return to the Syteline form that initiated the process. Search the list of displayed Contextname records for the "The", which you identified the Background Task History form  . Identify the specific process associated with the desired form and User, and the ProcessID.

Can then kill the process by running the following in Query Analyzer:

Kill spid

Where the SPID would is substituted with the ProcessID value returned in the query for you ran. For example, ' Kill 109 '.

Please note that killing the process would rollback the transaction so if it has been running for some time, it could take so Me time for SQL to rollback the transaction and for SQL Server the usage levels.