[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] CRON DAEMON ERROR MESSAGE
- Subject: Re: [cobalt-users] CRON DAEMON ERROR MESSAGE
- From: Gerald Waugh <gwaugh@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu May 29 07:20:00 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
On Thu, 29 May 2003, Bo von Hohenlohe wrote:
> I would appreciate an explanation. Thanks. Bo
> NOTICE: Index pg_attribute_attrelid_index: NUMBER OF INDEX' TUPLES (592)
> IS NOT THE SAME AS HEAP' (583)
> NOTICE: Index pg_attribute_relid_attnam_index: NUMBER OF INDEX' TUPLES
> (591) IS NOT THE SAME AS HEAP' (583)
> NOTICE: Index pg_attribute_attrelid_index: NUMBER OF INDEX' TUPLES (592)
> IS NOT THE SAME AS HEAP' (583)
> NOTICE: Index pg_attribute_relid_attnam_index: NUMBER OF INDEX' TUPLES
> (591) IS NOT THE SAME AS HEAP' (583)
quotas are screwed up.
You have to dump the postgre database, save a backup,
ecit and hash out the quotas section
drop the cobalt database, import the one you edited.
Search the archives for a detailed procedure
or look here http://www.raqware.com/how2.html
look for Fix TUPLES ISSUE
If it is a RaQ4 use dropdb cobalt instead of destroydb cobalt
Gerald
--
http://frontstreetnetworks.com | http://store.raqware.com
Front Street Networks LLC, 229 Front Street, Ste.#C
New Haven, CT 06513-3203 | phone: +1-203-785-0699