If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > apply, update anywhere subscription, order of execution

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-10-06, 18:50
craigmc craigmc is offline
Registered User
 
Join Date: Aug 2003
Location: austin,tx
Posts: 90
apply, update anywhere subscription, order of execution

Running DB2 8.1.
I have many clients running DB2 personal Edition. They all replicate to a master server with Update Anywhere subscription sets (think traveling salesmen).

There are two logically bound sets of data we replicate, so for each client, there are 4 subscription sets. That is, each client has 4 enties in the ASN.IBMSNAP_SUBS_SET table, a WHOS_ON_FIRST = F and a WHOS_ON_FIRST = S, one for each set of data.

So lets say I have a client ID = LAPTOPX
The entries in the ASN.IBMSNAP_SUBS_SET are as follows
APPLY_QUAL, SET_NAME, WHOS_ON_FIRST
------------------------------------------
LAPTOPX , DATASET1, F
LAPTOPX , DATASET1, S
LAPTOPX , DATASET2, F
LAPTOPX , DATASET2, S

My question is, when I run Apply, what determines the order that the sets are run?

Most of my clients seem to run them in this order:
DATASET1("F")
DATASET2("F")
DATASET1("S")
DATASET2("S")

I have a new client that is running them in this order:
DATASET1("S")
DATASET2("F")
DATASET2("S")
DATASET1("F")

This doesn't seem right, but I'm not sure where to look on the ordering.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On