EMERGENCY

Henrik Steffen wrote:

Hello Tom, anyone, please help me urgently:

select * from ANY_TABLE_IN_MY_DB;

ALWAYS GIVES:

ERROR: cannot open pg_statistic_relid_att_index: No such file or directory

this is happening in my LIVE System!! how can I repair this quickly ?

or is only an initb possible?

thanks in advance

ps.
it's certainly still due to the memory problem. I ordered a completely new
server which will be up and running in 2 or 3 hours hopefully. but what can I do
now??

Seems you lost your optimizer statistics. Not sure how to fix that.
There is a reindex command, but I don't know if it will recreate an
index that doesn't even exist anymore and creating system indexes can be
tricky. I think the only way to do that is to start a standalone
backend with the -O flag and recreate the index. The description I have
for the index is:

Indexes: pg_statistic_relid_att_index unique btree (starelid, staattnum)

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Henrik Steffen wrote:

Hello Tom, anyone, please help me urgently:

select * from ANY_TABLE_IN_MY_DB;

ALWAYS GIVES:

ERROR: cannot open pg_statistic_relid_att_index: No such file or directory

this is happening in my LIVE System!! how can I repair this quickly ?

I tried to reindex pg_statistic_relid_att_index here and got:

test=# reindex index pg_statistic_relid_att_index;
ERROR: "pg_statistic_relid_att_index" is a system index. call REINDEX
under standalone postgres with -O -P options

You might want to try the advice in the error message. But I'm no expert
on this either, so you might want to wait for someone else more
experienced to chime in.

Good luck!

Joe

hi,

thanks for you quick reply...

trying to create the index in stand-alone mode delivers

error: index allready exists

trying to drop the index delivers:

notice: relationBuildDesc: can't open pg_statistic_relid_att_index: No such file or diretory
notice: cannot unlink 16556/15835646

then again trying to create the index delivers:

FATAL 2: could not open /var/lib/pgsql/data/pg_clog/0FF2: no such file or directory

DEBUG: shutting down
DEBUG: system has been shut down (FYI: system messages translated from german)

this didn't quite help yet ... other ideas ?

Mit freundlichem Gru�

Henrik Steffen
Gesch�ftsf�hrer

top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.com Tel. +49 4141 991230
mail: steffen@topconcepts.com Fax. +49 4141 991233
--------------------------------------------------------
24h-Support Hotline: +49 1908 34697 (EUR 1.86/Min,topc)
--------------------------------------------------------
System-Partner gesucht: http://www.franchise.city-map.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------

----- Original Message -----
From: "Bruce Momjian" <pgman@candle.pha.pa.us>
To: "Henrik Steffen" <steffen@city-map.de>
Cc: "pg" <pgsql-general@postgresql.org>
Sent: Monday, July 15, 2002 7:28 PM
Subject: Re: [GENERAL] EMERGENCY

Use initdb to build ANOTHER database, leaving your existing one
in tact. Study the difference between the new on and yours.
Next copy some missing files from the new one. The
error messages sound like an "fopen" someplace is failing, posably
if the fopen worked it may proceed to do its re-index???

I think what this shows us it that we need something like an
"fsck" for databases. It should be possable to salvage anything
that is salvageable. This would have to be a stand alone program
that would run with no postmaster running. Maybe called "pgck".

I've had problems like this too and much hand work was required
to repair the damage. Fortunately I logged all my source data in
a way I could "play it back" but in general you can't do that.

--- Bruce Momjian <pgman@candle.pha.pa.us> wrote:

Henrik Steffen wrote:

Hello Tom, anyone, please help me urgently:

select * from ANY_TABLE_IN_MY_DB;

ALWAYS GIVES:

ERROR: cannot open pg_statistic_relid_att_index: No such file or

directory

this is happening in my LIVE System!! how can I repair this quickly

?

or is only an initb possible?

thanks in advance

ps.
it's certainly still due to the memory problem. I ordered a

completely new

server which will be up and running in 2 or 3 hours hopefully. but

what can I do

now??

Seems you lost your optimizer statistics. Not sure how to fix that.
There is a reindex command, but I don't know if it will recreate an
index that doesn't even exist anymore and creating system indexes can
be
tricky. I think the only way to do that is to start a standalone
backend with the -O flag and recreate the index. The description I
have
for the index is:

Indexes: pg_statistic_relid_att_index unique btree (starelid,
staattnum)

-- 
Bruce Momjian                        |  http://candle.pha.pa.us
pgman@candle.pha.pa.us               |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania
19026

---------------------------(end of
broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

=====
Chris Albertson
Home: 310-376-1029 chrisalbertson90278@yahoo.com
Cell: 310-990-7550
Office: 310-336-5189 Christopher.J.Albertson@aero.org

__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com