Deletes unreferenced objects from garbage-collectible containers in a federated database. Garbage-collectible containers can be created and used only by Objectivity for Java or Objectivity/Smalltalk applications.
Displays the object identifiers of containers and objects that would be deleted, but does not delete them.
Displays data about the number of roots, visited containers, visited objects, deleted containers, and deleted objects.
Suppresses the copyright notice and program title banner. Useful when invoking the tool from another tool or product.
Path to the boot file of the federated database containing the containers to be garbage-collected. You can omit this argument if you set the OO_FD_BOOT environment variable to the correct path. (HA) You can specify the boot file of any autonomous partition.
This tool can delete unreferenced objects from a garbage-collectible container only if it can get an update lock on that container. When a garbage-collectible container is unnamed and contains only unreferenced persistent objects, this tool deletes the container. A persistent object is considered referenced only if it can be reached from an Objectivity for Java or Objectivity/Smalltalk named root.
Garbage collection does not apply to non-garbage-collectible containers, which exist primarily for interoperating with applications written in a non-garbage-collected language, such as C++. All objects in a non-garbage-collectible container are assumed to be valid and remain in the database until explicitly deleted by an application.
Substantial virtual memory can be required for oogc’s temporary data, depending on how much garbage needs to be collected. Processing a large container with references to many other large containers also increases the memory requirement.
Warning: Do not run oogc and oobackup concurrently, because oogc may delete objects that oobackup references.
Tuesday, October 30, 2012