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 bg Command Reference
  10. infacmd cms Command Reference
  11. infacmd dis Command Reference
  12. Infacmd es Command Reference
  13. infacmd ipc Command Reference
  14. infacmd isp Command Reference
  15. infacmd ldm Command Reference
  16. infacmd mrs Command Reference
  17. infacmd ms Command Reference
  18. infacmd oie Command Reference
  19. infacmd ps Command Reference
  20. infacmd pwx Command Reference
  21. infacmd rms Command Reference
  22. infacmd rtm Command Reference
  23. infacmd sch Command Reference
  24. infacmd search Command Reference
  25. infacmd sql Command Reference
  26. infacmd tdm Command Reference
  27. infacmd wfs Command Reference
  28. infacmd ws Command Reference
  29. infacmd xrf Command Reference
  30. infacmd Control Files
  31. infasetup Command Reference
  32. pmcmd Command Reference
  33. pmrep Command Reference
  34. Working with pmrep Files



Exports objects to an XML file defined by the powrmart.dtd file. You export an object by name. If you enter an object, you must enter the name of the folder that contains it. If you do not enter a version number, you export the latest version of the object.
Use a persistent input file to specify different objects to export at one time. You can create this file by using the ExecuteQuery, Validate, or ListObjectDependencies
commands. If you use the persistent input file, do not use the other parameters to specify objects.
If you export a mapping, by default PowerCenter exports the mapping and its instances. If you want to include dependent objects, you must add the appropriate
options. You can optionally include reusable and non-reusable dependent objects, objects referenced by shortcuts, and related objects in a primary key-foreign key relationship.
To export mapping dependencies, you must use the -b and -r options.
The ObjectExport command uses the following syntax:
objectexport {{-n <object_name>  -o <object_type>  [-t <object_subtype>]  [-v <version_number>]  [-f <folder_name>]} |  -i <persistent_input_file>} [-m (export pk-fk dependency)] [-s (export objects referred by shortcut)] [-b (export non-reusable dependents)] [-r (export reusable dependents)] -u <xml_output_file_name> [-l <log_file_name>] [-e dbd_separator]
The following table describes
ObjectExport options and arguments:
Required if you do not use the -i option. Name of a specific object to export. If you do not enter this option,
exports all the latest or checked out objects in the folder. Use the -n option or the -i option, but not both.
Object type of the object name. You can specify source, target, transformation, mapping, mapplet, session, worklet, workflow, scheduler, session config, or task. If you use this option, you cannot use the -i option.
Type of transformation or task. This argument is ignored for other object types. For more information about valid subtypes, see Listing Object Types.
Optional. Exports the version of the object that you enter.
Name of the folder containing the object to export. If you do not enter an object name,
exports all the objects in this folder. If you use this option, you cannot use the -i option.
Required if you do not use the -n option. Text file list of objects generated from ExecuteQuery, Validate, or ListObjectDependencies. It contains object records with encoded IDs. If you use this parameter, you cannot use the -n, -o, or -f options.
Required to export dependent objects. Exports primary key table definitions when you export sources or targets with foreign keys.
Required to export dependent objects. Exports the original object referenced by the shortcut.
Required to export dependent objects. Exports non-reusable objects used by the object.
Required to export dependent objects. Exports reusable objects used by the object.
Required. Name of the XML file to contain the object information.
Optional. Log file that records each export step. If you omit this option, status messages output to the window.
Optional. If an ODBC source has a period (.) in the name, define a different separator character when you define the source object. For example, instead of database_name.source_name, define the source object as database_name\source_name, and define the dbd_separator as backslash (\).

Updated April 22, 2019