Table of Contents


  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. infacmd dps Command Reference
  16. infacmd edl Command Reference
  17. Infacmd es Command Reference
  18. infacmd ihs Command Reference
  19. infacmd ipc Command Reference
  20. infacmd isp Command Reference
  21. infacmd ldm Command Reference
  22. infacmd mas Command Reference
  23. infacmd mi Command Reference
  24. infacmd mrs Command Reference
  25. infacmd ms Command Reference
  26. infacmd oie Command Reference
  27. infacmd ps Command Reference
  28. infacmd pwx Command Reference
  29. infacmd roh Command Reference
  30. infacmd rms Command Reference
  31. infacmd rtm Command Reference
  32. infacmd sch Command Reference
  33. infacmd search Command Reference
  34. infacmd sql Command Reference
  35. infacmd tdm Command Reference
  36. infacmd tools Command Reference
  37. infacmd wfs Command Reference
  38. infacmd ws Command Reference
  39. infacmd xrf Command Reference
  40. infacmd Control Files
  41. infasetup Command Reference
  42. pmcmd Command Reference
  43. pmrep Command Reference
  44. Working with pmrep Files



Validates objects. You can output the results to a persistent output file or standard output.
It also displays a validation summary to stdout. The summary includes the number of valid objects, invalid objects, and skipped objects. The persistent output file contains standard information, encoded IDs, and a CRC check. You can save and check in the objects that change from invalid to valid.
You can validate the following types of objects:
  • Mappings
  • Mapplets
  • Sessions
  • Workflows
  • Worklet objects
If you use another type of object in the input parameter,
returns an error. If you use the wrong type of object in a persistent input file,
reports an error and skips the object.
Validate command does not validate shortcuts.
When you run Validate, you can output information about object status:
  • valid.
    Objects successfully validated.
  • saved.
    Objects saved after validation.
  • skipped.
    Shortcuts and object types that do not require validation.
  • save_failed.
    Objects that did not save because of lock conflicts or they were checked out by another user.
  • invalid_before.
    Objects invalid before the validation check.
  • invalid_after.
    Objects invalid after the validation check.
It is not possible to save a non-reusable object unless you save the reusable parent of the object. When you use the -s option, the command does not save validated non-reusable objects unless, as part of the same command, you list reusable objects that are the parents of the non-reusable objects.
The Validate command uses the following syntax:
validate {{-n <object_name> -o <object_type (mapplet, mapping, session, worklet, workflow)> [-v <version_number>] [-f <folder_name>]} |   -i <persistent_input_file>} [-s (save upon valid) [-k (check in upon valid) [-m <check_in_comments>]]] [-p <output_option_types (valid, saved, skipped, save_failed, invalid_before, invalid_after, or all)>] [-u <persistent_output_file_name> [-a (append)]] [-c <column_separator>] [-r <end-of-record_separator>] [-l <end-of-listing_indicator>] [-b (verbose)] [-y (print database type)]
The following table describes
Validate options and arguments:
Required. Name of the object to validate. Do not use this option if you use the -i argument.
When you validate a non-reusable session, include the workflow name. Enter the workflow name and the session name in the following format:
<workflow name>.<session instance name>
When you validate a non-reusable session in a non-reusable worklet, enter the workflow name, worklet name, and session name in the following format:
<workflow name>.<worklet name>.<session instance name>
Required if you are not using a persistent input file. Type of object to validate. You can specify mapplet, mapping, session, worklet, and workflow.
Optional. Version of the object to validate. Default is the latest or checked out version of the object.
Required. Name of the folder containing the object.
Optional. Text file from ExecuteQuery, Validate, or ListObjectDependencies commands. Contains a list of object records. You cannot use this file if you specify objects using the -n, -o, or -f arguments.
Optional. Save objects that change from invalid to valid to the repository.
Required if you use -s. Check in saved objects.
Required if you use the -k option, and the current repository requires checkin comments. Add comments when you check in an object.
Required if you use the -u argument. Type of object you want to output to the persistent output file or stdout after validation. You can specify valid, saved, skipped, save_failed, invalid_before, or invalid_after. To enter one or more options, separate them by commas.
Required if you use the - p argument. Name of an output text file. If you enter a file name, the query writes the results to a file.
Optional. Append the results to the persistent output file instead of overwriting it.
Optional. Character or set of characters used to separate object metadata columns.
Use a character or set of characters that is not used in repository object names. If any repository object name contains spaces, you might want to avoid using a space as a column separator.
If you omit this option,
uses a single space.
Optional. Character or set of characters used to specify the end of the object metadata.
Use a character or set of characters that is not used in repository object names.
Default is newline /n.
Optional. Character or set of characters used to specify the end of the object list. Enter a character or set of characters that is not used in repository object names.
If you omit this option,
uses a period.
Optional. Verbose. Displays more than the minimum information about the objects. If you omit this option,
displays a shorter format including the object type, the word reusable or non-reusable, the object name and path. Verbose format includes the version number and folder name.
The short format for global objects such as label, query, deployment group, and connection, includes the object type and object name. Verbose format includes the creator name and creation time.
Optional. Displays the database type of sources and targets.


We’d like to hear from you!