Обсуждение: OID IS INVALID?

Поиск
Список
Период
Сортировка

OID IS INVALID?

От
Mark Wilson
Дата:
Hello,

I've been using version 6.4.2 for quite a while with absolutely no
problems.  Yesterday morning, a block on the disk containing all of my
databases went bad.  I used the format command to fix the block but still
had problems.  Whenever I access a particular table I am given these error
messages:

NOTICE:  Rel log12130_max: TID 567/29: InsertTransactionInProgress 0 -
can't shrink relation
NOTICE:  Rel log12130_max: TID 567/29: TID IN TUPLEHEADER 0/0 IS NOT THE
SAME. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/29: TUPLE_LEN IN PAGEHEADER 72 IS NOT
THE SAME AS IN TUPLEHEADER 0. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/29: OID IS INVALID. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/30: InsertTransactionInProgress 0 -
can't shrink relation
NOTICE:  Rel log12130_max: TID 567/30: TID IN TUPLEHEADER 0/0 IS NOT THE
SAME. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/30: TUPLE_LEN IN PAGEHEADER 72 IS NOT
THE SAME AS IN TUPLEHEADER 0. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/30: OID IS INVALID. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/31: InsertTransactionInProgress 0 -
can't shrink relation
NOTICE:  Rel log12130_max: TID 567/31: TID IN TUPLEHEADER 0/0 IS NOT THE
SAME. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/31: TUPLE_LEN IN PAGEHEADER 72 IS NOT
THE SAME AS IN TUPLEHEADER 0. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/31: OID IS INVALID. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/32: InsertTransactionInProgress 0 -
can't shrink relation
NOTICE:  Rel log12130_max: TID 567/32: TID IN TUPLEHEADER 0/0 IS NOT THE
SAME. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/32: TUPLE_LEN IN PAGEHEADER 72 IS NOT
THE SAME AS IN TUPLEHEADER 0. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/32: OID IS INVALID. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/33: InsertTransactionInProgress 0 -
can't shrink relation
NOTICE:  Rel log12130_max: TID 567/33: TID IN TUPLEHEADER 0/0 IS NOT THE
SAME. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/33: TUPLE_LEN IN PAGEHEADER 72 IS NOT
THE SAME AS IN TUPLEHEADER 0. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/33: OID IS INVALID. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/34: InsertTransactionInProgress 0 -
can't shrink relation
NOTICE:  Rel log12130_max: TID 567/34: TID IN TUPLEHEADER 0/0 IS NOT THE
SAME. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/34: TUPLE_LEN IN PAGEHEADER 72 IS NOT
THE SAME AS IN TUPLEHEADER 0. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/34: OID IS INVALID. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/35: InsertTransactionInProgress 0 -
can't shrink relation
NOTICE:  Rel log12130_max: TID 567/35: TID IN TUPLEHEADER 0/0 IS NOT THE
SAME. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/35: TUPLE_LEN IN PAGEHEADER 72 IS NOT
THE SAME AS IN TUPLEHEADER 0. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/35: OID IS INVALID. TUPGONE 0.
NOTICE:  Rel log12130_max: TID 567/36: DeleteTransactionInProgress 0 -
can't shrink relation

Last night I reformatted the disk, create a new filesystem and restored
the last good full backup (from about a week ago) hoping I could get a
version of the system back on the disk prior to this event.  Unfortunately
I'm still given the same exact errors shown above.  Does anyone have an
idea of what I can to do fix these problems.  I really need to get the
database back online quickly.

I'm running version 6.4.2 on a Sun Ultra 30, Solaris 2.6, 384MB RAM.  The
disk in question is a 9GB Seagate ST19171W (not that that matters).

Any help would be greatly appreciated!  Thanks!!

-Mark.

---                                                   fax: (757)825-8659
Mark Wilson                                         voice: (757)827-4631
Analytical Services & Materials, Inc.    email: m.r.wilson@larc.nasa.gov

Re: [GENERAL] OID IS INVALID?

От
Leon
Дата:
Mark Wilson wrote:
>
> Hello,
>
> I've been using version 6.4.2 for quite a while with absolutely no
> problems.  Yesterday morning, a block on the disk containing all of my
> databases went bad.

If a disc happens to get a bad sector, it is advisable to throw it away
at once, because this means that surface got a scratch which grows
larger every time the disc head moves over it. Trash your disc, and
be happy again :)

--
Leon.
---------
"This may seem a bit weird, but that's okay, because it is weird." -
Perl manpage.

Re: [GENERAL] OID IS INVALID?

От
Vadim Mikheev
Дата:
Mark Wilson wrote:
>
> Last night I reformatted the disk, create a new filesystem and restored
> the last good full backup (from about a week ago) hoping I could get a
                ^^^^^^^^^^^
What did you use for backup ?
pg_dump/copy or you cp-ed datafiles to another place ?

> version of the system back on the disk prior to this event.  Unfortunately
> I'm still given the same exact errors shown above.  Does anyone have an
> idea of what I can to do fix these problems.  I really need to get the
> database back online quickly.

Either disk is still bad or you didn't use pg_dump/copy for backup.

Vadim

Re: [GENERAL] OID IS INVALID?

От
Hui Chun Kit
Дата:
Dear All,

    THis is a test, please ignore.. sorry to border..



Jacky Hui