7.4.2 initdb problem

From: "Medora Schauer" <mschauer(at)fairfield(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: 7.4.2 initdb problem
Date: 2004-04-19 19:54:46
Message-ID: 906E2C446A276048A1BE283F17BCB12C0146D191@encounter.fairind.fairfield.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I've installed 7.4.2 on a PowerPC system running linux 2.4.13. When I
try to run initdb to create to create the database cluster I get the
following:

$ initdb -D $PGDATA

The files belonging to this database system will be owned by user
"thebox".

This user must also own the server process.

The database cluster will be initialized with locale C.

fixing permissions on existing directory /home/thebox/data/database...
ok

creating directory /home/thebox/data/database/base... ok

creating directory /home/thebox/data/database/global... ok

creating directory /home/thebox/data/database/pg_xlog... ok

creating directory /home/thebox/data/database/pg_clog... ok

selecting default max_connections... 100

selecting default shared_buffers... 1000

creating configuration files... ok

creating template1 database in /home/thebox/data/database/base/1... ok

initializing pg_shadow... ok

enabling unlimited row size for system tables... ok

initializing pg_depend... ok

creating system views... ok

loading pg_description... ok

creating conversions... ERROR: could not load library
"/usr/local/pgsql-7.4.2/lib/ascii_and_mic.so":
/usr/local/pgsql-7.4.2/lib/ascii_and_mic.so: undefined symbol:
pg_mic2ascii

/usr/local/pgsql/bin/initdb: line 842: 11792 Broken pipe
grep -v '^DROP CONVERSION' $datadir/conversion_create.sql

11793 Done(1) | "$PGPATH"/postgres $PGSQL_OPT
template1 >/dev/null

initdb: failed

I'm at a loss as to where I should look for the problem.

Any guidance will be greatly appreciated,

Medora Schauer

Responses

Browse pgsql-general by date

  From Date Subject
Next Message scott.marlowe 2004-04-19 20:17:48 Re: [SQL] SQL script
Previous Message Bob Ghodsi 2004-04-19 19:37:43 Solution to Error 429