1

Topic: checkdb errors what to do?

I ask to help
There is a basis, at present it works, checked up , produced a heap of errors, took the most historical  monthly prescription, on it  a trouble what advise?
dbcc checkdb
Produced result - here a part.
[spoiler] Msg 8905, Level 16, State 1, Line 1
Extent (1:6264848) in database ID 12 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:6264856) in database ID 12 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 1252563896, index ID 4, partition ID 72057599258329088, alloc unit ID 72057599299616768 (type In-row data). Parent node for page (1:6261053) was not encountered.
Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 1252563896, index ID 4, partition ID 72057599258329088, alloc unit ID 72057599299616768 (type In-row data). The previous link (1:6261053) on page (1:18509054) does not match the previous page (1:18509053) that the parent (1:22546560), slot 11 expects for this page.
Msg 8951, Level 16, State 1, Line 1
Table error: table ' _AccumRg37121 ' (ID 1252563896). Data row does not have a matching index row in the index ' _Accum37121_ByDims37136_RTRN ' (ID 7). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:4623581:8) identified by (_Period = ' 4017-08-21 00:05:56.000 ' and _RecorderTRef = 0x0000029E and _RecorderRRef = 0x8FF1005056B6F20511E7844C44C66318 and _LineNo = 37.) with index values ' _Fld37126RRef = 0xB2C8ED89B0DC904E4A27502308421D76 and _Period = ' 4017-08-21 00:05:56.000 ' and _RecorderTRef = 0x0000029E and _RecorderRRef = 0x8FF1005056B6F20511E7844C44C66318 and _LineNo = 37. '.
Msg 8951, Level 16, State 1, Line 1
Table error: table ' _AccumRg37121 ' (ID 1252563896). Data row does not have a matching index row in the index ' _Accum37121_ByDims37136_RTRN ' (ID 7). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:4623581:9) identified by (_Period = ' 4017-08-21 00:05:56.000 ' and _RecorderTRef = 0x0000029E and _RecorderRRef = 0x8FF1005056B6F20511E7844C44C66318 and _LineNo = 38.) with index values ' _Fld37126RRef = 0xB2C8ED89B0DC904E4A27502308421D76 and _Period = ' 4017-08-21 00:05:56.000 ' and _RecorderTRef = 0x0000029E and _RecorderRRef = 0x8FF1005056B6F20511E7844C44C66318 and _LineNo = 38. '.
Msg 8951, Level 16, State 1, Line 1
Table error: table ' _AccumRg37121 ' (ID 1252563896). Data row does not have a matching index row in the index ' _Accum37121_ByDims37136_RTRN ' (ID 7). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1 [/spoiler]

2

Re: checkdb errors what to do?

To do new basis and to outweigh all data that is. A post to make dbcc checkdb + repair_allow_data_loss and to try to draw out something else.

3

Re: checkdb errors what to do?

Is  a fast method to outweigh all data?
Basis approximately on 400, hundreds tables.
By the way, I do  on tables which are shown in errors - fulfills normally.

4

Re: checkdb errors what to do?

odisssey wrote:

by the way, I do  on tables which are shown in errors - fulfills normally.

On a basis copy try  all
And to check up basis again

5

Re: checkdb errors what to do?

odisssey;
As a whole he at you swears on not clustered index _Accum37121_ByDims37136_RTRN, can try  it and create anew on the table.
Worse here it:
Msg 8905, Level 16, State 1, Line 1
Extent (1:6264848) in database ID 12 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:6264856) in database ID 12 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
That else writes checkdb in such variant:

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

6

Re: checkdb errors what to do?

To odisssey
Judging by a title the table at you basis 1. Try to recover fresh  in a test DB, then a configurator 1 preempt the data in dt, recover the data from dt a file in a test DB (measure time how many at you occupied these operations)
Check up a test DB once again dbcc checkdb. Test a DB on serviceability with the help 1 the client.
If all  in approaching on time (look time sampling on a test DB) in the free technological window preempt load the Configurator given in a working DB.
The configurator 1 at outswapping in dt a file saves the description of tables of indexes, etc. + the data in a text type, and then at recovery creates tables indexes, etc. and floods in them the data.
the Configurator 1 strikingly differs from  made means SQL

7

Re: checkdb errors what to do?

felix_ff;
a file.

8

Re: checkdb errors what to do?

max44 wrote:

To odisssey
The configurator 1 at outswapping in dt a file saves the description of tables of indexes, etc. + the data in a text type, and then at recovery creates tables indexes, etc. and floods in them the data.
the Configurator 1 strikingly differs from  made means SQL

Precisely! To preempt in  and it is reverse. Thanks! Now I will try.
But it would be desirable also other decision to know,  it there was no basis 1.

9

Re: checkdb errors what to do?

odisssey wrote:

But it would be desirable also other decision to know,  it there was no basis 1.

Import/export. But there will be many nuances.

10

Re: checkdb errors what to do?

To: odisssey
Forgot to specify still such nuance if in a DB 1 objects not by means of the Configurator 1, and in "manual mode" were added
For example: added the tables, stored procedures, indexes, representations ...
That most likely outswapping by means 1 these objects not "" I of it to state 100 % I can not (did not check in practice), but most likely it will be so and then it will be necessary in manual  these objects and to transfer the data.
If with basis worked exceptional through the Configurator 1 problems with outswapping in dt should not be.

11

Re: checkdb errors what to do?

odisssey wrote:

felix_ff;
a file.

, there all is sad enough.
It is a high time to recall about .
Possible variants to you were offered by Gavrilenko and max44.
it is necessary to you a lot of handwork

12

Re: checkdb errors what to do?

felix_ff wrote:

it is passed...
, there all is sad enough.
It is a high time to recall about .
Possible variants to you were offered by Gavrilenko and max44.
it is necessary to you a lot of handwork

And still the HARDWARE is written "at present by her works," - it is necessary to stop any operation on it.

13

Re: checkdb errors what to do?

All thanks.
Treated
DBCC CHECKDB (BD, REPAIR_REBUILD)
It that corrected that and then two times
DBCC CHECKDB (BD, REPAIR_ALLOW_DATA_LOSS)
Not clearly why did not treat from the first...
Checked up about the beginning on a test DB accounts department confirmed that all apprx.

14

Re: checkdb errors what to do?

odisssey wrote:

all thanks.
Treated
DBCC CHECKDB (BD, REPAIR_REBUILD)
It that corrected that and then two times
DBCC CHECKDB (BD, REPAIR_ALLOW_DATA_LOSS)
Not clearly why did not treat from the first...
Checked up about the beginning on a test DB accounts department confirmed that all apprx.

All  for a today?
But there is a probability that the debit at them does not converge with the credit...