Invalid page header in block 592826 of 319584981

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • gkhangelani
    New Member
    • Mar 2010
    • 17
    #1

    Invalid page header in block 592826 of 319584981

    Hi

    I am junior Database Administrator, I would like to know how to handle an error like below , please explain in simple terms . This error appears very often in our client's database (Postgres 7.3.4) running on Linux - CentOS :



    [root@e014400 bin]# cat /tmp/postgres.log
    LOG: database system was interrupted being in recovery at 2010-03-05 16:39:17 SAST
    This probably means that some data blocks are corrupted
    and you will have to use the last backup for recovery.
    LOG: checkpoint record is at 34B/16BBE754
    LOG: redo record is at 34B/16B3552C; undo record is at 0/0; shutdown FALSE
    LOG: next transaction id: 398339069; next oid: 320074847
    LOG: database system was not properly shut down; automatic recovery in progress
    LOG: redo starts at 34B/16B3552C
    PANIC: Invalid page header in block 592826 of 319584981
    LOG: startup process (pid 2983) was terminated by signal 6
    LOG: aborting startup due to startup process failure
    Tags: invalid page header
    • rski
      Recognized Expert Contributor
      • Dec 2006
      • 700
      #2
      LOG: database system was not properly shut down; automatic recovery in progress
      Does the client have any problems with closing database server.
      This error appears very often in our client's database
      Does it mean that these errors appears when database is working (not when starting up).

        Comment

        • gkhangelani
          New Member
          • Mar 2010
          • 17
          #3
          Once the error is there the user can't use the server to trade because the software disallows them.

            Comment

            • rski
              Recognized Expert Contributor
              • Dec 2006
              • 700
              #4
              Yes, but the error appears when database is working not when starting up. Am I right?

                Comment

                • gkhangelani
                  New Member
                  • Mar 2010
                  • 17
                  #5
                  Yes, you are right.. it's when the database is doing different things

                    Comment

                    • rski
                      Recognized Expert Contributor
                      • Dec 2006
                      • 700
                      #6
                      I'm afraid it is also problem with hd. Can you do a test and try to zip a directory with databases. As I wrote earlier try to run fsck (you don't have to fix bad blocks if there are any, just check a disk)
                      I think it is the similar to problem you wrote int another post.

                        Comment

                        • gkhangelani
                          New Member
                          • Mar 2010
                          • 17
                          #7
                          Many Thanks, I think you are right. I will try that.

                            Comment

                            • gkhangelani
                              New Member
                              • Mar 2010
                              • 17
                              #8
                              Yesterday we had a similar problem in one of the DB servers, a developer said he REINDEXed the affected table and the problem was fixed ...

                                Comment

                                Previous template Next
                                Working...