Table of Contents

Search

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

CreateConnection

CreateConnection

Creates a source or target connection in the repository. The connection can be a relational, application, or an FTP connection. Relational database connections for each relational subtype require a subset of all CreateConnection options and arguments. For example, Oracle connections do not accept the -z, -d, or -t options. Use the -k option to specify attributes for application connections.
The CreateConnection command uses the following syntax:
createconnection -s <connection_subtype> -n <connection_name> [{-u <user_name> [{-p <password> | -P <password_environment_variable> [-w (use parameter in password)]}]}]| -K <connection_to_the_Kerberos_server>] [-c <connect_string> (required for Oracle, Informix, DB2, Microsoft SQL Server, ODBC, and NetezzaRelational)] [-l <code_page>] [-r <rollback_segment> (valid for Oracle connection only)] [-e <connection_environment_SQL>] [-f <transaction_environment_SQL>] [-z <packet_size> (valid for Sybase ASE and MS SQL Server connection)] [-b <database_name> (valid for Sybase ASE, Teradata and MS SQL Server connection)] [-v <server_name> (valid for Sybase ASE and MS SQL Server connection)] [-d <domain_name> (valid for MS SQL Server connection only)] [-t (enable trusted connection, valid for MS SQL Server connection only)] [-a <data_source_name> (valid for Teradata connection only)] [-x (enable advanced security, lets users give Read, Write and Execute permissions only for themselves.)] [-k <connection_attributes> (attributes have the format name=value;name=value; and so on)] [-y (Provider Type (1 for ODBC and 2 for OLEDB), valid for MS SQL Server connection only)] [-m (UseDSN, valid for MS SQL Server connection only)] [-S <odbc_subtype> (valid for ODBC connection only, default is None)]
The following table describes
pmrep
CreateConnection options and arguments:
Option
Argument
Description
-s
connection_subtype
Required. Displays the connection subtype.
A connection can be one of the following types:
  • Application
  • FTP
  • Relational
For example, for a Relational connection, connection subtypes include Oracle, Sybase, and Microsoft SQL Server. For FTP connections, the valid subtype is FTP.
-n
connection_name
Required. Name of the connection.
-u
user_name
Required for some connection types. User name used for authentication.
-p
password
Required for some connection types. Password used for authentication when you connect to the relational database. Use the -p or -P option, but not both. If you specify a user name and you do not specify -p or -P, pmrep prompts you for the password.
To specify a parameter in the password, add the $Param prefix for the -p option and ensure that you use the -w option. Do not use a dollar sign ($) anywhere else in the -p option, and enter the parameter password without spaces. For example,
-p '$Param_abc' -w
-P
password_
environment_variable
Optional. Password environment variable used for authentication when you connect to the relational database. Use the -p or -P option, but not both. If you do not use the -p or -P option,
pmrep
prompts you for the password.
-w
-
Optional. Enables you to use a parameter in the password option.
pmrep
uses the password specified with the -p or -P option as the name of the session parameter at run time.
Valid only if you use the -p or -P option.
If you do not use a parameter in the password option,
pmrep
uses the user password specified with the -p or -P option.
-K
connection_to_the_Kerberos_server
Optional. Indicates that the database that you are connecting to runs on a network that uses Kerberos authentication.
-c
connect_string
Connect string the Integration Service uses to connect to the relational database.
-l
code_page
Required for some connection types. Code page associated with the connection.
-r
rollback_segment
Optional. Valid for Oracle connections. The name of the rollback segment. A rollback segment records database transactions that allow you to undo the transaction.
-e
connection_
environment_sql
Optional. Enter SQL commands to set the database environment when you connect to the database. The Integration Service executes the connection environment SQL each time it connects to the database.
-f
transaction_
environment_sql
Optional. Enter SQL commands to set the database environment when you connect to the database. The Integration Service executes the transaction environment SQL at the beginning of each transaction.
-z
packet_size
Optional. Valid for Sybase ASE and Microsoft SQL Server connections. Optimizes the ODBC connection to Sybase ASE and Microsoft SQL Server.
-b
database_name
Optional. Name of the database. Valid for Sybase ASE and Microsoft SQL Server connections.
-v
server_name
Optional Name of the database server. Valid for Sybase ASE and Microsoft SQL Server connections.
-d
domain_name
Optional Valid for Microsoft SQL Server connections. The name of the domain. Used for Microsoft SQL Server.
-t
-
Optional. Valid for Microsoft SQL Server connections. If enabled, the Integration Service uses Windows authentication to access the Microsoft SQL Server database. The user name that starts the Integration Service must be a valid Windows user with access to the Microsoft SQL Server database.
-a
data_source_name
Optional Teradata ODBC data source name. Valid for Teradata connections.
-x
-
Enables enhanced security. Grants you read, write, and execute permissions. Public and world groups are not granted any permissions. If this option is not enabled, all groups and users are granted read, write, and execute permissions.
-k
connection_attributes
Enables user-defined connection attributes. Attributes have the format <name>=<value>;<name>=<value>.
Do not add a space before the attribute name.
-y
-
Enables the provider type value. You can specify the following provider types:
  • 1 for ODBC
  • 2 for Oledb(Deprecated)
-m
-
Enables the Use DSN attribute.
The PowerCenter Integration Service retrieves the database and server names from the DSN.
-S
odbc_subtype
Optional. Enables the ODBC subtype for an ODBC connection.
An ODBC connection can be one of the following ODBC subtypes:
  • AWS Redshift
  • Azure DW
  • Greenplum
  • Google Big Query
  • PostgreSQL
  • Snowflake
  • SAP HANA
  • None
Default is None.
For more information about connection subtypes, see Connection Subtypes.


Updated May 05, 2020