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 dis Queries
  16. infacmd dp Command Reference
  17. infacmd idp Command Reference
  18. infacmd edp Command Reference
  19. Infacmd es Command Reference
  20. infacmd ics Command Reference
  21. infacmd ipc Command Reference
  22. infacmd isp Command Reference
  23. infacmd ldm Command Reference
  24. infacmd mas Command Reference
  25. infacmd mi Command Reference
  26. infacmd mrs Command Reference
  27. infacmd ms Command Reference
  28. infacmd oie Command Reference
  29. infacmd ps Command Reference
  30. infacmd pwx Command Reference
  31. infacmd roh Command Reference
  32. infacmd rms Command Reference
  33. infacmd rtm Command Reference
  34. infacmd sch Command Reference
  35. infacmd search Command Reference
  36. infacmd sql Command Reference
  37. infacmd tdm Command Reference
  38. infacmd tools Command Reference
  39. infacmd wfs Command Reference
  40. infacmd ws Command Reference
  41. infacmd xrf Command Reference
  42. infacmd Control Files
  43. infasetup Command Reference
  44. pmcmd Command Reference
  45. pmrep Command Reference
  46. Working with filemanager
  47. Working with pmrep Files



Configures custom database clients and the Informatica domain to use the specified custom Kerberos libraries instead of the default libraries that Informatica uses.
To use custom Kerberos libraries, do the following:
  1. Copy the custom Kerberos libraries you want to use to each node, or to a location that is accessible to all nodes in the Informatica domain.
  2. Shut down the domain.
  3. Run the infasetup updateMitKerberosLinkage command on each node in the domain.
  4. Start the domain after running the command on all nodes in the domain.
The updateMitKerberosLinkage command uses the following syntax:
updateMitKerberosLinkage <-useKeberos|-krb> true|false [<-mitKerberosDirectory|-mkd> kerberos_library_directory]
The following table describes the infasetup updateMitKerberosLinkage options and arguments:
Required. Boolean value. Set this value to true if the Informatica domain uses Kerberos authentication. If true, Informatica processes make Kerberos calls with the default Kerberos libraries or the libraries in the directory specified with the -mkd option.
Set this value to false if the Informatica domain does not use Kerberos. If false, Informatica does not load Kerberos libraries. Third-party clients, such as database clients, perform Kerberos calls with the libraries specified in the directory specified with the -mkd option.
Optional. The directory that contains the custom MIT Kerberos libraries. The directory must contain the library files. You cannot use symbolic links.
If the -krb option is true, ensure that the custom Kerberos libraries that you want to use are the same version number as the Kerberos libraries that Informatica uses by default.
If there are multiple versions of the same library, all versions must be the same size and have the same checksum. For instance, if the directory contains two versions of libkrb5, such as and, then both libraries should have the same file size and checksum value.
If the specified directory is empty, the command removes all custom Kerberos libraries from the Informatica domain.


We’d like to hear from you!