SQL people need help

[amazon]

**Deadlock/sec on application in critical**

how to resolve this? How to get it to normal?

[Aakupaccha_caradu]

ltt.

[mastercheif]

24 minutes ago, amazon said:

**Deadlock/sec on application in critical**

how to resolve this? How to get it to normal?

more details post man. google talli yem antundhi ?

[amazon]

Google talli dagara info ledu. 

Nenu SQL team kadu but ee alert ki solution/recommendation  Ivali. 

[amazon]

Oka application paina, component deadlocks/sec critical undi adi ela normal ki tesukaravali, ela troubleshoot cheyali. 

[srinima]

table pyna row level lock cheyamanu instead of table... not sure this can help or not... give it a try...

[mettastar]

2 minutes ago, amazon said:

Oka application paina, component deadlocks/sec critical undi adi ela normal ki tesukaravali, ela troubleshoot cheyali. 

dba ni reach avu .. table lock aithe vaallu resolve chestharu .. locks clear chestharu

[tywinn_lannister]

Check your application code and fix it.

The reason for the deadlock situation arises when there is a table level lock and at the same time interval if some other process is trying to update same rows in the table, deadlock situation arises.

Ask the developers to review theri code and fix it.

DBA can only kill the locks on the table temporarily, but the problem will come back again if the application logic is not corrected.

 

[mettastar]

Just now, tywinn_lannister said:

Check your application code and fix it.

The reason for the deadlock situation arises when there is a table level lock and at the same time interval if some other process is trying to update same rows in the table, deadlock situation arises.

Ask the developers to review theri code and fix it.

DBA can only kill the locks on the table temporaroly, but the problem will come back again if the applicaiton logic is not corrected.

 

+1 true.. row level lock occurs when different sessions trying to read and modify the same row at same time.. so ilanti situations rakunda chuskovali

[amazon]

6 minutes ago, tywinn_lannister said:

Check your application code and fix it.

The reason for the deadlock situation arises when there is a table level lock and at the same time interval if some other process is trying to update same rows in the table, deadlock situation arises.

Ask the developers to review theri code and fix it.

DBA can only kill the locks on the table temporarily, but the problem will come back again if the application logic is not corrected.

 

Have you got this kind of issue befor?

[amazon]

Nenu anukuntunna deadlocks/sec antay it calculates application usage anukuntunna. Same like windows servers lo performance monitor schedule chesi konni counters ki performance calculate chestam kada like pages/sec ala anukunna. 

But replies are complete different... 

 

[amazon]

Blind ga velli meeru chepina above suggestion ivochu antaraa?

[Michaelbarbosa]

30 minutes ago, tywinn_lannister said:

Check your application code and fix it.

The reason for the deadlock situation arises when there is a table level lock and at the same time interval if some other process is trying to update same rows in the table, deadlock situation arises.

Ask the developers to review theri code and fix it.

DBA can only kill the locks on the table temporarily, but the problem will come back again if the application logic is not corrected.

 

+1 

[ARYA]

evado changes chesi commit cheyyakunda table ni hold chesi padesadu emo...DBA ki ping sesi table meeda hold tesi padeyamni seppu