Data Load Error Messages 1003000 to 1003048
This document describes data load error messages and information messages.
The discussions of error messages include possible causes and possible
solutions for each problem, with links to the Analytic Services Database
Administrator's Guide and the Analytic Services Technical Reference
for more information on how to fix errors.
Click an error message number to view information about that error message.
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.
Make sure that the record that caused the data load to fail is valid.
If you are using a rules file, make sure that the rules file is valid.
If you are using ESSCMD, make sure that the ESSCMD
syntax is valid.
1003034
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.
If you are using ESSCMD, make
sure that the ESSCMD syntax is valid.
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.
See Also
1003015
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.
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.
See Also
1003005
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.
See Also
1003004
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.
1003007 Data value numericValue Encountered
Before All Dimensions Selected
Possible Problems
Analytic Services encountered a numeric data value in the data source
before all dimensions were specified.
Possible Solutions
Make sure that the data source
is valid.
1003008 With Data Value numericValue, Too
Many Values In Row, number Records Completed
Possible Problems
Analytic Services encountered more numeric data fields in the record
than it can map to the database.
Possible Solutions
Make sure 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?
Make sure that the rules file
is valid.
1003010 Data Value numericValue Does Not
Match #Missing Value in Database, number Records Completed
Possible Problems
Analytic Services encountered a problem when it tried to validate the
database against the data source to see if both contain the same values.
Possible Solutions
- Make sure that the data source is the contains the
same values as the database.
- Make sure that you are validating the database against
the correct data source.
- If you think that the data loaded incorrectly, make sure that the data source is
set up correctly.
See Also
1003011
1003012
1003013
1003011 Data Value numericValue Does Not
Match #Invalid Value in Database, number Records Completed
Possible Problems
Analytic Services encountered a problem when it tried to validate the
database against the data source to see if both contain the same values.
Possible Solutions
- Make sure that the data source contains the same
values as the database.
- Make sure that you are validating the database against
the correct data source.
- If you think that the data loaded incorrectly, make sure that the data source is
set up correctly.
See Also
1003010
1003012
1003013
1003012 Data Value numericValue Is Greater
Than Value in Database, number Records Completed
Possible Problems
Analytic Services encountered a problem when it tried to validate the
database against the data source to see if both contain the same values.
Possible Solutions
- Make sure that the data source contains the same
values as the database.
- Make sure that you are validating the database against
the correct data source.
- If you think that the data loaded incorrectly, make sure that the data source is
set up correctly.
See Also
1003010
1003011
1003013
1003013 Data Value numericValue Is Less
Than Value in Database, number Records Completed
Possible Problems
Analytic Services encountered a problem when it tried to validate the
database against the data source to see if both contain the same values.
Possible Solutions
- Make sure that the data source contains the same
values as the database.
- Make sure that you are validating the database against
the correct data source.
- If you think that the data loaded incorrectly, make sure that the data source is
set up correctly.
See Also
1003010
1003011
1003012
1003014 Unknown Member memberName in Data
Load, number Records Completed
Possible Problems
Analytic Services did not recognize the member name.
Possible Solutions
Make sure that the data source
is valid.
Make sure that the rules file is valid.
Make sure that the member name
is valid.
If you are using ESSCMD, make
sure that the ESSCMD syntax is valid.
If you are using Analytic Services Integration Services, make sure that
the following conditions are met.
- If you have members with the same name in different
dimensions, add a prefix or suffix to the member names to make them unique.
- Make sure that the outline build is successful before
starting the data load.
1003015 Member memberName is from the same
dimension as members defined in Header Name, number Records Completed
Possible Problems
Analytic Services 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.
Possible Solutions
Make sure that the data source is valid.
If you are using a rules file, make sure that the rules file is valid.
See Also
1003001
1003022 Unable to Open Data File
Possible Problems
Analytic Services cannot open the data file.
Possible Solutions
Make sure Analytic Services can find the data file.
- Are the data file name and path name correct? Check
for misspellings.
- If Analytic Server is on a computer running UNIX,
is capitalization correct?
- Is the data file in the specified location? Make
sure that no one has moved or deleted the data file.
Make sure Analytic Services can use the data file.
- Is the data file locked
by a another user?
- Does the data 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 data
file valid?
- Do you have the correct
permissions for the Analytic Services database into which you are
loading the data file?
- Do you have the correct operating system privileges
for the data file you are trying to load?
If you are using ESSCMD, make sure that you are using the IMPORT
command correctly. When you issue the IMPORT command, you have four
options to choose the location of the data file.
- 1 (local/client object):
Make sure the data file is in the client folder.
Make sure you have read access to the data file.
If Analytic Server is on a UNIX platform, remember that the file name
is case-sensitive and check capitalization.
- 2 (remote server object):
Make sure you have read access to the data file.
If Analytic Server is on a UNIX platform, remember that the file name
is case-sensitive and check capitalization.
- 3 (file): Make
sure that you specified the absolute path name and the full file name
(including the file type extension).
- 4 (SQL): Check
the ODBC connections.
Make sure Analytic Server is properly configured.
See Also
1003027
1003030
1003023 You have insufficient access privileges
to perform a lock on this database
Possible Problems
You did not have the necessary permissions to lock the database so that
you can load data.
Possible Solutions
Contact your Analytic Services System Administrator.
If you are a System Administrator, grant
yourself the correct permissions.
1003024 Data Load Elapsed time : number
seconds
This information message states how long it took Analytic Services to
load a data source. There is nothing wrong.
1003025 DATAERRORLIMIT reached numberOfRecords.
Rejected records will no longer be logged
Possible Problems
The error log was full. This means that you have too many error messages
to fit in the data load or dimension build error log or that you are rejecting
too many records to fit in the log.
Possible Solutions
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.
- If you do not have an
$ARBORPATH/bin/ essbase.cfg
file on the server computer, create one using a text editor.
- Add or increase the DATAERRORLIMIT
setting in the
$ARBORPATH/bin/essbase.cfg
file.
- Stop and restart
Analytic Server.
- Restart the
data load.
1003027 Unable to open file
Possible Problems
Analytic Services cannot open the file.
Possible Solutions
Make sure Analytic Services can find the file.
- Are the file name and path name correct? Check for
misspellings.
- If Analytic Server is on a UNIX platform, is capitalization
correct?
- Is file is in the specified location? Make sure that
no one has moved or deleted the file.
Make sure Analytic Services can use the file.
If you are using ESSCMD, make sure that you are using the IMPORT
command correctly. When you issue the IMPORT command, you have four
options to choose the location of the file.
- 1 (local/client object):
Make sure the data file is in the client folder.
Make sure you have read access to the data file.
If Analytic Server is on a UNIX platform, remember that the file name
is case-sensitive and check capitalization.
- 2 (remote server object):
Make sure you have read access to the data file.
If Analytic Server is on a UNIX platform, remember that the file name
is case-sensitive and check capitalization.
- 3 (file): Make
sure that you specified the absolute path name and the full file name
(including the file type extension).
- 4 (SQL): Check
the ODBC connections.
Make sure Analytic Server is properly configured.
See Also
1003022
1003030
1003028 File fileName is password protected
and could not be read
Possible Problems
Analytic Services did not have the necessary operating system privileges
to open the file you are trying to load.
Possible Solutions
Make sure that you have read privileges for the file. Consult the operating
system documentation for more information.
1003029 Encountered formatting error in spreadsheet
file fileName
Possible Problems
Analytic Services encountered a formatting error in the file.
Possible Solutions
Open the file outside of Analytic Services and make sure that the file
is valid.
1003030 Unable to load file fileName; see
server logfile for details
Possible Problems
Analytic Services cannot read the file.
Possible Solutions
Make sure Analytic Services can find the file.
- Are the file name and path name correct? Check for
misspellings.
- If Analytic Server is on a UNIX platform, is capitalization
correct?
- Is file is in the specified location? Make sure that
no one has moved or deleted the file.
Make sure Analytic Services can use the file.
If you are using ESSCMD, make sure that you are using the IMPORT
command correctly. When you issue the IMPORT command, you have four
options to choose the location of the file.
- 1 (local/client object):
Make sure the data file is in the client folder.
Make sure you have read access to the data file.
If Analytic Server is on a UNIX platform, remember that the file name
is case-sensitive and check capitalization.
- 2 (remote server object):
Make sure you have read access to the data file.
If Analytic Server is on a UNIX platform, remember that the file name
is case-sensitive and check capitalization.
- 3 (file): Make
sure that you specified the absolute path name and the full file name
(including the file type extension).
- 4 (SQL): Check
the ODBC connections.
Make sure Analytic Server is properly configured.
See Also
1003027
1003022
1003031 Commit at record recordNumber during
arithmetic data load
This information message states that Analytic Services saved the record
to the Analytic Services database. There is nothing wrong.
1003032 Input line too long near record recordNumber
Possible Problems
Analytic Services encountered a record that was too long to process.
Analytic Services cannot process records that contain more than 32,000
characters.
Possible Solutions
Make sure that all records are separated by a carriage return.
Make sure that no single record contains more than 32,000 characters.
1003034 Invalid member memberName in data
column
Possible Problems
Analytic Services encountered a non-numeric value in the in data column.
Data columns must contain numeric values only.
Possible Solutions
Make that sure that the data source is valid.
Make sure that the record that caused the data load to fail is valid.
If you are using a rules file, make sure that the rules file is valid.
See Also
1003000
1003035 No data values modified by load of this
data file
This information message states that Analytic Services did not change
any of the values in the Analytic Services database as a result of the
data load. There is nothing wrong.
1003036 Cannot load data. Member name too long:
memberName
Possible Problems
Analytic Services encountered a member name that was too long.
Possible Solutions
Make sure that the member name
is valid.
1003037 Data Load Updated numberOfCells
cells
This information message states that Analytic Services updated the indicated
number of cells in the database. There is nothing wrong.
1003038 Dataload queue overflow on node nodeNumber
Contact Hyperion Technical Support.
1003039 Cannot load data. Implied shared member
memberName does not have a real child
Possible Problems
Analytic Services cannot load data into the selected member because
the member is shared. Shared members cannot contain data.
Possible Solutions
Make sure that the member is not shared. Members are shared under the
following 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 have the same value;
therefore, the parent value is shared. 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.
This information message states that parallel data load is enabled.
There is nothing wrong.
1003041 Data Unlock Elapsed Time : number
seconds
This information message states the time required to unlock all the
locks after the Unlock command is issued in the Spreadsheet Add-in.
1003048 Loading Unicode-encoded data to non-Unicode
mode application is not supported
Possible Problems
You have attempted to load unicode-encoded data to a non-unicode application.
Possible Solutions
Verify that you have migrated
your application to unicode mode.