Questions? Feedback?powered byOlark live chat software
Bug 1936

Select from db is different by r2 and r3 09 October, 2019

roberto davolio
30 November, 2018
Product: PowerBuilder Category: Database
Version: 2017 R3 Publishing: Public
Status: Closed Priority: P3
Classification: Resolution: INVALID
Chris Pollach 05 February, 2019
Hi Roberto,

  Thank you for letting us know that you were able to proceed via a "work around". Since you have not been able to attach an SQL trace or a reproducible test case, we will now close this ticket.

  If in the future you can provide a concrete test case or low-level SQL trace(s) that we can analyze, please feel free to open a new ticket for this issue.

Regards ... Chris
roberto davolio 05 February, 2019
I found no solution.

i have use a workaroud to skip this error.
Chris Pollach 04 February, 2019
Hi Roberto,

   Since we have not heard back from you since our last few responses, we are assuming that you have resolved this issue. We will now proceed to close this ticket. 
   If you encounter another issue around this area, please feel free to open a new ticket.

Regards ... Chris
Chris Pollach 13 December, 2018
Hi Roberto;

  Any more information from your client with the PB run-time SQL execution issue?

Regards ... Chris
Chris Pollach 10 December, 2018
Hi Roberto;

We have lowered the priority of your issue to the default P3 to be consistent with the priority level definitions in our support policy posted to our Website: https://www.appeon.com/sites/default/files/pictures/Downloads/Appeon_2017_Standard_Support_Plan_Description.pdf

Please keep in mind a P3 priority is not a low priority (it is how most cases are processed).  Also, if we have multiple reports of the same P3 priority issue we would internally treat it as a higher priority than P3.

Thank you for your understanding.

Regards ... Chris
roberto davolio 03 December, 2018
Unfortunately it is a problem of production and I can not repeat the case because I overwrote R2 with R3
Now I am not at the customer and I can try to see Thursday if I reply the error.
I can try to see if the value on R3 on ASA behaves the same way
Chris Pollach 30 November, 2018
Hi Roberto;

 BTW: Is this a production issue or only one that your encountering in your development environment for now?

Regards ... Chris
Chris Pollach 30 November, 2018
 Thanks!

That is really weird why R3 behaves differently. 

   Can you run two SQL traces for me by setting the following in both the R2 and R3 IDE's ( Check the "Generate Trace" checkbox in the DB Profile painter ) ...

Preview should state => SQLCA.DBMS = "TRACE ASE"

Connect the IDE to the ASE database you are using. Then open the DB Painter and proceed to the iSQL pane. Enter the following SQL ...

select password
	from utente
	where
	login = '<your name here>'; 

Please attach the two SQL traces to this ticket .. thanks!

Regards ... Chris
roberto davolio 30 November, 2018
(In reply to Chris Pollach from comment #5)
   Thanks for the extra information. 

  If ASE 16.x and native DB Client ... then please verify that your PB IDE
(DB Profile Painter) and your PB Apps use the following connection settings
...


// Profile ASE 
SQLCA.DBMS = "ASE"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Release='16'"
YES is correct!!!!!
Chris Pollach 30 November, 2018
   Thanks for the extra information. 

  If ASE 16.x and native DB Client ... then please verify that your PB IDE (DB Profile Painter) and your PB Apps use the following connection settings ...


// Profile ASE 
SQLCA.DBMS = "ASE"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Release='16'"
roberto davolio 30 November, 2018
(In reply to Chris Pollach from comment #3)
Hi Roberto;

  Assuming ...
1) DB Client being used to connect to ASE is the same
2) ASE version, instance is the same
3) Your DB schema is the same

Yes, then that would be a weird thing for R3 to be doing vs R2. As AFAIK,
there were no changes to the ASE interface in R3.

Can you tell us ...
1) How are you connecting to ASE (that is SQLCA.DBMS = "???")?
2) What version of ASE are you using?

Regards ... Chris
i connect using ASE native driver openclient 16 ase db 16.0.sp3.pl3 but i view that r2 is ok with other old version, but r3 wrong to read data!
Chris Pollach 30 November, 2018
Hi Roberto;

  Assuming ...
1) DB Client being used to connect to ASE is the same
2) ASE version, instance is the same
3) Your DB schema is the same

Yes, then that would be a weird thing for R3 to be doing vs R2. As AFAIK, there were no changes to the ASE interface in R3.

Can you tell us ...
1) How are you connecting to ASE (that is SQLCA.DBMS = "???")?
2) What version of ASE are you using?

Regards ... Chris
roberto davolio 30 November, 2018
hi Chris,
in my script i have this select:
select password
	into :ls_password
	from utente
	where
	login = :is_login_name

if i execute this on pb 2017 r3 : 
ls_password = ‰b—·a
if i execute onr2:
ls_password = ‰b—·a
R2 have the correct value!!!!!

help me!!!!!!
Chris Pollach 30 November, 2018
Hi Roberto;

  Can you give us more information about your SQL issue? What you have described thus far is very vague.

  Please supply table description, full sql, SQL trace, error codes / text, etc so that we can assess your problem further.

  Also, what ASE version are you using and what DB client are you using to connect to ASE?

Regards ... Chris
roberto davolio 30 November, 2018
*Phenomenon:
when i do SELECT campo into :ls_campo ....
r3 : 
‰b—·a
r2:
‰b—·a

*Reproduce Steps:


Remark:

different read and stop application!!!!!
OS:
Windows 10 
Platform:
All 
Database Type:
SAP ASE 
Database Version: