DB-Version: 7.9.08.27 and 7.9.08.32
For most of our tables - not all - we get an error when trying to open the definition in Database-Studio.
A jdbc-program trying to call DatabaseMetaDataMaxDB.getPrimaryKeys also crashes:
com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [-9205]: System error: AK Catalog information not found:000000000003F5F5000A000F
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:1100)
at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:723)
at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:565)
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.CallableStatementSapDB.executeQuery(CallableStatementSapDB.java:763)
at com.sap.dbtech.jdbc.DatabaseMetaDataMaxDB.getPrimaryKeys(DatabaseMetaDataMaxDB.java:298)
at com.sap.dbtech.jdbc.trace.DatabaseMetaData.getPrimaryKeys(DatabaseMetaData.java:582)
at org.apache.tomcat.dbcp.dbcp.DelegatingDatabaseMetaData.getPrimaryKeys(DelegatingDatabaseMetaData.java:456)
We already tried to import a backup into a new server with the latest 7.9.08.32 - but the error remains the same.
In the Db Error File we get:
Thread | 0x6D22 Task | 285 2015-10-07 09:08:08 ERR AK CACHE 51105: 000000000003F5F5000A000F0000000000000000 |
Thread | 0x6D22 Task | 285 2015-10-07 09:08:08 ERR SYSERROR 51080: -9205 AK Catalog information not found:0 |
Thread | 0x6D22 Task | 285 2015-10-07 10:10:32 ERR AK CACHE 51105: 000000000003F5F5000A000F0000000000000000 |
Thread | 0x6D22 Task | 285 2015-10-07 10:10:32 ERR SYSERROR 51080: -9205 AK Catalog information not found:0 |
Running the "Structural Consistency Check" returned:
OK
Your database structure is consistent.
Pages Used: 31.546 Pages (252.368 KB)
All applications (beside those that access MetaData) work fine.
Access to the data itself works without problems.
Is there a way to repair the catalog information?
Any help is really appreciated.
Regards,
Bernhard