Category Archives: How To’s

Backup and Restore

Backing up your InfiniteGraph database is recommended to recover from catastrophic events like disk failure, and from logical or physical corruptions.   This documents goes over some basic backup and restore tasks using the oobackup and oorestore tools.

Recovering transactions

Recovery is the process of restoring a federated database to a consistent state after a transaction fails to commit. Depending on the nature of the failure, recovery is performed by the application that started the transaction or through one of several automatic mechanisms that you enable. There is also a manual recovery utility – oocleanup. […]

Updating the InfiniteGraph License

Each installation of InfiniteGraph requires a runtime license for use.  This license is controlled by a special encrypted file named “oolicense.txt” which is mailed to each registered user upon download of the product.   Each license is specific to a customer account.  Instructions for updating the product license will depended on prior experience with InfiniteGraph: […]

Deleting an Infinite Graph federation using oodeletefd

Infinite Graph use a federated database which is the highest level in the Objectivity/DB storage hierarchy. It is the unit of administrative control for a “federation” of associated databases and contains the data model, or schema, that describes all classes of objects stored in these databases. The federation is created automatically by your Infinite Graph […]

Concurrency Control: Lockserver (LS)

Infinite Graph provides concurrent multiuser access to data. To ensure that data remains consistent, database access is controlled through locks granted by a lock server. The lock server manages concurrent access to persistent objects by granting or refusing locks to requesting transactions. When a transaction requests data from a federated database, Infinite Graph locates the […]

File Servers: Advanced Multithreaded Server (AMS)

AMS enables remote applications to access to database files on the computer on which it is running.

Configuring MultipleDatabasePlacement placement strategy in the properties file

The properties file allows users to set the object placement strategy within the database.  The following shows an example entry in the properties file with regard to MultipleDatabasePlacement placement strategy:

Defining Persistence-Capable Classes for InfiniteGraph

A persistence-capable class is one whose instances can be made persistent and saved in an InfiniteGraph database. When you define a persistence-capable class, you must consider its position in the inheritance hierarchies of the application, the range of persistence behavior that the class should support publicly and privately, and which of its fields should be […]