Folks;
into trying to track down a particularly strange error appearing with our main MaxDB instance, and obviously only with this one (works well with testbed and local development systems):
com.sap.dbtech.jdbc.ConnectionSapDBFinalize@1514b420[T181].prepareStatement (/* OrderDAO.getAuftragsNummern */ SELECT AUFNR FROM AUFTRAG WHERE EMPFPPID IN (SELECT PPID FROM PPARTNER WHERE WEBUSER = ?) AND MEDIUM = 'PF' AND EINGDAT IS NULL)
=> com.sap.dbtech.jdbc.CallableStatementSapDBFinalize@42f659ce[T181][ParseID 08b5cf560000080154002c00]
com.sap.dbtech.jdbc.CallableStatementSapDBFinalize@42f659ce[T181][ParseID 08b5cf560000080154002c00].setString (1, DEMO_AKI-)
com.sap.dbtech.jdbc.CallableStatementSapDBFinalize@42f659ce[T181][ParseID 08b5cf560000080154002c00].execute ()
<-!
Timestamp: 2014-04-09 15:13:17.944com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [-9111]: ��V���� T��,��getA
at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:300)
at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:146)
at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:69)
at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:1096)
at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:720)
at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:562)
at com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:454)
at com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:319)
at com.sap.dbtech.jdbc.trace.log.PreparedStatement.execute(PreparedStatement.java:303)
at com.sap.dbtech.jdbc.trace.PreparedStatement.execute(PreparedStatement.java:153)
As far as I can tell the query itself is not too complex or strange, and I am a bit confused by the garbled response message all along with the 9111 error code. In the server log messages, there are -9111 Move errors. Could this be related? Any way of tracking down what happens here? All servers as well as the JDBC driver are 7.8 on top of 64bit Linux.
TIA and all the best,
Kristian