Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Error converting characters into server's character set. Some character(s) could not be converted.

4 posts in DataWindow Last posting was on 2009-02-13 14:57:43.0Z
Paula Posted on 2009-02-13 12:27:19.0Z
Reply-To: "Paula" <ft252@hotmail.com>
From: "Paula" <ft252@hotmail.com>
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Error converting characters into server's character set. Some character(s) could not be converted.
Lines: 37
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49956727$1@forums-1-dub>
Date: 13 Feb 2009 04:27:19 -0800
X-Trace: forums-1-dub 1234528039 10.22.241.152 (13 Feb 2009 04:27:19 -0800)
X-Original-Trace: 13 Feb 2009 04:27:19 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88795
Article PK: 418046

Error converting characters into server's character set. Some character(s)
could not be converted.

No changes made to database.

UPDATE Ticket_detail SET problem = 'mecho Team,

I have set up several table repdefs in our test environment (PROD_jam) to
determine the benefit of having table repdefs in addition to a database
repdef. After I set up one of the table repdefs I ran several updates on the
primary table to verify whether the where-clause was smaller on the
replicate database. When I reviewed the transaction in the outbound queue on
the secondary rep server (TEST_pqr) it was still including all of the
columns in the where-clause.


Could you review my set up below and let me know why I am still seeing all
of the columns in the where-clause? I'm not sure if this is a result of
specifying the 'send standby' option in the repdef but is my understanding
that the 'send standby' option was required when mixing database and table
level replication. Currently the table repdef includes all columns in the
table so it shouldn't matter whether 'send standby all columns' or 'send
standby replication definition columns' is used. Should this be expected
even with 'replicate minimal columns' specified in the table repdef? Any
help is greatly appreciated! ' WHERE TicketNo = 17



-----------------

Any Idea what to do ?


Paula Posted on 2009-02-13 12:41:22.0Z
Reply-To: "Paula" <ft252@hotmail.com>
From: "Paula" <ft252@hotmail.com>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <49956727$1@forums-1-dub>
Subject: Re: Error converting characters into server's character set. Some character(s) could not be converted.
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49956a72@forums-1-dub>
Date: 13 Feb 2009 04:41:22 -0800
X-Trace: forums-1-dub 1234528882 10.22.241.152 (13 Feb 2009 04:41:22 -0800)
X-Original-Trace: 13 Feb 2009 04:41:22 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88797
Article PK: 418048

Any solution that it will support all the ASCCI value
what i have to do in PowerBuilder ?

"Paula" <ft252@hotmail.com> wrote in message news:49956727$1@forums-1-dub...
> Error converting characters into server's character set. Some character(s)
> could not be converted.
>
> No changes made to database.
>
> UPDATE Ticket_detail SET problem = 'mecho Team,
>
> I have set up several table repdefs in our test environment (PROD_jam) to
> determine the benefit of having table repdefs in addition to a database
> repdef. After I set up one of the table repdefs I ran several updates on
> the primary table to verify whether the where-clause was smaller on the
> replicate database. When I reviewed the transaction in the outbound queue
> on the secondary rep server (TEST_pqr) it was still including all of the
> columns in the where-clause.
>
>
> Could you review my set up below and let me know why I am still seeing all
> of the columns in the where-clause? I'm not sure if this is a result of
> specifying the 'send standby' option in the repdef but is my understanding
> that the 'send standby' option was required when mixing database and table
> level replication. Currently the table repdef includes all columns in the
> table so it shouldn't matter whether 'send standby all columns' or 'send
> standby replication definition columns' is used. Should this be expected
> even with 'replicate minimal columns' specified in the table repdef? Any
> help is greatly appreciated! ' WHERE TicketNo = 17
>
>
>
> -----------------
>
> Any Idea what to do ?
>
>
>
>
>
>


"Jason 'Bug' Fenter [TeamSybase]" <NO_SPAMMING_jason.fenter_ Posted on 2009-02-13 14:32:29.0Z
From: "Jason 'Bug' Fenter [TeamSybase]" <NO_SPAMMING_jason.fenter_@_teamsybase.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: Error converting characters into server's character set. Some character(s) could not be converted.
References: <49956727$1@forums-1-dub> <49956a72@forums-1-dub>
In-Reply-To: <49956a72@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4995847d$1@forums-1-dub>
Date: 13 Feb 2009 06:32:29 -0800
X-Trace: forums-1-dub 1234535549 10.22.241.152 (13 Feb 2009 06:32:29 -0800)
X-Original-Trace: 13 Feb 2009 06:32:29 -0800, vip152.sybase.com
Lines: 49
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88801
Article PK: 418054

This sounds more like a database question than a programming tool
question. You might want to ask this in a newsgroup dedicated to the
RDBMS that you use.

Paula wrote:
> Any solution that it will support all the ASCCI value
> what i have to do in PowerBuilder ?
> "Paula" <ft252@hotmail.com> wrote in message news:49956727$1@forums-1-dub...
>> Error converting characters into server's character set. Some character(s)
>> could not be converted.
>>
>> No changes made to database.
>>
>> UPDATE Ticket_detail SET problem = 'mecho Team,
>>
>> I have set up several table repdefs in our test environment (PROD_jam) to
>> determine the benefit of having table repdefs in addition to a database
>> repdef. After I set up one of the table repdefs I ran several updates on
>> the primary table to verify whether the where-clause was smaller on the
>> replicate database. When I reviewed the transaction in the outbound queue
>> on the secondary rep server (TEST_pqr) it was still including all of the
>> columns in the where-clause.
>>
>>
>> Could you review my set up below and let me know why I am still seeing all
>> of the columns in the where-clause? I'm not sure if this is a result of
>> specifying the 'send standby' option in the repdef but is my understanding
>> that the 'send standby' option was required when mixing database and table
>> level replication. Currently the table repdef includes all columns in the
>> table so it shouldn't matter whether 'send standby all columns' or 'send
>> standby replication definition columns' is used. Should this be expected
>> even with 'replicate minimal columns' specified in the table repdef? Any
>> help is greatly appreciated! ' WHERE TicketNo = 17
>>
>>
>>
>> -----------------
>>
>> Any Idea what to do ?
>>
>>
>>
>>
>>
>>
>
>


Chris Pollach Posted on 2009-02-13 14:57:43.0Z
From: "Chris Pollach" <cpollach@travel-net.com>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <49956727$1@forums-1-dub>
Subject: Re: Error converting characters into server's character set. Some character(s) could not be converted.
Lines: 64
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49958a67$1@forums-1-dub>
Date: 13 Feb 2009 06:57:43 -0800
X-Trace: forums-1-dub 1234537063 10.22.241.152 (13 Feb 2009 06:57:43 -0800)
X-Original-Trace: 13 Feb 2009 06:57:43 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88802
Article PK: 418055

Hi Paula;

Yes, I have had this problem before as well. Especially with PB 10 and
higher being UTF-16LE Unicode based and the database and/or DBMS set-up as
ANSI. In that case, sending special characters from the Unicode based PB
application to the ANSI database could get this error situation. In the
cases where I was caught on this I had to either change the DB to Unicode
(ie Upgrade), change the DB connection parameters, use the String (xxxxx,
ANSI! ) conversion method or even convert the special character to an escape
sequence and back again on the Select to get around this limitation.

Can you tell us ...

1) DBMS & version
2) PB version
3) OS (for PB and DB)
etc

--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com

"Paula" <ft252@hotmail.com> wrote in message news:49956727$1@forums-1-dub...
> Error converting characters into server's character set. Some character(s)
> could not be converted.
>
> No changes made to database.
>
> UPDATE Ticket_detail SET problem = 'mecho Team,
>
> I have set up several table repdefs in our test environment (PROD_jam) to
> determine the benefit of having table repdefs in addition to a database
> repdef. After I set up one of the table repdefs I ran several updates on
> the primary table to verify whether the where-clause was smaller on the
> replicate database. When I reviewed the transaction in the outbound queue
> on the secondary rep server (TEST_pqr) it was still including all of the
> columns in the where-clause.
>
>
> Could you review my set up below and let me know why I am still seeing all
> of the columns in the where-clause? I'm not sure if this is a result of
> specifying the 'send standby' option in the repdef but is my understanding
> that the 'send standby' option was required when mixing database and table
> level replication. Currently the table repdef includes all columns in the
> table so it shouldn't matter whether 'send standby all columns' or 'send
> standby replication definition columns' is used. Should this be expected
> even with 'replicate minimal columns' specified in the table repdef? Any
> help is greatly appreciated! ' WHERE TicketNo = 17
>
>
>
> -----------------
>
> Any Idea what to do ?
>
>
>
>
>
>