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



Imports objects from an .xml file. This command requires a control file to specify the objects to import and how to resolve conflicts. The control file is an .xml file defined by the impcntl.dtd file.
The ObjectImport command uses the following syntax:
objectimport -i <input_xml_file_name> -c <control_file_name> [-l <log_file_name>] [-p (retain persistent value)]
The following table describes
ObjectImport options and arguments:
Required. Name of the .xml file to import.
Required. Name of the control file that defines import options.
Optional. Log file that records each export step. If you omit this option, status messages output to the window.
Optional. Retains persistent values for mapping variables.
The ObjectImport command does not create a folder if the folder name you enter does not exist in the repository.
You can generate audit logs when you import an .xml file into the PowerCenter repository with the pmrep ObjectImport command. When you import one or more repository objects, you can generate audit logs. To include security audit trails in the user activity log events, enable the SecurityAuditTrail property for the PowerCenter Repository Service in the Administrator tool before you import an .xml file. The user activity logs captures all the audit messages.
The audit logs contain the following information about the .xml file imported:
  • Host name and IP address of the client machine from which the .xml file was imported
  • Full local path of the .xml import file
  • The file name
  • The file size in bytes
  • Logged in user name
  • Number of objects imported
  • Time stamp of the import operation

Updated April 22, 2019