We are using ASE 12.5 as consolidated, ASA 9.0.2 3267 as remote.

The upload_update script for our 'request_queue' table is failing with the
following error:

E. 08/14 14:55:43. Message: ODBC: [DataDirect][ODBC Sybase Wire Protocol
driver]String data, right truncated. Error in parameter 3. (ODBC State =
22001, Native error code = 0).  Table Name: Request_Queue.  Primary Key(s):
11686

The definition of the remote table is as follows:

CREATE TABLE "dbo"."Request_Queue" (
 "Request_Queue_Id"       unsigned int NOT NULL ,
 "Client"       varchar(128) NULL ,
 "Code"         smallint NULL ,
 "Stmt"     varchar(16000) NULL ,
 "Status"          varchar(10) NULL ,
  PRIMARY KEY ("Request_Queue_Id") )

The definition of the consolidated table is as follows:

create table dbo.Request_Queue
(Request_Queue_Id numeric(18,0) identity,
Client varchar(128) default db_name() not null,
Code smallint default 1 not null,
Stmt text default 'New Request Queue' not null,
Status varchar(10) default 'NEW' not null,
Lastmodified datetime default getdate() not null)

The upload_update script looks like this:

update Request_Queue
set Client = ?, Code = ?, Stmt = ?, Status = ?
where Request_Queue_Id = ?

Parameter 3, as specified in the error message is 'Stmt'. The actual length
of the column in the remote is 8,398 bytes. But I don't see anywhere where a
truncation error should be happening. We have successfully synched with
lengths of less than 3,000 but this is our first synch with a text value
this big. (We are updating remote stored procedures using MobiLink. That big
Stmt column contains a stored procedure)

Does anybody else see something?

While I do not see the specific ASE error for this, the use of
identity is not normally an option for ML with ASE.

Ignoring the lack of  an explicit declaration for a primary key
(which may be the source of the actual error you are getting
 right this moment) and ignoring the mismatch in data types
(which are not equivalent at all and should be reconciled),
you will hit a known issue with the identity default.

For inserts at the remote ML must provide the value for the
primary key to the ASE server.   The ASE server is going
to simply reject all such attempts unless *ALL* of the following
are true:

    - The account ML is using is the table owner (the so called
      dboo) or the database owner (the so called dbo); the dbo
      also must be granted explicit insert permissions on this
      column.  The sa account can fall into the role of the dbo.

    - You explicitly 'set' the ASE option 'identity_insert' on
and
    - you have not collided on the insert forcing an 'upsert'
      situation (for which you need to see identity_update too
      and figure a way to make both work all of the time)

which is exactly something you probably should not be attempting
normally.  You have not attempted setting the option, and you may
not want to connect with the owner/dbo account permissions.

Possibly the most disturbing  aspect of this is the fact that ASE does
not perform duplicate checking with this option set; unless you correct
the lack of the explicit primary key mentioned above.

A procedure owned by the table owner (with the appropriate
permissions granted) may be an option but I would recommend
a complete rethink before going this route.

Some references of note:

   - for the 'set' command see the Reference Manual : Commands
     in your online set or one of the web available ones like:
     http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.commands/html/commands/commands85.htm

    - for the functionality of identity_insert and the limitations of this
      approach scroll down the descript of this feature as well as the
      other reference guide sections; notably the Transact SQL User Guide
      "Chapter 9: Adding, Changing, and Deleting Data".

    - also visit the identity_update while you are there

    - see the Note: for ASE when setting up your ODBC DSN
    http://www.ianywhere.com/developer/technotes/odbc_mobilink902.html#_Sybase_Adaptive_Server_1


"Douglas" <doogie414@yahoo.com> wrote in message 
news:44e0f906$1@forums-1-dub...
> We are using ASE 12.5 as consolidated, ASA 9.0.2 3267 as remote.
>
> The upload_update script for our 'request_queue' table is failing with the
> following error:
>
> E. 08/14 14:55:43. Message: ODBC: [DataDirect][ODBC Sybase Wire Protocol
> driver]String data, right truncated. Error in parameter 3. (ODBC State =
> 22001, Native error code = 0).  Table Name: Request_Queue.  Primary 
> Key(s):
> 11686
>
> The definition of the remote table is as follows:
>
> CREATE TABLE "dbo"."Request_Queue" (
> "Request_Queue_Id"       unsigned int NOT NULL ,
> "Client"       varchar(128) NULL ,
> "Code"         smallint NULL ,
> "Stmt"     varchar(16000) NULL ,
> "Status"          varchar(10) NULL ,
>  PRIMARY KEY ("Request_Queue_Id") )
>
> The definition of the consolidated table is as follows:
>
> create table dbo.Request_Queue
> (Request_Queue_Id numeric(18,0) identity,
> Client varchar(128) default db_name() not null,
> Code smallint default 1 not null,
> Stmt text default 'New Request Queue' not null,
> Status varchar(10) default 'NEW' not null,
> Lastmodified datetime default getdate() not null)
>
> The upload_update script looks like this:
>
> update Request_Queue
> set Client = ?, Code = ?, Stmt = ?, Status = ?
> where Request_Queue_Id = ?
>
> Parameter 3, as specified in the error message is 'Stmt'. The actual 
> length
> of the column in the remote is 8,398 bytes. But I don't see anywhere where 
> a
> truncation error should be happening. We have successfully synched with
> lengths of less than 3,000 but this is our first synch with a text value
> this big. (We are updating remote stored procedures using MobiLink. That 
> big
> Stmt column contains a stored procedure)
>
> Does anybody else see something?
>
>
>
> 

I strongly suspect the problem will go away if you change the data type of 
the "Stmt" column to match between the remote and consolidated.  Is there a 
reason you defined the column to be varchar(16000) on the remote and a text 
column on the consolidated?

-- 
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/swd/base.do
   -> Choose SQL Anywhere Studio
   -> Set filter to "Display ALL platforms IN ALL MONTHS"


"Douglas" <doogie414@yahoo.com> wrote in message 
news:44e0f906$1@forums-1-dub...
> We are using ASE 12.5 as consolidated, ASA 9.0.2 3267 as remote.
>
> The upload_update script for our 'request_queue' table is failing with the
> following error:
>
> E. 08/14 14:55:43. Message: ODBC: [DataDirect][ODBC Sybase Wire Protocol
> driver]String data, right truncated. Error in parameter 3. (ODBC State =
> 22001, Native error code = 0).  Table Name: Request_Queue.  Primary 
> Key(s):
> 11686
>
> The definition of the remote table is as follows:
>
> CREATE TABLE "dbo"."Request_Queue" (
> "Request_Queue_Id"       unsigned int NOT NULL ,
> "Client"       varchar(128) NULL ,
> "Code"         smallint NULL ,
> "Stmt"     varchar(16000) NULL ,
> "Status"          varchar(10) NULL ,
>  PRIMARY KEY ("Request_Queue_Id") )
>
> The definition of the consolidated table is as follows:
>
> create table dbo.Request_Queue
> (Request_Queue_Id numeric(18,0) identity,
> Client varchar(128) default db_name() not null,
> Code smallint default 1 not null,
> Stmt text default 'New Request Queue' not null,
> Status varchar(10) default 'NEW' not null,
> Lastmodified datetime default getdate() not null)
>
> The upload_update script looks like this:
>
> update Request_Queue
> set Client = ?, Code = ?, Stmt = ?, Status = ?
> where Request_Queue_Id = ?
>
> Parameter 3, as specified in the error message is 'Stmt'. The actual 
> length
> of the column in the remote is 8,398 bytes. But I don't see anywhere where 
> a
> truncation error should be happening. We have successfully synched with
> lengths of less than 3,000 but this is our first synch with a text value
> this big. (We are updating remote stored procedures using MobiLink. That 
> big
> Stmt column contains a stored procedure)
>
> Does anybody else see something?
>
>
>
> 

Right you are Reg. I changed the remote datatype of column 'Stmt' to 'long
varchar' and the problem went away.

But due to the allowable length of ASE rows, we have to define Stmt as
'text' in the consolidated. That doesn't exist in ASA (does it?) so we'll go
with 'long varchar'. So we never can get a 'match' in datatypes, can we?

*sigh* I wish the client would just go all ASA..


"Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
wrote in message news:44e1fe09$1@forums-1-dub...
> I strongly suspect the problem will go away if you change the data type of
> the "Stmt" column to match between the remote and consolidated.  Is there
a
> reason you defined the column to be varchar(16000) on the remote and a
text
> column on the consolidated?
>
> --
> 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/swd/base.do
>    -> Choose SQL Anywhere Studio
>    -> Set filter to "Display ALL platforms IN ALL MONTHS"
>
>
> "Douglas" <doogie414@yahoo.com> wrote in message
> news:44e0f906$1@forums-1-dub...
> > We are using ASE 12.5 as consolidated, ASA 9.0.2 3267 as remote.
> >
> > The upload_update script for our 'request_queue' table is failing with
the
> > following error:
> >
> > E. 08/14 14:55:43. Message: ODBC: [DataDirect][ODBC Sybase Wire Protocol
> > driver]String data, right truncated. Error in parameter 3. (ODBC State =
> > 22001, Native error code = 0).  Table Name: Request_Queue.  Primary
> > Key(s):
> > 11686
> >
> > The definition of the remote table is as follows:
> >
> > CREATE TABLE "dbo"."Request_Queue" (
> > "Request_Queue_Id"       unsigned int NOT NULL ,
> > "Client"       varchar(128) NULL ,
> > "Code"         smallint NULL ,
> > "Stmt"     varchar(16000) NULL ,
> > "Status"          varchar(10) NULL ,
> >  PRIMARY KEY ("Request_Queue_Id") )
> >
> > The definition of the consolidated table is as follows:
> >
> > create table dbo.Request_Queue
> > (Request_Queue_Id numeric(18,0) identity,
> > Client varchar(128) default db_name() not null,
> > Code smallint default 1 not null,
> > Stmt text default 'New Request Queue' not null,
> > Status varchar(10) default 'NEW' not null,
> > Lastmodified datetime default getdate() not null)
> >
> > The upload_update script looks like this:
> >
> > update Request_Queue
> > set Client = ?, Code = ?, Stmt = ?, Status = ?
> > where Request_Queue_Id = ?
> >
> > Parameter 3, as specified in the error message is 'Stmt'. The actual
> > length
> > of the column in the remote is 8,398 bytes. But I don't see anywhere
where
> > a
> > truncation error should be happening. We have successfully synched with
> > lengths of less than 3,000 but this is our first synch with a text value
> > this big. (We are updating remote stored procedures using MobiLink. That
> > big
> > Stmt column contains a stored procedure)
> >
> > Does anybody else see something?
> >
> >
> >
> >
>
>

There is a TEXT data type in ASA, but it's just a domain that is implemented 
as a LONG VARCHAR allowing NULL.  That's all the TEXT data type on ASE is.

The following sections in the ML documentation says what data types you 
should use to map ASE data types to ASA data types.

MobiLink Administration Guide
DataType Conversions
Adaptive Server Enterprise data mapping

-- 
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/swd/base.do
   -> Choose SQL Anywhere Studio
   -> Set filter to "Display ALL platforms IN ALL MONTHS"


"Douglas" <doogie414@yahoo.com> wrote in message 
news:44e1ff06$1@forums-2-dub...
> Right you are Reg. I changed the remote datatype of column 'Stmt' to 'long
> varchar' and the problem went away.
>
> But due to the allowable length of ASE rows, we have to define Stmt as
> 'text' in the consolidated. That doesn't exist in ASA (does it?) so we'll 
> go
> with 'long varchar'. So we never can get a 'match' in datatypes, can we?
>
> *sigh* I wish the client would just go all ASA..
>
>
> "Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
> wrote in message news:44e1fe09$1@forums-1-dub...
>> I strongly suspect the problem will go away if you change the data type 
>> of
>> the "Stmt" column to match between the remote and consolidated.  Is there
> a
>> reason you defined the column to be varchar(16000) on the remote and a
> text
>> column on the consolidated?
>>
>> --
>> 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/swd/base.do
>>    -> Choose SQL Anywhere Studio
>>    -> Set filter to "Display ALL platforms IN ALL MONTHS"
>>
>>
>> "Douglas" <doogie414@yahoo.com> wrote in message
>> news:44e0f906$1@forums-1-dub...
>> > We are using ASE 12.5 as consolidated, ASA 9.0.2 3267 as remote.
>> >
>> > The upload_update script for our 'request_queue' table is failing with
> the
>> > following error:
>> >
>> > E. 08/14 14:55:43. Message: ODBC: [DataDirect][ODBC Sybase Wire 
>> > Protocol
>> > driver]String data, right truncated. Error in parameter 3. (ODBC State 
>> > =
>> > 22001, Native error code = 0).  Table Name: Request_Queue.  Primary
>> > Key(s):
>> > 11686
>> >
>> > The definition of the remote table is as follows:
>> >
>> > CREATE TABLE "dbo"."Request_Queue" (
>> > "Request_Queue_Id"       unsigned int NOT NULL ,
>> > "Client"       varchar(128) NULL ,
>> > "Code"         smallint NULL ,
>> > "Stmt"     varchar(16000) NULL ,
>> > "Status"          varchar(10) NULL ,
>> >  PRIMARY KEY ("Request_Queue_Id") )
>> >
>> > The definition of the consolidated table is as follows:
>> >
>> > create table dbo.Request_Queue
>> > (Request_Queue_Id numeric(18,0) identity,
>> > Client varchar(128) default db_name() not null,
>> > Code smallint default 1 not null,
>> > Stmt text default 'New Request Queue' not null,
>> > Status varchar(10) default 'NEW' not null,
>> > Lastmodified datetime default getdate() not null)
>> >
>> > The upload_update script looks like this:
>> >
>> > update Request_Queue
>> > set Client = ?, Code = ?, Stmt = ?, Status = ?
>> > where Request_Queue_Id = ?
>> >
>> > Parameter 3, as specified in the error message is 'Stmt'. The actual
>> > length
>> > of the column in the remote is 8,398 bytes. But I don't see anywhere
> where
>> > a
>> > truncation error should be happening. We have successfully synched with
>> > lengths of less than 3,000 but this is our first synch with a text 
>> > value
>> > this big. (We are updating remote stored procedures using MobiLink. 
>> > That
>> > big
>> > Stmt column contains a stored procedure)
>> >
>> > Does anybody else see something?
>> >
>> >
>> >
>> >
>>
>>
>
>