ASE -> ASE replication with NFS mount

I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data between two
servers. All my tests to replicate database between two databases on the
same server work fine using the file system as a way to replicated data. I
am now trying to replicate a database between two servers still using the
file system but using an nfs mount versus ftp but it does not work, the data
is never relicated.

Does the directory structure need to be the same on both machines?

On the source server the directory structure is:
     /sybase_backup/replication/source
     /sybase_backup/replication/target

On the remote server I mount  the /sybase_backup on /repdata so I get
    /repdata/replication/source
    /repdata/replication/target

I run sremote inside the replication directory. Does ssremote remember the
complete directory structure name when it gets the data out of the source
system?




0
Germano
1/26/2000 7:06:36 PM
sybase.sqlanywhere.replication 4591 articles. 0 followers. Follow

8 Replies
746 Views

Similar Articles

[PageSpeed] 9

What version and build number?
Have you set a SQL Remote environment variable?
What are the message addresses for the consolidated and the remote
databases?


--
-------------------------------------------------------
Robert Waywell
Sybase
Please Respond to Newsgroups

Germano Silva wrote in message ...
>I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data between two
>servers. All my tests to replicate database between two databases on the
>same server work fine using the file system as a way to replicated data. I
>am now trying to replicate a database between two servers still using the
>file system but using an nfs mount versus ftp but it does not work, the
data
>is never relicated.
>
>Does the directory structure need to be the same on both machines?
>
>On the source server the directory structure is:
>     /sybase_backup/replication/source
>     /sybase_backup/replication/target
>
>On the remote server I mount  the /sybase_backup on /repdata so I get
>    /repdata/replication/source
>    /repdata/replication/target
>
>I run sremote inside the replication directory. Does ssremote remember the
>complete directory structure name when it gets the data out of the source
>system?
>
>
>
>


0
Robert
1/26/2000 11:02:55 PM
Just so we are clear.

You would create ALL messages on 1 drive.  The other server maps a drive to
that box.

so the consolidated would have:
set SQLREMOTE=c:\repmsgs
c:\repmsgs\cons
c:\repmsgs\remote

On the remote you would:
net use x: \\cons_server\share_to_repmsgs
set SQLREMOTE=x:\

In either case, the addresses stored in the database are "cons" and
"remote",
ie  grant remote to dave type file address 'remote'
or the equivalent for ssremote.


--
David Fishburn
Sybase
Please only post to the newsgroup

Sybase Developers Network
http://sdn.sybase.com/sdn/mec/mec_home.stm

Germano Silva <Germano_Silva@brown.ed> wrote in message
news:v3muyDDa$GA.303@forums.sybase.com...
> I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data between
two
> servers. All my tests to replicate database between two databases on the
> same server work fine using the file system as a way to replicated data. I
> am now trying to replicate a database between two servers still using the
> file system but using an nfs mount versus ftp but it does not work, the
data
> is never relicated.
>
> Does the directory structure need to be the same on both machines?
>
> On the source server the directory structure is:
>      /sybase_backup/replication/source
>      /sybase_backup/replication/target
>
> On the remote server I mount  the /sybase_backup on /repdata so I get
>     /repdata/replication/source
>     /repdata/replication/target
>
> I run sremote inside the replication directory. Does ssremote remember the
> complete directory structure name when it gets the data out of the source
> system?
>
>
>
>


0
David
1/26/2000 11:28:58 PM
Let me clarify my setup.

First of all, I'm runing this on a UNIX box and here's the output of running
ssremote on both server:

On the consolidated database the SQLREMOTE variable is set to
/sybase_backup/replication as you can see below. Under this directory, there
are two more directories (source and target). I used the following command
in isql to set the remote type to file and point to the source directory.

use testdb
go
exec sp_remote_type file, source
go

----------------------------------------------------------------------------
----------------------------
SQLREMOTE=/sybase_backup/replication
advprod.adis.brown.edu% ssremote -v -c
"eng=srvprod;dbn=testdb;uid=source_user;pwd=source_pwd"
I. 01/27 10:03:16. Sybase SQL Remote Message Agent Version 6.0.3.2833
I. 01/27 10:03:16.
I. 01/27 10:03:16. This software contains confidential and trade secret
information of
I. 01/27 10:03:16. Sybase, Inc.  Use, duplication or disclosure of the
software and
I. 01/27 10:03:16. documentation by the U.S. Government is subject to
restrictions set forth
I. 01/27 10:03:16. in a license agreement between the Government and Sybase,
Inc. or other
I. 01/27 10:03:16. written agreement specifying the Government's rights to
use the software
I. 01/27 10:03:16. and any applicable FAR provisions, for example, FAR
52.227-19.
I. 01/27 10:03:16.
I. 01/27 10:03:16. Copyright 1989-1999 Sybase, Inc.  All rights reserved.
I. 01/27 10:03:16. All unpublished rights reserved.
I. 01/27 10:03:16.
I. 01/27 10:03:16. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608,
USA
I. 01/27 10:03:16.
I. 01/27 10:03:17. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
I. 01/27 10:03:29. Scanning logs starting at offset beginning
I. 01/27 10:03:29. Scanning transactions from transaction log into stable
queue
I. 01/27 10:03:32. Processing transactions from stable queue
I. 01/27 10:03:32. Sending message to "target_user" (0-0000000000-0)
I. 01/27 10:03:35. Execution completed
----------------------------------------------------------------------------
----------------------------

On the remote database the SQLREMOTE variable is set to /repdata/replication
and I use the following SQL command to set the remote typw:

use testdb
go
--
-- Declare a message type
--
exec sp_remote_type file, target
go


----------------------------------------------------------------------------
----------------------------
SQLREMOTE=/repdata/replication
devdemo.adis.brown.edu% pwd
/repdata/replication
devdemo.adis.brown.edu% ls -lp
total 4
drwxrwxrwx   2 65535    other        512 Jan 27 09:20 source/
drwxrwxrwx   2 65535    other        512 Jan 27  2000 target/
devdemo.adis.brown.edu% ssremote -v -c
"eng=srvdemo;dbn=testdb;uid=target_user;pwd=target_pwd"
I. 01/27 09:52:02. Sybase SQL Remote Message Agent Version 6.0.3.2833
I. 01/27 09:52:02.
I. 01/27 09:52:02. This software contains confidential and trade secret
information of
I. 01/27 09:52:02. Sybase, Inc.  Use, duplication or disclosure of the
software and
I. 01/27 09:52:02. documentation by the U.S. Government is subject to
restrictions set forth
I. 01/27 09:52:02. in a license agreement between the Government and Sybase,
Inc. or other
I. 01/27 09:52:02. written agreement specifying the Government's rights to
use the software
I. 01/27 09:52:02. and any applicable FAR provisions, for example, FAR
52.227-19.
I. 01/27 09:52:02.
I. 01/27 09:52:02. Copyright 1989-1999 Sybase, Inc.  All rights reserved.
I. 01/27 09:52:02. All unpublished rights reserved.
I. 01/27 09:52:02.
I. 01/27 09:52:02. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608,
USA
I. 01/27 09:52:02.
I. 01/27 09:52:02. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
I. 01/27 09:52:06. Scanning logs starting at offset beginning
I. 01/27 09:52:06. Scanning transactions from transaction log into stable
queue
I. 01/27 09:52:09. Processing transactions from stable queue
I. 01/27 09:52:09. Sending message to "source_user" (0-0000000000-0)
I. 01/27 09:52:11. Execution completed

This works fine on the same server and yesterday I ran a test by setting the
directory structure exactly the same on both servers and ftp'ing the file
and everything worked fine. I would like to bypass the ftp process my just
doing a nfs mount (mapping a drive) from the remote to the consolidated box,
but when I do that, things don't work as you can see.




David Fishburn <spamoff_fishburn@sybase.com> wrote in message
news:SzNaPWFa$GA.96@forums.sybase.com...
> Just so we are clear.
>
> You would create ALL messages on 1 drive.  The other server maps a drive
to
> that box.
>
> so the consolidated would have:
> set SQLREMOTE=c:\repmsgs
> c:\repmsgs\cons
> c:\repmsgs\remote
>
> On the remote you would:
> net use x: \\cons_server\share_to_repmsgs
> set SQLREMOTE=x:\
>
> In either case, the addresses stored in the database are "cons" and
> "remote",
> ie  grant remote to dave type file address 'remote'
> or the equivalent for ssremote.
>
>
> --
> David Fishburn
> Sybase
> Please only post to the newsgroup
>
> Sybase Developers Network
> http://sdn.sybase.com/sdn/mec/mec_home.stm
>
> Germano Silva <Germano_Silva@brown.ed> wrote in message
> news:v3muyDDa$GA.303@forums.sybase.com...
> > I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data between
> two
> > servers. All my tests to replicate database between two databases on the
> > same server work fine using the file system as a way to replicated data.
I
> > am now trying to replicate a database between two servers still using
the
> > file system but using an nfs mount versus ftp but it does not work, the
> data
> > is never relicated.
> >
> > Does the directory structure need to be the same on both machines?
> >
> > On the source server the directory structure is:
> >      /sybase_backup/replication/source
> >      /sybase_backup/replication/target
> >
> > On the remote server I mount  the /sybase_backup on /repdata so I get
> >     /repdata/replication/source
> >     /repdata/replication/target
> >
> > I run sremote inside the replication directory. Does ssremote remember
the
> > complete directory structure name when it gets the data out of the
source
> > system?
> >
> >
> >
> >
>
>


0
Germano
1/27/2000 3:15:51 PM
Here are some more findings from tests that I did today.

On the consolidated database server I set SQLREMOTE to point to
/sybase_backup/replication, run ssremote from anywhere as  ssremote -v -c
"eng=srv1;dbn=testdb;uid=source_user;pwd=source_pwd" and the file gets
written as /sybase_backup/replication/target/source.0

I now go over to the remote machine and set SQLREMOTE to
/repdata/replication, which is mapped to remote:/sybase_backup/replication,
run ssremote from anywhere as ssremote -v -c
"eng=srv2;dbn=testdb;uid=target_user;pwd=target_pwd" and nothing is
replicated. I copy the files from the source server to
/sybase_backup/replication/target/*, set SQLREMOTE to
/sybase_backup/replication, run same ssremote command and everything works
fine.

So, it looks like the environment variable SQLREMOTE means nothing or it has
to point to the same directory structure, which is not possible in UNIX,
unless I create the same directories on both servers and ftp the data
accross, which is what I'm trying to get away from.

Has this thing ever been tested to do replication with a similar setup as
mine:

ASE to ASE using the file system wih two UNIX servers


David Fishburn <spamoff_fishburn@sybase.com> wrote in message
news:SzNaPWFa$GA.96@forums.sybase.com...
> Just so we are clear.
>
> You would create ALL messages on 1 drive.  The other server maps a drive
to
> that box.
>
> so the consolidated would have:
> set SQLREMOTE=c:\repmsgs
> c:\repmsgs\cons
> c:\repmsgs\remote
>
> On the remote you would:
> net use x: \\cons_server\share_to_repmsgs
> set SQLREMOTE=x:\
>
> In either case, the addresses stored in the database are "cons" and
> "remote",
> ie  grant remote to dave type file address 'remote'
> or the equivalent for ssremote.
>
>
> --
> David Fishburn
> Sybase
> Please only post to the newsgroup
>
> Sybase Developers Network
> http://sdn.sybase.com/sdn/mec/mec_home.stm
>
> Germano Silva <Germano_Silva@brown.ed> wrote in message
> news:v3muyDDa$GA.303@forums.sybase.com...
> > I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data between
> two
> > servers. All my tests to replicate database between two databases on the
> > same server work fine using the file system as a way to replicated data.
I
> > am now trying to replicate a database between two servers still using
the
> > file system but using an nfs mount versus ftp but it does not work, the
> data
> > is never relicated.
> >
> > Does the directory structure need to be the same on both machines?
> >
> > On the source server the directory structure is:
> >      /sybase_backup/replication/source
> >      /sybase_backup/replication/target
> >
> > On the remote server I mount  the /sybase_backup on /repdata so I get
> >     /repdata/replication/source
> >     /repdata/replication/target
> >
> > I run sremote inside the replication directory. Does ssremote remember
the
> > complete directory structure name when it gets the data out of the
source
> > system?
> >
> >
> >
> >
>
>


0
Germano
1/27/2000 7:58:16 PM
Can you try turning on the debug mode using the sp_link_option system proc
and post the output from running dbremote after adding that option? Can you
also post the sp_remote procedure calls that you used to define the remote
and consolidated users on the consolidated and remote databases
respectively?

    The output you have posted isn't sufficient for me to see the problem
you are experiencing.

--
-------------------------------------------------------
Robert Waywell
Sybase
Please Respond to Newsgroups

Germano Silva wrote in message ...
>Let me clarify my setup.
>
>First of all, I'm runing this on a UNIX box and here's the output of
running
>ssremote on both server:
>
>On the consolidated database the SQLREMOTE variable is set to
>/sybase_backup/replication as you can see below. Under this directory,
there
>are two more directories (source and target). I used the following command
>in isql to set the remote type to file and point to the source directory.
>
>use testdb
>go
>exec sp_remote_type file, source
>go
>
>---------------------------------------------------------------------------
-
>----------------------------
>SQLREMOTE=/sybase_backup/replication
>advprod.adis.brown.edu% ssremote -v -c
>"eng=srvprod;dbn=testdb;uid=source_user;pwd=source_pwd"
>I. 01/27 10:03:16. Sybase SQL Remote Message Agent Version 6.0.3.2833
>I. 01/27 10:03:16.
>I. 01/27 10:03:16. This software contains confidential and trade secret
>information of
>I. 01/27 10:03:16. Sybase, Inc.  Use, duplication or disclosure of the
>software and
>I. 01/27 10:03:16. documentation by the U.S. Government is subject to
>restrictions set forth
>I. 01/27 10:03:16. in a license agreement between the Government and
Sybase,
>Inc. or other
>I. 01/27 10:03:16. written agreement specifying the Government's rights to
>use the software
>I. 01/27 10:03:16. and any applicable FAR provisions, for example, FAR
>52.227-19.
>I. 01/27 10:03:16.
>I. 01/27 10:03:16. Copyright 1989-1999 Sybase, Inc.  All rights reserved.
>I. 01/27 10:03:16. All unpublished rights reserved.
>I. 01/27 10:03:16.
>I. 01/27 10:03:16. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608,
>USA
>I. 01/27 10:03:16.
>I. 01/27 10:03:17. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
>Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
>I. 01/27 10:03:29. Scanning logs starting at offset beginning
>I. 01/27 10:03:29. Scanning transactions from transaction log into stable
>queue
>I. 01/27 10:03:32. Processing transactions from stable queue
>I. 01/27 10:03:32. Sending message to "target_user" (0-0000000000-0)
>I. 01/27 10:03:35. Execution completed
>---------------------------------------------------------------------------
-
>----------------------------
>
>On the remote database the SQLREMOTE variable is set to
/repdata/replication
>and I use the following SQL command to set the remote typw:
>
>use testdb
>go
>--
>-- Declare a message type
>--
>exec sp_remote_type file, target
>go
>
>
>---------------------------------------------------------------------------
-
>----------------------------
>SQLREMOTE=/repdata/replication
>devdemo.adis.brown.edu% pwd
>/repdata/replication
>devdemo.adis.brown.edu% ls -lp
>total 4
>drwxrwxrwx   2 65535    other        512 Jan 27 09:20 source/
>drwxrwxrwx   2 65535    other        512 Jan 27  2000 target/
>devdemo.adis.brown.edu% ssremote -v -c
>"eng=srvdemo;dbn=testdb;uid=target_user;pwd=target_pwd"
>I. 01/27 09:52:02. Sybase SQL Remote Message Agent Version 6.0.3.2833
>I. 01/27 09:52:02.
>I. 01/27 09:52:02. This software contains confidential and trade secret
>information of
>I. 01/27 09:52:02. Sybase, Inc.  Use, duplication or disclosure of the
>software and
>I. 01/27 09:52:02. documentation by the U.S. Government is subject to
>restrictions set forth
>I. 01/27 09:52:02. in a license agreement between the Government and
Sybase,
>Inc. or other
>I. 01/27 09:52:02. written agreement specifying the Government's rights to
>use the software
>I. 01/27 09:52:02. and any applicable FAR provisions, for example, FAR
>52.227-19.
>I. 01/27 09:52:02.
>I. 01/27 09:52:02. Copyright 1989-1999 Sybase, Inc.  All rights reserved.
>I. 01/27 09:52:02. All unpublished rights reserved.
>I. 01/27 09:52:02.
>I. 01/27 09:52:02. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608,
>USA
>I. 01/27 09:52:02.
>I. 01/27 09:52:02. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
>Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
>I. 01/27 09:52:06. Scanning logs starting at offset beginning
>I. 01/27 09:52:06. Scanning transactions from transaction log into stable
>queue
>I. 01/27 09:52:09. Processing transactions from stable queue
>I. 01/27 09:52:09. Sending message to "source_user" (0-0000000000-0)
>I. 01/27 09:52:11. Execution completed
>
>This works fine on the same server and yesterday I ran a test by setting
the
>directory structure exactly the same on both servers and ftp'ing the file
>and everything worked fine. I would like to bypass the ftp process my just
>doing a nfs mount (mapping a drive) from the remote to the consolidated
box,
>but when I do that, things don't work as you can see.
>
>
>
>
>David Fishburn <spamoff_fishburn@sybase.com> wrote in message
>news:SzNaPWFa$GA.96@forums.sybase.com...
>> Just so we are clear.
>>
>> You would create ALL messages on 1 drive.  The other server maps a drive
>to
>> that box.
>>
>> so the consolidated would have:
>> set SQLREMOTE=c:\repmsgs
>> c:\repmsgs\cons
>> c:\repmsgs\remote
>>
>> On the remote you would:
>> net use x: \\cons_server\share_to_repmsgs
>> set SQLREMOTE=x:\
>>
>> In either case, the addresses stored in the database are "cons" and
>> "remote",
>> ie  grant remote to dave type file address 'remote'
>> or the equivalent for ssremote.
>>
>>
>> --
>> David Fishburn
>> Sybase
>> Please only post to the newsgroup
>>
>> Sybase Developers Network
>> http://sdn.sybase.com/sdn/mec/mec_home.stm
>>
>> Germano Silva <Germano_Silva@brown.ed> wrote in message
>> news:v3muyDDa$GA.303@forums.sybase.com...
>> > I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data between
>> two
>> > servers. All my tests to replicate database between two databases on
the
>> > same server work fine using the file system as a way to replicated
data.
>I
>> > am now trying to replicate a database between two servers still using
>the
>> > file system but using an nfs mount versus ftp but it does not work, the
>> data
>> > is never relicated.
>> >
>> > Does the directory structure need to be the same on both machines?
>> >
>> > On the source server the directory structure is:
>> >      /sybase_backup/replication/source
>> >      /sybase_backup/replication/target
>> >
>> > On the remote server I mount  the /sybase_backup on /repdata so I get
>> >     /repdata/replication/source
>> >     /repdata/replication/target
>> >
>> > I run sremote inside the replication directory. Does ssremote remember
>the
>> > complete directory structure name when it gets the data out of the
>source
>> > system?
>> >
>> >
>> >
>> >
>>
>>
>
>


0
Robert
1/27/2000 8:08:48 PM
The only sp_remote call that I'm making is ob the consolidated database as
follow:

exec sp_remote reset, target_user

This is the last command before I start replicating data. As far as running
sp_link_option, I cannot find any documentation on what options can be
turned on, also, do you realise that I don't run dbremote,. In UNIX ssremote
is used to perform both operations.

Can you tell me how to run sp_link_option?



I can't find any documentation on how to use sp_link_option
Robert Waywell <rwaywell@sybase.com> wrote in message
news:rBjSCLQa$GA.85@forums.sybase.com...
> Can you try turning on the debug mode using the sp_link_option system proc
> and post the output from running dbremote after adding that option? Can
you
> also post the sp_remote procedure calls that you used to define the remote
> and consolidated users on the consolidated and remote databases
> respectively?
>
>     The output you have posted isn't sufficient for me to see the problem
> you are experiencing.
>
> --
> -------------------------------------------------------
> Robert Waywell
> Sybase
> Please Respond to Newsgroups
>
> Germano Silva wrote in message ...
> >Let me clarify my setup.
> >
> >First of all, I'm runing this on a UNIX box and here's the output of
> running
> >ssremote on both server:
> >
> >On the consolidated database the SQLREMOTE variable is set to
> >/sybase_backup/replication as you can see below. Under this directory,
> there
> >are two more directories (source and target). I used the following
command
> >in isql to set the remote type to file and point to the source directory.
> >
> >use testdb
> >go
> >exec sp_remote_type file, source
> >go
> >
>
>---------------------------------------------------------------------------
> -
> >----------------------------
> >SQLREMOTE=/sybase_backup/replication
> >advprod.adis.brown.edu% ssremote -v -c
> >"eng=srvprod;dbn=testdb;uid=source_user;pwd=source_pwd"
> >I. 01/27 10:03:16. Sybase SQL Remote Message Agent Version 6.0.3.2833
> >I. 01/27 10:03:16.
> >I. 01/27 10:03:16. This software contains confidential and trade secret
> >information of
> >I. 01/27 10:03:16. Sybase, Inc.  Use, duplication or disclosure of the
> >software and
> >I. 01/27 10:03:16. documentation by the U.S. Government is subject to
> >restrictions set forth
> >I. 01/27 10:03:16. in a license agreement between the Government and
> Sybase,
> >Inc. or other
> >I. 01/27 10:03:16. written agreement specifying the Government's rights
to
> >use the software
> >I. 01/27 10:03:16. and any applicable FAR provisions, for example, FAR
> >52.227-19.
> >I. 01/27 10:03:16.
> >I. 01/27 10:03:16. Copyright 1989-1999 Sybase, Inc.  All rights reserved.
> >I. 01/27 10:03:16. All unpublished rights reserved.
> >I. 01/27 10:03:16.
> >I. 01/27 10:03:16. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA
94608,
> >USA
> >I. 01/27 10:03:16.
> >I. 01/27 10:03:17. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
> >Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
> >I. 01/27 10:03:29. Scanning logs starting at offset beginning
> >I. 01/27 10:03:29. Scanning transactions from transaction log into stable
> >queue
> >I. 01/27 10:03:32. Processing transactions from stable queue
> >I. 01/27 10:03:32. Sending message to "target_user" (0-0000000000-0)
> >I. 01/27 10:03:35. Execution completed
>
>---------------------------------------------------------------------------
> -
> >----------------------------
> >
> >On the remote database the SQLREMOTE variable is set to
> /repdata/replication
> >and I use the following SQL command to set the remote typw:
> >
> >use testdb
> >go
> >--
> >-- Declare a message type
> >--
> >exec sp_remote_type file, target
> >go
> >
> >
>
>---------------------------------------------------------------------------
> -
> >----------------------------
> >SQLREMOTE=/repdata/replication
> >devdemo.adis.brown.edu% pwd
> >/repdata/replication
> >devdemo.adis.brown.edu% ls -lp
> >total 4
> >drwxrwxrwx   2 65535    other        512 Jan 27 09:20 source/
> >drwxrwxrwx   2 65535    other        512 Jan 27  2000 target/
> >devdemo.adis.brown.edu% ssremote -v -c
> >"eng=srvdemo;dbn=testdb;uid=target_user;pwd=target_pwd"
> >I. 01/27 09:52:02. Sybase SQL Remote Message Agent Version 6.0.3.2833
> >I. 01/27 09:52:02.
> >I. 01/27 09:52:02. This software contains confidential and trade secret
> >information of
> >I. 01/27 09:52:02. Sybase, Inc.  Use, duplication or disclosure of the
> >software and
> >I. 01/27 09:52:02. documentation by the U.S. Government is subject to
> >restrictions set forth
> >I. 01/27 09:52:02. in a license agreement between the Government and
> Sybase,
> >Inc. or other
> >I. 01/27 09:52:02. written agreement specifying the Government's rights
to
> >use the software
> >I. 01/27 09:52:02. and any applicable FAR provisions, for example, FAR
> >52.227-19.
> >I. 01/27 09:52:02.
> >I. 01/27 09:52:02. Copyright 1989-1999 Sybase, Inc.  All rights reserved.
> >I. 01/27 09:52:02. All unpublished rights reserved.
> >I. 01/27 09:52:02.
> >I. 01/27 09:52:02. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA
94608,
> >USA
> >I. 01/27 09:52:02.
> >I. 01/27 09:52:02. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
> >Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
> >I. 01/27 09:52:06. Scanning logs starting at offset beginning
> >I. 01/27 09:52:06. Scanning transactions from transaction log into stable
> >queue
> >I. 01/27 09:52:09. Processing transactions from stable queue
> >I. 01/27 09:52:09. Sending message to "source_user" (0-0000000000-0)
> >I. 01/27 09:52:11. Execution completed
> >
> >This works fine on the same server and yesterday I ran a test by setting
> the
> >directory structure exactly the same on both servers and ftp'ing the file
> >and everything worked fine. I would like to bypass the ftp process my
just
> >doing a nfs mount (mapping a drive) from the remote to the consolidated
> box,
> >but when I do that, things don't work as you can see.
> >
> >
> >
> >
> >David Fishburn <spamoff_fishburn@sybase.com> wrote in message
> >news:SzNaPWFa$GA.96@forums.sybase.com...
> >> Just so we are clear.
> >>
> >> You would create ALL messages on 1 drive.  The other server maps a
drive
> >to
> >> that box.
> >>
> >> so the consolidated would have:
> >> set SQLREMOTE=c:\repmsgs
> >> c:\repmsgs\cons
> >> c:\repmsgs\remote
> >>
> >> On the remote you would:
> >> net use x: \\cons_server\share_to_repmsgs
> >> set SQLREMOTE=x:\
> >>
> >> In either case, the addresses stored in the database are "cons" and
> >> "remote",
> >> ie  grant remote to dave type file address 'remote'
> >> or the equivalent for ssremote.
> >>
> >>
> >> --
> >> David Fishburn
> >> Sybase
> >> Please only post to the newsgroup
> >>
> >> Sybase Developers Network
> >> http://sdn.sybase.com/sdn/mec/mec_home.stm
> >>
> >> Germano Silva <Germano_Silva@brown.ed> wrote in message
> >> news:v3muyDDa$GA.303@forums.sybase.com...
> >> > I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data
between
> >> two
> >> > servers. All my tests to replicate database between two databases on
> the
> >> > same server work fine using the file system as a way to replicated
> data.
> >I
> >> > am now trying to replicate a database between two servers still using
> >the
> >> > file system but using an nfs mount versus ftp but it does not work,
the
> >> data
> >> > is never relicated.
> >> >
> >> > Does the directory structure need to be the same on both machines?
> >> >
> >> > On the source server the directory structure is:
> >> >      /sybase_backup/replication/source
> >> >      /sybase_backup/replication/target
> >> >
> >> > On the remote server I mount  the /sybase_backup on /repdata so I get
> >> >     /repdata/replication/source
> >> >     /repdata/replication/target
> >> >
> >> > I run sremote inside the replication directory. Does ssremote
remember
> >the
> >> > complete directory structure name when it gets the data out of the
> >source
> >> > system?
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>


0
Germano
1/27/2000 8:32:50 PM
Just to let everyone know that the cause of this problem was a very simple
one. It was only a delete permission on the nfs mount. When sremote ran on
the remote server, it did not have permission to delete the file from
/repdata/target. The problem was that it never gave me any errors at all, I
found out when I tried to delete the file to start another test. Once I
reset the file permissions, everything worked fine.

Robert Waywell <rwaywell@sybase.com> wrote in message
news:rBjSCLQa$GA.85@forums.sybase.com...
> Can you try turning on the debug mode using the sp_link_option system proc
> and post the output from running dbremote after adding that option? Can
you
> also post the sp_remote procedure calls that you used to define the remote
> and consolidated users on the consolidated and remote databases
> respectively?
>
>     The output you have posted isn't sufficient for me to see the problem
> you are experiencing.
>
> --
> -------------------------------------------------------
> Robert Waywell
> Sybase
> Please Respond to Newsgroups
>
> Germano Silva wrote in message ...
> >Let me clarify my setup.
> >
> >First of all, I'm runing this on a UNIX box and here's the output of
> running
> >ssremote on both server:
> >
> >On the consolidated database the SQLREMOTE variable is set to
> >/sybase_backup/replication as you can see below. Under this directory,
> there
> >are two more directories (source and target). I used the following
command
> >in isql to set the remote type to file and point to the source directory.
> >
> >use testdb
> >go
> >exec sp_remote_type file, source
> >go
> >
>
>---------------------------------------------------------------------------
> -
> >----------------------------
> >SQLREMOTE=/sybase_backup/replication
> >advprod.adis.brown.edu% ssremote -v -c
> >"eng=srvprod;dbn=testdb;uid=source_user;pwd=source_pwd"
> >I. 01/27 10:03:16. Sybase SQL Remote Message Agent Version 6.0.3.2833
> >I. 01/27 10:03:16.
> >I. 01/27 10:03:16. This software contains confidential and trade secret
> >information of
> >I. 01/27 10:03:16. Sybase, Inc.  Use, duplication or disclosure of the
> >software and
> >I. 01/27 10:03:16. documentation by the U.S. Government is subject to
> >restrictions set forth
> >I. 01/27 10:03:16. in a license agreement between the Government and
> Sybase,
> >Inc. or other
> >I. 01/27 10:03:16. written agreement specifying the Government's rights
to
> >use the software
> >I. 01/27 10:03:16. and any applicable FAR provisions, for example, FAR
> >52.227-19.
> >I. 01/27 10:03:16.
> >I. 01/27 10:03:16. Copyright 1989-1999 Sybase, Inc.  All rights reserved.
> >I. 01/27 10:03:16. All unpublished rights reserved.
> >I. 01/27 10:03:16.
> >I. 01/27 10:03:16. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA
94608,
> >USA
> >I. 01/27 10:03:16.
> >I. 01/27 10:03:17. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
> >Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
> >I. 01/27 10:03:29. Scanning logs starting at offset beginning
> >I. 01/27 10:03:29. Scanning transactions from transaction log into stable
> >queue
> >I. 01/27 10:03:32. Processing transactions from stable queue
> >I. 01/27 10:03:32. Sending message to "target_user" (0-0000000000-0)
> >I. 01/27 10:03:35. Execution completed
>
>---------------------------------------------------------------------------
> -
> >----------------------------
> >
> >On the remote database the SQLREMOTE variable is set to
> /repdata/replication
> >and I use the following SQL command to set the remote typw:
> >
> >use testdb
> >go
> >--
> >-- Declare a message type
> >--
> >exec sp_remote_type file, target
> >go
> >
> >
>
>---------------------------------------------------------------------------
> -
> >----------------------------
> >SQLREMOTE=/repdata/replication
> >devdemo.adis.brown.edu% pwd
> >/repdata/replication
> >devdemo.adis.brown.edu% ls -lp
> >total 4
> >drwxrwxrwx   2 65535    other        512 Jan 27 09:20 source/
> >drwxrwxrwx   2 65535    other        512 Jan 27  2000 target/
> >devdemo.adis.brown.edu% ssremote -v -c
> >"eng=srvdemo;dbn=testdb;uid=target_user;pwd=target_pwd"
> >I. 01/27 09:52:02. Sybase SQL Remote Message Agent Version 6.0.3.2833
> >I. 01/27 09:52:02.
> >I. 01/27 09:52:02. This software contains confidential and trade secret
> >information of
> >I. 01/27 09:52:02. Sybase, Inc.  Use, duplication or disclosure of the
> >software and
> >I. 01/27 09:52:02. documentation by the U.S. Government is subject to
> >restrictions set forth
> >I. 01/27 09:52:02. in a license agreement between the Government and
> Sybase,
> >Inc. or other
> >I. 01/27 09:52:02. written agreement specifying the Government's rights
to
> >use the software
> >I. 01/27 09:52:02. and any applicable FAR provisions, for example, FAR
> >52.227-19.
> >I. 01/27 09:52:02.
> >I. 01/27 09:52:02. Copyright 1989-1999 Sybase, Inc.  All rights reserved.
> >I. 01/27 09:52:02. All unpublished rights reserved.
> >I. 01/27 09:52:02.
> >I. 01/27 09:52:02. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA
94608,
> >USA
> >I. 01/27 09:52:02.
> >I. 01/27 09:52:02. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
> >Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
> >I. 01/27 09:52:06. Scanning logs starting at offset beginning
> >I. 01/27 09:52:06. Scanning transactions from transaction log into stable
> >queue
> >I. 01/27 09:52:09. Processing transactions from stable queue
> >I. 01/27 09:52:09. Sending message to "source_user" (0-0000000000-0)
> >I. 01/27 09:52:11. Execution completed
> >
> >This works fine on the same server and yesterday I ran a test by setting
> the
> >directory structure exactly the same on both servers and ftp'ing the file
> >and everything worked fine. I would like to bypass the ftp process my
just
> >doing a nfs mount (mapping a drive) from the remote to the consolidated
> box,
> >but when I do that, things don't work as you can see.
> >
> >
> >
> >
> >David Fishburn <spamoff_fishburn@sybase.com> wrote in message
> >news:SzNaPWFa$GA.96@forums.sybase.com...
> >> Just so we are clear.
> >>
> >> You would create ALL messages on 1 drive.  The other server maps a
drive
> >to
> >> that box.
> >>
> >> so the consolidated would have:
> >> set SQLREMOTE=c:\repmsgs
> >> c:\repmsgs\cons
> >> c:\repmsgs\remote
> >>
> >> On the remote you would:
> >> net use x: \\cons_server\share_to_repmsgs
> >> set SQLREMOTE=x:\
> >>
> >> In either case, the addresses stored in the database are "cons" and
> >> "remote",
> >> ie  grant remote to dave type file address 'remote'
> >> or the equivalent for ssremote.
> >>
> >>
> >> --
> >> David Fishburn
> >> Sybase
> >> Please only post to the newsgroup
> >>
> >> Sybase Developers Network
> >> http://sdn.sybase.com/sdn/mec/mec_home.stm
> >>
> >> Germano Silva <Germano_Silva@brown.ed> wrote in message
> >> news:v3muyDDa$GA.303@forums.sybase.com...
> >> > I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data
between
> >> two
> >> > servers. All my tests to replicate database between two databases on
> the
> >> > same server work fine using the file system as a way to replicated
> data.
> >I
> >> > am now trying to replicate a database between two servers still using
> >the
> >> > file system but using an nfs mount versus ftp but it does not work,
the
> >> data
> >> > is never relicated.
> >> >
> >> > Does the directory structure need to be the same on both machines?
> >> >
> >> > On the source server the directory structure is:
> >> >      /sybase_backup/replication/source
> >> >      /sybase_backup/replication/target
> >> >
> >> > On the remote server I mount  the /sybase_backup on /repdata so I get
> >> >     /repdata/replication/source
> >> >     /repdata/replication/target
> >> >
> >> > I run sremote inside the replication directory. Does ssremote
remember
> >the
> >> > complete directory structure name when it gets the data out of the
> >source
> >> > system?
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>


0
Germano
1/28/2000 2:47:16 PM
From the 6.0.3 on-line documentation:
-------------------------------------------------------

  Data Replication with SQL Remote
    PART 4 . Reference
      CHAPTER 18.  Command Reference for Adaptive Server Enterprise

 sp_link_option procedure

    Your earlier posts had indicated that you were using 6.0.3. This syntax
was introduced in 6.0.3 and did not exist in earlier versions.

    I did indeed realize that you were using ssremote which is why I
referred to the sp_link_option procedure instead of referring you to the SET
REMOTE OPTION statement which would be more commonly used on ASA.

    Glad to hear that you found the answer.

--
-------------------------------------------------------
Robert Waywell
Sybase
Please Respond to Newsgroups

http://sdn.sybase.com/sdn/mec/mec_down.stm


Germano Silva wrote in message ...
>The only sp_remote call that I'm making is ob the consolidated database as
>follow:
>
>exec sp_remote reset, target_user
>
>This is the last command before I start replicating data. As far as running
>sp_link_option, I cannot find any documentation on what options can be
>turned on, also, do you realise that I don't run dbremote,. In UNIX
ssremote
>is used to perform both operations.
>
>Can you tell me how to run sp_link_option?
>
>
>
>I can't find any documentation on how to use sp_link_option
>Robert Waywell <rwaywell@sybase.com> wrote in message
>news:rBjSCLQa$GA.85@forums.sybase.com...
>> Can you try turning on the debug mode using the sp_link_option system
proc
>> and post the output from running dbremote after adding that option? Can
>you
>> also post the sp_remote procedure calls that you used to define the
remote
>> and consolidated users on the consolidated and remote databases
>> respectively?
>>
>>     The output you have posted isn't sufficient for me to see the problem
>> you are experiencing.
>>
>> --
>> -------------------------------------------------------
>> Robert Waywell
>> Sybase
>> Please Respond to Newsgroups
>>
>> Germano Silva wrote in message ...
>> >Let me clarify my setup.
>> >
>> >First of all, I'm runing this on a UNIX box and here's the output of
>> running
>> >ssremote on both server:
>> >
>> >On the consolidated database the SQLREMOTE variable is set to
>> >/sybase_backup/replication as you can see below. Under this directory,
>> there
>> >are two more directories (source and target). I used the following
>command
>> >in isql to set the remote type to file and point to the source
directory.
>> >
>> >use testdb
>> >go
>> >exec sp_remote_type file, source
>> >go
>> >
>>
>>--------------------------------------------------------------------------
-
>> -
>> >----------------------------
>> >SQLREMOTE=/sybase_backup/replication
>> >advprod.adis.brown.edu% ssremote -v -c
>> >"eng=srvprod;dbn=testdb;uid=source_user;pwd=source_pwd"
>> >I. 01/27 10:03:16. Sybase SQL Remote Message Agent Version 6.0.3.2833
>> >I. 01/27 10:03:16.
>> >I. 01/27 10:03:16. This software contains confidential and trade secret
>> >information of
>> >I. 01/27 10:03:16. Sybase, Inc.  Use, duplication or disclosure of the
>> >software and
>> >I. 01/27 10:03:16. documentation by the U.S. Government is subject to
>> >restrictions set forth
>> >I. 01/27 10:03:16. in a license agreement between the Government and
>> Sybase,
>> >Inc. or other
>> >I. 01/27 10:03:16. written agreement specifying the Government's rights
>to
>> >use the software
>> >I. 01/27 10:03:16. and any applicable FAR provisions, for example, FAR
>> >52.227-19.
>> >I. 01/27 10:03:16.
>> >I. 01/27 10:03:16. Copyright 1989-1999 Sybase, Inc.  All rights
reserved.
>> >I. 01/27 10:03:16. All unpublished rights reserved.
>> >I. 01/27 10:03:16.
>> >I. 01/27 10:03:16. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA
>94608,
>> >USA
>> >I. 01/27 10:03:16.
>> >I. 01/27 10:03:17. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
>> >Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
>> >I. 01/27 10:03:29. Scanning logs starting at offset beginning
>> >I. 01/27 10:03:29. Scanning transactions from transaction log into
stable
>> >queue
>> >I. 01/27 10:03:32. Processing transactions from stable queue
>> >I. 01/27 10:03:32. Sending message to "target_user" (0-0000000000-0)
>> >I. 01/27 10:03:35. Execution completed
>>
>>--------------------------------------------------------------------------
-
>> -
>> >----------------------------
>> >
>> >On the remote database the SQLREMOTE variable is set to
>> /repdata/replication
>> >and I use the following SQL command to set the remote typw:
>> >
>> >use testdb
>> >go
>> >--
>> >-- Declare a message type
>> >--
>> >exec sp_remote_type file, target
>> >go
>> >
>> >
>>
>>--------------------------------------------------------------------------
-
>> -
>> >----------------------------
>> >SQLREMOTE=/repdata/replication
>> >devdemo.adis.brown.edu% pwd
>> >/repdata/replication
>> >devdemo.adis.brown.edu% ls -lp
>> >total 4
>> >drwxrwxrwx   2 65535    other        512 Jan 27 09:20 source/
>> >drwxrwxrwx   2 65535    other        512 Jan 27  2000 target/
>> >devdemo.adis.brown.edu% ssremote -v -c
>> >"eng=srvdemo;dbn=testdb;uid=target_user;pwd=target_pwd"
>> >I. 01/27 09:52:02. Sybase SQL Remote Message Agent Version 6.0.3.2833
>> >I. 01/27 09:52:02.
>> >I. 01/27 09:52:02. This software contains confidential and trade secret
>> >information of
>> >I. 01/27 09:52:02. Sybase, Inc.  Use, duplication or disclosure of the
>> >software and
>> >I. 01/27 09:52:02. documentation by the U.S. Government is subject to
>> >restrictions set forth
>> >I. 01/27 09:52:02. in a license agreement between the Government and
>> Sybase,
>> >Inc. or other
>> >I. 01/27 09:52:02. written agreement specifying the Government's rights
>to
>> >use the software
>> >I. 01/27 09:52:02. and any applicable FAR provisions, for example, FAR
>> >52.227-19.
>> >I. 01/27 09:52:02.
>> >I. 01/27 09:52:02. Copyright 1989-1999 Sybase, Inc.  All rights
reserved.
>> >I. 01/27 09:52:02. All unpublished rights reserved.
>> >I. 01/27 09:52:02.
>> >I. 01/27 09:52:02. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA
>94608,
>> >USA
>> >I. 01/27 09:52:02.
>> >I. 01/27 09:52:02. Sybase Client-Library/11.1.1/P-EBF8058/sun_svr4/SPARC
>> >Solaris 2.5.1/1/OPT/Sat Aug  8 00:37:35 1998
>> >I. 01/27 09:52:06. Scanning logs starting at offset beginning
>> >I. 01/27 09:52:06. Scanning transactions from transaction log into
stable
>> >queue
>> >I. 01/27 09:52:09. Processing transactions from stable queue
>> >I. 01/27 09:52:09. Sending message to "source_user" (0-0000000000-0)
>> >I. 01/27 09:52:11. Execution completed
>> >
>> >This works fine on the same server and yesterday I ran a test by setting
>> the
>> >directory structure exactly the same on both servers and ftp'ing the
file
>> >and everything worked fine. I would like to bypass the ftp process my
>just
>> >doing a nfs mount (mapping a drive) from the remote to the consolidated
>> box,
>> >but when I do that, things don't work as you can see.
>> >
>> >
>> >
>> >
>> >David Fishburn <spamoff_fishburn@sybase.com> wrote in message
>> >news:SzNaPWFa$GA.96@forums.sybase.com...
>> >> Just so we are clear.
>> >>
>> >> You would create ALL messages on 1 drive.  The other server maps a
>drive
>> >to
>> >> that box.
>> >>
>> >> so the consolidated would have:
>> >> set SQLREMOTE=c:\repmsgs
>> >> c:\repmsgs\cons
>> >> c:\repmsgs\remote
>> >>
>> >> On the remote you would:
>> >> net use x: \\cons_server\share_to_repmsgs
>> >> set SQLREMOTE=x:\
>> >>
>> >> In either case, the addresses stored in the database are "cons" and
>> >> "remote",
>> >> ie  grant remote to dave type file address 'remote'
>> >> or the equivalent for ssremote.
>> >>
>> >>
>> >> --
>> >> David Fishburn
>> >> Sybase
>> >> Please only post to the newsgroup
>> >>
>> >> Sybase Developers Network
>> >> http://sdn.sybase.com/sdn/mec/mec_home.stm
>> >>
>> >> Germano Silva <Germano_Silva@brown.ed> wrote in message
>> >> news:v3muyDDa$GA.303@forums.sybase.com...
>> >> > I'm still evaluating SQL Remote on ASE 11.5.1 to replicate data
>between
>> >> two
>> >> > servers. All my tests to replicate database between two databases on
>> the
>> >> > same server work fine using the file system as a way to replicated
>> data.
>> >I
>> >> > am now trying to replicate a database between two servers still
using
>> >the
>> >> > file system but using an nfs mount versus ftp but it does not work,
>the
>> >> data
>> >> > is never relicated.
>> >> >
>> >> > Does the directory structure need to be the same on both machines?
>> >> >
>> >> > On the source server the directory structure is:
>> >> >      /sybase_backup/replication/source
>> >> >      /sybase_backup/replication/target
>> >> >
>> >> > On the remote server I mount  the /sybase_backup on /repdata so I
get
>> >> >     /repdata/replication/source
>> >> >     /repdata/replication/target
>> >> >
>> >> > I run sremote inside the replication directory. Does ssremote
>remember
>> >the
>> >> > complete directory structure name when it gets the data out of the
>> >source
>> >> > system?
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>


0
Robert
1/28/2000 6:06:54 PM
Reply:

Similar Artilces:

Replication between ASE and ASE URGENT
HI everybody Can you help me please with the following question. We need to syncronize ASE to ASE ( bidirectional) Initially, it was planned to implement with SQL remote, but it isn't available. With replication server, it isn't a solution beacuse, the customer doesn=B4t have a comunntication channel all time. We think use Mobiliink Server to replictase ASE to ASE, but using an ASA in the middle, so that, first it replicate ASE to ASA, and later, ASA to ASE, is it this feasible ??? Thanks four your answer "Marco" <mbarrion@uniplex.com.ec> wr...

2-way replication from ASE to ASE
We are looking at implementing replication server bi-directional. Specifically, we have two databases (for redundancy) on two differnet physical servers, two different ASE databases, but the two databases are named the same, and same architecture. Sybase Learning suggested the only way to do this is to use stored procedures (request function). This is not really bi-directional and does not have the data available in the secondary immediately. Using stored procedures will cause a complete re-write of the application, so it is not really worth it. What we wanted it to do is that i...

ASE Replicator / ASE 12.5
Welcome, Adaptive Server Enterprise/12.5.0.3/EBF 10696 IR/P/Linux Intel/Linux 2.4.7-10smpi686/rel12503/1915/32-bit/OPT/ I had started ASE Replicator with primary connection xxx (with subs,articles,etc.), then I changed primary connection into yyy (and the rest). Everything was fine. But when I try to back to xxx primary connection Sybase returns me this error: 1> sp_addprimaryconn "xxx" 2> go Msg 32000, Level 20, State 0: Server 'ASE_Rep', Procedure 'sp_addprimaryconn', Line 1: Command <sp_addprimaryconn> failed - Could not add Primary...

Replication ASE
Hi, How can i replicate data between 2 ASE servers using SQL Remote, because when i use ssxtract it extracts a anywhere database .db. other question is i wanto replicate data via email, is microsoft exchage server enough for this or i'll need other mail server. thanks in advance Joan jmcd wrote in message <37616E0E.91D29322@else.com.pe>... >Hi, > >How can i replicate data between 2 ASE servers using SQL Remote, because >when i use ssxtract it extracts a anywhere database .db. > Hi I try this type of replication. In documentation i d...

ASE to ASE replication using SQL Remote
Since 11.9.2 comes with SQL Remote, can I use it for replication from ASE to ASE instead of a more expensive Replication Server? Yes you can. A couple of considerations: 1) SQL Remote is not intended for near real-time replication. Even with the new hover mode features, you should plan on at least 1 minute latency in each direction. 2) SSXtract does not support automatically extracting a remote ASE database. You will have to manually configure the remote and consolidated databases, including the initial synchronization of data before you start replication. This is certainly...

ASE to ASE replication using SQL Remote
Since 11.9.2 comes with SQL Remote, can I use it for replication from ASE to ASE instead of a more expensive Replication Server? ...

Replication ASA-ASE stops because ASE is full
I have a replication between a consolidated DB on ASE and 4 remote DB on ASA. During a replication, ssremote was unable to apply messages from the remotes because the segments of the consolidated DB where full. The message of ssremote was : E. 03/31 06:00:06. bourget: Error 1105: Can't allocate space for object 'depot' in database 'stp_qual' because 'default' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase size of the segment. I have increas...

ASE replicator
To all, Can anyone tell me if the ASE Replicator software, included in ASE 12.5.0.1 for other platforms, will be available on linux in the near future? I wasn't able to find anything on this on the Sybase website. Thanks in advance, Dave Winchell "David Winchell" <winchell@bnl.gov> wrote in message news:3D11F86D.33D6280D@bnl.gov... > To all, > Can anyone tell me if the ASE Replicator software, included in > ASE 12.5.0.1 for other platforms, will be available on linux in the > near future? I wasn't able to find anything on this on the S...

ASE Replicator
Hello, I have installed ASE Replicator version 12.5 on Windows N.T.=20 available for download on Sybase?s web site. I have a few problems configuring it. In my java edition of Sybase central = I get the message =AB =AB The ASE replicator not responding. Check the stat= e of=20 the server and the external login permissions =BB when selecting =AB ASE=20 Replicator =BB from the menu. Using ISQL : When I connect onto my ASE, all ASE Replicator commands (sp=5Fconfigurep, ?= )=20 return the following error message : =AB Another Execute Immediate statemen= t=20 cannot be executed in...

ASE and ASE
Could it be possible to take scripts from ASA and load them in an ASE Any information is welcome jean-fran�ois ASA supports a fairly large sub-set of Transact-SQL, so if you write your stored procedures and triggers in ASA using T-SQL, you should be able to create scripts that will run against both ASE and ASA. If you're planning to do this though, I would suggest developing your database schema against ASA, since everything you write in T-SQL in ASA will be supported on ASE, but the reverse is not true. Check out the section in the ASA documentation entitled "Tra...

ASE to ASE
Hi, Is anyone out there doing ASE to ASE replication using SQL remote? If you are have created your own version of the SSEXTRACT utility to set up a replicant database in ASE rather than ASA? Or does anyone know if SYBASE has created a version SSEXTRACT for use with ASE to ASE replication? Thanks in advance Doug Trainer Hi Douglas, I thought the SQL Remote Replication support in ASE11.5 was meant for a consolidate-database only (by design)! At least that was what Sybase said when they announced support for SQL Remote technology support in ASE11.5. I will be happy to...

ASE Replication
We implemented Sybase Replication on our production system last weekend and= =20 have found that we are having to reboot our replication server, because=20 things just appear to stop. When things stop we get error 14027, we also have lots of stuff for concern in our log - as=20 below: E. 2002/04/18 05:49:34. ERROR #14027 USER(rep=5Fra) - =FFexecint.c(1438) Replication Agent for 'prod1.info' is already connected. I. 2002/04/18 05:50:29. Connection to server 'prod2' as user 'rep=5Fmaint' = has been faded out (closed).=20 I. 2002/04/18 05:50:37. Repl...

ASE Replicator
Hi all, I need to replicate an entire database for read only access to some users, since Replication Server is too expensive, I'd like to know if is it possible to use the ASE 12.5 REPLICATOR to replicate all tables of a db , like warm standby with replication server but just in one direction without the possibility to switch between active and standby. Is it possible to realize this ?? Thanks a lot Hi, Yes, you can configure Replicator to replicate the complete contents (user tables and user stored procedures) of a database. However, it will not replicate DDL. I ...

Log Shipping vs. ASE Replicator vs. Replication Server
Dear all, We have recently looked into buying Replication Server, but potentially have decided not to move forward. We are looking into ASE Replicator or Log Shipping instead. What are your thoughts about both strategies (database is about 30 GB in size, can afford up to 2 hour down time, etc.)? We first got a quote for Replication Server and were under the impression that since Replication Server only uses one CPU, you only have to pay for a single CPU license. We just learned today that since we have a 8 CPU server, we will have to pay for a 8 CPU license. They gave us a ...

ASE Replicator
Is anyone here using the ASE Replicator in a production system? Any comments? I've got a system that I may want to implement using this tool - so far my tests show *reasonable* performance, though I haven't really made any load tests, or long running tests as yet. Michael -- Michael Peppler Data Migrations, Inc. mpeppler@peppler.org http://www.peppler.org/ Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or long term contract positions - http://www.peppler.org/resume.html See my comments at ...

Web resources about - ASE -> ASE replication with NFS mount - sybase.sqlanywhere.replication

DNA replication - Wikipedia, the free encyclopedia
DNA replication is a biological process that occurs in all living organisms and copies their DNA ; it is the basis for biological inheritance ...

Facebook Slashes Data Replication With HDFS RAID
Avoiding replication is a key component of efficient data storage , and one method Facebook uses to accomplish this task is HDFS RAID , which ...

PolSci Replication (@PolSciReplicate) on Twitter
Sign in Sign up To bring you Twitter, we and our partners use cookies on our and other websites. Cookies help personalize Twitter content, tailor ...

Encryption in demand for backup and replication: Veeam
When it comes to backup and replication, Veeam has found encryption is one of the most requested feature by businesses.

John Sands Australia cuts data replication time from 14 hours to three
Corporate data replication was taking up to 14 hours to complete at greeting card company John Sands Australia until data acceleration software ...

EMC gives VMware admins the reins to replication and recovery
EMC is putting replication and recovery into the hands of VMware administrators with a software version of its RecoverPoint appliance that's ...

Facebook Slashes Data Replication With HDFS RAID - SocialTimes
Avoiding replication is a key component of efficient data storage , and one method Facebook uses to accomplish this task is HDFS RAID , which ...


Violin to bring deduplication, replication, other tools to all-flash storage arrays
Violin Memory plans to add deduplication, thin provisioning, snapshots and other features in a software update for its all-flash storage arrays, ...

Art & Craft: The Story of an Art Forger Whose Artwork Replication Isn't Actually Illegal
Let me just start off by saying that I don't condone illegal forgery or theft—but I do think that someone who can put the art world in a tizzy ...

Resources last updated: 12/5/2015 12:54:07 AM