Error when mantaining a dimension

Question

I have a very simple AW with 3 dimensions (PLAYER, YEAR, TEAM) containing baseball data. The TEAM dimension has one hierarchy with 3 levels: TEAMS_ALL, LEAGUE, TEAMID. For a spell, I was able to maintain this dimension successfully and use it in reports. Now when I try to maintain the TEAMS dimension I get the error:
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01600:
OLAP DML Error "AA is already a value of AW_BALL2!TEAM_LEAGUE_SURROGATE." while executing DML "SYS.AWXML!R11_LOAD_DIM('TEAM.LEAGUE.LEVEL'  SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'TEAM.LONG_DESCRIPTION.ATTRIBUTE' 'TEAM.SHORT_DESCRIPTION.ATTRIBUTE' 'TEAM.LEAGUE_LONG_DESCRIPTION.ATTRIBUTE' 'TEAM.LEAGUE_SHORT_DESCRIPTION.ATTRIBUTE' 'TEAM.TEAMS_ALL_LONG_DESCRIPTION.ATTRIBUTE' 'TEAM.TEAMS_ALL_SHORT_DESCRIPTION.ATTRIBUTE' 'TEAM.TEAMHIER.HIERARCHY')", Generic at TxsOqStdFormCommand::execute
FYI, 'AA' is the first alphabetical value in the 'League' Level of the TEAM dimension.
I am also getting a similar error when I try to maintain my YEAR dimension which has one hierachy and two levels (TIME_ERA and YEAR). Which is:
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01600:
OLAP DML Error "1870s is already a value of AW_BALL2!YEAR_TIME_ERA_SURROGATE." while executing DML "SYS.AWXML!R11_LOAD_DIM('YEAR.TIME_ERA.LEVEL'  SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'YEAR.LONG_DESCRIPTION.ATTRIBUTE' 'YEAR.SHORT_DESCRIPTION.ATTRIBUTE' 'YEAR.TIME_ERA_LONG_DESCRIPTION.ATTRIBUTE' 'YEAR.TIME_ERA_SHORT_DESCRIPTION.ATTRIBUTE' 'YEAR.YEARHIER.HIERARCHY')", Generic at TxsOqStdFormCommand::execute
FYI, '1870s' is is the first alphabetical value in the 'TIME_ERA' Level of the YEAR dimension.
Any help on what I need to do to fix this would be appreciated. Thanks.

Answer 1

Brijesh, thanks for your reply. I solved this problem by selecting the option *'Generate Surrogate Keys in the Analytic Workspace'* in the *'Implementation Details'* tab for the PLAYERS dimension. I'm not sure why the alternative option of *'Use keys from data source'* would work fine in the initial build but then fail in a later MAINTAIN command since I did not alter the data since the initial load
Frankly, my experience with using AW via the GUI so far is that I will not get the same results when performing the same tasks on the same data. What this realistically means is that the GUI does not fully and/or accurately represent the underlying state of conditions in the AW. I also find that when errors arise I do not get as much information and guidance from the GUI as I would like. For instance, in the above scenario perhaps an error message to the effect of *'you are attempting to load a value that matches another value on some level of this dimension. This problem might be solved by switching to surrogate keys in the Implementation Details of the dimension to ensure uniqueness.'*
Thanks