TD-15968/TD-15761: Data truncated(Oracle) in Long String TD6 Sp3

[Sunil]

Hello,

I am using Oracle 10g server and 10g on client. I am using two Pc , one for Deployment and another for Development.
I had download deploy60 and patch sp3 and run deploy60 on Deployment PC and patch sp3 on development PC.

I have seen that date of sqlora32.dll is still 01.04.2011 on Deployment PC , that mean sqlora32.dll has not been updated
after deployment using new deploy60.

I have seen that date of sqlora32.dll changed to 28.06.2011 on development PC where new patch applied.

//deployment PC
select long string data from oracle table into multiline text ( long ) is ok here.
//development PC
select long string data from oracle table into multiline text ( long) ,here text truncated.

to repro the case, I have copied sqlora32.dll from deployment PC to development PC and tried again , this time that was ok.

Please look this issue which is very serious issues.

Regards.
Sunil

[Jeff Luther]

Yes, here's what I see when I click Deploy60x
It prompts me to save TD-60SP2-DEPLOY.zip

which means that QA/internal people have not updated the deploy download yet. Sounds like that is why your sqlora32.dll files are not in sync; the dev. one is for SP3, while the deploy one is for SP2.

I'll remind the 'internal types' that deploy60 needs to be updated to SP3. Thanks for letting us know. And in the meantime copy the updated SP3 DLL to your deploy folder, as you've done.

[Sunil]

No, Jeff.
I had download deploy60sp3.zip from this link earlier and applied the same on deployment PC. I agreed , this is showing now sp2 deployer. Please look this issue asap.

Regards.
Sunil

[Ana Paula Bonani]

Fixed.

Please download the deployment package again.

Thanks,

[Sunil]

Hello.
I have download and applied but problem is still there, I am sending two sqlora32_old.dll and sqlora32_new.dll . sqlora32_new.dll [ Problem DLL ] is new one which is download as ana said.

Regards.
Sunil

[Jeff Luther]

Sunil: If you are still having this "data truncated Oracle" issue after downloading/installing v6 SP3, then I will need a small reproducible test case from you (test app + SQL script to create/insert some data into Oracle) so I can test this data truncation issue myself.

Earlier, you had an inconsistency in sqlora32.dll between runtime and dev/IDE, but I believe you got the correct SP3 runtime

I just installed the runtime and compare sqlora32.dll to my dev. folder and they are the same file now:

JL-v6SP3-DEV_sqlora32_DLL-OK.png

JL-v6SP3-RUNTIME_sqlora32_DLL-OK.png

** We need a test case to see what this "problem is still there" issue is.

[Sunil]

Hello jeff.

find enclosed sqlora of Sp2 and Sp3 , sp2 is correctly working where as sp3 is truncating data when populate long string into multiline text(datatype long).

Regards.
sunil

[giscon]

Hello,
I can confirm this problem.


I described a problem with TD6, SqlBase 11.6 and LongString (the two extra bytes at the end are missing when selecting into a variable).
Jeff told, that this defect has got the id TD-15761.

With the testcase I uploaded with my above mentioned bug report, the bug was only with SqlBase 11.6, with Oracle-DB's all ran fine.
That was the situation with SP2 EMP5347.

Now, reading this new bug report, I tried my testcase again with SP3 and an Oracle-DB.
And oops, now the LongString is truncated - instead of getting the 'Testvalue' ( string length 9, with the two null-bytes bufferlength 20), now you get only 'Testv' ( stringlength 5, bufferlength 12 ).

Maybe that testcase helps also a bit to reproduce this new bug
Guenter

[Mike Vandine]

Hi Guenter,

This should be fixed with EMP5361 as well.

[Sunil]

This is fixed for SQLBase but not for Oracle. Data fetched from Oracle Long string to Multiline text is still truncating.

Regards.
Sunil

[giscon]

Indeed, the EMP5361 contains in fact a new sqlora32.dll (from 2011-07-21), but this bug is still there as Sunil wrote:

This is fixed for SQLBase but not for Oracle. Data fetched from Oracle Long string to Multiline text is still truncating.

Don't know if some other oracle-issues are fixed with this sqlora32.dll, because in the README-EMP5361.txt is nothing to find about Oracle.

As mentioned above in this topic, this bug with Oracle Long String truncation appeared new in SP3 with that sqlora32.dll.
With my uploaded testcase you should have got 'Testvalue" (stringlength 9, bufferlength 20) and of course it should work for a SELECT into a Long String Variable, a Data Field or a Multiline-Field as well.

But since SP3 the string is always truncated (in the example to string length 5, buffer size 12).
Now with the SP3 EMP5361 the string is still truncated, but when selecting into a long string variable, the buffer has even 2 more useless bytes (truncated string with length of only 5, but a buffer length of 14 ).

Regards
Guenter

[Mike Vandine]

Hi Sunil,

Looking at the thread and also at the defect, it looks like the comments from Guenter, "Jeff told, that this defect has got the id TD-15761", were seen by Ana (who escalated *that* defect), but unfortunately that defect did NOT have the Oracle issue reported with it so the Oracle bit was not fixed.

I have reported this urgently to Development as defect TD-15968, specifically for the Oracle problem.

So sorry for the delay in getting this resolved.

Best regards,

[klaus@easypro]

Hi all,

our application (at the moment on TD6.0SP3+EMP5361) connects to Oracle 11g R1 and I didn't get truncated data so far.
But I obviously ran into the defect regarding two trailing null-bytes. As in one of the two other topics, any further string processing fails.

Resetting the bufferlength or just trim the string would be a workaround but unfortunately it is impossible to use that workaround because the statements with into variables are build dynamically at runtime.
As this is a really urgent issue, I hope that there will be an EMP asap.

kind regards
klaus

[Jean-Marc Gemperle]

Hi

Will be fixed with EMP5363

Jean-Marc

[giscon]

Hi,
in the other topic your refer to

Will be fixed with EMP5363 see viewtopic.php?f=69&t=6879

you added two bitmaps.
The lower of them shows that the concatenation problem because of wrong buffer length (here 2 bytes too long) may be fixed, but the truncation problem with Oracle still exists ! Only 5 characters are selected, but with the testcase there should be 9 ("Testvalue") !!
Hope that this will be fixed, too.

Regards
Guenter