If you want to unload data to pipes, you can create the named pipes manually before running the cloning job instead of configuring Fast Clone to generate the pipes.
When you run the cloning job later, Fast Clone unloads data to the named pipes that you manually created. The target load utility reads data from the pipes and loads it to the target.
The advantage of manually creating pipes, in comparison to Fast Clone generation of the pipes, is that you do not need to monitor when pipes are generated or create a script that delays the load job until after Fast Clone creates the pipes.
Create a cloning configuration file.
Specify connection information for the source and target databases, the source tables to unload, the load script base name, and other settings, as needed.
To generate a load script for the target utility, complete the following steps:
Configure Fast Clone to generate the load script in one of the following ways:
In the Fast Clone Console, select the
Generate loader input only, do not unload data
option on the
Runtime Settings
tab >
File Locations
view.
At the command line, enter the create_load_input_only=true parameter.
In the configuration file, enter the create_load_input_only=true parameter.
Save the cloning configuration file.
Run the Fast Clone Console with the updated cloning configuration file.
Fast Clone generates a .cmd load script on Windows or a .sh load script on Linux and UNIX in the output directory.
Configure Fast Clone to unload data without overwriting the generated load script in one of the following ways:
In the Fast Clone Console, clear the
Generate loader input only, do not unload data
option and select the
Unload data only, do not generate loader input
option on the
Runtime Settings
tab >
File Locations
view.
At the command line, enter the create_load_input_only=false and unload_data_only=true parameters.
In the configuration file, enter the create_load_input_only=false and unload_data_only=true parameters.
Create a named pipe for each table that you selected for unload processing in the output directory.
For example, issue the following commands on Linux and UNIX to create a named pipe for a table:
rm /
output_directory
/
table_name
.dat
mknod /
output_directory
/
table_name
.dat p
Configure Fast Clone to use the pipes that you manually created in one of the following ways:
In the Fast Clone Console, verify that the
Create output as pipes instead of files
option on the
Runtime Settings
tab >
Miscellaneous Conditions
view is cleared.
In the configuration file, enter the create_output_pipe_instead_of_file= false parameter.
Run the data unload job.
Fast Clone writes the unloaded data to the named pipes that you manually created in the output directory.
Run the load script that was generated in Step 2.
The target load utility reads data from the named pipes and loads it to the target.