When executing a Sybase stored procedure using SimpleJdbcCall class, the database metadata is not being loaded. The logs show the following messages:
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory - SQL Server is not one of the databases fully supported for procedure calls -- supported are: [Apache Derby, DB2, MySQL, Microsoft SQL Server, Oracle, Sybase]
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory - Metadata processing disabled - you must specify all parameters explicitly
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory - Using org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider
After little research, I found that our Sybase database is named "SQL Server" and the commonDatabaseName method in JdbcUtils being used to get the database name compares against the string "sql server".
This problem gets fixed if the comparison with "sql server" is done without considering the case.
I am using the BEA's Sybase Driver (Type 4) Versions:11.x, 12.x that comes with Weblogic 10.3. The driver class name is: weblogic.jdbc.sybase.SybaseDriver
And here is the db information I got from DBA: Adaptive Server Enterprise/15.0.2/EBF 15961 ESD#6/P/RS6000/AIX 5.2/ase1502/2537/64-bit/FBO/Thu Oct 2 00:22:14 2008
spring-projects-issues commentedAug 29, 2009
•
edited
Balaji Varanasi opened SPR-6053 and commented
When executing a Sybase stored procedure using SimpleJdbcCall class, the database metadata is not being loaded. The logs show the following messages:
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory - SQL Server is not one of the databases fully supported for procedure calls -- supported are: [Apache Derby, DB2, MySQL, Microsoft SQL Server, Oracle, Sybase]
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory - Metadata processing disabled - you must specify all parameters explicitly
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory - Using org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider
After little research, I found that our Sybase database is named "SQL Server" and the commonDatabaseName method in JdbcUtils being used to get the database name compares against the string "sql server".
This problem gets fixed if the comparison with "sql server" is done without considering the case.
Affects: 2.5.6, 3.0 M4
Attachments:
Issue Links:
Referenced from: commits ea674f2, b482d6d
The text was updated successfully, but these errors were encountered: