Objectivity Administrative Tools

To determine the type of a file belonging to a federated database, run oofile with the name of the file. The output indicates whether the file is a boot file, database file, and so on. By convention, the type of a particular file is indicated by its filename extension, although specific extensions are not required.

Return to top

To create a new federated database:

1. Verify that a lock server is running on the intended lock-server host for the new federated database.
2. Verify that your license file is set up.
3. Run oonewfd with the -fdfilepath option, the -lockserverhost option, and the bootFilePath. (Specify additional options to set nondefault values for the other properties.) Add the -licensefile option if your license file is in a nondefault location.

Return to top

To be able to run administrative task on a federated database that belonged to a different host, run ooinstallfd on the boot file with the appropriate flags and arguments. Run ooinstallfd -help to see flag options.

Return to top

You can use the basic procedure for installing a federated database in a new operating environment, if all the application-created data files fit into a single directory:

1. Put the system-database file and boot file in the desired location(s) in the new environment.
2. Put all application-created data files (that is, all database files and any container files) in a single directory in the new environment.
3. Verify that a lock server is running on the desired lock-server host in the new environment, and start it.
4. Run ooinstallfd with the bootFilePath. Depending on where you put the system-database file, the data files, and the lock server, you may also need to specify the -fdfilepath, -dbdirpath and -lockserverhost options. You can also include options to change the federated database’s identifier and Objectivity license.
5. If desired, distribute the data files to their final locations; see “Moving or Renaming a Database File” in the Objectivity/DB Administration book.

Return to top

To delete an entire federated database, including all its files, run oodeletefd with the bootFilePath.

Return to top

In rare circumstances, Objectivity/DB may not be able to recover a federated database automatically. In these situations, you can recover a federated database manually using the procedures described in the section, "Performing Manual Recovery" in the Objectivity Administration book. In most cases, you will be required to run the oocleanup tool. The oocleanup tool uses journal files to roll back the uncommitted changes made by incomplete transactions. If the lock server is still running, oocleanup also releases the locks held by the incomplete transactions.

Return to top

You can generate a printout of your workstation's configuration and environment using oosupportinfo tool. When you report a problem to Objectivity Customer Support, you should include the output of this command for the federated database that has the problem.

Return to top

Yes. You can use oochange to change the properties of a federated database or autonomous partition. oochange can also display the properties of a federated database. Run oochange -help to get a full listing of federated database parameter values that can be changed.

Return to top

Please see the "Backup and Restore" chapter in the Objectivity Administration book. The chapter describes how to use Objectivity/DB administration tools to back up and restore a federated database. You can run these tools either from the command line or within a shell script, and they include options that allow you to customize backup and restore tasks for special needs. Objectivity/DB also supports full user access (read and update) during backup.

Return to top