Home > Archive > SQL Anywhere Mobile > July 2005 > data exists but not coming up in the upload stream









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 data exists but not coming up in the upload stream
Kevin Dunn

2005-07-26, 9:24 am

We are using ASA 9.0.1.1841 and are in the process of converting to the new scripts for uploads ( upload_insert, upload_update) instead of upload_cursor. The problem some tables that still use upload_cursor seem to be failing sporadically: The following error occured stating the column long_desc cannot be null but it seems to have data in the position for the column. The table has the column defined as NOT NULL, so I know the data exists in the remote database. Any ideas to why this would happen? The upload_cursor does work sometimes, I have verified the columns are in the correct order as well.

E. 07/22 11:59:11. <2.2> [peposti]: Error: [-10002] ODBC: [Sybase][ODBC Driver][Adaptive Server Anywhere]Column 'long_desc' in table 'narrative' cannot be NULL (ODBC State = 23000, Native error code = -195)
E. 07/22 11:59:11. <2.2> [peposti]: Error: Unable to insert into table 'narrative' using upload_cursor
I. 07/22 11:59:11. <2.2> [peposti]: Error Context:
I. 07/22 11:59:11. <2.2> [peposti]: User Name: peposti
I. 07/22 11:59:11. <2.2> [peposti]: Modified User Name: peposti
I. 07/22 11:59:11. <2.2> [peposti]: Transaction: upload
I. 07/22 11:59:11. <2.2> [peposti]: Table Name: narrative
I. 07/22 11:59:11. <2.2> [peposti]: Insert Row:
I. 07/22 11:59:11. <2.2> [peposti]: 38552111031481000784
358
I. 07/22 11:59:11. <2.2> [peposti]: 38552111031391000784
358
I. 07/22 11:59:11. <2.2> [peposti]: NULL
I. 07/22 11:59:11. <2.2> [peposti]: Daily checks
I. 07/22 11:59:11. <2.2> [peposti]: [29 Characters] ------------ long_desc
I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000
I. 07/22 11:59:11. <2.2> [peposti]: 900078
I. 07/22 11:59:11. <2.2> [peposti]: 38412177600100064358

I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000
I. 07/22 11:59:11. <2.2> [peposti]: NULL
I. 07/22 11:59:11. <2.2> [peposti]: Y
I. 07/22 11:59:11. <2.2> [peposti]: A
I. 07/22 11:59:11. <2.2> [peposti]: 1
I. 07/22 11:59:11. <2.2> [peposti]: 27
I. 07/22 11:59:11. <2.2> [peposti]: 38412177600100064358

I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000

--
Kevin Dunn
Email: kevin.dunn@spsinc.com
Home Email: kdunn2@carolina.rr.com
H: 704-263-2450
W: 704-544-5501 ext 295
David Fishburn

2005-07-26, 8:25 pm

"Kevin Dunn" <nospam_kevin.dunn@spsinc.com> wrote in
news:42e63b6e@forums
-2-dub of sybase.public.sqlanywhere.mobilink:

You never showed the script being executed, it would have been just
after the output you did post.

Doing the conversion, you may have mistakenly switched the order of some
of the columns.

If you start ML using -v+, the first part of the sync describes the
remotes schema. You can use this to line up the output and the scripts
you wrote.

--
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 (dbeng9 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm

Developer Community / Whitepapers
http://www.ianywhere.com/developer

CaseXpress - to report bugs
http://casexpress.sybase.com

CodeXchange - Free samples
[url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]

Kevin Dunn

2005-07-26, 8:25 pm

The error is occurring with the old script upload_cursor, it works sometimes
and sometimes it doesn't. The column order has been verified: The long
desc field is where it states [29 characters] the long_desc field is a long
varchar datatype. Could it be relating to using the upload_cursor?

Here is the whole output:
E. 07/22 11:59:11. <2.2> [peposti]: Error: [-10002] ODBC: [Sybase][ODBC
Driver][Adaptive Server Anywhere]Column 'long_desc' in table 'narrative'
cannot be NULL (ODBC State = 23000, Native error code = -195)
E. 07/22 11:59:11. <2.2> [peposti]: Error: Unable to insert into table
'narrative' using upload_cursor
I. 07/22 11:59:11. <2.2> [peposti]: Error Context:
I. 07/22 11:59:11. <2.2> [peposti]: User Name: peposti
I. 07/22 11:59:11. <2.2> [peposti]: Modified User Name: peposti
I. 07/22 11:59:11. <2.2> [peposti]: Transaction: upload
I. 07/22 11:59:11. <2.2> [peposti]: Table Name: narrative
I. 07/22 11:59:11. <2.2> [peposti]: Insert Row:
I. 07/22 11:59:11. <2.2> [peposti]: 38552111031481000784
358
I. 07/22 11:59:11. <2.2> [peposti]: 38552111031391000784
358
I. 07/22 11:59:11. <2.2> [peposti]: NULL
I. 07/22 11:59:11. <2.2> [peposti]: Daily checks
I. 07/22 11:59:11. <2.2> [peposti]: [29 Characters]
I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000
I. 07/22 11:59:11. <2.2> [peposti]: 900078
I. 07/22 11:59:11. <2.2> [peposti]: 38412177600100064358

I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000
I. 07/22 11:59:11. <2.2> [peposti]: NULL
I. 07/22 11:59:11. <2.2> [peposti]: Y
I. 07/22 11:59:11. <2.2> [peposti]: A
I. 07/22 11:59:11. <2.2> [peposti]: 1
I. 07/22 11:59:11. <2.2> [peposti]: 27
I. 07/22 11:59:11. <2.2> [peposti]: 38412177600100064358

I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000
I. 07/22 11:59:11. <2.2> [peposti]: Script Version: NULL
I. 07/22 11:59:11. <2.2> [peposti]: Script: SELECT narrative_id, event_id,
narrative_type_id, short_desc, long_desc, mod_datetime, site_id, mod_user,
loaded_date, language_type_id, primary_narr, status, source_site_id,
data_source, add_user, add_datetime FROM narrative WHERE narrative_id = ?
I. 07/22 11:59:11. <2.2> [peposti]: End of Error Context
W. 07/22 11:59:11. <2.2> [peposti]: Warning: [10010] No handle_error script
is defined. The default action code (3000) will decide the error behavior
I. 07/22 11:59:11. <2.2> [peposti]: An error occurred while uploading an
insert row into table 'narrative'. The inserted column values are as
follows:
I. 07/22 11:59:11. <2.2> [peposti]: 38552111031481000784
358
I. 07/22 11:59:11. <2.2> [peposti]: 38552111031391000784
358
I. 07/22 11:59:11. <2.2> [peposti]: NULL
I. 07/22 11:59:11. <2.2> [peposti]: Daily checks
I. 07/22 11:59:11. <2.2> [peposti]: [29 Characters]
I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000
I. 07/22 11:59:11. <2.2> [peposti]: 900078
I. 07/22 11:59:11. <2.2> [peposti]: 38412177600100064358

I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000
I. 07/22 11:59:11. <2.2> [peposti]: NULL
I. 07/22 11:59:11. <2.2> [peposti]: Y
I. 07/22 11:59:11. <2.2> [peposti]: A
I. 07/22 11:59:11. <2.2> [peposti]: 1
I. 07/22 11:59:11. <2.2> [peposti]: 27
I. 07/22 11:59:11. <2.2> [peposti]: 38412177600100064358

I. 07/22 11:59:11. <2.2> [peposti]: 2005-07-21 11:10:31.481000
W. 07/22 11:59:11. <2.2> [peposti]: Warning: [10040] 1 row(s) were ignored
in updating table narrative
I. 07/22 11:59:11. <2.2> [peposti]: ROLLBACK Transaction: end_upload
I. 07/22 11:59:11. <2.2> [peposti]: ROLLBACK Transaction:
end_synchronization
I. 07/22 11:59:11. <2.2> [peposti]: COMMIT Transaction: end_connection
I. 07/22 11:59:11. <2.2> [peposti]: Disconnected from consolidated database
I. 07/22 11:59:11. <2.2> [peposti]: Synchronization failed

--
Kevin Dunn
Email: kevin.dunn@spsinc.com
Home Email: kdunn2@carolina.rr.com
H: 704-263-2450
W: 704-544-5501 ext 295
"David Fishburn" <fishburn_spam@off.ianywhere.com> wrote in message
news:Xns969F98BC0692
5fishburnsybasecom@1
27.0.0.1...
> "Kevin Dunn" <nospam_kevin.dunn@spsinc.com> wrote in
> news:42e63b6e@forums
-2-dub of sybase.public.sqlanywhere.mobilink:
>
> You never showed the script being executed, it would have been just
> after the output you did post.
>
> Doing the conversion, you may have mistakenly switched the order of some
> of the columns.
>
> If you start ML using -v+, the first part of the sync describes the
> remotes schema. You can use this to line up the output and the scripts
> you wrote.
>
> --
> 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 (dbeng9 -v).
>
> EBFs and Maintenance Releases
> http://downloads.sybase.com/swx/sdmain.stm
>
> Developer Community / Whitepapers
> http://www.ianywhere.com/developer
>
> CaseXpress - to report bugs
> http://casexpress.sybase.com
>
> CodeXchange - Free samples
> [url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]
>


David Fishburn

2005-07-27, 7:27 am

"Kevin Dunn" <nospam_kevin.dunn@spsinc.com> wrote in
news:42e69b7c$1@foru
ms-1-dub of sybase.public.sqlanywhere.mobilink:

KD> The error is occurring with the old script upload_cursor, it works
KD> sometimes and sometimes it doesn't. The column order has been
KD> verified: The long desc field is where it states [29 characters] the
KD> long_desc field is a long varchar datatype. Could it be relating to
KD> using the upload_cursor?

It is the first I have heard of it.

Can you try converting this table over to the new (and much faster)
statement based scripts and see if the problem goes away?

--
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 (dbeng9 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm

Developer Community / Whitepapers
http://www.ianywhere.com/developer

CaseXpress - to report bugs
http://casexpress.sybase.com

CodeXchange - Free samples
[url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com