Quantcast
Channel: SCN: Message List - SAP MaxDB
Viewing all articles
Browse latest Browse all 2539

Re: Error "-9400 AK Cachedirectory full"

$
0
0

Hi Thorsten,

 

Thanks for your answer, this is great news. Do you have any clue when 7.8.02.42 might be released, or is there any possibility to get a patched-binary so that we can "survive" until 7.8.02.42 is released? We would be glad to beta-test that version and give you feedback to let you know if it fixes our problem.

 

By the way now that you're talking about constraints, maybe another minor problem that we have is also related: sometimes when we get a constraint violation exception, the JDBC driver reports the wrong constraint name: there is usually an offset of 1, that means it reports the previous or next constraint from that table (I don't remember if it's the previous or next). Do you think that this is related?

 

Finally, there is also another minor problem that we get almost every day, not sure if this is related. We sometimes get a JDBC exception when we read a lot of rows (one at a time) from any table. The exception is

 

java.lang.ArrayIndexOutOfBoundsException: 41

        at com.sap.dbtech.util.StructuredBytes.getInt2(StructuredBytes.java:168) ~[sap-jdbc-7.6.09.02.jar:na]

        at com.sap.dbtech.jdbc.packet.ReplyPacket.clearPartCache(ReplyPacket.java:778) ~[sap-jdbc-7.6.09.02.jar:na]

        at com.sap.dbtech.jdbc.packet.ReplyPacket.<init>(ReplyPacket.java:52) ~[sap-jdbc-7.6.09.02.jar:na]

        at com.sap.dbtech.jdbc.packet.ReplyPacketFactory.getReplyPacket(ReplyPacketFactory.java:28) ~[sap-jdbc-7.6.09.02.jar:na]

        at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:653) ~[sap-jdbc-7.6.09.02.jar:7.6.09    Build 000-000-010-635]

        at com.sap.dbtech.util.GarbageCan.emptyCan(GarbageCan.java:70) ~[sap-jdbc-7.6.09.02.jar:na]

        at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:687) ~[sap-jdbc-7.6.09.02.jar:7.6.09    Build 000-000-010-635]

        at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:565) ~[sap-jdbc-7.6.09.02.jar:7.6.09    Build 000-000-010-635]

        at com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:454) ~[sap-jdbc-7.6.09.02.jar:7.6.09    Build 000-000-010-635]

        at com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:319) ~[sap-jdbc-7.6.09.02.jar:7.6.09    Build 000-000-010-635]

        at com.sap.dbtech.jdbc.CallableStatementSapDB.executeQuery(CallableStatementSapDB.java:763) ~[sap-jdbc-7.6.09.02.jar:7.6.09    Build 000-000-010-635]

        at com.sap.dbtech.jdbc.trace.PreparedStatement.executeQuery(PreparedStatement.java:161) ~[sap-jdbc-7.6.09.02.jar:na]

 

It's always that ArrayIndexOutOfBoundsException: 41 ... it's not too bad because it just happens from time to time, but maybe interesting for you to know about that.

 

Thanks again for your great support, and please let me know about 7.8.02.42.

 

Best regards,

Christophe


Viewing all articles
Browse latest Browse all 2539

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>