1003000 to 1003048: Data Load Messages

Table 3 lists data load error and informational messages.

Table 3. Data Load Messages 1003000 to 1003048

Message Number Message Possible Cause Possible Solution

1003000

Related Topics

1003034

Unknown Item itemName in Data Load, number Records Completed

Essbase encountered a field in the data source that it did not recognize.

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

Ensure 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?

Ensure 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?

  • Are there multiple numeric data fields in the record?

  • Try removing the record that caused the data load to fail and running the data load again.

If you are using a rules file, ensure 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, ensure that the syntax is valid.

  • Check the error log in the ESSCMD script to determine where the unknown item exists.

  • Are the parameters correct and enclosed in quotation marks? For example:

    IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y"; 
  • Do the files you are loading exist in the correct locations?

  • Can you run the data load using Administration Services?

1003001

Related Topics

1003015

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

Essbase encountered multiple members from a dimension in one record. Essbase does not load this record and skips to the next record.

Ensure that the data source is valid.

  • Does each record contain only one member name for each dimension? For example, the Time dimension can contain only January in one record. If columns contain duplicate members in a record, ignore those columns.

  • Is each member name mapped to the correct dimension? For example, in the Sample Basic database, January should be mapped to the Time dimension.

  • Are member or alias names duplicated in other dimensions? Member and alias names must be unique. For example, January cannot exist in the Time and Market dimensions. If names of members or aliases in other dimensions match, add 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 one dimension on one line in the data source?

If you are using a rules file, ensure that it is valid.

  • Are extra member names ignored in the rules file?

  • Do you need to move columns to ensure that each member is connected to the correct dimension?

If you are using ESSCMD, ensure that the syntax is valid.

  • Check the error log in the ESSCMD script to determine where the duplicate member exists.

  • Are the parameters cirrect and enclosed in quotation marks? For example:

    IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y";
  • 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 these steps:

  • Ensure that duplicate members that are shared are tagged as such.

  • Ensure that member names are unique.

  • Map all members to the correct dimension.

  • Ensure that you are using the correct DataDirect drivers.

  • Launch Integration Server using a non-default value for the -B parameter.

  • In Integration Services Console, select Delete All Members First; in Integration Services shell, use OTL_CLEAR=[Y].

1003003

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

Essbase aborted the data load. This error message usually occurs after other error messages that describe why the data load failed.

Look through the data load error log to see why the data load failed.

If no data load error log exists, 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, ensure that all data fields are after the member name fields. In the rules file, ensure that you define the fields using dimension names instead of member names.

1003004

Related Topics

1003005

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

Essbase encountered more or fewer columns than it expected while reading the data source.

Ensure 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?

1003005

Related Topics

1003004

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

Essbase encountered more or fewer columns than it expected while reading the data source.

Ensure 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?

1003006

Unknown Text File Type After recordNumber Records Completed

Essbase did not recognize the text file.

Ensure that the text file is valid.

If multiple records loaded, ensure that ranges in the data source are correctly formatted.

1003007

Data value numericValue Encountered Before All Dimensions Selected

Essbase encountered a numeric data value in the data source before all dimensions were specified.

Ensure that the data source is valid.

  • Is a member from each dimension specified correctly in the data source or rules file?

  • Is the numeric data field at the end of the record? If not, move the numeric data field in the data source or move the numeric data field in the rules file.

  • Are all members that might contain numbers (such as "100") enclosed in quotation marks in the data source?

  • If you are using a header, is the header set up correctly? Remember that you can add missing dimension names to the header.

  • Does the data source contain extra spaces or tabs?

  • Has the updated outline been saved?

1003008

With Data Value numericValue, Too Many Values In Row, number Records Completed

Essbase encountered more numeric data fields in the record than it can map to the database.

Ensure that the data source is valid.

  • Are all members that might contain numbers (such as "100") enclosed in quotation marks in the data source?

  • Are extra numeric data fields in the record? If so, you can ignore extra data fields.

  • Is the numeric data field the last field in the record? If not, move the numeric data field in the data source or move the numeric data field in the rules file.

  • Is each field in the data source valid?

  • Is each dimension specified in the data source or the rules file?

Ensure that the rules file is valid.

1003010

Related Topics

1003011

1003012

1003013

Data Value numericValue Does Not Match #Missing Value in Database, number Records Completed

Essbase encountered a problem when it tried to validate the database against the data source to see if both contain the same values.

Ensure that the data source is the contains the same values as the database.

Ensure that you are validating the database against the correct data source.

If you think that the data loaded incorrectly, ensure that the data source is set up correctly.

1003011

Related Topics

1003010

1003012

1003013

Data Value numericValue Does Not Match #Invalid Value in Database, number Records Completed

Essbase encountered a problem when it tried to validate the database against the data source to see if both contain the same values.

Ensure that the data source contains the same values as the database.

Ensure that you are validating the database against the correct data source.

If you think that the data loaded incorrectly, ensure that the data source is set up correctly.

1003012

Related Topics

1003010

1003011

1003013

Data Value numericValue Is Greater Than Value in Database, number Records Completed

Essbase encountered a problem when it tried to validate the database against the data source to see if both contain the same values.

Ensure that the data source contains the same values as the database.

Ensure that you are validating the database against the correct data source.

If you think that the data loaded incorrectly, ensure that the data source is set up correctly.

1003013

Related Topics

1003010

1003011

1003012

Data Value numericValue Is Less Than Value in Database, number Records Completed

Essbase encountered a problem when it tried to validate the database against the data source to see if both contain the same values.

Ensure that the data source contains the same values as the database.

Ensure that you are validating the database against the correct data source.

If you think that the data loaded incorrectly, ensure that the data source is set up correctly.

1003014

Unknown Member memberName in Data Load, number Records Completed

Essbase did not recognize the member name.

Ensure that the data source is valid.

  • Are you using the correct data source?

  • Is there an incorrect member in the data source? If so, delete that member.

  • Did you try to load the correct data source with the correct rules file?

  • Is the file extension correct for the data source? All text files must have a file extension of .txt. All rules files must have a file extension of .rul.

Ensure that the rules file is valid.

  • Are you using the correct rules file?

  • Is the rules file connected to the correct outline?

  • Can you validate the rules file?

Ensure that the member name is valid.

  • Are member names or variable names enclosed in quotation marks where necessary?

  • Does the member exist in the outline? If not, you can add the member by modifying the outline during the data load or by adding the member in the Outline Editor.

  • Ensure that the member is not specified in both the header file and the text file.

If you are using ESSCMD, ensure that the ESSCMD syntax is valid.

  • Check the error log in the ESSCMD script to determine where the unknown member name 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 Oracle Essbase Integration Services, ensure that these conditions are met.

  • If members in other dimensions have matching names, add a prefix or suffix to the member names to make them unique.

  • Ensure that the outline build is successful before starting the data load.

1003015

Related Topics

1003001

Member memberName is from the same dimension as members defined in Header Name, number Records Completed

Essbase aborted the load because two different members were specified for the same dimension. One member from the dimension was specified in the header record and another member from the same dimension was specified in a record in the data source.

Ensure that the data source is valid.

  • Did you set the correct record as the header record?

  • Do members that you specify in the header also appear in the data source? If so, you must change the header record or the data source.

If you are using a rules file, ensure that the rules file is valid.

  • Did you set the correct record as the header record?

  • Are extra member names that should be ignored in the rules file?

  • Can you validate the rules file?

  • Did you accidentally reject the header record?

1003022

Related Topics

1003027

1003030

Unable to Open Data File

Essbase cannot open the data file.

Ensure Essbase can find the data file.

  • Are the data file name and path name correct? Check for misspellings.

  • If Essbase Server is on a computer running UNIX, is capitalization correct?

  • Is the data file in the specified location? Ensure that no one moved or deleted the data file.

Ensure Essbase can use the data file.

  • Is the data file locked by a another user (see Unlocking Objects)

  • Is the file extension for the data file correct? All text files must have a file extension of .txt. All rules files must have a file extension of .rul.

  • Is the data file valid?

  • Are your permissions correct for the Essbase database into which you are loading the data file?

  • Are your operating system privileges correct for the data file you are trying to load?

If you are using ESSCMD, ensure that you are using the IMPORT command correctly. When you issue the IMPORT command, you have four options to choose the data file location.

  • 1 (local/client object): Ensure the data file is in the client folder.

    Ensure you have read access to the data file.

    If Essbase Server is on a UNIX platform, remember that the file name is case-sensitive and check capitalization.

  • 2 (remote server object): Ensure you have read access to the data file.

    If Essbase Server is on a UNIX platform, remember that the file name is case-sensitive and check capitalization.

  • 3 (file): Ensure that you specified the absolute path name and the full file name (including the file type extension).

  • 4 (SQL): Check the ODBC connections.

Ensure Essbase Server is properly configured.

1003023

You have insufficient access privileges to perform a lock on this database

You did not have the necessary permissions to lock the database so that you can load data.

Contact your Essbase system administrator.

If you are a system administrator, grant yourself the correct permissions.

1003024

Data Load Elapsed time : number seconds

Length of time it took Essbase to load a data source.

Not applicable

1003025

DATAERRORLIMIT reached numberOfRecords. Rejected records will no longer be logged

The error log was full.

You have too many error messages to fit in the data load or dimension build error log, or you are rejecting too many records to fit in the log.

Fix the errors in the data load or dimension build error log and restart the data load.

Change the maximum number of records allowed in the data load or dimension build error log.

  1. If ESSBASEPATH/bin/ essbase.cfg does not exist on the server computer, create one using a text editor.

  2. Add or increase the DATAERRORLIMIT setting in the ESSBASEPATH/bin/essbase.cfg file.

  3. Stop and restart Essbase Server.

  4. Restart the data load.

1003027

Related Topics

1003022

1003030

Unable to open file

Essbase cannot open the file.

Ensure Essbase can find the file.

  • Are the file name and path name correct? Check for misspellings.

  • If Essbase Server is on a UNIX platform, is capitalization correct?

  • Is file is in the specified location? Ensure that no one has moved or deleted the file.

Ensure Essbase can use the file.

  • Is the data file locked by another user (see Unlocking Objects) ?

  • Does the file have the correct file extension? All text files must have a file extension of .txt. All rules files must have a file extension of .rul.

  • Is the file valid?

  • Do you have the correct permissions for the Essbase database into which you are loading the file?

  • Do you have the correct operating system privileges for the file you are trying to load?

If you are using ESSCMD, ensure that you are using the IMPORT command correctly. When you issue the IMPORT command, you have four options to choose the file location .

  • 1 (local/client object): Ensure that the data file is in the client folder.

    Ensure that you have read access to the data file.

    If Essbase Server is on a UNIX platform, remember that the file name is case-sensitive and check capitalization.

  • 2 (remote server object): Ensure that you have read access to the data file.

    If Essbase Server is on a UNIX platform, remember that the file name is case-sensitive and check capitalization.

  • 3 (file): Ensure that you specified the absolute path name and the full file name (including the file type extension).

  • 4 (SQL): Check the ODBC connections.

Ensure Essbase Server is properly configured.

1003028

File fileName is password protected and could not be read

Essbase did not have the necessary operating system privileges to open the file you are trying to load.

Ensure that you have read privileges for the file. See the operating system documentation.

1003029

Encountered formatting error in spreadsheet file fileName

Essbase encountered a formatting error in the file.

Open the file outside of Essbase and Ensure that the file is valid.

  • Is the data load running correctly?

  • Is the file corrupt?

  • Is the file empty?

  • Is the file a type that you can load into Essbase?

1003030

Related Topics

1003027

1003022

Unable to load file fileName; see server logfile for details

Essbase cannot read the file.

Ensure Essbase can find the file.

  • Are the file name and path name correct? Check for misspellings.

  • If Essbase Server is on a UNIX platform, is capitalization correct?

  • Is file is in the specified location? Ensure that no one has moved or deleted the file.

Ensure Essbase can use the file.

  • Is the data file locked by another user (see Unlocking Objects) ?

  • Does the file have the correct file extension? All text files must have a file extension of .txt. All rules files must have a file extension of .rul.

  • Is the file valid?

  • Do you have the correct permissions for the Essbase database into which you are loading the file?

  • Do you have the correct operating system privileges for the file you are trying to load?

If you are using ESSCMD, ensure that you are using the IMPORT command correctly. When you issue the IMPORT command, you have four options to choose the file location.

  • 1 (local/client object): Ensure that the data file is in the client folder.

    Ensure that you have read access to the data file.

    If Essbase Server is on a UNIX platform, remember that the file name is case-sensitive and check capitalization.

  • 2 (remote server object): Ensure that you have read access to the data file.

    If Essbase Server is on a UNIX platform, remember that the file name is case-sensitive and check capitalization.

  • 3 (file): Ensure that you specified the absolute path name and the full file name (including the file type extension).

  • 4 (SQL): Check the ODBC connections.

Ensure that Essbase Server is properly configured.

1003031

Commit at record recordNumber during arithmetic data load

Essbase saved the record to the Essbase database.

Not applicable

1003032

Input line too long near record recordNumber

Essbase encountered a record that was too long to process. Essbase cannot process records that contain more than 32,000 characters.

Ensure that all records are separated by a carriage return.

Ensure that no single record contains more than 32,000 characters.

1003034

Related Topics

1003000

Invalid member memberName in data column

Essbase encountered a non-numeric value in the in data column. Data columns must contain numeric values only.

Make that sure that the data source is valid.

  • Is the data source corrupt?

  • Is the data source correctly formatted?

Ensure 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?

  • Are there multiple numeric data fields in the record? If so, you can ignore extra data fields.

  • Is the numeric data field at the end of the record? If not, move the numeric data field in the data source or move the numeric data field in the rules file.

  • Are all member names that might contain numbers (such as "100") enclosed in quotation marks?

  • Try removing the record that caused the data load to fail and running the data load again.

If you are using a rules file, ensure that the rules file is valid.

  • Is the rules file in the correct location?

  • Is the header record in the rules file set up correctly?

  • Can you validate the rules file?

  • Are all dimensions specified in the dimensions specified in the data source or rules file?

1003035

No data values modified by load of this data file

Essbase did not change the values in the Essbase database as a result of the data load.

Not applicable

1003036

Cannot load data. Member name too long: memberName

Essbase encountered a member name that was too long.

Ensure that the member name is valid.

  • Is the member name less than 80 bytes?

  • Did you set the file delimiter?

  • Does a prefix or suffix make the member name too long?

1003037

Data Load Updated numberOfCells cells

Essbase updated the indicated number of cells in the database.

Not applicable

1003038

Dataload queue overflow on node nodeNumber

 

Contact Oracle Support.

1003039

Cannot load data. Implied shared member memberName does not have a real child

Essbase cannot load data into the selected member because the member is shared. Shared members cannot contain data.

Ensure that the member is not shared. Members are shared under these conditions:

  • If you tag the member as shared in the outline.

  • If the member is a parent with only one child. If a member only has one child, the parent and the child share a value. This is called an implied share.

  • If the member has multiple children, but only one child that consolidates to the parent. This is also called an implied share.

1003040

Parallel dataload enabled: number block prepare threads, number write threads.

Parallel data load is enabled.

Not applicable

1003041

Data Unlock Elapsed Time : number seconds

The time required to unlock all locks after the Unlock command is issued in the Spreadsheet Add-in.

Not applicable

1003048

Loading Unicode-encoded data to non-Unicode mode application is not supported

You have attempted to load Unicode encoded data to a non-Unicode application.

Verify that you have migrated your application to Unicode mode.