1. Jerry M
  2. PowerBuilder
  3. Thursday, 15 November 2018 14:42 PM UTC

Hi,

 

I am using PB 2017 standard version, and receive following error when retrieve data that is defined as varchar(400)

in Sybase. Has this problem been resolved ? I really don't want to change the definition in the table since that is going to impact other applications. Any suggestion is greatly appreciated !

 

Jerry M Accepted Answer Pending Moderation
  1. Friday, 16 November 2018 16:42 PM UTC
  2. PowerBuilder
  3. # 1

Hi, Guys,, 

 

The issue has been resolved. 

In our deployment environment, we are using the right version of open client. But in PB IDE,

the database profile was created using "SYC SAP ASE" interface, which I believe is an older one. I re-created the profile using "ASE SAP ASE 15x|16x" interface and the dw is now working properly. No error message !!! 

 

Thank you all for your helps !

Regards,

 

Jerry 

 

Comment
  1. Chris Pollach @Appeon
  2. Friday, 16 November 2018 18:48 PM UTC
Excellent news Jerry.



Don't forget to correct your DBPARM setting as well! ;-)
  1. Helpful
There are no comments made yet.
Kim Berghall Accepted Answer Pending Moderation
  1. Thursday, 15 November 2018 22:02 PM UTC
  2. PowerBuilder
  3. # 2

Could also try to cast the column as text.

Comment
  1. Jerry M
  2. Friday, 16 November 2018 13:35 PM UTC
Hi,

How do you cast varchar to text in PB ?



Thanks !
  1. Helpful
  1. Kim Berghall
  2. Friday, 16 November 2018 14:02 PM UTC
Select cast(longcolumnname as text) as longcolumnname

from xyztable
  1. Helpful
There are no comments made yet.
Jerry M Accepted Answer Pending Moderation
  1. Thursday, 15 November 2018 19:32 PM UTC
  2. PowerBuilder
  3. # 3

Hi,

Does Appeon PB IDE comes with a native Sybase driver ?

 

Thanks !

 

jerry

 

Comment
  1. Chris Pollach @Appeon
  2. Friday, 16 November 2018 14:37 PM UTC
Hi Jerry;



Yes, it sure does!



Older PB/ASE versions: SQLCA.DBMS = "SYC"

Newer PB/ASE versions: SQLCA.DBMS = "ASE"



HTH

Regards ... Chris

  1. Helpful
There are no comments made yet.
Jerry M Accepted Answer Pending Moderation
  1. Thursday, 15 November 2018 16:22 PM UTC
  2. PowerBuilder
  3. # 4

Thank you guys for your help. I will look into the issue and let you know the result.

Really appreciate it !

 

Jerry

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 15 November 2018 16:09 PM UTC
  2. PowerBuilder
  3. # 5

Sybase ASE used to only support char(255). I believe that you are using an older version of Open Client that doesn't know that a char column can have more than 255 characters.

Comment
There are no comments made yet.
Jerry M Accepted Answer Pending Moderation
  1. Thursday, 15 November 2018 15:59 PM UTC
  2. PowerBuilder
  3. # 6

Chris,

 

Here is the columns specification

 

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 15 November 2018 15:42 PM UTC
  2. PowerBuilder
  3. # 7

This might be caused by Sybase Open Client not supporting char columns over 255. Make sure your Open Client version matches the database server.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 15 November 2018 15:02 PM UTC
  2. PowerBuilder
  3. # 8

Hi Jerry;

   The DWO default for handling Char or VarChar data is 32K. So this seems like a very strange error. I wonder what the DW definition of the column looks like? Can you check that in the DW painter under the Column Pane and let us know?

   Also, can you tell us ...

  1. What DBMS are you using - SA or ASE?
  2. What version of the DBMS
  3. What client are you using to connect (ie: ADO.Net. ODBC, native, etc)?

Thanks ... Chris

Comment
  1. Jerry M
  2. Thursday, 15 November 2018 15:54 PM UTC
HI Chris,

I am using

Adaptive Server Enterprise/16.0/EBF 22493 SMP/P/Sun_svr4/OS 5.10/asecepheus/3530/64-bit/FBO/Sun Feb 16 07:58:08 2014

I believe we are using native DB driver.

Just FYI, we just recently migrated all our applications from Sap PB to Appeon . What I was doing is I increased the column size from varchar(255) to varchar(500 ) in Sybase . And in PB,, I edit the source of the DW and change the column specification of that column from 255 to 500.. I received the error when preview the DW. THank you for your response.



Jerry



  1. Helpful
  1. Chris Pollach @Appeon
  2. Thursday, 15 November 2018 16:10 PM UTC
Since you are on a newer version of ASE, are you using the newer native ASE driver in your PB App?

For example ...

SQLCA.DBMS = "ASE"

SQLCA.DBParm = "Release='16'"
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.