Administration Tools - ooinstallfd

Printer-friendly version
Updates the properties of a federated database and its components, after its files have been placed in a new operating environment.
ooinstallfd
[-lockserverhost lockServerHost]
[-fdnumber fdId]
[[-fdfilehost fdFileHost] -fdfilepath fdFilePath]
[[-dbdirhost dbDirHost] -dbdirpath dbDirPath]
[[-jnldirhost jnlDirHost] -jnldirpath jnlDirPath]
[-licensefile fileName]
[-purgeAps]
[-nocheck]
[-standalone]
[-notitle]
[-quiet]
[-help]
bootFilePath
Options
-lockserverhost lockServerHost
Lock-server host for the newly installed federated database. The default is the host on which you are running this tool.
-fdnumber fdId
Integer identifier of the newly installed federated database. The default is the identifier specified in the boot file. The maximum identifier is 65533.
Warning: The identifier for a pre-Release 9.0 federated database should not exceed 32767 if that federated database is to be accessed by unrebuilt pre-Release 9.0 applications.
-fdfilehost fdFileHost
Data-server host of the system-database file to be installed. If you omit this option, the default host is:
n
The current host, if -fdfilepath specifies a local path.
n
The host implied by -fdfilepath, if an NFS mount name is specified.
n
The host of the specified boot file, if -fdfilepath is also omitted.
If -fdfilepath specifies a Windows UNC share name, fdFileHost is set to the literal string oo_local_host; any value you specify is ignored.
-fdfilepath fdFilePath
Path (including the filename) to the system-database file to be installed. If the -fdfilehost option specifies a remote system, fdFilePath must be full, not relative.
If you omit both the -fdfilepath and -fdfilehost options, the default path consists of the system-database filename in the directory of the specified boot file (where the system-database filename is extracted from the boot file.)
-dbdirhost dbDirHost
Data-server host of directory containing the data files (database files and any container files) to be installed. If you omit this option, the default host is:
n
The current host, if -dbdirpath specifies a local path.
n
The host implied by -dbdirpath, if an NFS mount name is specified.
n
The host of the specified boot file, if -dbdirpath is also omitted.
If -dbdirpath specifies a Windows UNC share name, dbDirHost is set to the literal string oo_local_host; any value you specify is ignored.
-dbdirpath dbDirPath
Path to the directory containing the data files (database files and any container files) to be installed. If the -dbdirhost option specifies a remote system, dbDirPath must be full, not relative. If you omit both the -dbdirpath and -dbdirhost options, the default is the directory of the specified boot file.
-jnldirhost jnlDirHost
Host of the journal directory for the newly installed federated database. If you omit this option, the default host is:
n
The current host, if -jnldirpath specifies a local path.
n
The host implied by -jnldirpath, if an NFS mount name is specified.
n
The host of the specified boot file, if -jnldirpath is also omitted.
If -jnldirpath specifies a Windows UNC share name, jnlDirHost is set to the literal string oo_local_host; any value you specify is ignored.
-jnldirpath jnlDirPath
Path to the journal directory for the newly installed federated database. If the -jnldirhost option specifies a remote system, jnlDirPath must be full, not relative. If you omit both the -jnldirhost and -jnldirpath options, the default is the directory of the specified boot file.
-licensefile fileName
File containing the license to be placed in the newly installed federated database. You may optionally include a path to the directory containing the license file; if you specify a filename without a path, the license file must reside in the current directory.
If you omit this option, the installed federated database keeps its current license.
-purgeAps
Deletes any references to autonomous partitions from the global catalog of the federated database being installed. The partition indicated by bootFilePath becomes the newly installed (unpartitioned) federated database. Any database without an image in the partition indicated by bootFilePath is detached, but not deleted.
-nocheck
Continues the installation even if a data file cannot be found in the location specified by dbDirHost and dbDirPath. By default, ooinstallfd terminates if any expected data file cannot be found there.
-standalone
Nonconcurrent mode. Use this option if no lock server is running or to bypass a running lock server.
Warning: Corruption can occur if concurrent access to the federated database is attempted while any process is using this mode.
-notitle
Suppresses the copyright notice and program title banner. Useful when invoking the tool from another tool or product.
-quiet
Suppresses all normal program output.
-help
Prints the tool syntax and definition to the screen.
bootFilePath
Path to the boot file of the federated database to be installed. This argument is required.
Discussion
You use this tool when setting up a federated database after its files have been placed in a new operating environment, such as a new host. This tool is typically used by an end user who has received the files of a deployed federated database, by a QA engineer who has received federated-database files for testing, or by a technical-support engineer who has received federated-database files from a customer for troubleshooting.
No preparation of the federated-database files is required, other than placing its system-database file in the desired location and placing all data files (that is, all database files and any container files) in a single directory. This tool updates the properties of the federated database and its data files to reflect the new locations. You can use oochangedb or a custom administrative tool to distribute individual database files (and any related container files) to their final locations.
By default, ooinstallfd requires that all of the federated database’s data files are present in the specified directory. If some data files do not fit into that directory, you can place them in their desired locations and then run ooinstallfd with the -nocheck option. This option allows ooinstallfd to run to completion, printing a warning for each data file not found in the specified directory. You must then adjust the host and path properties for each reported data file. For a database file, you can do this by using oochangedb with the -catalogonly option; you add the -localcontainerfiles option to include any collocated container files belonging to the database. For an individual container file, you must use a custom administrative tool.
(HA) Because autonomous partitions are highly specific to a particular operating environment, this tool assumes the federated database being installed is unpartitioned. If you need to install a federated database that has partitions, you must specify the -purgeAps option; otherwise, ooinstallfd will terminate with an error. The -purgeAps option:
n
Purges the partitions from the global catalog, leaving only the partition whose boot file was specified to ooinstallfd; this partition becomes the newly installed federated database.
n
Detaches any database that did not have an image in the boot partition.
After installing, you can optionally create any desired partitions and then use ooattachdb to reattach the desired databases.

Date: 
Tuesday, October 30, 2012
Product: 
Objectivity/DB
Version: 
10.2.1
10.2
10.1.4
10.1.2
9.4.1