Parameter Name

Description

Value

Default

Unique to ArchiveManager

–import <filename>

Enter the –import switch, followed by the file, or files, containing the object data to import. Files are processed in the order they are listed. This parameter is required to import.

String

No

–allow_null

Allows a null relation to be a part of an object's unique key.

Boolean

No

Yes

–bad_fields

When a mismatch occurs and the archive contents contain fields or relations that are not present on the target database of an import, ArchiveManager issues an error and terminates the data load. To prevent ArchiveManager from terminating the import, use the –bad_fields parameter to tell ArchiveManager to issue warnings instead of errors.

Boolean

No

Yes

–bad_schema

Allows ArchiveManager to import data that has a schema revision value that disagrees with the schema revision of the database.

Boolean

No

Yes

–eindex

Generates new DART indexes for the import file and does not import the data into the database.

Boolean

No

Yes

–esplit <split string>

Uses the specified string as the split string in DART index files.

String

!!#*$

Yes

–insert_only

Use -insert_only when only using the import command to insert new rows into a database without updating or deleting data. This parameter notifies ArchiveManager that all objects in the input stream are new, so that it will not look for updates on existing objects, which will reduce the import time. This parameter is not to be confused with the insert_only keyword added to Dataex in Clarify 12.0. For more time-saving tactics, see the –no_recovery entry.

Boolean

No

Yes

–lite

Because ArchiveManager stores much of its information in memory, large imports require considerable memory swapping, which can slow down the import if using a machine with less than 1 gig of memory. To limit the memory swapping, use the –lite parameter, which limits the amount of information saved in memory for each object.

Recommendation: Only use this parameter if there is not enough system memory and swap file space to run ArchiveManager efficiently.

Boolean

No

Yes

–mto

Allows OTOP (one to one primary) relations that have been treated as MTO (many to one) by Clarify to also be treated as MTO relations in ArchiveManager. Use this parameter to allow exported data with this error to be reimported.

String

Yes

–no_recovery

When importing a large amount of data, the recovery files will also be large and could potentially take a long time to write out. To save time, you can use the –no_recovery parameter to prevent ArchiveManager from creating recovery files. If using this parameter, we recommend backing up your database as a safety measure. If the import fails, you can restore to the saved database and reload the data from scratch. For more time-saving tactics, see the –insert_only entry.

Boolean

No

Yes

–no_write

Only the verification parameters are run. No database data is inserted, updated, or deleted.

Boolean

No

Yes

–object <name>

The –purge parameter can generate archive files that contain thousands of object groups. To selectively reimport one or more of these groups and the related objects, use the –object parameter. The <name> value is the top-level object in the group. This parameter can be specified more than once.

String

All objects imported

Yes

–objid

An object's id is normally ignored during an import. With this parameter, object ids will be stored and used for unique keys.

Boolean

No

Yes

–pick_one

When testing references, if more than one object matching the unique list exists in the database, this parameter will select any one of them to match. These are normally reported as errors.

Boolean

No

Yes

–recovery

If an import error occurs and the import fails, ArchiveManager can recover and restart the import from where it left off. To recover, add –recovery to the original parameters and rerun ArchiveManager.

Boolean

No

Yes

–rfile

<filename>

When an import fails and the –recovery parameter is used to restart the process, by default, the recovery files are named recovery.1 and recovery.2. To define a different prefix filename, use the –rfile parameter with the -recovery parameter.

String

recovery

Yes

–uniqueness

A common import mistake is to have more than one archive entry in the import file refer to a single database object. When this occurs, the second archive entry overwrites the first. To check for overlap, use the –uniqueness parameter. If any problems are found, ArchiveManager will stop the data load.

Note: Uniqueness constraints are not checked by default, because this process can be time-consuming.

Boolean

No

Yes

–unused

Pulls table objids from the unused objid table. In later versions of Clarify, objids can be fetched, and if unused, returned to the system via the unused objid table. This parameter allows systems that are tight on objids to fetch objids first using this table.

Recommendation: Due to possible efficiency and locking problems, we recommend not using the unused objid table.

Boolean

No

Yes

See Also

Import Command Syntax

Import Command Syntax Examples

Next

Import Command Syntax Examples