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



Adds objects to a deployment group. Use AddToDeploymentGroup to add source, target, transformation, mapping, session, worklet, workflow, scheduler, session configuration, and task objects.
You cannot add checked out objects to a deployment group. You can specify objects using command options or you can use a persistent input file. If you use a persistent input file, you can enter the deployment group name option.
Use AddToDeploymentGroup to add reusable input objects. If you want to add non-reusable input objects, you must use a persistent input file that contains encoded object IDs.
If AddToDeploymentGroup runs successfully, it either sends back no status information, or it returns a list of objects that are already in the deployment group. If the command fails, it displays the reason for failure.
The AddToDeploymentGroup command uses the following syntax:
addtodeploymentgroup -p <deployment_group_name> {{-n <object_name>   -o <object_type>   -t <object_subtype>]   [-v <version_number>]   [-f <folder_name>]} |   [-i <persistent_input_file>]} [-d <dependency_types (all, "non-reusable", or none)>] [-s dbd_separator]
The following table describes
AddToDeploymentGroup options and arguments:
Required. Name of the deployment group to add objects to.
Required when you add a specific object. Name of the object you are adding to the deployment group. You cannot enter the name of a checked out object. You cannot use the -n option if you use the -i option.
Required when adding a specific object. Type of object you are adding. You can specify source, target, transformation, mapping, session, worklet, workflow, scheduler, session configuration, task, cube, and dimension.
Required when using valid subtypes. Type of task or transformation you are adding. For more information about valid subtypes, see Listing Object Types.
Optional. Version of the object to add. Default is the latest version of the object. The command fails if you specify a version number for a non-versioned repository.
Required when you enter an object name. Folder that contains the object you are adding.
A text file generated from ExecuteQuery, Validate, or ListObjectDependencies that contains a list of object records with encoded IDs. If you use this parameter,
does not allow the -n, -o, and -f options.
Optional. Dependent objects to add to the deployment group with the object. Enter one of the following:
  • all.
    adds the objects and all dependent objects, reusable and non-reusable, to the deployment group.
  • “non-reusable”.
    adds the objects and the corresponding non-reusable dependent objects to the deployment group.
  • none.
    does not add dependent objects to the deployment group.
If you omit this parameter,
adds the objects and all dependent objects to the deployment group.
Use double quotes around arguments that contain spaces or non-alphanumeric characters.
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