If you cannot install Fast Clone on the Oracle source system because of system or security restrictions, you can deploy Fast Clone on a standalone system. In this topology, Fast Clone uses the conventional path unload method to unload Oracle data from the remote source database.
The following image shows a deployment topology in which Fast Clone runs on a standalone system:
Fast Clone components, such as the Fast Clone Console and Fast Clone executable, run on the standalone system. From the Fast Clone Console, you can create cloning configuration files and run data unload jobs locally on the Fast Clone system. Fast Clone uses the Oracle Call Interface (OCI) to read the Oracle source data from the remote source system. Fast Clone unloads data to output files.
After you copy the output files to the target system, you can run the load script on the target system to load data. Fast Clone uses the target database load utility to load data.
Alternatively, you can install the target database load utility on the system where you run the Fast Clone executable and then run the load script on this system. If you load data from pipes, install the target load utility on the system where you run the Fast Clone executable.