|
Home > Archive > SQL Anywhere Mobile > May 2005 > Upload Update Warning Message...
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 |
Upload Update Warning Message...
|
|
| Sanjay 2005-04-29, 8:26 pm |
| ASA/ML 9.0.1 (1922)
Hi All,
I am getting this warning message while synchronizing, for which i am not
able to find any reason
"Error detected while using multi-row cursor -- retrying with single row
cursor"
Basically it's simple uploadupdate script (update statement) which is
causing the problem, I found that out from log.
table has 10 columns, 9 are char, 1 is datetime.
none of the value is null.
The only exception is that the table in consolidate db has 3 columns in PK
while same table in remote has
2 columns included in PK. Extra column in consolidate db is seq_num of type
integer (default autoincrement).
BTY sync. completes without error. But why this warning??
Any clue??
SanJay
| |
| Breck Carter 2005-04-29, 8:26 pm |
| Ignore those messages, they mean nothing.
Breck
> ASA/ML 9.0.1 (1922)
>
> Hi All,
>
> I am getting this warning message while synchronizing, for
> which i am not able to find any reason
> "Error detected while using multi-row cursor -- retrying
> with single row cursor"
> Basically it's simple uploadupdate script (update
> statement) which is causing the problem, I found that out
> from log. table has 10 columns, 9 are char, 1 is datetime.
> none of the value is null.
> The only exception is that the table in consolidate db has
> 3 columns in PK while same table in remote has
> 2 columns included in PK. Extra column in consolidate db
> is seq_num of type integer (default autoincrement).
>
> BTY sync. completes without error. But why this warning??
>
> Any clue??
>
>
> SanJay
>
>
>
>
| |
| Sanjay 2005-04-29, 8:26 pm |
| Thanks for your reply Breck..
I have another problem which may or may not be related with this warning.
My aim with this uploadupdate script is to call SP, which will handle the
info.
But for some reason this SP is called twice. I can see in log also that
there is same update sql in
"begin_upload" event and "upload_update" event.
Now i don't have any script written in begin_upload event so why is it call
in this event?
Thanks
Sanjay
<Breck Carter> wrote in message news:4272a73e.1541.1681692777@sybase.com...[color=darkred]
> Ignore those messages, they mean nothing.
>
> Breck
>
| |
| Breck Carter 2005-04-29, 8:26 pm |
| It's not related. Show us your mobilink server messages.
Also, you can query the various ml_script and
ml_connection_script
and ml_table_script tables to find out
what you really have. You may have accidentally put the
wrong script in the wrong event, and never deleted it.
Breck
> Thanks for your reply Breck..
>
> I have another problem which may or may not be related
> with this warning. My aim with this uploadupdate script is
> to call SP, which will handle the info.
> But for some reason this SP is called twice. I can see in
> log also that there is same update sql in
> "begin_upload" event and "upload_update" event.
> Now i don't have any script written in begin_upload event
> so why is it call in this event?
>
> Thanks
>
> Sanjay
>
>
> <Breck Carter> wrote in message
> messages, they mean nothing. >
>
>
| |
| Graham Hurst 2005-04-30, 3:26 am |
| What that message is telling you is that ML got an error from the
database when it tried to apply updates to several rows at once, but
can't tell which row had the problem. So it retries with just one row at
a time, assuming that it will get same error but can now point you to
the problematic row.
However in your case it is working one row at time, but not with several
rows at a time. It's up to you whether you want to investigate that, but
better performance is possible if multi-row works.
You can also use the -s option to control how many rows ML tries to
apply at once. Setting that to 1 will force MobiLink to also just use
one row at a time.
Cheers,
Graham
Breck Carter wrote:[color=darkred
]
> Ignore those messages, they mean nothing.
>
> Breck
>
>
| |
| Breck Carter [TeamSybase] 2005-04-30, 11:25 am |
| FWIW I've seen my fair share of MobiLink errors <g>, and *that*
message has never been associated with any real problem.
Breck
On 29 Apr 2005 22:20:00 -0700, Graham Hurst
< spam_guard_hurst@ian
ywhere.com> wrote:
[color=darkred]
>What that message is telling you is that ML got an error from the
>database when it tried to apply updates to several rows at once, but
>can't tell which row had the problem. So it retries with just one row at
>a time, assuming that it will get same error but can now point you to
>the problematic row.
>
>However in your case it is working one row at time, but not with several
>rows at a time. It's up to you whether you want to investigate that, but
> better performance is possible if multi-row works.
>
>You can also use the -s option to control how many rows ML tries to
>apply at once. Setting that to 1 will force MobiLink to also just use
>one row at a time.
>
>Cheers,
>
>Graham
>
>Breck Carter wrote:
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Sanjay 2005-05-02, 9:23 am |
| Yes i have made sure that there is no script that i don't want.
I looked thru SQL Central.
BTW here is the snippet of the log file...
I. 04/29 11:39:38. <1.5> [01;tech=223]: begin_upload sd_service_master_no
tes
(no script)
I. 04/29 11:39:38. <1.5> [01;tech=223]: begin_upload_rows sd_search_sm (no
script)
I. 04/29 11:39:38. <1.5> [01;tech=223]: Translated SQL:
savepoint it0
I. 04/29 11:39:38. <1.5> [01;tech=223]: Updated row (new values):
I. 04/29 11:39:38. <1.5> [01;tech=223]: 01
I. 04/29 11:39:38. <1.5> [01;tech=223]: 223
I. 04/29 11:39:38. <1.5> [01;tech=223]: toward 671..m
I. 04/29 11:39:38. <1.5> [01;tech=223]:
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: 2005-04-29 11:40:56.000000
I. 04/29 11:39:38. <1.5> [01;tech=223]: upload_update sd_search_sm (open for
write):
Update sd_search_sm
set company = ?, first_name = ?, last_name = ?,
address1 = ?, city = ?,
zip_code = ?, phone_num = ?, search_made_on = ?
where company_code = ? and tech_num = ?
I. 04/29 11:39:38. <1.5> [01;tech=223]: Translated SQL:
Update sd_search_sm
set company = ?, first_name = ?, last_name = ?,
address1 = ?, city = ?,
zip_code = ?, phone_num = ?, search_made_on = ?
where company_code = ? and tech_num = ?
I. 04/29 11:39:38. <1.5> [01;tech=223]: upload_update sd_search_sm (close)
I. 04/29 11:39:38. <1.5> [01;tech=223]: Translated SQL:
rollback to savepoint it0
W. 04/29 11:39:38. <1.5> [01;tech=223]: Warning: [10039] Error detected
while using multi-row cursor -- retrying with single row cursor
I. 04/29 11:39:38. <1.5> [01;tech=223]: Updated row (new values):
I. 04/29 11:39:38. <1.5> [01;tech=223]: 01
I. 04/29 11:39:38. <1.5> [01;tech=223]: 223
I. 04/29 11:39:38. <1.5> [01;tech=223]: toward 671..m
I. 04/29 11:39:38. <1.5> [01;tech=223]:
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
I. 04/29 11:39:38. <1.5> [01;tech=223]: 2005-04-29 11:40:56.000000
I. 04/29 11:39:38. <1.5> [01;tech=223]: upload_update sd_search_sm (open for
write):
Update sd_search_sm
set company = ?, first_name = ?, last_name = ?,
address1 = ?, city = ?,
zip_code = ?, phone_num = ?, search_made_on = ?
where company_code = ? and tech_num = ?
I. 04/29 11:39:38. <1.5> [01;tech=223]: Cached ODBC statement:
Update sd_search_sm
set company = ?, first_name = ?, last_name = ?,
address1 = ?, city = ?,
zip_code = ?, phone_num = ?, search_made_on = ?
where company_code = ? and tech_num = ?
W. 04/29 11:39:38. <1.5> [01;tech=223]: Warning: [10044] A row in table
'sd_search_sm' could not be updated because it no longer exists in the
consolidated database
I. 04/29 11:39:38. <1.5> [01;tech=223]: upload_update sd_search_sm (close)
W. 04/29 11:39:38. <1.5> [01;tech=223]: Warning: [10040] 1 row(s) were
ignored in updating table sd_search_sm
I. 04/29 11:39:38. <1.5> [01;tech=223]: end_upload_rows sd_search_sm (no
script)
..
..
..
As you can see here i have same sql query in both begin_upload_rows /
upload_update event.
I am trying to develop search that technician can do from the field. So i
developed the screen first, inserted the
search criteria then wrote upload_update/upload insert/download cursor
scripts. Now i have row in remote which is trying to update an non existing
row in consolidate db. Bet if delete the row from remotedb and start over
again it will be fine.
TIA
SanJay
<Breck Carter> wrote in message news:4272bd47.6323.1681692777@sybase.com...[color=darkred]
> It's not related. Show us your mobilink server messages.
>
> Also, you can query the various ml_script and
> ml_connection_script
and ml_table_script tables to find out
> what you really have. You may have accidentally put the
> wrong script in the wrong event, and never deleted it.
>
> Breck
>
| |
| Sanjay 2005-05-02, 9:23 am |
| ASA 9.0.1 (1922)
Graham,
I have 0 rows in consolidate db and 1 row in remote db.
Actually I entered row in remote db first and then wrote the script. I am
sure that caused the problem.
SanJay
"Graham Hurst" < spam_guard_hurst@ian
ywhere.com> wrote in message
news:42731580@forums
-1-dub...[color=darkred]
> What that message is telling you is that ML got an error from the
> database when it tried to apply updates to several rows at once, but
> can't tell which row had the problem. So it retries with just one row at
> a time, assuming that it will get same error but can now point you to
> the problematic row.
>
> However in your case it is working one row at time, but not with several
> rows at a time. It's up to you whether you want to investigate that, but
> better performance is possible if multi-row works.
>
> You can also use the -s option to control how many rows ML tries to
> apply at once. Setting that to 1 will force MobiLink to also just use
> one row at a time.
>
> Cheers,
>
> Graham
>
> Breck Carter wrote:
| |
| Breck Carter 2005-05-02, 1:24 pm |
| You do not have any script for begin_upload:
begin_upload_rows sd_search_sm (no script)
That's probably OK, those scripts are rarely needed.
In this case, the uploaded UPDATE specifies a row that no
long exists in the consolidated database:
W. 04/29 11:39:38. <1.5> [01;tech=223]: Warning: [10044]
A row in table 'sd_search_sm' could not be updated because
it no longer exists in the consolidated database
That probably happened because some other process deleted
that row from the consolidated database after it was
previously downloaded. If you want to download deletes, you
have write a download_delete_curs
or script. If you don't
synchronize deletes, you will get warnings like this.
Breck
> Yes i have made sure that there is no script that i don't
> want. I looked thru SQL Central.
> BTW here is the snippet of the log file...
>
>
> I. 04/29 11:39:38. <1.5> [01;tech=223]: begin_upload
> sd_service_master_no
tes (no script)
> I. 04/29 11:39:38. <1.5> [01;tech=223]: begin_upload_rows
> sd_search_sm (no script)
> I. 04/29 11:39:38. <1.5> [01;tech=223]: Translated SQL:
> savepoint it0
> I. 04/29 11:39:38. <1.5> [01;tech=223]: Updated row (new
> values): I. 04/29 11:39:38. <1.5> [01;tech=223]: 01
> I. 04/29 11:39:38. <1.5> [01;tech=223]: 223
> I. 04/29 11:39:38. <1.5> [01;tech=223]: toward 671..m
> I. 04/29 11:39:38. <1.5> [01;tech=223]:
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: 2005-04-29
> 11:40:56.000000 I. 04/29 11:39:38. <1.5> [01;tech=223]:
> upload_update sd_search_sm (open for write):
> Update sd_search_sm
> set company = ?, first_name = ?,
> last_name = ?, address1 = ?, city = ?,
> zip_code = ?, phone_num = ?,
> search_made_on = ?
> where company_code = ? and tech_num =
> ? I. 04/29 11:39:38. <1.5> [01;tech=223]: Translated SQL:
> Update sd_search_sm
> set company = ?, first_name = ?,
> last_name = ?, address1 = ?, city = ?,
> zip_code = ?, phone_num = ?,
> search_made_on = ?
> where company_code = ? and tech_num =
> ? I. 04/29 11:39:38. <1.5> [01;tech=223]: upload_update
> sd_search_sm (close) I. 04/29 11:39:38. <1.5> [01
> ;tech=223]: Translated SQL:
> rollback to savepoint it0
> W. 04/29 11:39:38. <1.5> [01;tech=223]: Warning: [10039]
> Error detected while using multi-row cursor -- retrying
> with single row cursor I. 04/29 11:39:38. <1.5> [01
> ;tech=223]: Updated row (new values): I. 04/29 11:39:38.
> <1.5> [01;tech=223]: 01 I. 04/29 11:39:38. <1.5> [01
> ;tech=223]: 223 I. 04/29 11:39:38. <1.5> [01;tech=223]:
> toward 671..m I. 04/29 11:39:38. <1.5> [01;tech=223]:
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: NULL
> I. 04/29 11:39:38. <1.5> [01;tech=223]: 2005-04-29
> 11:40:56.000000 I. 04/29 11:39:38. <1.5> [01;tech=223]:
> upload_update sd_search_sm (open for write):
> Update sd_search_sm
> set company = ?, first_name = ?,
> last_name = ?, address1 = ?, city = ?,
> zip_code = ?, phone_num = ?,
> search_made_on = ?
> where company_code = ? and tech_num =
> ? I. 04/29 11:39:38. <1.5> [01;tech=223]: Cached ODBC
> statement:
> Update sd_search_sm
> set company = ?, first_name = ?,
> last_name = ?, address1 = ?, city = ?,
> zip_code = ?, phone_num = ?,
> search_made_on = ?
> where company_code = ? and tech_num =
> ? W. 04/29 11:39:38. <1.5> [01;tech=223]: Warning: [10044]
> A row in table 'sd_search_sm' could not be updated because
> it no longer exists in the consolidated database
> I. 04/29 11:39:38. <1.5> [01;tech=223]: upload_update
> sd_search_sm (close) W. 04/29 11:39:38. <1.5> [01
> ;tech=223]: Warning: [10040] 1 row(s) were ignored in
> updating table sd_search_sm I. 04/29 11:39:38. <1.5> [01
> ;tech=223]: end_upload_rows sd_search_sm (no script)
> .
> .
> .
> As you can see here i have same sql query in both
> begin_upload_rows / upload_update event.
>
> I am trying to develop search that technician can do from
> the field. So i developed the screen first, inserted the
> search criteria then wrote upload_update/upload
> insert/download cursor scripts. Now i have row in remote
> which is trying to update an non existing row in
> consolidate db. Bet if delete the row from remotedb and
> start over again it will be fine.
>
> TIA
>
> SanJay
>
>
> <Breck Carter> wrote in message
> related. Show us your mobilink server messages. >
> it. >
>
>
|
|
|
|
|