PAREXPORT

Starts the parallel data-export process.

The export process does not begin until all users are logged out of the database. After the export process begins, the database is in read-only mode. Users can read the data but they cannot change it. After the export process is finished, Essbase returns the database to read-write mode and users can make changes to the data.

Syntax

PAREXPORT [-threads n] [-in input_filename] | [output_filename] amount formatOption

Parameter	Description
-threads n	Overrides the default number of export threads set in the EXPORTTHREADS setting in the essbase.cfg file. The maximum value is 8. If n is greater than 8, Essbase assumes the value to be 8.
-in input_filename	Specifies the full path name of an input file that contains a list of export file names. The number of files listed in the input file must match the number of export threads. Parallel export gracefully errors out if there is a mismatch. If the data for any export thread exceeds 2 GB, Essbase creates additional files, none of which exceeds 2 GB. See Note for details. If -in is not specified, the next value is assumed to be the value of the output_filename parameter. If the listed files in the input file do not include a path, the files are created in the ARBORPATH\app directory.
output_filename	Specifies the path and root for the file names created to contain the export data. For each thread, a number is appended to the specified output_filename. For example, if outfile_filename is outfile and two threads are specified, the resulting file names are outfile1 and outfile2. If the data for a thread exceeds 2 GB, that export data is divided into multiple files with a second number appended to the file names. See Note for details. If no path is specified, the file is created in the ARBORPATH\app directory.
amount	Specifies the number representing the data to export. 1 - All data 2 - Only level 0 blocks 3 - Only data from blocks with input data
formatOption	Specifies the format of the data. 0 (null) - Non-columnar format. This is the default. 1 - Columnar format

Notes

With this command, users can override the default number of export threads specified in the EXPORTTHREADS setting, and they can provide a list of export file names. During the export process, multiple threads can retrieve data and write to their corresponding export files concurrently.
Parallel export creates multiple export files based on the number of export threads specified. The database is divided as evenly as possible among the number of parallel export threads.
If the data for an export thread exceeds 2 GB, that data is separated into multiple files. Each file is less than 2 GB. The first file name retains the original name; Essbase appends _1, _2, and so on, as needed, to the additional files.
The PARAEXPORT command works on both aggregate storage and block storage databases, however aggregate storage exports work differently from block storage exports. See the Oracle Essbase Database Administrator's Guide for more information.

Example

PAREXPORT -threads 4 -in e:\data\input.txt 1 1;

Note that e:\data\input.txt is a text file that contains four file names on separate lines; that is,

e:\data\export1.txt
e:\data\export2.txt
d:\data\export3.txt
d:\data\export4.txt

In this example, all data in the database is divided among four export threads to create four export files. The data is exported in columnar format.

If the data intended for a file is greater than 2 but less than 4 GB, Essbase creates two files. For example, for the data apportioned to e:\data\export2.txt, Essbase would create e:\data\export2.txt and e:\data\export2_1.txt.