You configure Fast Clone to create a named pipe for a table prior to unloading data from the table. However, a named pipe was previously created for this table in the output directory and the load utility reads data from this pipe. When you start the cloning job, Fast Clone creates another named pipe in the output directory. The target load utility reads data from the first pipe, and Fast Clone writes data to the second pipe. Consequently, both the unload and load processes remain in a pending state.

You configure Fast Clone to create a named pipe for a table prior to unloading data from the table. You run the data unload job and then run the load job. However, Fast Clone did not create the named pipe by the time you started the load job. The load job fails because it cannot read data from the named pipe. Consequently, the unload process remains in a pending state.