Administration Tools - ootidy

Printer-friendly version
Consolidates a fragmented database or federated database.
[-db dbSysName | -id dbId]
[[-tmpdirhost hostName] -tmpdirpath dirPath]
-db dbSysName
System name of the database to be tidied. By default, this tool tidies all databases within the specified federated database.
-id dbId
Integer identifier of the database to be tidied (for example, 78). This option also accepts the identifier specified in D-C-P-S format (for example, 78-0-0-0).
By default, ootidy tidies all databases within the specified federated database.
-tmpdirhost hostName
Host on which to create temporary files. If you omit this option, the default host is:
The host on which you are running this tool, if -tmpdirpath specifies a local path.
The host implied by -tmpdirpath, if an NFS mount name is specified.
If -tmpdirpath specifies a Windows UNC share name, hostName is set to the literal string oo_local_host; any value you specify is ignored.
-tmpdirpath dirPath
Path to the directory on the designated host in which to create temporary files. If the -tmpdirhost option specifies a remote system, dirPath must be full, not relative. If you omit both the -tmpdirhost and -tmpdirpath options, temporary files are created in the directory of each database file being tidied.
Nonconcurrent mode. Use this option only if the lock server for the specified federated database or autonomous partition is stopped. If the lock server is running, the tool reports an error and terminates.
Suppresses the copyright notice and program title banner. Useful when invoking the tool from another tool or product.
Suppresses all normal program output.
Prints the tool syntax and definition to the screen.
Path to the boot file of the federated database to be tidied. 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.
To hold temporary data files created during its execution, ootidy requires free disk space equal to the size of the federated database or database you are tidying.
Warning: To prevent potential database corruption, make sure that no other processes access a database or federated database being tidied. Do not run ootidy and oobackup concurrently, because ootidy may delete objects that oobackup references.
Warning: Do not run ootidy if you suspect that the federated database has been corrupted. It can make the problem significantly worse.

Tuesday, October 30, 2012