gp_dump: error in finding the last system oid: ERROR: get_relation_info: Relation 1262 not found

Started by Nonameabout 23 years ago3 messagesgeneral
Jump to latest
#1Noname
charette@writeme.com

I'm running into a few database problems, and having a hard time
solving them. Version() tells me PostgreSQL 7.2.3 on
i686-pc-linux-gnu, compiled by GCC 2.95.2.

The problem: when I try to use pg_dumpall, this is the error that I
get:

[...cut...]
--
-- Database log
--
\connect template1 "admin"
CREATE DATABASE "log" WITH TEMPLATE = template0;
\connect "log" "admin"
dumping database "log"...
pg_dump: error in finding the last system oid: ERROR:
get_relation_info: Relation 1262 not found
pg_dump failed on log, exiting

What does this mean, and how do I fix it?

Thanks,

Stephane Charette
stephanecharette <nospam> AT telus <nospam> .net

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Noname (#1)
Re: gp_dump: error in finding the last system oid: ERROR: get_relation_info: Relation 1262 not found

charette@writeme.com (Stephane Charette) writes:

dumping database "log"...
pg_dump: error in finding the last system oid: ERROR:
get_relation_info: Relation 1262 not found

Don't tell me you did something as foolish as dropping pg_database?
No? Well, maybe you've got a corrupted index. Try running a reindex on
pg_class, or on all the system catalogs if that doesn't help. See the
REINDEX reference page for details on the arcane procedure to follow.

regards, tom lane

#3Noname
charette@writeme.com
In reply to: Tom Lane (#2)
Re: gp_dump: error in finding the last system oid: ERROR: get_relation_info: Relation 1262 not found

tgl@sss.pgh.pa.us (Tom Lane) wrote in message news:<7673.1044166693@sss.pgh.pa.us>...

charette@writeme.com (Stephane Charette) writes:

dumping database "log"...
pg_dump: error in finding the last system oid: ERROR:
get_relation_info: Relation 1262 not found

Don't tell me you did something as foolish as dropping pg_database?
No? Well, maybe you've got a corrupted index. Try running a reindex on
pg_class, or on all the system catalogs if that doesn't help. See the
REINDEX reference page for details on the arcane procedure to follow.

No, I did not drop pg_database. I followed the steps to start a
standalone backend in the reference guide under "REINDEX", but it
doesn't seem to be working. This is what I tried:

$ /usr/local/pgsql/bin/postgres -D /usr/local/stuff/data -O -P log
DEBUG: database system was shut down at 2003-01-31 22:10:57 GMT
DEBUG: checkpoint record is at 0/1AF664

DEBUG: redo record is at 0/1AF664; undo record is at 0/0; shutdown
TRUE
DEBUG: next transaction id: 196; next oid: 16632
DEBUG: database system is ready

POSTGRES backend interactive interface
$Revision: 1.245.2.3 $ $Date: 2002/09/30 20:47:22 $

backend> reindex database log force
NOTICE: relation 1247 was reindexed
NOTICE: relation 1249 was reindexed
ERROR: Cannot create unique index. Table contains non-unique values
backend>

What does this mean, and how do I fix it?

Stephane Charette
stephanecharette <nospam> AT telus <nospam> .net