Skip to Content

Sybase support

Feb 17, 2017 at 09:47 PM


avatar image
Former Member

I am using sybase 15.5 developer edition.

getting below error even after executing stored procedures using Jconnect.

2017-01-23 23:50:59,630 ERROR org.hibernate.util.JDBCExceptionReporter - JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
2017-01-23 23:50:59,644 FATAL Server - Could not access configuration storage
com.mosol.configstore.ConfigRuntimeException: Cannot save new atom
at com.mosol.configstore.impl.hibernate.ConfigImpl$ConfigTransactionImpl.addAtomToSave(
at com.mosol.configstore.impl.hibernate.AtomCache.getAtom(
at com.mosol.configstore.impl.hibernate.ConfigImpl.loadImpl(
at com.mosol.configstore.impl.hibernate.ConfigImpl.loadEntries(
at com.mosol.configstore.impl.wrap.ConfigImpl.loadEntries(
at com.mosol.Formula.Server.ServerImpl.getElementPersistence(
Caused by: org.hibernate.exception.GenericJDBCException: could not insert: [com.mosol.configstore.impl.hibernate.Atom]

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Mark A Parsons Feb 17, 2017 at 10:19 PM

You'll likely need to get the DBA to load a set of jConnect-related tables and procs into the database in question.

A SQL script containing these objects should be under the ASE dataserver's installation:



- X_Y is the desired jConnect version (eg, 6_0, 7_0)

- A.B.C is a version number that is equal to or less than your ASE version (eg, 15.0 for ASE 15.5)

If there's more than one jConnect* directory under $SYBASE, pick the one most appropriate for the client's jconnect version. [To be honest, I load the latest/greatest version and have found that's usually sufficient, ymmv.]

For ASE 15.5, and assuming the latest/greatest jConnect directory is jConnect-7, the DBA would want to load the $SYBASE/jConnect-7_0/sp/sql_server15.0.sql script into the database the application is attempting to use. [Yes, if there is more than one database in question then load the script into each database.]

Once the tables/procs have been loaded run the application again to see if this resolves the issue.

10 |10000 characters needed characters left characters exceeded