dbremote execution completed
paulattard
immediately receive the message 'Execution Completed' at my
consolidated db. I've seen this message before but usually
accompanied with some text that gives error details.
Note this only occurred after I had to reboot the server for
another reason (dbremote was fine beforehand).
I have been noticing for the last few months after reboots
that I occasionally get this message. Solution has been on
some occasions to shut down other db's that autostart on the
same server, other occasions just restarting the dbserver or
rebooting has done the trick. This time it appears to be
stuck totally. Have also tried running dbremote from another
server but getting same message execution completed.
In the meantime I've had transactions coming in from 3
remote db's which I don't want to lose. Only thing I can
think of at this point is to resync log offsets but
concerned I'll lose today's transactions (guess I can apply
SQL from transactions directly against db if needed).
Bit rusty on replication as usually I just leave well alone
and it ticks away. Any ideas would be appreciated.
Thanks,
Paul
Reg Domaratzki [Sybase iAnywhere]
Can you add -v -o dbr.txt to the dbremote start line and then post the
output here? Be careful not to post any uid/pwd that may be in the log.
Don't be concerned about the transactions coming in. Once sql remote
starts running again, it will pick up all the outstanding messages.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Please reply only to the newsgroup
Documentation : Exercise your WRITE @DocCommentXchange: DCX.sybase.com
SQL Anywhere Patches and EBFs : http://downloads.sybase.com/swd/base.do
-> Choose SQL Anywhere
-> Optionally set filter to "Display ALL platforms IN ALL MONTHS"
paulattard
Here's the output:
I. 01/28 09:56:51. 1: -c
I. 01/28 09:56:51. 2:
*****************************************************************
I. 01/28 09:56:51. 3: -v
I. 01/28 09:56:51. 4: x:\bbmplant_log\bbmplant
I. 01/28 09:56:51. SQL Remote Message Agent Version
9.0.2.3924
I. 01/28 09:56:51.
I. 01/28 09:56:51. Copyright © 1989-2007 Sybase, Inc.
Portions Copyright © 2002-2007,
iAnywhere Solutions, Inc.
I. 01/28 09:56:51. All rights reserved. All unpublished
rights reserved.
I. 01/28 09:56:51.
I. 01/28 09:56:51. This software contains confidential and
trade secret information of
I. 01/28 09:56:51. iAnywhere Solutions, Inc.
Use, duplication or disclosure of the
software and documentation
I. 01/28 09:56:51. by the U.S. Government is subject to
restrictions set forth in a license
I. 01/28 09:56:51. agreement between the Government and
iAnywhere Solutions, Inc. or
I. 01/28 09:56:51. other written agreement specifying the
Government's rights to use the
I. 01/28 09:56:51. software and any applicable FAR
provisions, for example, FAR 52.227-19.
I. 01/28 09:56:51.
I. 01/28 09:56:51. iAnywhere Solutions, Inc., One Sybase
Drive, Dublin, CA 94568, USA
I. 01/28 09:56:51.
I. 01/28 09:56:52. Execution completed
Reg Domaratzki [Sybase iAnywhere]
This came up in our tech support queue bash today, so I assume it was
being talked about because of you.
You will see this happen if there is no publisher defined in the
database you are running dbremote against. I'll looking at adding a
error message.
Reg Domaratzki [Sybase iAnywhere]
>
> This came up in our tech support queue bash today, so I assume it was
> being talked about because of you.
>
> You will see this happen if there is no publisher defined in the
> database you are running dbremote against. I'll looking at adding a
> error message.
>
Fixed in the following builds :
11.0.1 ( 2383 )
11.0.0 ( 1654 )
10.0.1 ( 4020 )
9.0.2 ( 3950 )
paulattard
publisher had somehow had its publish authority revoked.
All good now.
Paul