Reviewing an Example of a Dimension Build and Data Load Error Log

The following data log entry indicates that because the 500 member did not exist in the outline, no data was loaded to it.

\\ Member 500 Not Found In Database
500   500-10   500-10-10

To resolve this problem, you can perform either of the following actions and restart the load:

The following dimension build log entry indicates that the 600-20 member is not the parent of the 600 member. Ensure that you use the correct rules file with the correct text file. The record looks like it is for a level (bottom-up) build, but the error message indicates that Essbase Server is trying to perform a generation (top-down) build. After you correct the problem, restart the dimension build.

\\Record #2 - Incorrect Parent [600-20] For Member [600] (3307)
600-20-10   600-20   600