Data load fails after archiving if data overlaps with archiving selection

[padmaja_khanna2]

We archived data from an infocube using the selection criteria 0CALYEAR <= '2006'. Later, in one of the delta loads into the same infocube, we happened to get some records with dates < '2006' and the data load failed with the following error:

" RSDA 239 - Data record locked by archiving request"

The question now is: Does archiving prevent data being loaded into an InfoCube if the data overlaps with the selection criteria used for archiving? If yes, then what can we do to be able to continue with our data loads?

Any help would be greatly appreciated. This is a production issue for us at this time, and is causing us some grief.

Thanks,

Padmaja

[Former Member · Accepted solution]

Hello Padmaja,

I believe starting in BI 7.0, once a certain time slice/period has been archived, that time slice becomes "write protected". In order to load new data for the archived time slice, the archived data would need to be reloaded. The time slice would then be released and the data load can run. You could then re-archive that time slice if needed.

Best Regards,

Karin Tillotson

[Former Member · Accepted solution]

Thanks Karin for your response and the workaround suggested.

However, loading the archived time-slice back into the cube will not serve the purpose for which I archived in the first place. And I do not have much control over the delta that comes in every day and that may occassionally have records that overlap with the archived time-slice.

Is there any way to unprotect/unlock the time-slice without reloading it into the cube?

[former_member193630 · Accepted solution]

Did you resolved this issue...I would like to know the solution if you have one. Because, once we archive...there is a chance occasionaly similar archived condition data might come again. In this case, it makes sense to move this new record also back to archive, insead of moving the archived data back to cube and re-archiving everything back.

Thanks

Gopi

[Former Member · Accepted solution]

I had opened an OSS message at the time to see what other options I may have. However, OSS gave the same explanation as the others on this forum, that if we archive a selection once, we cannot load any data that meets that selection criteria again.

I had to change my DTP to make sure no such records make it through the load in the future.

Another alternative I had considered but did not follow was to create a copy of the cube, restore the archived data to this copy-cube, delete the archiving process on the original cube (so no more archive locks remain), and then continue with loads to the original cube as before. This, however, would not be useful if you are trying to free up storage space, as the archived data would be sitting in a different cube. But it will address query performance, as it will take the data off the cube that you use for reporting.

Hope this helps.

[former_member193630 · Accepted solution]

Thanks for the reply. II thought there might be some straight forward solution and its interesting to see this workaround solution as the regular solution from SAP. Your reply really helps.

Thanks

Gopi

[Former Member]

Hi Padmaja,

I had the same problem. But when I used a DTP for overlapping archived data an error occurs. When I used an InfoPackage, I can load the data. Can anyone explain this difference between 3.x Infopackages and DTP?

Best regards.

Simone.