[Bacula-users] moving from UTF-8 to SQL_ASCII
2009-06-13 00:18:19
bacula-server-3.0.0, postgresql-server-8.2.13
Looking for guidance on moving a database from UTF-8 to SQL_ASCII.
I've been getting a bunch of warnings like this since moving to bacula 3.x:
bacula-dir JobId 0: Warning: Encoding error for database "bacula".
Wanted SQL_ASCII, got UTF8
I am apparently using UTF-8:
nye# su - pgsql -c 'psql -l | grep bacula'
bacula | bacula | UTF8
Dan Langille's message here suggested a fix:
http://www.mail-archive.com/bacula-devel AT lists.sourceforge DOT
net/msg02632.html
But these instructions produced a database-not-found error:
nye# sudo su - pgsql -c 'pg_dump /usr/home/bacula/baculaold >
/tmp/bacula.sql'
pg_dump: [archiver (db)] connection to database
"/usr/home/bacula/baculaold" failed: FATAL: database
"/usr/home/bacula/baculaold" does not exist
This is odd, since that file does exist and is world-readable:
nye# ls -l /usr/home/bacula/baculaold
total 290
-rw-r--r-- 1 bacula bacula 140976 Oct 25 2007 baculaold
..
Thanks in advance for any clues on getting this conversion done.
dn
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Bacula-users] moving from UTF-8 to SQL_ASCII,
David Newman <=
|
|
|