Version 15 client compatibility

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
Sorry in a hurry so not much detail provided.

Running a reorg on a table with a long name from trunk.132 results in the 
following errors

Beginning REORG REBUILD of table 'a_external_support_report'.
The identifier that starts with '[dbo.a_external_support_repor' is too 
long. Maximum length is 28.
REORG REBUILD of table 'a_external_support_report' failed due to an 
internal error. Please contact SYBASE Technical Support.
(1 rows affected)

What version of the product are you using? On what operating system?
Sybase 15.0.2 on Solaris 10 and trunk.132 on Windows XP

Please provide any additional information below.
Seems to be related to the following
http://www.petersap.nl/SybaseWiki/index.php?
title=Version_15_client_compatibility&printable=yes

Original issue reported on code.google.com by glen.w.k...@gmail.com on 19 Nov 2009 at 5:22

[GoogleCodeExporter]

Sorry forgot to mention that running the reorg command from an isql command 
line on 
the Solaris 10 box itself completes correctly

Original comment by glen.w.k...@gmail.com on 19 Nov 2009 at 5:23

[GoogleCodeExporter]

Sorry to just simplify again, the error above was from running a stored 
procedure, I 
just did the same thing without the stored procedure

The sql command in ASEisql is 'reorg rebuild dbo.a_external_support_report'

The error is

------------------------ Execute ------------------------
Beginning REORG REBUILD of table 'a_external_support_report'.
The identifier that starts with '[dbo.a_external_support_repor' is too long. 
Maximum 
length is 28.
REORG REBUILD of table 'a_external_support_report' failed due to an internal 
error. 
Please contact SYBASE Technical Support.
----------------- Done ( 2 errors ) ------------------

Original comment by glen.w.k...@gmail.com on 19 Nov 2009 at 5:29

[GoogleCodeExporter]

what is the version of your sybase client?

Original comment by daggett....@gmail.com on 21 Nov 2009 at 11:01

[GoogleCodeExporter]

Ah, I see see, it is not the client program which is the issue but the 
connectivity 
software.

I just had a look on my PC and it appears the SOE for my work includes a very 
old 
connectivity version

Sybase: C:\SQL\
libct.dll:  C:\SQL\libct.dll
CS Version: Sybase Client-Library/12.0/P/PC Intel/1/OPT/Mon Oct 04 15:42:12 1999
Provider:   InterfacesDriver
Interface file: C:\SQL\\ini\sql.ini

I will see if I can get it updated. Feel free to close this issue.

Original comment by glen.w.k...@gmail.com on 22 Nov 2009 at 11:04