Data Pump - Oracle 10g/11g Data and Database Management Utilities - page 13

The options used to generate an export dump in parallel with multiplexed dump
files are:
USERID=sh/sh
DUMPFILE=shParallelExp01%u,shParallelExp02%u
DIRECTORY=default_dp_dest
JOB_NAME=shParallelExp
TABLES=SALES
LOGFILE=default_log_dest:shParallelExp
ESTIMATE=statistics
PARALLEL=4
Notice the %u flag, which will append a two digit suffix to the Data Pump file. These
options will direct export data pump to generate four dump files which will be
accessed in a round robin fashion, so they get uniformly filled.
The resulting export dump files are:
shParallelExp0101.dmp
shParallelExp0102.dmp
shParallelExp0201.dmp
shParallelExp0202.dmp
Transporting data among different versions
Data Pump allows data transfers among different Oracle versions that support
the feature. (Note the feature was introduced in Oracle Database 10g Release. 1).
The database must be configured for compatibility of 9.2.0 or higher. This feature
simplifies data transfer tasks. In order for this to work it is important to consider the
source version versus the destination version. It works in an ascending compatible
mode, so a Data Pump export taken from a lower release can always be read by the
higher release, but an export taken from a higher release must be taken with the
VERSION parameter declaring the compatibility mode. This parameter can either take
the value of COMPATIBLE (default) which equals the compatible instance parameter
value, LATEST , which equals the metadata version or any valid database version
greater than 9.2.0. This last statement doesn't mean Data Pump can be imported on
a 9.2.0 database. Rather, it stands for the recently migrated 10g databases which still
hold the compatible instance parameter value set to 9.2.0.
If the COMPATIBLE parameter is not declared an export taken from a higher release
won't be read by a lower release and a run time error will be displayed.