Hi Experts,
We are in dilemma how is it possible -
On Source Server sql 2012, we ran DBCC CHECKDB successfully, without any issue it came clean.
We took backup and migrated to sql server 2017 and restored successfully.
In error log , it printed message
DBCC Checkdb executed successfully on 29-Nov-2019 without any error. no action required.
We started DBCC Checkdb, it failed with PFS Corruption issue and Repair_Allow_data_loss the recommended step.
Msg 8948, level 16 state 6 line 1
Database error: Page (1:1204771) is marked with wrong type in PFS Page(1:1197024). PFS Status 0x40, expected 0x60
There were 20 or more errors which we corrected with repair_allow_data_loss.
To check whether there are more error in database or not, we ran dbcc checkdb again
Again it failed with many below errors
msg 8906, Level 16,state 1 line 1
Page(1:1156305) in database id 9 is allocated in SGAM (1:1022465) and PFS(1:1148496) but was not allocated in any IAM . PFS Flags ';Mixed_EXT_Allocated 0_PCT_Full'
msg 8906, Level 16,state 1 line 1
Page(1:1156306) in database id 9 is allocated in SGAM (1:1022465) and PFS(1:1148496) but was not allocated in any IAM . PFS Flags ';Mixed_EXT_Allocated 0_PCT_Full'
msg 8906, Level 16,state 1 line 1
Page(1:1156307) in database id 9 is allocated in SGAM (1:1022465) and PFS(1:1148496) but was not allocated in any IAM . PFS Flags ';Mixed_EXT_Allocated 0_PCT_Full'
msg 8906, Level 16,state 1 line 1
Page(1:1156308) in database id 9 is allocated in SGAM (1:1022465) and PFS(1:1148496) but was not allocated in any IAM . PFS Flags ';Mixed_EXT_Allocated 0_PCT_Full'
Now after running repair_allow_data_loss , it got successful.
Please let me know is this the BUG.
Please If not, how can I recover all data without any loss. Thank you very much
Manish