importdb

Purpose

Imports the given database schema.

Location

<InstallationDirectory>\InForm\Bin\DBOra folder.

Usage

importdb [connection-string] [dump-file-directory-path] [dump-file-name] [from-userid] /Prompt [log options] [/AdditionalParametersFile:optionsfile] [/NotTrial]

importdb [connection-string] [dump-file-directory-path] [dump-file-name] [from-userid] /AccountParams:[paramfile] [log options] [/AdditionalParametersFile:options-file] [/NotTrial]

Where:

Parameter	Description
connection-string	Database TNS Instance Name.
dump-file-directory-path	Physical path on database server where the dump is located. Note: The path must conform to the proper OS path format, and the path is expected to be case-sensitive.
dump-file-name	Filename of the dump file to import. Note: The name must conform to the proper OS format for the database server, and the name is expected to be case-sensitive.
from-userid	Original schema owner User ID when exported.
paramfile	Path to text file containing the list of parameters.
log-options	Optional parameters for specifying the log file name and/or location. The log file defaults to being named ImportDB.log. The log file path defaults to the current working directory. Options: /LogFile:[filespec] filespec = fully qualified name and path for created log file. If a relative path is given, it is based from the current working folder. Overrides the logfile-path to be the resolved path to the given filespec. Overrides the logfile-name to be the resolved name of the given filespec. Do not specify this if either of the other logging options are specified. /LogFilePath:[pathspec] pathspec = fully qualified path to create the log file in. If a relative path is given, it is based from the current working folder. Overrides the logfile-path to be the resolved path to the given pathspec. Does not change logfile-name. /LogFileName:[filename] filespec = Filename for the log file. Overrides the logfile-name for the log file. Does not change logfile-path.
options-file	Path to a text file containing list of additional import parameters. These options are added to the default import parameters, allowing customization of the import operation. Operations such as remap_schema and remap_tablespace may be added to the file, each on a separate line, with no intervening spaces. For example: remap_schema=oldschemaownerid:newschemaownerid remap_tablespace=oldtablespacename:INFORM See the impdp documentation for details on import options.
/NotTrial	Prevents pre-import tablespace analysis of the schema prior to importing. This behavior is only supported for Trial Schemas, and should be prevented through this parameter for any other type of schema being imported.

Command line prompts

If using prompting, you are prompted for the following parameters:

To User Schema Owner User ID—Database trial/schema owner user ID for the schema to which the dump should be imported.
To User Schema Owner User Password—Password for the schema owner user. The password must conform to local restrictions.
Database Adminstrator User Name—Name of the Database Administrator User (for example, pfdbadmin).
Database Administrator User Password—Password for the Database Administrator User.

Parameter file contents

When using a parameter file, the path to a text file is given. The format of the parameter file is parameter=value, with each value on a separate line, and no spaces between the parameter name, =, and value.

The parameter file must contain the following parameters:

Trial_user—Trial/Schema Owner User ID for the schema to which the dump should be imported.
Trial_user_pass—Trial/Schema Owner User Password. Password must conform to local restrictions.
Pfdbadmin_user—Name of the InForm Database Administrator User (for example, pfdbadmin).
Pfdbadmin_user_pass—Password for the InForm Database Administrator User.

The parameter file may contain the following parameters:

AdditionalParametersFile—options-file—Identical to specifying on the command line. See command line parameter explanation for details. Only one additional parameter file may be specified, either on the command line or in the parameter file, not both.

Example

importdb trial1 /backups backup.dmp pfst63uid /prompt
importdb trial1 /backups backup.dmp pfst631uid /accountparams:myparamfile.txt
importdb trial1 /backups backup.dmp pfst6211 /prompt /logfilepath:c:\exportlogs
importdb trial1 /backups other.dmp oldotherschemuid /prompt /nottrial