validate Command

The validate keyword is used to validate stores, locations, indexes, and vaults or other items such as physical IDs, upgrades, uniqueness, and dynamic relationships. You must have System Administrator privileges to run the validate command.

This page discusses:

User Level

System Administrator

Syntax

Use this syntax to issue the validate command.

validate [level 0|1|2|3|4] [output FILENAME] [VALIDATE_ITEM {VALIDATE_ITEM}];
  • FILENAME is the name of a file to write the results of the validation to
  • VALIDATE_ITEM is:
vault VAULT_NAME {,VAULT_NAME}
 
store STORE_NAME |file FILENAME                                                |;
                 |fcsfileexist [prefix PREFIXNAME] [file FILEFILE] [indexmode] |
                 |fcsorphanfileexist [prefix PREFIXNAME]                       |
                 |fcsorphanfiledelete [prefix PREFIXNAME]                      |
 
location LOCATION_NAME |file FILENAME                                                |;
                       |fcsfileexist [prefix PREFIXNAME] [file FILEFILE] [indexmode] |
                       |fcsorphanfileexist [prefix PREFIXNAME]                       |
                       |fcsorphanfiledelete [prefix PREFIXNAME]                      |
 
index [summary]
 
index INDEX_NAME {,INDEX_NAME}
 
index vault VAULT_NAME table TABLE_NAME 
unique [tnr]
Important: The unique [tnr] clause lets you validate the uniqueness of all or a specific (if you provide the type, name, and revision) object in release V6R2011x and earlier. Do not use this clause for later releases.

You can also validate the following items:

Validate Item Description
validate physicalid count; Validates that the number of physical IDs is correct.
validate physicalid oids [output FILENAME]; Validates the physical OIDs and optionally saves the output in the specified file.
validate upgrade; Validates system tables after an upgrade.
validate lxfileunique; Performs manual cleanup of the LXFILE table after running validate upgrade. This table might have non-unique rows caused by obsolete rows. This command returns any corrupted business object with its vault name, corresponding database table, business object id and corresponding int value in lxbo column.
validate fcsfileidupgrade [show N]; Before running upgrade fcsfileidupgrade, this validate command provides the number of unpopulated rows. If you use the show N clause, the output includes that number of row identifiers of unpopulated rows.
validate dynamic-relationship; Validates that data migrated using the transition dynamic-relationship command is proper.
validate bestsofar; Validates that each family has exactly one BSF object and that it is the correct member of the pointed family.
validate adminnames [output FILENAME] ; Validates the names of all administrative types and generates a report of invalid names.

A list of forbidden characters for administrative type names has been defined, but is only used when the MX_RESTRICT_ADMINNAME variable in enovia.ini is set to TRUE, which is the default value. Installing the release and enabling this change does not update any existing administrative type names.

The output from this command lists any administrative type that uses a forbidden character in its name. The validation does not attempt to change the name to a valid equivalent. You can continue to use the existing admin types with invalid names as long as you do not try to define a new invalid name. For example, you can rename the administrative objects so that they do not contain invalid characters:

mod type <invalidName> <validName>

Validating Stores and Locations

When validating stores and locations, you can use an index file for the validation in place of a file system scan. The index file used for validation is an XML file that contains lists of directories and files and their sizes. These file indexes can be built for a store or location, and can include prefixes.

If you want to use an index file to optimize the validation, the MQL command for index file generation is: mod store <name_store> addfileindex [thread <number> <parallel_mode>];

Note:

If the index has already been generated less than 7 days before, the previous command will update the index in order not to regenerate all the data which are still valid.

For more information, see the Installation and Setup: Administrate: 3DEXPERIENCE Platform: 3DSpace: File Collaboration Server: Setting Up the FCS: FCS File Validation

The fcsfileexist clause lets you specify that the validation should use the FCS file index as defined by the value of indexmode.

indexmode can be one of these values:

  • noindex - (default) the command executes the file existence check without using a file index.
  • index - the command processes the file index if it exists and if it is valid. If the file index does not exist, processes using an index.
  • forceindex - the command allows processing only if the file exists and is valid.

The fcsorphanfileexists clause displays orphan files without deleting them.

The fcsorphanfiledelete clause displays orphan files and then deletes them.

For more information, see the File Collaboration Server Administrator's Guide.