Hi!

Sorry, I was blind! Double thanks!! Now it works...

Sebastian


----- Original Message ----- 
From: "Christopher Browne" <cbbrowne at ca.afilias.info>
To: "Sebastian K?hner" <skuehner at veraza.com>
Cc: <slony1-general at gborg.postgresql.org>
Sent: Thursday, September 08, 2005 4:02 PM
Subject: Re: [Slony1-general] switchover


Sebastian K?hner <skuehner at veraza.com> writes:
> I'm trying to execute the following swithcover.sh script:
>
> #!/bin/bash
> CLUSTER=sql_cluster5
> H1=192.168.1.225
> H2=192.168.1.223
> U=postgres
> DB1=contact
> DB2=contact
> /usr/local/pgsql/bin/slonik << _END_
> cluster name=$CLUSTER;
> lock set (id=1, origin=1);
> wait for event (origin=1, confirmed=2);
> move set (id=1, old origin=1, new origin=2);
> wait for event (origin = 1, confirmed = 2);
> _END_
>
>
> ...and I'm getting the following error:
>
> <stdin>:2: ERROR: syntax error at or near lock
>
> That means that slonik doesn't recognize the "lock" command?

I think that the problem is that you haven't specified any "node admin
conninfo" entries in the preamble.

Consider:  You have shell variables H1, H2, DB1, and DB2.

But those values are found nowhere in the script that is submitted to
slonik.  So slonik has no idea how to communicate with your databases.
-- 
output = ("cbbrowne" "@" "ca.afilias.info")
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)