Data Corruption PSQL10 Windows SBS 2008

Last post 08-02-2010 10:44 AM by j50agl. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 07-26-2010 9:40 AM

    • j50agl
    • Not Ranked
    • Joined on 02-07-2002
    • Posts 2

    Data Corruption PSQL10 Windows SBS 2008

    PSQL Engine 10.21 - Transactional only.

    Has been working with absolutely  no problems on a Window 2003 Server (4 GB RAM - No MS Exchange or other big application) for over 12 months.

    We recently re-installed on a Windows 2008 Small Business  (12 GB RAM - Exchange but little else). Things seemed to be fine for just over a week then received Error 2 (File I/O errors) in one file then another. Rebuilt these and all went quiet for just under two weeks then started to get more Error 2s in various files.

    Have moved the production database back to original hardware (but with disk subsystem replaced) to get customer up and runnning and all seems well again. So problem would appear to be with SBS 2008 and or machine configuration.

    Any ideas where to start looking?

  • 07-26-2010 9:53 AM In reply to

    Re: Data Corruption PSQL10 Windows SBS 2008

    What's in the PVSW.LOG from when the status 2s occur? 

    Are there any entries in the Event Log at the time of the status 2s?

    Have you tried updating to 10.31?  

    I haven't heard of anything like this on SBS 2008 (or any version of WIndows). 

    Mirtheil
    I do not answer question via email. Please post questions in the forum.
    Think before responding. Do not post in old threads. Start a new one.
  • 07-26-2010 9:57 AM In reply to

    Re: Data Corruption PSQL10 Windows SBS 2008

    I echo Mirtheil's comments.  Check the PVSW.LOG to see when the errors started, and whether any OS errors were reported (last number in the xxx.x.x triad).

    There is really no way to tell what is wrong without analyzing at least two corrupted files.  You may see that there are single-bit errors in the structure, which could indicate hardware problems for sure.  Analyzing the files is non-trivial, though, so unless you need to disposition the box (or return it to the manufacturer), it might not be worth the time and money.

    Bill Bach
    Goldstar Software Inc.
    www.goldstarsoftware.com
  • 08-02-2010 10:44 AM In reply to

    • j50agl
    • Not Ranked
    • Joined on 02-07-2002
    • Posts 2

    Re: Data Corruption PSQL10 Windows SBS 2008

    Mirtheil,

    Thanks for your response:

    Typical PVSW Log contenrs:-

    16/07/2010 12:02:18         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 12:04:10         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 12:06:47         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 12:07:54         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 12:11:59         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 12:19:47         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 12:53:40         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.6.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 12:59:54         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 13:01:44         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.9.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 13:06:06         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.6.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 13:07:38         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.9.0 File: F:\DATA\L&P\STOCK\STOKAUDT
    16/07/2010 14:25:31         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.2.0 File: F:\DATA\L&P\STOCK\SOIITEM
    16/07/2010 14:48:13         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.6.0 File: F:\DATA\L&P\STOCK\SOIITEM
    16/07/2010 14:54:34         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.6.0 File: F:\DATA\L&P\STOCK\SOIITEM
    16/07/2010 14:58:11         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.7.0 File: F:\DATA\L&P\STOCK\SOIITEM
    16/07/2010 15:04:41         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.36.0 File: F:\DATA\L&P\STOCK\SOIITEM
    16/07/2010 15:45:35         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.37.0 File: F:\DATA\L&P\STOCK\STOKAUDTSAV
    16/07/2010 15:47:06         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.36.0 File: F:\DATA\L&P\STOCK\STOKAUDTSAV
    16/07/2010 15:59:14         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\STOCK\SOIITEM
    19/07/2010 09:52:07         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\PRINDICT
    19/07/2010 09:53:48         MKDE            3536     NTDBSMGR.EXE    LP2-2003-A      E     System Error: 116.-3.0 File: F:\DATA\L&P\PRINDICT

    No associated events in the Event Log except on a couple of occassions when our Application (Magic based) was being run on the server and it exited due to the error.

    Haven't updated to 10.31 yet. The aim was to switch to the new server using all the old application software. All has been quiet since we moved the database back to the old server.

     

Page 1 of 1 (4 items)