Hallo! I reported a couple of days ago a bug in Orion server concerning table name length. This is something that was introduced after Orion 1.1.24 where it works correctly. As of your current release 1.1.37 this doesn't work correctly. A little background: In transact SQL (used by Sybase and SQLServer) you can by default have a table name of 30 characters. Each table is owned by a table and a server. This means that you can access the table by writing <server>.<database>.<owner>.<table name>. If one have for instance more than one user accessing a database one must address the table by <owner>.<table name> where table name can be up to 30 characters or more if you have reconfigured the default of the database. In an environment with a big shared database between different programs application servers and so on one will use more than one database user to track changes, performance issues and so on. The problem: In orion-ejb-jar.xml one configures source and table, if your are addressing a table which is called more than 30 characters the rest will be shopped of. This means that a table that is more than 26 characters in length can not be addressed by <owner>.<database> which is a big problem. For instance I have a table owned by user dbo and called EricssonAccumulatedHscsdBSC (dbo.EricssonAccumulatedHscsdBSC) which in Orion after deployment will become EricssonAccumulatedHscsdBS (dbo.EricssonAccumulatedHscsdBS) which of' course fails horrible. (This in the new orion-ejb-jar.xml written by Orion after deployment.) I can't change the table name because of it's in use by different application and is feed from something that the people which is in the telecom business can guess easily. :-) The fix for the problem is to handle T-SQL addressing of tables correctly. Regards, Torgeir Lerkerød Telenor Mobile Plan IT
