|
Home > Archive > SQL Anywhere database replication > November 2005 > time_received column in sys.sysremoteusers after running dbunload command
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
time_received column in sys.sysremoteusers after running dbunload command
|
|
| Jason Davenport 2005-11-16, 9:23 am |
| A quick question,
I am running tests to ugrade our current consolidated
(replicating)databas
e 6.xx SQL Anywhere databases to ASA
9.0.2. I am using the command line utility dbunload with -ar
switch to keep the replicating envornment 'in tact'. When I
select the sys.sysremoteuser(s) table after the upgrade the
date_raised column values have been set to NULL, is this
normal behaviour? N.B. the sent & recieved offsets are the
same as well as the send, recieve, re-recieve counters for
each remote user.
| |
| Rob Waywell 2005-11-16, 1:23 pm |
| Are you sure you have the right column name there? I don't see a
"date_raised" column on the sys.sysremoteuser table or in the
sys.sysremoteusers view.
ASA SQL Reference
System Tables
SYSREMOTEUSER system table
--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional
Sybase's iAnywhere Solutions
Please respond ONLY to newsgroup
EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all
To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288
<Jason Davenport> wrote in message
news:437b345e.241a.1681692777@sybase.com...
>A quick question,
>
> I am running tests to ugrade our current consolidated
> (replicating)databas
e 6.xx SQL Anywhere databases to ASA
> 9.0.2. I am using the command line utility dbunload with -ar
> switch to keep the replicating envornment 'in tact'. When I
> select the sys.sysremoteuser(s) table after the upgrade the
> date_raised column values have been set to NULL, is this
> normal behaviour? N.B. the sent & recieved offsets are the
> same as well as the send, recieve, re-recieve counters for
> each remote user.
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-11-16, 1:23 pm |
| Only the following columns are maintained in the SYS.SYSREMOTEUSER table
during a rebuild :
log_sent
confirm_sent
send_count
resend_count
log_received
confirm_received
receive_count
rereceive_count
The time based columns as only needed when dbremote is running in continuous
mode (i.e. while the process is running). An assumption is made that
dbremote is NOT running while you're doing your upgrade, so there is no need
to maintain this information during a rebuild.
--
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
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"
<Jason Davenport> wrote in message
news:437b345e.241a.1681692777@sybase.com...
> A quick question,
>
> I am running tests to ugrade our current consolidated
> (replicating)databas
e 6.xx SQL Anywhere databases to ASA
> 9.0.2. I am using the command line utility dbunload with -ar
> switch to keep the replicating envornment 'in tact'. When I
> select the sys.sysremoteuser(s) table after the upgrade the
> date_raised column values have been set to NULL, is this
> normal behaviour? N.B. the sent & recieved offsets are the
> same as well as the send, recieve, re-recieve counters for
> each remote user.
| |
| Jason Davenport 2005-11-17, 9:23 am |
| Hi,
Apologies ;-) As you can probably tell I composed original
question in a hurry. It was supposed to read the
"time_received" column, as stated before, all the other
offset values remain the same after the unload
Regards
Jason
| |
| Rob Waywell 2005-11-17, 9:23 am |
| OK, so Reg's response covers it then, the time_received is not preserved by
design since it is only relevant while dbremote is running in continuous
mode. When you run dbremote in continuous mode after the reload, it will
read the NULL value and determine that it is time to run a receive phase.
--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional
Sybase's iAnywhere Solutions
Please respond ONLY to newsgroup
EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all
To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288
<Jason Davenport> wrote in message
news:437c4c21.33d8.1681692777@sybase.com...
> Hi,
> Apologies ;-) As you can probably tell I composed original
> question in a hurry. It was supposed to read the
> "time_received" column, as stated before, all the other
> offset values remain the same after the unload
>
> Regards
>
> Jason
|
|
|
|
|