After manually extracting the data and making it in synch on the remote
database, you should execute a remote rest on the consolidated for the new
remote user and on the remote database for the consolidated user.
See the following section of the docs :
SQL Remote User's Guide
18. Command Reference for Adaptive Server Enterprise
sp_remote procedure
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"jshutter" wrote in message
news:[email protected]...
>
> I am using all ASE's in my SQLRemote setup.
>
> My current installation consists of a Consolidated ASE & 2 Remote ASE's.
>
>
>
> My attempt to add another Remote ASE to the existing installation
> consists of these steps:
>
> - Install the sqlremote system objects in the new Remote
>
> - Install the stable queues in the new Remote
>
> - Manually extract a bcp file of the shared table from the Cons
> server
>
> - Configure the Cons server for another subscriber
>
> - Configure the new Remote's shared table, publications, &
> subscriptions.
>
> - Manually bcp the table's contents into the new Remote's table
>
> - Execute all the Message Agents as before - with the new one as
> well.
>
> - (of course, I add all the appropriate logins, users,
> permissions, etc.)
>
>
>
> The old members of the installation still talk to one another. However,
> the Consolidated can't receive messages from the new Remote, and the new
> Remote can't receive messages from the Cons.
>
>
>
> Msg Agent Errors:
>
> Cons: Not applying operations with old resend count
>
> Rmt: Warning: Received operations sent to previous extract of this
> database or sent to pre-recovered version of this database.
>
>
>
> Is this just a limitation of ASE-to-ASE replication, since I can't use
> the "extract" tool -- or is there something I can do?
>
>
> --
> Posted via http://dbforums.com