Basis Errors and Solutions

Empty sqljdbc.jar is deployed for Microsoft JDBC Driver

July 3, 2009 at 12:42 am

[deployment] [driver] [Empty] [informix jdbc jar] [jar] [JDBC] [jdbc jar] [Microsoft] [oracle jdbc jar] [Server] [SQL] [sqljdbc.jar]

Empty string interpretation as NullSymptom JDBC Adapter Receiver when stored procedures are used does not interpreted empty string values as null, even though the channel is configured to do so. Instead empty strings are inserted into...

Symptom
Deploying Microsoft JDBC Driver for SQL Server (sqljdbc.jar) deploys an empty jar file in /bin/ext/ directoryOther terms

Microsoft JDBC driver deployment, empty jar, sqljdbc.jar, SQL Server
Reason and Prerequisites

Version 1.2 of the Microsoft JDBC Driver (583.286 bytes) contains besides the classes implementing the JDBC connectivity two additional files, namely:
sqljdbc.jar (0 bytes in size)sqljdbc.jar.old (287 KBs in size)

Due to a programming error, the Engine deploys as a driver the inner sqljdbc.jar (0 bytes in size), instead of the wrapping sqljdbc.jar (583.286 bytes).
If the wrapping sqljdbc.jar file is renamed to archive different than sqljdbc.jar or sqljdbc.jar.old (e.g. sqljdbc1.jar) then the deployment works.
Solution

I. Upgrade the J2EE Engine and retry the deployment

For SAP J2EE Engine 6.40 to SP 24 or higherFor SAP J2EE Engine 7.00 to SP 19 or higherFor SAP J2EE Engine 7.01 to SP 04 or higher

II. If upgrade is not possible for whatever reason, as a workaround you can do either of the following steps
Rename the JDBC driver file that does not deploy and retry the deployment with the renamed driver (for example name it sqljdbc_workaround.jar)Obtain a driver with correct structure from the JDBC driver vendor and retry the deployment with the fixed driver