Essbase : Multiple SQL Data Loads in Parallel to Aggregate Storage Databases

Most of the time, loading Essbase data from SQL Server  in serial mode works just fine:

alter database EssApp.EssDb initialize load_buffer with buffer_id 1;

import database EssApp.EssDb data

connect as SQLUser identified by SQLPswd

using server rules_file   'Load.rul' to load_buffer with buffer_id 1

on error write to 'errorfile.err';

import database ASOsamp.Sample data from load_buffer with buffer_id 1;

But if you have a lot of SQL data loads that take a long time, you might run into complaints from your client to speed of the data load process.  Well, your in luck!

1003006 Unknown Text File Type After recordNumber Records Completed

Possible Problems
Analytic Services did not recognize the text file.

Possible Solutions
Make sure that the text file is valid.

If more than one record loaded, make sure that ranges in the data source are correctly formatted.

1003005 Incorrect Number of Column Members in Asymmetric File After recordNumber Records Completed

Possible Problems
Analytic Services encountered either more or fewer columns than it expected while reading the data source.

Possible Solutions
Make sure that the data source is valid.

Are all members that might contain possible file delimiters (such as spaces or commas) surrounded by quotation marks in the data source?
Are all ranges set up correctly in the data source?

1003004 Incorrect Number of Column Members in Symmetric File After recordNumber Records Completed

Possible Problems
Analytic Services encountered either more or fewer columns than it expected while reading the data source.

Possible Solutions
Make sure that the data source is valid.

Are all members that might contain possible file delimiters (such as spaces or commas) surrounded by quotation marks in the data source?
Are all ranges set up correctly in the data source?

1003003 Unable to Continue Data Load After Item itemName, number Records Completed

Possible Problems
Analytic Services aborted the data load. This error message usually occurs after other error messages that describe why the data load failed.

Possible Solutions
Look through the data load error log to see why the data load failed.
If you have no data load error log, set up the load to create an error log and restart the data load.
Check the error messages that preceded this error message to determine what happened.
In the data source, make sure that all data fields are after the member name fields. In the rules file, make sure that you define the fields using dimension names instead of member names.

1003001 Duplicate Members From Same Dimension On Data Record, number Records Completed

Possible Problems
Analytic Services encountered more than one member from a dimension in a single record. Analytic Services will not load this record and will skip to the next record.

Possible Solutions
Make sure that the data source is valid.

Does each record contain only one member name for each dimension? For example, in the Time dimension you can have only the January member in a single record, not January and February. If you have columns containing duplicate members in a record, ignore those columns.
Is each member name mapped to the correct dimension? For example, in the Sample Basic database the January member should be mapped to the Time dimension and not to the Market dimension.
Are duplicate member or alias names under different dimensions? Member and alias names must be unique. For example, you cannot have a January member in both the Time dimension and the Market dimension. If you do have members or aliases with the same name in different dimensions, consider adding a prefix or suffix to the members or aliases in one dimension to make them unique.
Are ranges set up correctly?
Are all members that might contain numbers (such as "100") enclosed in quotation marks in the data source?
Are two members from the same dimension on one line in the data source?
If you are using a rules file, make sure that the rules file is valid.

Are extra member names ignored in the rules file?
Do you need to move columns around to ensure that each member is connected to the correct dimension?
Can you validate the rules file?
If you are using ESSCMD, make sure that the ESSCMD syntax is valid.

Check the error log in the ESSCMD script to determine where the duplicate member exists.
Are the parameters enclosed in quotation marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y";
Are the parameters correct?
Do the files you are loading exist in the correct locations?
Can you run the data load using Administration Services?
If you are using Integration Services, try the following steps:

If the duplicate member is a shared member, make sure that it is tagged as a shared member.
If you have members with the same names in different dimensions, be sure to add prefixes or suffixes to the member names.
Map all members to the correct dimension.
Make sure that you are using the correct Intersolv drivers.
Launch Analytic Services Integration Services using a non-default value for the -B parameter.
In Hyperion OLAP Builder, select the Delete All Members First option.

1003000 Unknown Item itemName in Data Load, number Records Completed

Possible Problems
Analytic Services encountered a field in the data source that it did not recognize.

Possible Solutions

Examine the data load log for any other messages that may help to identify the problem.

Make sure that the data source is valid. If no records loaded, either the first record is invalid or the entire data source is invalid.

Is the data source corrupt?
Is the data source in the correct location?
Is the data source correctly formatted?
Make sure that the record that caused the data load to fail is valid.

Is a member from each dimension specified in the data source or the rules file?
Is each member name in the record valid?
Is there more than one numeric data field in the record?
Did you try removing the record that caused the data load to fail and running the data load again?
If you are using a rules file, make sure that the rules file is valid.

Is the rules file in the correct location?
Is the rules file set up correctly?
Can you validate the rules file?
If you are using ESSCMD, make sure that the ESSCMD syntax is valid.

Check the error log in the ESSCMD script to determine where the unknown item exists.
Are the parameters enclosed in quotation marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y";
Are the parameters correct?
Do the files you are loading exist in the correct locations?
Can you run the data load using Administration Services?