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

Model Repository Service Options

Model Repository Service Options

Use the Model Repository Service options with the infacmd mrs UpdateServiceOptions command.
Enter Model Repository Service options in the following format:
... -o option_name=value option_name=value ...
To enter multiple options, separate them with a space. To enter a value that contains a space or other non-alphanumeric character, enclose the value in quotation marks.
The following table describes Model Repository Service options:
true | false
Enables the Model Repository Service to store Model repository objects in cache memory. To apply changes, restart the Model Repository Service.
JVM options for the Model Repository Service cache. To configure the amount of memory allocated to cache, configure the maximum heap size. This field must include the maximum heap size, specified by the -Xmx option. The default value and minimum value for the maximum heap size is -Xmx128m.
The options you configure apply when Model Repository Service cache is enabled. To apply changes, restart the Model Repository Service. The options you configure in this field do not apply to the JVM that runs the Model Repository Service.
Required. Account for the repository database. Set up this account using the database client.
Required. Repository database password for the database user.
Optional. The schema name for a particular database.
Required for a DB2 database only. When you configure a tablespace name, the Model Repository Service creates all repository tables in the same tablespace. You cannot use spaces in the tablespace name.
For a multi-partition IBM DB2 database, the tablespace must span a single node and a single partition.
Required. Database types include:
  • db2
  • oracle
  • mssqlserver
  • sybase
JDBC Connect String
The JDBC connection string to connect to the Model repository database. Use the following syntax for each supported database:
  • IBM Db2.
    jdbc:informatica:db2://<host name>:<port number>;DatabaseName=<database name>;BatchPerformanceWorkaround=true;DynamicSections=3000
  • Microsoft SQL Server that uses the default instance.
    jdbc:informatica:sqlserver://<host name>:<port number>;DatabaseName=<database name>;SnapshotSerializable=true
  • Microsoft SQL Server that uses a named instance.
    jdbc:informatica:sqlserver://<host name>\<named instance name>;DatabaseName=<database name>;SnapshotSerializable=true
  • Azure SQL Server.
    jdbc:informatica:sqlserver://<host name>:<port number>;DatabaseName=<database name>;SnapshotSerializable=true; SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.<hostnameincertificate>;ValidateServerCertificate=true
  • Oracle.
    jdbc:informatica:oracle://<host name>:<port number>;SID=<database name>;MaxPooledStatements=20;CatalogOptions=0;BatchPerformanceWorkaround=true
    To connect to Oracle using Oracle Connection Manager, use the following connection string:
    jdbc:Informatica:oracle:TNSNamesFile=<fully qualified path to the tnsnames.ora file>;TNSServerName=<TNS server name>;
  • PostgreSQL.
    jdbc:informatica:postgresql://<host name>:<port number>;DatabaseName=
Secure JDBC Parameters
If the Model repository database is secured with the SSL protocol, you must enter the secure database parameters.
Enter the parameters as
pairs separated by semicolon characters (;). For example:
The SQL dialect for a particular database. The dialect maps java objects to database objects.
For example:
The Data Direct driver used to connect to the database.
For example:
Fully qualified Java class name
Fully qualified Java class name of the search analyzer.
By default, the Model Repository Service uses the following search analyzer for English:
You can specify the following Java class name of the search analyzer for Chinese, Japanese and Korean languages:
Or, you can create and specify a custom search analyzer.
Fully qualified Java class name
Fully qualified Java class name of the factory class if you used a factory class when you created a custom search analyzer.
If you use a custom search analyzer, enter the name of either the search analyzer class or the search analyzer factory class.
IP_address or host name
Required to configure versioning properties for the Model repository on Perforce.
The URL, IP address, or host name of the machine where the Perforce version control system runs.
Do not use this option when you configure SVN or Git as the version control system.
URL of the Subversion repository
Required to configure versioning properties for the Model repository on SVN and Git.
URL of the Subversion repository. For example:
Do not use this option when you configure Perforce as the version control system.
Required to configure versioning properties for the Model repository.
Port number that the version control system host uses to listen for packets from the Model repository.
Required to configure versioning properties for the Model repository.
User account for the version control system user.
This account must have write permissions on the version control system. After you configure the connection with this single version control system user and password, all Model repository users connect to the version control system through this account.
For the Perforce version control system, the account type must be a Standard user.
Required to configure versioning properties for the Model repository.
Password for the version control system user.
Required to configure versioning properties for the Model repository.
The supported version control system that you want to connect to. You can choose Perforce, SVN, or Git.
Required to configure versioning properties for the Model repository with Perforce.
Path to the root directory of the version control system copy of Model repository objects.
When you run the command, the Model repository connects to the version control system and generates the specified directory if the directory does not exist yet.
Only one Model Repository Service can use this directory.
For Perforce, use the syntax:
is the Perforce directory root, and
is the remainder of the path to the root directory of Model repository objects.
Do not use this option when you configure SVN or Git as the version control system.

Updated July 02, 2020