TD-15932: Quoted string too long

[Reinhard]

Hi,

I have installed EMP5361 (TD6.0 SP3) and was glad to see, that TD-15932 is fixed correctly.
But now there is a new error ("Quoted string too long"), which did not appear before installing
EMP5361. Database is ORACLE 10g.
The statement below is created dynamically by classes.

Best regards

Reinhard

Statement:

Statement.txt

[Jeff Luther]

So, passing that string to SqlPrepare(), for example, causes the SQL error "quoted string too long" ??

Or is it because you referred to TD-15932, which was a fix for SqlPLSQLCommand, that this is the function you now call for your SP (that query is the SP?) and get the "quoted string" error from Oracle? Is this an Oracle error, and if so what #? And if it is a TD error, then that means TD is trying to parse this query and displaying the "quoted string" error. If so, what TD function are you calling with this query as a parameter?

I am just trying to 'read between the lines' a bit to figure out what you are actually reporting.

I'll ask internally about this. I did talk with the router developer who also asked: Did you write this query using v6 SP3, or is this a query that worked before SP3? BTW, If it is an Oracle issue and dev. needs the SP to be able to analyze what is going on, the developer said he would need an unload for all those tables and data. That query is far too complex to try to recreate from the beginning. Thanks.

[Reinhard]

Hello,

there is no coherence/context between these two erros. The first error was the problem with SqlPLSqlCommand and it was solved after installing EMP5361.
The second error (the long dynamically created statement) is completely different code in another APL.
So, with installing EMP5361, I've one error less and another more, because the second error did not appear before installing EMP5361.
TD-Version is 6.0-SP3 Build 25674
ORACLE-Version is 10.2.4.0

best regards

reinhard

[Jeff Luther]

The second error (the long dynamically created statement) is completely different code in another APL.

So specifically where is that error now occurring, that is on what line of SAL code?

And the error is a TD error, like a msg. box with "SQLWindows" in the title? Or is it an Oracle error? And, if so, which one?

Well, I thought the error sounded like it might be a missing quote, and so I copy/pasted your full statement into Notepad and counted them. I get an odd number with this line fragment as the likely culprit:

Code: Select all

...Where
(
NAMESP_TEXT Like 'HADERTHA And PERSON.PERSON_SEQ In (Select V.PERSON_SEQ From KA_VERTRAG V Where...

That's a single quote before HADERTHA but no closing quote after it. I'd expect "... LIKE 'HADERTHA%'..." since you have a LIKE operator before it.

[Reinhard]

[SOLVED] with EMP5365

[Jeff Luther]

Great! Thanks for letting us know. I'll amend this thread title to reflect that.