Great. It works now. Thank a ton.
This forum is amazing. Really appreciating all your help.


-----Original Message-----
From: Jan Wieck [mailto:jan at wi3ck.info] 
Sent: Thursday, April 17, 2014 11:58 AM
To: Samir Parikh; Glyn Astill; slony1-general at lists.slony.info
Subject: Re: [Slony1-general] Slony setup error

On 04/17/14 14:56, Jan Wieck wrote:
> On 04/17/14 14:51, Samir Parikh wrote:
>> Some success. I  could now set up the replication after dropping/recreating the replication schema on both nodes.
>> Now I am trying to add tables to set using slonik script and stuck with this syntax error. I googled it and found many instances of this error but could not find any solution that work for me.
>>
>> <stdin>:1: ERROR: syntax error at or near replication
>> [root at vmbndbdev01 ~]# slonik <<_EOF_
>>> cluster name = 'replication'
>>> _EOF_
>> <stdin>:1: ERROR: syntax error at or near replication
>
> The bison parser for this isn't the best in the world.
>
> It expects at least one admin conninfo and one actual command too.
> Otherwise it is not considered a complete script and in bison "syntax 
> error" is pretty much all you get.

Plus you need a semicolon at the end of course.


Jan

>
>
> Jan
>
>
>>
>> I tried with single,double and no quotes, but not luck with either of those.
>>
>> Thanks much.
>> Samir
>>
>>
>>
>>
>> -----Original Message-----
>> From: Jan Wieck [mailto:jan at wi3ck.info]
>> Sent: Thursday, April 17, 2014 10:30 AM
>> To: Samir Parikh; Glyn Astill; slony1-general at lists.slony.info
>> Subject: Re: [Slony1-general] Slony setup error
>>
>> On 04/17/14 12:50, Samir Parikh wrote:
>>> Thanks for the quick response. Yes, you are right function getLocalNodeId does not exist on subscriber node but it does exists on primary node. On further check I could see on primary node under replication schema total 127 functions but in subscriber node I could see only 112. Not sure why there are missing functions which include getLocalNodeId.
>>>
>>> This is the very first time I am trying to set up slony replication. I am following documentation on slony.info.
>>
>> That sounds very odd.
>>
>> I would suggest doing an UNINSTALL NODE, DROP NODE (both for the non-functioning one), waiting until all traces of the dropped node are gone from the system (or using a different node ID to be sure) and then start over from STORE NODE, STORE PATH all the way.
>>
>> And make sure you use 2.2 or at least 2.1. 2.0 is marked end of life and earlier versions have not received any updates/fixes for quite a while now.
>>
>>
>> Regards,
>> Jan
>>
>>
>>>
>>> Thanks again.
>>> Samir
>>>
>>> -----Original Message-----
>>> From: Glyn Astill [mailto:glynastill at yahoo.co.uk]
>>> Sent: Thursday, April 17, 2014 2:20 AM
>>> To: Samir Parikh; slony1-general at lists.slony.info
>>> Subject: Re: [Slony1-general] Slony setup error
>>>
>>>> From: Samir Parikh <SParikh at CarCharging.com>
>>>
>>>>To: "slony1-general at lists.slony.info" 
>>>><slony1-general at lists.slony.info>
>>>>Sent: Thursday, 17 April 2014, 2:06
>>>>Subject: [Slony1-general] Slony setup error
>>>>
>>>>
>>>>I am getting following error while trying to set up replication ? Can somebody help ?
>>>>
>>>>./slonik_subscribe_set 1 2 | ./slonik
>>>><stdin>:5: PGRES_FATAL_ERROR select max(ev_seqno) FROM 
>>>>"_replication".sl_event , "_replication".sl_node  where ev_origin="_replication".getLocalNodeId('_replication')  AND ev_type <> 'SYNC'  AND sl_node.no_id= ev_origin - ERROR:  function _replication.getlocalnodeid(unknown) does not exist LINE 1: ...l_event , "_replication".sl_node  where ev_origin="_replicat...
>>>>                                                             ^
>>>>HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
>>>>error: unable to query event history on node 2
>>>
>>>
>>> Well have you checked to see if the "_replication" schema and getlocalnodeid function are present on your new subscriber?
>>>
>>>  From the error message I can only assume you've not run "STORE 
>>> NODE" against the node you're trying to subscribe,
>>>
>>>
>>>>waiting for events  (2,221473472232) only at (2,0) to be confirmed 
>>>>on node 1
>>>
>>>
>>> This reinforces my thoughts, as well as running STORE NODE/PATH for your new subscriber you need to make sure you have a slon running against it too.
>>>
>>> Perhaps you could fill us in on the steps you've taken so far so we can see where you've gone off course.
>>>
>>>
>>> Glyn.
>>>
>>> p.s. I'll use this as a test to see if I can still post to the list 
>>> from my yahoo.com address too; I've not much hope it will :-(
>>>
>>> _______________________________________________
>>> Slony1-general mailing list
>>> Slony1-general at lists.slony.info
>>> http://lists.slony.info/mailman/listinfo/slony1-general
>>>
>>
>>
>
>


--
Jan Wieck
Senior Software Engineer
http://slony.info