DBCC CHECKDB Cannot continue the Execution because the Session is in the Kill state

Asked

Viewed 140 times

1

In our current database scenario, we have two databases

  1. A main database: BANCO01
  2. And a BANCO01 dependency database used for testing: BANCO02

After running the database integrity check script.

DBCC CHECKDB ( BANCO01 ) WITH ALL_ERRORMSGS;

has returned the following message:

Mensagem 596, Nível 21, Estado 1, Linha 2
Cannot continue the execution because the session is in the kill state.
Mensagem 0, Nível 20, Estado 0, Linha 2
Erro grave no comando atual. Os resultados, se houver algum, deverão ser descartados.

This message is returned when any DBCC script runs.

I also checked the LOG returns more I do not understand why the messages also.

log

The current size of BANCO01 is about 80GB.

BANCO01

Same script was executed on BANCO02 and occurred normally. But this BANCO02 is about 160 GB.

BANCO02

Our current storage scenario we have about 111GB Free available.

ESPACO

How could I fix, to be able to run DBCC CHECKDB normally?

  • this error may have many causes, but from what you have put, I suggest doing the BANCO02 Shrink and freeing up space first. Remember that the db/log size will be doubled (unless it is configured differently), and he may want to do this for this operation, which would need another 160Gb. So to resolve this, free up the resources first and try again, because from what you wrote, the bank 02 must supposedly be the same size as the 01

No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.