Table of Contents

Search

  1. Preface
  2. Fast Clone Overview
  3. Configuring and Using the Fast Clone Server
  4. Creating Cloning Configuration Files in the Fast Clone Console
  5. Unloading Data from the Source Database
  6. Loading Data to a Target
  7. Remote Configuration Management
  8. Fast Clone Command Line Interface
  9. Troubleshooting
  10. Fast Clone Configuration File Parameters
  11. Glossary

User Guide

User Guide

Configuration File Overview

Configuration File Overview

In the Fast Clone Console, you can create and manage cloning configuration files. Fast Clone uses the configuration files to unload source data, generate load scripts, enable integration with Informatica Data Replication, and configure reporting and SNMP traps for monitoring.
A configuration file is a text file. Informatica recommends that you use the Fast Clone Console to create and manage configuration files to reduce the risk of error. Alternatively, you can create and edit configuration files in a text editor.
By default, the Fast Clone Console saves a configuration file as unload.ini to the
FastClone_installation
directory in a local file system. You can optionally save the configuration file under another name.
In the Fast Clone Console, you can open a configuration file to edit unload settings or use it to run a data unload job. If you open the configuration file to run data unload job, the Fast Clone Console overrides the unload.ini file in the
FastClone_installation
directory if it already exists.
If you use the Fast Clone Server to run data unload jobs on a remote system, you can enable remote configuration management in the Fast Clone Console. You can then open and save the configuration files on the remote system from the Fast Clone Console using an FTP server.
A configuration file is not required for data cloning if you run Fast Clone from the command line. However, you must then manually specify all of the parameters at the command line for the Fast Clone executable.

0 COMMENTS

We’d like to hear from you!