locked
Consistency errors seen in tables of Content/SSP Search DB after SQL server cluster fail over due to unexpected DB server node reboot! RRS feed

  • Question

  • Hi everyone,

    I need understanding data stored in them & impact of repair will loss command. Else suggest best action to be taken.

    Recently we had a active SQL Server node reboot causing access issue to application for quite sometime. Basically the passive node didn't get all drives required, hence certain DBs were in suspect mode. DBA / Windows team worked hard to get them back online. Now we hear from DBA team that the one of application Content DB table (table named EventCache only) and SSP Search DB table (table named MSSDocProps only)  have in consistency in them. Hence they want to know the impact if they do below to claim as DBCC check alone isn't doing any good.

    DBCC CHECKDB ('table_name', REPAIR_ALLOW_DATA_LOSS) 

    Thank you in Advance for you time and help.

    Ram


    Ramakrishna Pulipati SharePoint Consultant, Bangalore, INDIA

    Wednesday, January 29, 2014 10:47 AM

Answers

  • Hi Ram,

    in my opinion, please backup your database first, before do the steps, because once database corrupt and it will be not reversible unless you have the back up.

    that is correct from the article that was said before, if you need to repair the database, then sharepoint have that STSADM for repair, and it is a administration command, means that you run it once, and whole of Sharepoint farm will be repaired.

    if you see those inconsistencies based on alrets from sharepoint, you may try to clean up the cache first, which is less impact

    http://support.microsoft.com/kb/939308/en-us

    and if the issue persist you may also check this article:

    http://social.technet.microsoft.com/Forums/sharepoint/en-US/d5b88149-55da-4287-a76f-1cb2af3e2fc9/wss-30-receiving-inconsistent-alerts-but-getting-alert-subscription-notifications?forum=sharepointgenerallegacy


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Reach Ram Wednesday, February 26, 2014 12:28 PM
    Friday, January 31, 2014 6:50 AM
  • Hi Ram,

    please help to post the full error message that you see in this thread, and i will try to check with my SQL team regarding this error messages.

    as i know the inconsistencies may happened if there is a bottleneck issue, or checking in some application, for example DPM.

    http://social.technet.microsoft.com/Forums/en-US/441beade-c693-407a-86f0-df9b4fec7acc/dpm-2010-inconsistent-replica-for-sharepoint-db-id-104-error-0x80070057?forum=dpmsqlbackup

    if your SQL team, want to try the command: DBCC CHECKDB ('table_name', REPAIR_ALLOW_DATA_LOSS) , then i suggest that you backup all your database before trial.

    i am not quite sure if the consistencies happened, is regarding the database that is outgrown or the consistencies regarding the data is not match. those 2 databases are different in someway around, while eventcache usually regarding timer jobs, and mssdocprops is regarding search and indexing.

    this link: http://support.microsoft.com/kb/939308/en-us, is basically to refresh the cache at sharepoint, so it should be having any big impact, and i hope it can narrow down the event cache for the timer jobs. for the mssdocprops, you may do reset index to refresh it, and do full crawl after that.

    if should this issue is urgent state, you need to backup the database first, and you may call our customer representative, to submit a ticket, so that we can check your environment directly.http://support.microsoft.com/


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Proposed as answer by Jin Chen Thursday, February 13, 2014 7:14 AM
    • Unproposed as answer by Reach Ram Wednesday, February 26, 2014 12:28 PM
    • Marked as answer by Reach Ram Wednesday, February 26, 2014 12:28 PM
    Wednesday, February 5, 2014 7:50 AM
  • Hi Aries,

    Thank you for your response, DBA team have resolved the content DB related consistency issue by running DBCC check with REPAIR_ALLOW_DATA_LOSS. The action worked well and now the DB is looks fine. Sites are accessible, indexing is fine and content is searchable too. DBA now plans to perform similar action on MOSS SSP search DB.

    Note: We performed the action on tables in QA farm, then in production. Similar is planned for MOSSSSP Search DB too.

    Thank you everyone.

    Regards,
    Ram


    Ramakrishna Pulipati SharePoint Consultant, Bangalore, INDIA

    Monday, February 17, 2014 3:49 PM

All replies

  • Hi Ram,

    I am trying to involve someone familiar with this topic to further look at this issue.

    Thanks,
    Daniel Yang
    Forum Support
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Daniel Yang
    TechNet Community Support

    Thursday, January 30, 2014 3:51 AM
    Moderator
  • Hi Ram,

    please be notice regarding this article: http://support.microsoft.com/kb/841057/en-us

    if you need to repair those databases, please have a check this article: http://technet.microsoft.com/en-us/library/cc263282(v=office.12).aspx

    as it is part of database, i strongly suggest that you make a backup first before the testing take place.


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, January 30, 2014 8:48 AM
  • Thank you Daniel, would look forward to provide if any info required.

    Cheers,

    Ram


    Ramakrishna Pulipati SharePoint Consultant, Bangalore, INDIA

    Thursday, January 30, 2014 1:37 PM
  • Hi Aries,

    Firstly thank you for responding to my query. 

    Secondly, does databaserepair operation using STSADM will resolve the consistency errors on table/s? As the article ref says it will handle below situations(hope you read situation);

    • A Windows SharePoint Services Web site that does not have a parent Windows SharePoint Services Web site

    • A subweb that does not have a parent Windows SharePoint Services Web site

    • A list that does not have a parent Windows SharePoint Services Web site

    • A document that does not have a parent document library

    • A list item that does not have a parent list

    • A Web page that does not have a parent Windows SharePoint Services Web site

    • Missing security scopes on Webs, lists and items

    Thirdly, Can i run the same command on MOSS Search DB? I mean same command!

    Thank you in advance.

    Best regards,

    Ram


    Ramakrishna Pulipati SharePoint Consultant, Bangalore, INDIA

    Thursday, January 30, 2014 1:48 PM
  • Hi Ram,

    in my opinion, please backup your database first, before do the steps, because once database corrupt and it will be not reversible unless you have the back up.

    that is correct from the article that was said before, if you need to repair the database, then sharepoint have that STSADM for repair, and it is a administration command, means that you run it once, and whole of Sharepoint farm will be repaired.

    if you see those inconsistencies based on alrets from sharepoint, you may try to clean up the cache first, which is less impact

    http://support.microsoft.com/kb/939308/en-us

    and if the issue persist you may also check this article:

    http://social.technet.microsoft.com/Forums/sharepoint/en-US/d5b88149-55da-4287-a76f-1cb2af3e2fc9/wss-30-receiving-inconsistent-alerts-but-getting-alert-subscription-notifications?forum=sharepointgenerallegacy


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Reach Ram Wednesday, February 26, 2014 12:28 PM
    Friday, January 31, 2014 6:50 AM
  • Hi Aries,

    We do to see issue/errors logs, we have been contacted to our DBA team with mentioned DBs having consistency error on tables mentioned. DBA team says that the one of application Content DB table (table named EventCache only) and SSP Search DB table (table named MSSDocProps only)  have in consistency in them.

    Hence the suggested articles are not the situaiton we have.

    Thank you & regards,

    Ram


    Ramakrishna Pulipati SharePoint Consultant, Bangalore, INDIA

    Monday, February 3, 2014 10:40 AM
  • Hi Ram,

    please help to post the full error message that you see in this thread, and i will try to check with my SQL team regarding this error messages.

    as i know the inconsistencies may happened if there is a bottleneck issue, or checking in some application, for example DPM.

    http://social.technet.microsoft.com/Forums/en-US/441beade-c693-407a-86f0-df9b4fec7acc/dpm-2010-inconsistent-replica-for-sharepoint-db-id-104-error-0x80070057?forum=dpmsqlbackup

    if your SQL team, want to try the command: DBCC CHECKDB ('table_name', REPAIR_ALLOW_DATA_LOSS) , then i suggest that you backup all your database before trial.

    i am not quite sure if the consistencies happened, is regarding the database that is outgrown or the consistencies regarding the data is not match. those 2 databases are different in someway around, while eventcache usually regarding timer jobs, and mssdocprops is regarding search and indexing.

    this link: http://support.microsoft.com/kb/939308/en-us, is basically to refresh the cache at sharepoint, so it should be having any big impact, and i hope it can narrow down the event cache for the timer jobs. for the mssdocprops, you may do reset index to refresh it, and do full crawl after that.

    if should this issue is urgent state, you need to backup the database first, and you may call our customer representative, to submit a ticket, so that we can check your environment directly.http://support.microsoft.com/


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Proposed as answer by Jin Chen Thursday, February 13, 2014 7:14 AM
    • Unproposed as answer by Reach Ram Wednesday, February 26, 2014 12:28 PM
    • Marked as answer by Reach Ram Wednesday, February 26, 2014 12:28 PM
    Wednesday, February 5, 2014 7:50 AM
  • Hi Ram,

    Is there any update on this issue?

    Thanks


    Daniel Yang
    TechNet Community Support

    Thursday, February 13, 2014 6:52 AM
    Moderator
  • Hi Aries,

    Thank you for your response, DBA team have resolved the content DB related consistency issue by running DBCC check with REPAIR_ALLOW_DATA_LOSS. The action worked well and now the DB is looks fine. Sites are accessible, indexing is fine and content is searchable too. DBA now plans to perform similar action on MOSS SSP search DB.

    Note: We performed the action on tables in QA farm, then in production. Similar is planned for MOSSSSP Search DB too.

    Thank you everyone.

    Regards,
    Ram


    Ramakrishna Pulipati SharePoint Consultant, Bangalore, INDIA

    Monday, February 17, 2014 3:49 PM