Administration Tools - ooexportdata

Printer-friendly version
Creates an XML document representing the objects in a federated database.
ooexportdata
[-id identifier | (-db dbSysName [-cont contSysName])]
[-outfile filename [-maxfilesize value][-compress]
[-exists ask | delete | quit]]
[-nws]
[-shortnames]
[-verbose]
[-standardmaps]
[-stoponerror]
[-schemalock lockVal]
[-standalone]
[-notitle]
[-quiet]
[-help]
bootFilePath
Options
-id identifier
Identifier of the data to be exported. You can specify:
n
The integer identifier of a database (for example, 78). This option also accepts the identifier specified in D-C-P-S format (for example, 78-0-0-0).
n
The object identifier in D-C-P-S format of a container or basic object (for example, 78-16-43-5).
By default, this tool exports the data in all databases within the specified federated database. If you use this option, you cannot use the -db option.
-db dbSysName
System name of a particular database to be exported. By default, this tool exports all databases within the specified federated database. If you use this option, you cannot use the -id option.
-cont contSysName
System name of a particular container to export. If contSysName contains spaces, you must enclose it in double-quote (" ") characters.
If you use this option, you must also use the -db option to specify the database that contains this container. You can omit -cont to export all containers within the specified database.
-outfile filename
Base name for all output files. You may optionally include a path to an existing directory in which to create the output files; if you do not include a path, the output files are created in the directory in which you ran the tool.
You can omit this option to send the generated XML document to stdout.
Specifying this option creates the following output files:
n
One or more files containing the XML document. The first or only such file is called filename.xml; subsequent files are numbered sequentially, starting with filename_2.xml. Multiple files are generated only to keep the file size within the limit specified by -maxfilesize.
n
A report file called filenameReport.xml summarizing the number of XML elements of each kind in the XML document.
-maxfilesize value
Maximum size of each output file, expressed as an integer number of megabytes (MB). You can omit this option to set the maximum size to 100 MB.
This option applies only when the -outfile option is also specified.
-compress
Compresses the output files using a built-in gzip utility. When you specify this option, each output file has the additional extension .gz—for example, filename.xml.gz
This option applies only when the -outfile option is also specified.
-exists
Action to take if a file already exists with the same name as a generated output file.
ask Prompts whether to overwrite the existing file. If the answer is No, the program terminates. No is the default.
delete Deletes any existing file.
quit Terminates the program if the file currently exists.
The default value is ask.
This option applies only when the -outfile option is also specified.
-nws
Suppresses all nonessential “white space” (spaces, tabs, and blank lines), producing an XML document that is more compact, but less readable.
You can omit this option to format each XML tag on a separate line, indented to indicate its level of nesting.
-shortnames
Shortens all XML tag names and attribute names, producing an XML document that is more compact, but less readable. Each shortened name is usually a single character and is not necessarily mnemonic—for example:
<l i="7/>.
You can omit this option to generate XML tags and attributes with longer, more mnemonic names—for example: <Basic value="7/>.
-verbose
Expands various XML elements to include additional detail, producing an XML document that is more readable, but less compact. You can omit this option to generate XML elements that contain only the minimum information required by ooimport.
For example, a verbose XML element for a persistent object includes the name and type number of the object’s class. In contrast, the corresponding nonverbose version includes just the type number, which is sufficient for identifying the object’s class to ooimport.
-standardmaps
Simplifies the XML representation of name maps (instances of ooMap or OoMap), producing a more compact and readable XML document. You may specify this option only if all of the name maps to be exported use the default hashing function.
Warning: Do not specify -standardmaps if the name maps to be exported use an application-defined hashing function. Doing so will produce an XML representation of the name maps that cannot be reconstructed by ooimport; such name maps will be unusable after they have been imported.
Omitting this option generates an XML representation of name maps that more closely corresponds to their comparatively complex internal structure.
When specified, this option causes name maps to be represented using just two types of XML element (<Map> and <MapElement>).
-stoponerror
Terminates immediately when an error is detected.
Omitting this option causes the tool to report errors to stderr and continue processing. Each reported error contains an XPath expression for the node being processed at the time of the error, followed by an explanatory message.
-schemalock lockVal
64-bit unsigned integer key for unlocking the schema for this export operation. You can normally omit this option because, by default, the schema is not locked. This option is required only if you have explicitly locked the schema of a federated database using Objectivity/DB Active Schema.
-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 containing the data to be exported. 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.
Discussion
This tool exports persistent objects from a federated database by representing them textually in Extensible Markup Language (XML). More specifically, this tool creates an XML document containing a hierarchy of XML elements representing the desired objects. You can specify this XML document to the ooimport tool to transfer the exported persistent objects to a destination federated database. You can also transform the XML document to a different XML Schema (for example, using a standard XSLT tool), and then import the transformed document into a third-party application.
The XML document produced by ooexportdata has no schema or catalog information, so you can import it only into a destination federated database that already has a compatible schema and any referenced databases. Use ooexportfd to export both data and schema in the same XML document.
By default, this tool exports all persistent objects in all containers in all databases. To export a subset of the persistent objects, you can:
n
Use the -db option to export a particular database.
n
Use the -cont option with the -db option to export a particular container
n
Use the -id option to export a particular database, container, or basic object
You can control the size and readability of the XML document with the -nws, -shortnames, -verbose, and -standardmaps options.
By default, the XML document is sent to stdout. You can save this document to one or more files by specifying the -outfile option. This option also generates a summary report of the XML elements present in the XML document. You control the size of the output files with the -maxfilesize and -compress options.
You can use this command as an alternative to oodump.
See also

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