Table of Contents

Search

  1. Preface
  2. mmcmd
  3. mmLineageMigrator
  4. mmRepoCmd
  5. mmXConPluginUtil
  6. rcfmu
  7. rmu

Metadata Manager Command Reference

Metadata Manager Command Reference

restoreRepository Options

restoreRepository Options

The command uses the following options:
[<-dn | --domainName>]
Required if the domain uses Kerberos authentication and you do not specify the --gateway option. Name of the Informatica domain.
This option uses the gateway connectivity information in the domains.infa file. If the domains.infa file is missing or contains connectivity information that is out of date, you must use the --gateway option instead.
[<-hp | --gateway>]
Required if the domain uses Kerberos authentication and you do not specify the --domainName option. Also required if the domain uses Kerberos authentication and the domains.infa file is missing or contains connectivity information that is out of date. Host names and port numbers of the gateway nodes in the domain.
If there are multiple gateway nodes, separate the gateways with a space. For example:
-hp host1:6001 host2:6002
If you run the command from a machine where the Informatica client or the Informatica utilities are installed, the host name must be fully qualified.
[<-mm | --mmServiceName>]
Required if the domain uses Kerberos authentication. Name of the Metadata Manager Service.
<<-url>>
Host name and port number of the Metadata Manager Service that runs the Metadata Manager application. Use the following format:
http(s)://<host>:<port>
.
If a secure connection is configured for the Metadata Manager web application, the host name must match the common name (CN) used to generate the keystore that you use for the HTTPS connection to the Metadata Manager Service.
<<-u | --user>>
Metadata Manager user name.
[-ep | --encryptedPassword]
Required if you specify an encrypted password. Encrypted password flag. Use with the password option to indicate that the password for the Metadata Manager user is encrypted. For example:
-ep -pw WP+qtfYwB2KYLXID9jgC+6WHbMOg/94AO8R1nOC1vd0=
[<-pw | --password>]
Required if the domain does not use Kerberos authentication. Also required if the domain uses Kerberos authentication and you do not specify the --keyTab option. Password for the Metadata Manager user. For example:
-pw Administrator
To specify an encrypted password, you must specify the --encryptedPassword option in addition to this option.
[<-n | --namespace>]
Required if the domain uses LDAP authentication or Kerberos authentication. Optional if the domain uses native authentication. Name of the security domain to which the Metadata Manager user belongs. The security domain name is case sensitive.
[<-kt | --keyTab>]
Required if the domain uses Kerberos authentication and you do not specify a password. Path and file name of the keytab file for the Metadata Manager user.
<<-f | --file>>
Name of the file from which you want to restore Metadata Manager repository database contents.
The backup file must exist in the
backup
subdirectory of the Metadata Manager file location that is set for the Metadata Manager Service.
[<-nt | --numThreads>]
Number of processing threads that the Metadata Manager Service uses when it writes data to the Metadata Manager repository database. Must be a positive integer. Default is 5.
[<-ci | --commitInt>]
Number of rows after which the Metadata Manager Service commits the data into the Metadata Manager repository. The restoreRepository command uses a batch commit each time it writes this number of rows. Using a batch commit reduces the size of the undo tablespace required if the command fails and mmRepoCmd rolls back the restore operation.
If set to 0, the command commits all rows at the end of the restore operation. Default is 10,000.
[<-sl | --skipLineage>]
When the value is set to Y, the command skips lineage restore during Metadata Manager repository restore. Default value is N.
The restoreRepository command does not restore lineage backup files when the following conditions are true:
  1. You chose the skipLineage value as Y during Metadata Manager repository backup.
  2. You chose skipLineage value as N during Metadata Manager repository restore.

0 COMMENTS

We’d like to hear from you!