ObjectDB ObjectDB

Internal Website Search

151-160 of 200 resultsRefresh

Query debugging configuration from class

for. I would like to log (in the console or in a separate log file) what it's actually executing

Database corrupted after schema change

is also missing in the list. Neither ObjectDB log, nor the application log wrote any errors, so it looks

Class loading problem with private packages in OSGi environment

a stack trace of the error (from the log file) or provide a sample database file that can be used to reproduce the exception? support Support Hello, following the stack trace in the log

ObjectDB 2.x is working without any activation code

put activation code for a machine in conf file the logs were not opening but recentely we have faced a strange ... to open the logs without any issue , what could be the reason for this ? Also how to find

Object Relations Error after Schema Change

of your application. support Support Hi, we only use one entity class version. Attached second log file. Problem occurs when we create a new entry in the class we have changed the relation. Quote from the log “08

Query execution causes an unexpected internal exception (Error 990)

an unexpected index state during a query update. You should see some log lines starting at "Attempt to remove a non existing index entry" in the ObjectDB server log file. Could you please post


. There is log from ObjectDB: java.lang.ArrayIndexOutOfBoundsException: 49 at com.objectdb.o.UTY.aI(UTY ... problems in more logs: java.lang.ArrayIndexOutOfBoundsException: -102141 at com.objectdb.o.PGC.w

Indexes broken after schema update

per the previous issue I logged, I haven't added or removed any entities but I try and query ... ) and the below errors in the logs. I can query the object fine by non-indexed fields and by the @Id. [2012-08-19

Corrupt database page

the database file, is it possible that the db log file remains in the file system after closing the database and the db doctor is able to repair the corrupted page by the db log so that the repaired database

Service terminated silently (crashed?)...is there any way to cause a crash dump?

After running without issue, uninterrupted for seven months, our instance stopped silently. The contents of the log are as follows: Object DB log: ObjectDB Server started on port 6138. ObjectDB Server stopped. ObjectDB Server started on port 6138. ObjectDB Server stopped. ObjectDB Server started

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support