SQL Remote with Existing Replication Server Installation

I've been trying to run SQL Remote with RS and have not yet figured it
out.  Keep getting the following error once I create a RS connection to
the SQL Remote Open Server:

E. 12/22 12:33:50. Error 2812: Stored procedure 'bogus' not found.
Specify owner.objectname or use sp_help to check whether the object
exists (sp_help may produce lots of output).
I. 12/22 12:33:50. ATTENTION handler active
E. 12/22 12:33:59. CTLIB Failure 01010110: ct_command(): user api layer:
external error: This routine cannot be called while results are pending
for a command that has been sent to the server.
I. 12/22 12:33:59. exec sp_queue_set_progress  0, 0, 0000000001,
0000000000, 'Dec 22 1999 11:13:18:653AM'
I. 12/22 12:33:59. Stable Queue Error: cannot set progress

What results are pending?  Has anybody been able to get RS and SQL
Remote to run successfully on the same installation?  Do I need to
purchase the Open Server package?  Any help would be appreciated.

BTW,
Replication Server and Consolidated Database
NT 4.0 SP4
ASE 11.9.2
RS 11.5.1

Remote Database
NT40 SP4
ASA 6.0

Thanks.

D 12/23/1999 8:58:58 PM

Yes, I have done this many, many times.
Since you are using ASA, it speaks native TDS, therefore no Open Server
Package is required.

To make things easier, please list the following:
1.  DBSRV6 start line
2.  SQL.INI file
3.  CREATE CONNECTION statement used for ASA against RS
4.  CREATE CONNECTION statement used for the SQLRemote Open Server (ie
SSQueue.exe)
5.  SSQueue.exe start line

That should get us started.

--
David Fishburn
Sybase
Please only post to the newsgroup



D  wrote in message news:38628D12.7124D247@work.com...
> I've been trying to run SQL Remote with RS and have not yet figured it
> out.  Keep getting the following error once I create a RS connection to
> the SQL Remote Open Server:
>
> E. 12/22 12:33:50. Error 2812: Stored procedure 'bogus' not found.
> Specify owner.objectname or use sp_help to check whether the object
> exists (sp_help may produce lots of output).
> I. 12/22 12:33:50. ATTENTION handler active
> E. 12/22 12:33:59. CTLIB Failure 01010110: ct_command(): user api layer:
> external error: This routine cannot be called while results are pending
> for a command that has been sent to the server.
> I. 12/22 12:33:59. exec sp_queue_set_progress  0, 0, 0000000001,
> 0000000000, 'Dec 22 1999 11:13:18:653AM'
> I. 12/22 12:33:59. Stable Queue Error: cannot set progress
>
> What results are pending?  Has anybody been able to get RS and SQL
> Remote to run successfully on the same installation?  Do I need to
> purchase the Open Server package?  Any help would be appreciated.
>
> BTW,
> Replication Server and Consolidated Database
> NT 4.0 SP4
> ASE 11.9.2
> RS 11.5.1
>
> Remote Database
> NT40 SP4
> ASA 6.0
>
> Thanks.
>

David 12/30/1999 9:20:25 PM

The error has been resolved (via tech support).  As it turns out, I needed a
patch to get ssqueue to the same version as ASA.  But...

I still haven't been able to get 2-way replication going between the remote
ASA site and consolidated ASE site.  I am able to replicate up from the remote
site.

I started ssqueue against my consolidated database and created an RS
connection to the SQL Remote Open Server as an Open Server via Sybase
Central.  This was done with no problem.

I was not able to create the proper RS replication definitions and
subscriptions to the SR tables (from the ssremote.rs script).  Don't know
which server.database names to supply.

Do I need to create an RS connection to the remote ASA databases?  How is this
done?
Are there any shortcomings by doing all of this using Sybase Central?  Should
I be using command line?

The documented procedures from the manual Data Replication With SQL Remote
(Part 3 Chapter 13) are quite ambiguous to me.

Any help will be appreciated.

BTW,
ssqueue start line:
ssqueue.exe -r -s -c"eng=PDB_1;dbn=pdb;uid=sa;pwd=password" -o
"s:
s\osafter.log" "SROS"
no CREATE CONNECTION statements since I used Sybase Central

Thanks.

David Fishburn wrote:

> Yes, I have done this many, many times.
> Since you are using ASA, it speaks native TDS, therefore no Open Server
> Package is required.
>
> To make things easier, please list the following:
> 1.  DBSRV6 start line
> 2.  SQL.INI file
> 3.  CREATE CONNECTION statement used for ASA against RS
> 4.  CREATE CONNECTION statement used for the SQLRemote Open Server (ie
> SSQueue.exe)
> 5.  SSQueue.exe start line
>
> That should get us started.
>
> --
> David Fishburn
> Sybase
> Please only post to the newsgroup
>
> D  wrote in message news:38628D12.7124D247@work.com...
> > I've been trying to run SQL Remote with RS and have not yet figured it
> > out.  Keep getting the following error once I create a RS connection to
> > the SQL Remote Open Server:
> >
> > E. 12/22 12:33:50. Error 2812: Stored procedure 'bogus' not found.
> > Specify owner.objectname or use sp_help to check whether the object
> > exists (sp_help may produce lots of output).
> > I. 12/22 12:33:50. ATTENTION handler active
> > E. 12/22 12:33:59. CTLIB Failure 01010110: ct_command(): user api layer:
> > external error: This routine cannot be called while results are pending
> > for a command that has been sent to the server.
> > I. 12/22 12:33:59. exec sp_queue_set_progress  0, 0, 0000000001,
> > 0000000000, 'Dec 22 1999 11:13:18:653AM'
> > I. 12/22 12:33:59. Stable Queue Error: cannot set progress
> >
> > What results are pending?  Has anybody been able to get RS and SQL
> > Remote to run successfully on the same installation?  Do I need to
> > purchase the Open Server package?  Any help would be appreciated.
> >
> > BTW,
> > Replication Server and Consolidated Database
> > NT 4.0 SP4
> > ASE 11.9.2
> > RS 11.5.1
> >
> > Remote Database
> > NT40 SP4
> > ASA 6.0
> >
> > Thanks.
> >

D 1/3/2000 6:56:17 PM

I do everything from the command line via script files, I have never used
Sybase Central to set this up.  The reason I use scripts is due to the fact
I have to do this over and over again.

Here is an example of the script files I run against my server.  I start
SSQueue.exe using the interface entry "ssqueue".

ssqdef.rs  is run against RS and sets everything up.
ssqdel.rs is run against RS and undoes everything.

ssq.bat is my command line for starting SSQueue.exe

ssremote must be run with either:
1.   -r -s
2.  -r
3.  -s

You must always specify these, so that you never specify -i, since the Rep
Agent for ASE should be the one scanning the ASE transaction log, NOT
ssremote.exe

Start there, compare it with what you did, and I will answer any questions.



--
David Fishburn
Sybase
Please only post to the newsgroup



D  wrote in message news:3870F0D1.6A4BBCDA@work.com...
> The error has been resolved (via tech support).  As it turns out, I needed
a
> patch to get ssqueue to the same version as ASA.  But...
>
> I still haven't been able to get 2-way replication going between the
remote
> ASA site and consolidated ASE site.  I am able to replicate up from the
remote
> site.
>
> I started ssqueue against my consolidated database and created an RS
> connection to the SQL Remote Open Server as an Open Server via Sybase
> Central.  This was done with no problem.
>
> I was not able to create the proper RS replication definitions and
> subscriptions to the SR tables (from the ssremote.rs script).  Don't know
> which server.database names to supply.
>
> Do I need to create an RS connection to the remote ASA databases?  How is
this
> done?
> Are there any shortcomings by doing all of this using Sybase Central?
Should
> I be using command line?
>
> The documented procedures from the manual Data Replication With SQL Remote
> (Part 3 Chapter 13) are quite ambiguous to me.
>
> Any help will be appreciated.
>
> BTW,
> ssqueue start line:
> ssqueue.exe -r -s -c"eng=PDB_1;dbn=pdb;uid=sa;pwd=password" -o
> "s:
s\osafter.log" "SROS"
> no CREATE CONNECTION statements since I used Sybase Central
>
> Thanks.
>
> David Fishburn wrote:
>
> > Yes, I have done this many, many times.
> > Since you are using ASA, it speaks native TDS, therefore no Open Server
> > Package is required.
> >
> > To make things easier, please list the following:
> > 1.  DBSRV6 start line
> > 2.  SQL.INI file
> > 3.  CREATE CONNECTION statement used for ASA against RS
> > 4.  CREATE CONNECTION statement used for the SQLRemote Open Server (ie
> > SSQueue.exe)
> > 5.  SSQueue.exe start line
> >
> > That should get us started.
> >
> > --
> > David Fishburn
> > Sybase
> > Please only post to the newsgroup
> >
> > D  wrote in message news:38628D12.7124D247@work.com...
> > > I've been trying to run SQL Remote with RS and have not yet figured it
> > > out.  Keep getting the following error once I create a RS connection
to
> > > the SQL Remote Open Server:
> > >
> > > E. 12/22 12:33:50. Error 2812: Stored procedure 'bogus' not found.
> > > Specify owner.objectname or use sp_help to check whether the object
> > > exists (sp_help may produce lots of output).
> > > I. 12/22 12:33:50. ATTENTION handler active
> > > E. 12/22 12:33:59. CTLIB Failure 01010110: ct_command(): user api
layer:
> > > external error: This routine cannot be called while results are
pending
> > > for a command that has been sent to the server.
> > > I. 12/22 12:33:59. exec sp_queue_set_progress  0, 0, 0000000001,
> > > 0000000000, 'Dec 22 1999 11:13:18:653AM'
> > > I. 12/22 12:33:59. Stable Queue Error: cannot set progress
> > >
> > > What results are pending?  Has anybody been able to get RS and SQL
> > > Remote to run successfully on the same installation?  Do I need to
> > > purchase the Open Server package?  Any help would be appreciated.
> > >
> > > BTW,
> > > Replication Server and Consolidated Database
> > > NT 4.0 SP4
> > > ASE 11.9.2
> > > RS 11.5.1
> > >
> > > Remote Database
> > > NT40 SP4
> > > ASA 6.0
> > >
> > > Thanks.
> > >
>


begin 666 ssqdel.rs
M+2U&:7)S="!D0T*9V\-"D12
M3U @4D503$E#051)3TX@1$5&24Y)5$E/3B!S'0@9')O<"!A;&P@=&AE(')E<&QI8V%T:6]N
M(&1E9FEN:71I;VYS(%-3475E=64@;F5E9&5D#0IDF4@5$\@
M)RTQ)PT*9V\-"@T*0T].1DE'55)%($-/3DY%0U1)3TX@5$\@6]U<@T*+2T@9&%T82!S97)V97(@
M;F%M92!A;F0@9&%T86)A2!A="!&25-(0E523BYS2!K97D@* T*"0EP=6)L:6-A
M=&EO;E]I9"P-"@D)=7-E2!A="!&25-(0E523BYS2 H#0H)"6]P97)A=&EO;BP-"@D)=F%L=64L
M#0H)"6ED("D-"F=O#0H-"F1E9FEN92!S=6)S8W)I<'1I;VX@2 H#0H)"2)M87)K97(B("D-"F=O#0H-"F1E9FEN
M92!S=6)S8W)I<'1I;VX@0T** T*"7!O;&EC>5]K97D@("!)3E1%1T52+ T*"6-U2!#2$%2*" Q,B I#0HI#0I04DE-05)9($M%
M62 H<&]L:6-Y7VME>2P@8W5S=%]K97DL(')E<%]K97DI#0IG;PT*"0D)"0D)
M"0D)"0D@#0I$149)3D4@4U5"4T-225!424].('-S<75E=65?4&]L:6-Y7W-U
M8@T*1D]2('-S0T*5TE42"!215!,24-!5$4@050@0T*5TE42"!215!,24-!
M5$4@050@0T*
M5TE42"!215!,24-!5$4@050@0T*5TE42"!215!,24-!5$4@050@0T*5TE42"!215!,24-!5$4@050@0T*5TE42"!215!,24-!5$4@
M050@0T*5TE42"!2
M15!,24-!5$4@050@0T*5TE42"!215!,24-!5$4@050@0T*5TE42"!2
M15!,24-!5$4@050@1DE32$)54DXN=V5B5]S=6(-"D9/4B!S0T*5TE42"!215!,24-!5$4@050@
M1DE32$)54DXN=V5B5]S=6(-"D9/4B!S0T*5TE42"!215!,24-!5$4@050@1DE32$)54DXN=V5B
/
                
                     0 
                    David
                    1/3/2000 8:22:04 PM

Everything seems to be working except that I can not replicate from the consolidated
to the remote.  I am trying to replicate from a test table in the consolidated
database that currently is set up for SQL Remote replication.  I created a RS
replication definition for the table and the corresponding subscription to ssqueue but
replication still does not happen.  No errors in the RS log and the table is marked
for replication.

I do have a question about the connection string to the ssqueue in your script.  In
the CREATE CONNECTION you specify ssqueue.ssqueue as the server.database your are
creating the connection for.  When I look at your ssqueue start line, there is no
database called ssqueue.  Shouldn't the connection be created for ssqueue.website (the
database where the stable queue resides)?

David Fishburn wrote:

> I do everything from the command line via script files, I have never used
> Sybase Central to set this up.  The reason I use scripts is due to the fact
> I have to do this over and over again.
>
> Here is an example of the script files I run against my server.  I start
> SSQueue.exe using the interface entry "ssqueue".
>
> ssqdef.rs  is run against RS and sets everything up.
> ssqdel.rs is run against RS and undoes everything.
>
> ssq.bat is my command line for starting SSQueue.exe
>
> ssremote must be run with either:
> 1.   -r -s
> 2.  -r
> 3.  -s
>
> You must always specify these, so that you never specify -i, since the Rep
> Agent for ASE should be the one scanning the ASE transaction log, NOT
> ssremote.exe
>
> Start there, compare it with what you did, and I will answer any questions.
>
> --
> David Fishburn
> Sybase
> Please only post to the newsgroup
>
> D  wrote in message news:3870F0D1.6A4BBCDA@work.com...
> > The error has been resolved (via tech support).  As it turns out, I needed
> a
> > patch to get ssqueue to the same version as ASA.  But...
> >
> > I still haven't been able to get 2-way replication going between the
> remote
> > ASA site and consolidated ASE site.  I am able to replicate up from the
> remote
> > site.
> >
> > I started ssqueue against my consolidated database and created an RS
> > connection to the SQL Remote Open Server as an Open Server via Sybase
> > Central.  This was done with no problem.
> >
> > I was not able to create the proper RS replication definitions and
> > subscriptions to the SR tables (from the ssremote.rs script).  Don't know
> > which server.database names to supply.
> >
> > Do I need to create an RS connection to the remote ASA databases?  How is
> this
> > done?
> > Are there any shortcomings by doing all of this using Sybase Central?
> Should
> > I be using command line?
> >
> > The documented procedures from the manual Data Replication With SQL Remote
> > (Part 3 Chapter 13) are quite ambiguous to me.
> >
> > Any help will be appreciated.
> >
> > BTW,
> > ssqueue start line:
> > ssqueue.exe -r -s -c"eng=PDB_1;dbn=pdb;uid=sa;pwd=password" -o
> > "s:
s\osafter.log" "SROS"
> > no CREATE CONNECTION statements since I used Sybase Central
> >
> > Thanks.
> >
> > David Fishburn wrote:
> >
> > > Yes, I have done this many, many times.
> > > Since you are using ASA, it speaks native TDS, therefore no Open Server
> > > Package is required.
> > >
> > > To make things easier, please list the following:
> > > 1.  DBSRV6 start line
> > > 2.  SQL.INI file
> > > 3.  CREATE CONNECTION statement used for ASA against RS
> > > 4.  CREATE CONNECTION statement used for the SQLRemote Open Server (ie
> > > SSQueue.exe)
> > > 5.  SSQueue.exe start line
> > >
> > > That should get us started.
> > >
> > > --
> > > David Fishburn
> > > Sybase
> > > Please only post to the newsgroup
> > >
> > > D  wrote in message news:38628D12.7124D247@work.com...
> > > > I've been trying to run SQL Remote with RS and have not yet figured it
> > > > out.  Keep getting the following error once I create a RS connection
> to
> > > > the SQL Remote Open Server:
> > > >
> > > > E. 12/22 12:33:50. Error 2812: Stored procedure 'bogus' not found.
> > > > Specify owner.objectname or use sp_help to check whether the object
> > > > exists (sp_help may produce lots of output).
> > > > I. 12/22 12:33:50. ATTENTION handler active
> > > > E. 12/22 12:33:59. CTLIB Failure 01010110: ct_command(): user api
> layer:
> > > > external error: This routine cannot be called while results are
> pending
> > > > for a command that has been sent to the server.
> > > > I. 12/22 12:33:59. exec sp_queue_set_progress  0, 0, 0000000001,
> > > > 0000000000, 'Dec 22 1999 11:13:18:653AM'
> > > > I. 12/22 12:33:59. Stable Queue Error: cannot set progress
> > > >
> > > > What results are pending?  Has anybody been able to get RS and SQL
> > > > Remote to run successfully on the same installation?  Do I need to
> > > > purchase the Open Server package?  Any help would be appreciated.
> > > >
> > > > BTW,
> > > > Replication Server and Consolidated Database
> > > > NT 4.0 SP4
> > > > ASE 11.9.2
> > > > RS 11.5.1
> > > >
> > > > Remote Database
> > > > NT40 SP4
> > > > ASA 6.0
> > > >
> > > > Thanks.
> > > >
> >
>
>                 Name: ssqdel.rs
>    ssqdel.rs    Type: unspecified type (application/octet-stream)
>             Encoding: x-uuencode
>
>                 Name: ssqdef.rs
>    ssqdef.rs    Type: unspecified type (application/octet-stream)
>             Encoding: x-uuencode
>
>               Name: ssq.bat
>    ssq.bat    Type: MS-DOS Batch File (application/x-unknown-content-type-batfile)
>           Encoding: x-uuencode

D 1/4/2000 4:28:41 PM

For me to verify your setup, it would be best if you supplied all the SQL
statements you used to set this up.
Did you use SSXtract to generate the ASA remote?
Can you try re-extracting that user again and seeing if anything new
replicates.

> the CREATE CONNECTION you specify ssqueue.ssqueue as the server.database
your are

SSQueue is an open server.  It is connected to the database supplied in the
DBN portion of the connect string.  So in this case the database_name in
server.database_name is irrelevant.  SSQueue is only connected to 1 database
at all times, it cannot switch databases.  So you could issue create
connection ssqueue.bob and it wouldn't matter.


--
David Fishburn
Sybase
Please only post to the newsgroup



D  wrote in message news:38721FB9.D63BB3CE@work.com...
> Everything seems to be working except that I can not replicate from the
consolidated
> to the remote.  I am trying to replicate from a test table in the
consolidated
> database that currently is set up for SQL Remote replication.  I created a
RS
> replication definition for the table and the corresponding subscription to
ssqueue but
> replication still does not happen.  No errors in the RS log and the table
is marked
> for replication.
>
> I do have a question about the connection string to the ssqueue in your
script.  In
> the CREATE CONNECTION you specify ssqueue.ssqueue as the server.database
your are
> creating the connection for.  When I look at your ssqueue start line,
there is no
> database called ssqueue.  Shouldn't the connection be created for
ssqueue.website (the
> database where the stable queue resides)?
>
> David Fishburn wrote:
>
> > I do everything from the command line via script files, I have never
used
> > Sybase Central to set this up.  The reason I use scripts is due to the
fact
> > I have to do this over and over again.
> >
> > Here is an example of the script files I run against my server.  I start
> > SSQueue.exe using the interface entry "ssqueue".
> >
> > ssqdef.rs  is run against RS and sets everything up.
> > ssqdel.rs is run against RS and undoes everything.
> >
> > ssq.bat is my command line for starting SSQueue.exe
> >
> > ssremote must be run with either:
> > 1.   -r -s
> > 2.  -r
> > 3.  -s
> >
> > You must always specify these, so that you never specify -i, since the
Rep
> > Agent for ASE should be the one scanning the ASE transaction log, NOT
> > ssremote.exe
> >
> > Start there, compare it with what you did, and I will answer any
questions.
> >
> > --
> > David Fishburn
> > Sybase
> > Please only post to the newsgroup
> >
> > D  wrote in message news:3870F0D1.6A4BBCDA@work.com...
> > > The error has been resolved (via tech support).  As it turns out, I
needed
> > a
> > > patch to get ssqueue to the same version as ASA.  But...
> > >
> > > I still haven't been able to get 2-way replication going between the
> > remote
> > > ASA site and consolidated ASE site.  I am able to replicate up from
the
> > remote
> > > site.
> > >
> > > I started ssqueue against my consolidated database and created an RS
> > > connection to the SQL Remote Open Server as an Open Server via Sybase
> > > Central.  This was done with no problem.
> > >
> > > I was not able to create the proper RS replication definitions and
> > > subscriptions to the SR tables (from the ssremote.rs script).  Don't
know
> > > which server.database names to supply.
> > >
> > > Do I need to create an RS connection to the remote ASA databases?  How
is
> > this
> > > done?
> > > Are there any shortcomings by doing all of this using Sybase Central?
> > Should
> > > I be using command line?
> > >
> > > The documented procedures from the manual Data Replication With SQL
Remote
> > > (Part 3 Chapter 13) are quite ambiguous to me.
> > >
> > > Any help will be appreciated.
> > >
> > > BTW,
> > > ssqueue start line:
> > > ssqueue.exe -r -s -c"eng=PDB_1;dbn=pdb;uid=sa;pwd=password" -o
> > > "s:
s\osafter.log" "SROS"
> > > no CREATE CONNECTION statements since I used Sybase Central
> > >
> > > Thanks.
> > >
> > > David Fishburn wrote:
> > >
> > > > Yes, I have done this many, many times.
> > > > Since you are using ASA, it speaks native TDS, therefore no Open
Server
> > > > Package is required.
> > > >
> > > > To make things easier, please list the following:
> > > > 1.  DBSRV6 start line
> > > > 2.  SQL.INI file
> > > > 3.  CREATE CONNECTION statement used for ASA against RS
> > > > 4.  CREATE CONNECTION statement used for the SQLRemote Open Server
(ie
> > > > SSQueue.exe)
> > > > 5.  SSQueue.exe start line
> > > >
> > > > That should get us started.
> > > >
> > > > --
> > > > David Fishburn
> > > > Sybase
> > > > Please only post to the newsgroup
> > > >
> > > > D  wrote in message
news:38628D12.7124D247@work.com...
> > > > > I've been trying to run SQL Remote with RS and have not yet
figured it
> > > > > out.  Keep getting the following error once I create a RS
connection
> > to
> > > > > the SQL Remote Open Server:
> > > > >
> > > > > E. 12/22 12:33:50. Error 2812: Stored procedure 'bogus' not found.
> > > > > Specify owner.objectname or use sp_help to check whether the
object
> > > > > exists (sp_help may produce lots of output).
> > > > > I. 12/22 12:33:50. ATTENTION handler active
> > > > > E. 12/22 12:33:59. CTLIB Failure 01010110: ct_command(): user api
> > layer:
> > > > > external error: This routine cannot be called while results are
> > pending
> > > > > for a command that has been sent to the server.
> > > > > I. 12/22 12:33:59. exec sp_queue_set_progress  0, 0, 0000000001,
> > > > > 0000000000, 'Dec 22 1999 11:13:18:653AM'
> > > > > I. 12/22 12:33:59. Stable Queue Error: cannot set progress
> > > > >
> > > > > What results are pending?  Has anybody been able to get RS and SQL
> > > > > Remote to run successfully on the same installation?  Do I need to
> > > > > purchase the Open Server package?  Any help would be appreciated.
> > > > >
> > > > > BTW,
> > > > > Replication Server and Consolidated Database
> > > > > NT 4.0 SP4
> > > > > ASE 11.9.2
> > > > > RS 11.5.1
> > > > >
> > > > > Remote Database
> > > > > NT40 SP4
> > > > > ASA 6.0
> > > > >
> > > > > Thanks.
> > > > >
> > >
> >
> >                 Name: ssqdel.rs
> >    ssqdel.rs    Type: unspecified type (application/octet-stream)
> >             Encoding: x-uuencode
> >
> >                 Name: ssqdef.rs
> >    ssqdef.rs    Type: unspecified type (application/octet-stream)
> >             Encoding: x-uuencode
> >
> >               Name: ssq.bat
> >    ssq.bat    Type: MS-DOS Batch File
(application/x-unknown-content-type-batfile)
> >           Encoding: x-uuencode
>

David 1/5/2000 1:40:52 PM

David,

I re-extracted the database and everything that I want to happen is
happening.  Thanks for all the time and help.

-D

David Fishburn wrote:
> 
> For me to verify your setup, it would be best if you supplied all the SQL
> statements you used to set this up.
> Did you use SSXtract to generate the ASA remote?
> Can you try re-extracting that user again and seeing if anything new
> replicates.
> 
> > the CREATE CONNECTION you specify ssqueue.ssqueue as the server.database
> your are
> 
> SSQueue is an open server.  It is connected to the database supplied in the
> DBN portion of the connect string.  So in this case the database_name in
> server.database_name is irrelevant.  SSQueue is only connected to 1 database
> at all times, it cannot switch databases.  So you could issue create
> connection ssqueue.bob and it wouldn't matter.
> 
> --
> David Fishburn
> Sybase
> Please only post to the newsgroup
> 
> D  wrote in message news:38721FB9.D63BB3CE@work.com...
> > Everything seems to be working except that I can not replicate from the
> consolidated
> > to the remote.  I am trying to replicate from a test table in the
> consolidated
> > database that currently is set up for SQL Remote replication.  I created a
> RS
> > replication definition for the table and the corresponding subscription to
> ssqueue but
> > replication still does not happen.  No errors in the RS log and the table
> is marked
> > for replication.
> >
> > I do have a question about the connection string to the ssqueue in your
> script.  In
> > the CREATE CONNECTION you specify ssqueue.ssqueue as the server.database
> your are
> > creating the connection for.  When I look at your ssqueue start line,
> there is no
> > database called ssqueue.  Shouldn't the connection be created for
> ssqueue.website (the
> > database where the stable queue resides)?
> >
> > David Fishburn wrote:
> >
> > > I do everything from the command line via script files, I have never
> used
> > > Sybase Central to set this up.  The reason I use scripts is due to the
> fact
> > > I have to do this over and over again.
> > >
> > > Here is an example of the script files I run against my server.  I start
> > > SSQueue.exe using the interface entry "ssqueue".
> > >
> > > ssqdef.rs  is run against RS and sets everything up.
> > > ssqdel.rs is run against RS and undoes everything.
> > >
> > > ssq.bat is my command line for starting SSQueue.exe
> > >
> > > ssremote must be run with either:
> > > 1.   -r -s
> > > 2.  -r
> > > 3.  -s
> > >
> > > You must always specify these, so that you never specify -i, since the
> Rep
> > > Agent for ASE should be the one scanning the ASE transaction log, NOT
> > > ssremote.exe
> > >
> > > Start there, compare it with what you did, and I will answer any
> questions.
> > >
> > > --
> > > David Fishburn
> > > Sybase
> > > Please only post to the newsgroup
> > >
> > > D  wrote in message news:3870F0D1.6A4BBCDA@work.com...
> > > > The error has been resolved (via tech support).  As it turns out, I
> needed
> > > a
> > > > patch to get ssqueue to the same version as ASA.  But...
> > > >
> > > > I still haven't been able to get 2-way replication going between the
> > > remote
> > > > ASA site and consolidated ASE site.  I am able to replicate up from
> the
> > > remote
> > > > site.
> > > >
> > > > I started ssqueue against my consolidated database and created an RS
> > > > connection to the SQL Remote Open Server as an Open Server via Sybase
> > > > Central.  This was done with no problem.
> > > >
> > > > I was not able to create the proper RS replication definitions and
> > > > subscriptions to the SR tables (from the ssremote.rs script).  Don't
> know
> > > > which server.database names to supply.
> > > >
> > > > Do I need to create an RS connection to the remote ASA databases?  How
> is
> > > this
> > > > done?
> > > > Are there any shortcomings by doing all of this using Sybase Central?
> > > Should
> > > > I be using command line?
> > > >
> > > > The documented procedures from the manual Data Replication With SQL
> Remote
> > > > (Part 3 Chapter 13) are quite ambiguous to me.
> > > >
> > > > Any help will be appreciated.
> > > >
> > > > BTW,
> > > > ssqueue start line:
> > > > ssqueue.exe -r -s -c"eng=PDB_1;dbn=pdb;uid=sa;pwd=password" -o
> > > > "s:
s\osafter.log" "SROS"
> > > > no CREATE CONNECTION statements since I used Sybase Central
> > > >
> > > > Thanks.
> > > >
> > > > David Fishburn wrote:
> > > >
> > > > > Yes, I have done this many, many times.
> > > > > Since you are using ASA, it speaks native TDS, therefore no Open
> Server
> > > > > Package is required.
> > > > >
> > > > > To make things easier, please list the following:
> > > > > 1.  DBSRV6 start line
> > > > > 2.  SQL.INI file
> > > > > 3.  CREATE CONNECTION statement used for ASA against RS
> > > > > 4.  CREATE CONNECTION statement used for the SQLRemote Open Server
> (ie
> > > > > SSQueue.exe)
> > > > > 5.  SSQueue.exe start line
> > > > >
> > > > > That should get us started.
> > > > >
> > > > > --
> > > > > David Fishburn
> > > > > Sybase
> > > > > Please only post to the newsgroup
> > > > >
> > > > > D  wrote in message
> news:38628D12.7124D247@work.com...
> > > > > > I've been trying to run SQL Remote with RS and have not yet
> figured it
> > > > > > out.  Keep getting the following error once I create a RS
> connection
> > > to
> > > > > > the SQL Remote Open Server:
> > > > > >
> > > > > > E. 12/22 12:33:50. Error 2812: Stored procedure 'bogus' not found.
> > > > > > Specify owner.objectname or use sp_help to check whether the
> object
> > > > > > exists (sp_help may produce lots of output).
> > > > > > I. 12/22 12:33:50. ATTENTION handler active
> > > > > > E. 12/22 12:33:59. CTLIB Failure 01010110: ct_command(): user api
> > > layer:
> > > > > > external error: This routine cannot be called while results are
> > > pending
> > > > > > for a command that has been sent to the server.
> > > > > > I. 12/22 12:33:59. exec sp_queue_set_progress  0, 0, 0000000001,
> > > > > > 0000000000, 'Dec 22 1999 11:13:18:653AM'
> > > > > > I. 12/22 12:33:59. Stable Queue Error: cannot set progress
> > > > > >
> > > > > > What results are pending?  Has anybody been able to get RS and SQL
> > > > > > Remote to run successfully on the same installation?  Do I need to
> > > > > > purchase the Open Server package?  Any help would be appreciated.
> > > > > >
> > > > > > BTW,
> > > > > > Replication Server and Consolidated Database
> > > > > > NT 4.0 SP4
> > > > > > ASE 11.9.2
> > > > > > RS 11.5.1
> > > > > >
> > > > > > Remote Database
> > > > > > NT40 SP4
> > > > > > ASA 6.0
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > >
> > >
> > >                 Name: ssqdel.rs
> > >    ssqdel.rs    Type: unspecified type (application/octet-stream)
> > >             Encoding: x-uuencode
> > >
> > >                 Name: ssqdef.rs
> > >    ssqdef.rs    Type: unspecified type (application/octet-stream)
> > >             Encoding: x-uuencode
> > >
> > >               Name: ssq.bat
> > >    ssq.bat    Type: MS-DOS Batch File
> (application/x-unknown-content-type-batfile)
> > >           Encoding: x-uuencode
> >

D 1/5/2000 3:30:19 PM

Reply:

(Thread closed)