ObjectDB ObjectDB

Internal Website Search

51-60 of 133 resultsRefresh

locks on pure query activities

" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout ... " /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false ... " max-threads="48" /> <index-update enabled="true" priority="40" /> <query-cache results

First query takes 4+ minutes to complete

="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr ... enabled="true" sync="false" path="$objectdb/" max="512mb" /> <recording enabled="false" sync ... ="256mb" max-threads="10" /> <query-cache results="64mb" programs="50" /> <extensions drop="temp

Replication Issue

" user="true" password="true" />                 <log path="$objectdb/log/" max="8mb" stdout="false ... " sync="false" path="." max="128mb" />                 <recording enabled="false" sync="false" path ... cache="64mb" max-threads="10" />                 <query-cache results="32mb" programs="500

Out of memory

/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive ... " /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false ... " /> <processing cache="64mb" max-threads="64" /> <query-cache results="256mb

Best practice: Database update/migration of embedded databases in products

{ String firstName; String familyName; String address; } DB1: [firstName=”Max”; familyName=”Mustermann”; address=”26135 Oldenburg”] V1.1: EntityPerson{ String name; String address; } DB2: [name=”Max ... : [name=”Max Mustermann”; zip=”26135”; city=”Oldenburg”] How can we load the Database DB1

Start ObjectDB inside java code.

activate those line of code now? i mean where do i put the <server> <connection port="6136" max="100 ... try something like : String [] test = new String[2] ; test[0] = "connection port=6136 max=100" ; test ... command or argument: connection port=6136 max=100 (error 531) Am not sure this is the right place

ODB IndexActivation NullPointerException

' * Batch ended at MAX * Batch ended at '2LG' * Batch ended at '2oq' * Batch ended at '2LG' * Batch ended at '2LG' * Batch ended at '2oq' * Batch ended at MAX If MAX is the last, then it looks like

Doctor - high memory usage

have at least 2GB RAM, I don't think that running the Doctor with 512MB max heap size should be a problem ... max heap size (-Xmx512m) it works well with the default configuration - it took ~10 seconds to check the database and additional 20 seconds to rebuild a new database. With 256MB max heap size I got

Use temporary files to enable very large transactions

/log/" max="8mb" stdout="true" stderr="false" />                 <log-archive path="$objectdb/log ... " />                 <recovery enabled="true" sync="false" path="." max="128mb" />                 <recording enabled ... " />                 <processing cache="64mb" max-threads="10" />                 <query-cache results="32mb

Best practise loading big data

" max-threads="10" /> Query Cache: <query-cache results="32mb" programs="500" /> Entity Chaches ... ="256mb" max-threads="10" /> > Query Cache: <query-cache results="32mb" programs="500 ... response. I have tried out with the proposed setting of <processing cache="16mb" max-threads="10

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