Thanks in advance,
Jp
[SQL Anywhere MobiLink Client Version 10.0.1.3662]
The reason for dbmlsync not shutting down is
at the root of this problem. It seems not to
detect any errors (network or otherwise).
Diagnosing that more will be required to see
what is really happening.
If there are any redirection involved, check that
layer out in more detail.
Describing in detail which Internet Connection ?loss?
you are experiencing and how that is being detected.
<John Pollard> wrote in message news:48a98246.5d8...@sybase.com...
--
Joshua Savill
Sybase iAnywhere - Product Manager
JS> This is expected behaviour as only one dbmlsync client can be run
JS> against a SQL Anywhere database at a time.
To clarify, this is expected if this case is detected.
Fiddling with timeouts sounds like what you want so this case
does not happen is the route to go. I will respond to a
previous post.
--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng10 -v).
EBFs and Maintenance Releases
http://downloads.sybase.com/
Developer Community / Whitepapers
http://www.ianywhere.com/developer
Case-Express - to report bugs
http://case-express.sybase.com
CodeXchange - Free samples
http://ianywhere.codexchange.sybase.com/servlets/ProjectDocumentList
> The reason for dbmlsync not shutting down is
> at the root of this problem. It seems not to
> detect any errors (network or otherwise).
> Diagnosing that more will be required to see
> what is really happening.
>
> If there are any redirection involved, check that
> layer out in more detail.
>
> Describing in detail which Internet Connection ?loss?
> you are experiencing and how that is being detected.
Inline with what Nick has asked:
1. What protocol are you syncing with?
2. If HTTP, is it going through a web server?
3. Any load balancers?
4. What timeout settings have you applied?
- Please run dbunload -n against one of your remotes.
- Post the REMOTE DEFINITIONS section so we can see.
5. Post your MobiLink server command line.
6. Versions:
- You supplied SQL Anywhere MobiLink Client Version
10.0.1.3662
- What is your consolidated version (and build)
7. How many ML servers are there?
8. What type of load balancer are you using?
> "Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@>
> wrote in news:48a98fc3$1@forums-1-dub of
> sybase.public.sqlanywhere.mobilink:
>
> > The reason for dbmlsync not shutting down is
> > at the root of this problem. It seems not to
> > detect any errors (network or otherwise).
> > Diagnosing that more will be required to see
> > what is really happening.
> >
> > If there are any redirection involved, check that
> > layer out in more detail.
> >
> > Describing in detail which Internet Connection ?loss?
> > you are experiencing and how that is being detected.
>
> Inline with what Nick has asked:
> 1. What protocol are you syncing with?
TCP/IP
> 2. If HTTP, is it going through a web server?
N/A
> 3. Any load balancers?
No
> 4. What timeout settings have you applied?
?
> - Please run dbunload -n against one of your
remotes.
> - Post the REMOTE DEFINITIONS section so we can
see.
---------------------------------------------
-------------------------------------------------
-- Create SQL Remote definitions
-------------------------------------------------
CREATE PUBLICATION "support"."BRANCH_PLUS"
(
TABLE "support"."zipcode_tbl" ,
TABLE "support"."bp_account_accrual_tbl" ,
TABLE "support"."bp_account_activity_tbl" ,
TABLE "support"."bp_account_banking_tbl" ,
TABLE "support"."bp_account_bankrupt_tbl" ,
TABLE "support"."bp_account_charge_calc_tbl" ,
TABLE "support"."bp_account_charge_off_tbl" ,
TABLE "support"."bp_account_charge_tbl" ,
TABLE "support"."bp_account_collateral_tbl" ,
TABLE "support"."bp_account_component_tbl" ,
TABLE "support"."bp_account_customer_affil_tbl" ,
TABLE "support"."bp_account_decision_tbl" ,
TABLE "support"."bp_account_history_tbl" ,
TABLE "support"."bp_account_insurance_tbl" ,
TABLE "support"."bp_account_payment_affil_tbl" ,
TABLE "support"."bp_account_payment_tbl" ,
TABLE "support"."bp_account_pmt_schedule_tbl" ,
TABLE "support"."bp_account_summary_tbl" ,
TABLE "support"."bp_account_tbl" ,
TABLE "support"."bp_bank_detail_tbl" ,
TABLE "support"."bp_bank_summary_tbl" ,
TABLE "support"."bp_branch_banking_tbl" ,
TABLE "support"."bp_branch_ops_summ_master_tbl" ,
TABLE "support"."bp_branch_ops_summ_tbl" ,
TABLE "support"."bp_branch_setup_tbl" ,
TABLE "support"."bp_comment_tbl" ,
TABLE "support"."bp_cred_rpt_main_tbl" ,
TABLE "support"."bp_customer_home_tbl" ,
TABLE "support"."bp_customer_reference_tbl" ,
TABLE "support"."bp_customer_tbl" ,
TABLE "support"."bp_dealer_rep_tbl" ,
TABLE "support"."bp_dealer_reserve_tbl" ,
TABLE "support"."bp_dealer_statistics_tbl" ,
TABLE "support"."bp_dealer_tbl" ,
TABLE "support"."bp_employee_banking_affil_tbl" ,
TABLE "support"."bp_employee_tbl" ,
TABLE "support"."bp_employment_tbl" ,
TABLE "support"."bp_general_ledger_summary_tbl" ,
TABLE "support"."bp_location_tbl" ,
TABLE "support"."bp_repo_history_tbl" ,
TABLE "support"."bp_supervisor_visit_tbl" ,
TABLE "support"."bp_user_text_tbl" ,
TABLE "support"."tt_clock_tbl" ,
TABLE "support"."tt_timesheet_summary_tbl" ,
TABLE "support"."tt_timesheet_tbl" ,
TABLE "support"."bp_general_ledger_detail_tbl" ,
TABLE "support"."bp_transaction_tbl" ,
TABLE "support"."bp_allowance_for_loss_tbl" ,
TABLE "support"."schema_change_tbl" ,
TABLE "support"."version_tbl"
)
go
-------------------------------------------------
-- Create MobiLink definitions
-------------------------------------------------
call dbo.sa_sync( 1, 'SET NEXTSYNCID', '' )
go
CREATE SYNCHRONIZATION USER "NC_1377"
TYPE 'TCPIP'
OPTION ScriptVersion='BRANCH_PLUS'
go
call dbo.sa_sync( 2, 'SET NEXTSYNCID', '' )
go
CREATE SYNCHRONIZATION SUBSCRIPTION TO
"support"."BRANCH_PLUS"
FOR "NC_1377"
TYPE 'TCPIP'
ADDRESS 'host=S1-MOBI-0;port=2439;'
OPTION
ScriptVersion='BRANCH_PLUS_57',MobiLinkPwd='NC_1377'
go
call dbo.sa_sync_sub( 1, 'NC_1377', 'set progress',
198135934 )
go
call dbo.sa_sync_sub( 1, 'NC_1377', 'set log_sent',
198135934 )
go
call dbo.sa_sync_sub( 1, 'NC_1377', 'set created', 5825645 )
go
call dbo.sa_sync_sub( 1, 'NC_1377', 'set lastdownloadtime',
'2008-08-28 20:09:33.000000' )
go
call dbo.sa_sync_sub( 1, 'NC_1377', 'set lastuploadtime',
'2008-08-28 20:14:30.000000' )
go
call dbo.sa_sync_sub( 1, 'NC_1377', 'set generation_number',
1 )
go
call dbo.sa_sync_sub( 1, 'NC_1377', 'set extended_state', ''
)
go
go
call dbo.sa_sync( 0 , 'RESET NEXTSYNCID', '' )
go
---------------------------------------------
> 5. Post your MobiLink server command line.
[server command line]
mlsrv10.exe
-c "DSN=secfin;uid=%UID%;pwd=%PWD%"
-zs "s1-mobi-4"
-vpns
-os 5M
-o %ASA_PATH%\mlserver.txt
-x "tcpip(port=2439)"
-cm 800M
-cn 50
-zp
-zu-
-b
-fr
-sm 20
-w 20
-wu 10
[remote command-line]
dbmlsync.exe
-q
-e adr='host=%1;port=2439';lt='off'
-c
"uid=%UID%;pwd=%PWD%;start=dbsrv10;eng=%ENG%;dbn=secfin;dbf=%BRANCH_PATH%\db\secfin.db"
-n %PUB_NAME%
-k
-vn
-o %ERROR_LOG%
%BRANCH_PATH%\db
> 6. Versions:
> - You supplied SQL Anywhere MobiLink Client
Version 10.0.1.3662
> - What is your consolidated version (and build)
Adaptive Server Enterprise/12.5.4/EBF 14911 CONTROLLED
ESD#6/P/x86_64/Enterprise Linux/ase1254/2080/64-bit/OPT/Wed
Aug 8 13:31:47 2007
> 7. How many ML servers are there?
4
> 8. What type of load balancer are you using?
None...they are manually balances between servers and
remotes.
>
This is becoming a real problem lately.
I am having to manually drop the 2 orphaned connections
before they will sync.
I did not see this addressed in any EBF notes.
I can't be the only one with this issue.
We connect over a hardware VPN.
Sometimes the remotes time out or pass the 10 deadlock
threshold.
Please advise,
Jp
At this point I would suggest you follow this techdoc:
MobiLink & TCP/IP Keep-Alive
http://www.sybase.com/detail?id=1013181
Windows default TCPIP setup does not perform any liveliness testing
and has a default timeout of 2 hours, which is essentially useless.
I update these settings every time I get a new computer.
Please let us know if this has a positive effect. Note, for best
results you need to change these settings at the server and the remote
machines.