We had an issue after system copy.
After a system copy the data in the standard DSOs(all of them) cannot be activated. The DOSs themselves are active, the transformations are active but if one attempts to load data and activate u2013 it does not work. The job terminates with shortdump SAPSQL_EMPTY_TABNAME.
Found the issue is caused by u201Cmore than one versionu201D of the change log.
We tried the Program RSAR_RSTSODS_CHANGELOG_VRS but it didn't work.
We had the solution like this:
After activating the DSO itself(the object) using RSDG_ODSO_ACTIVATE the issue disappears and the data can be activated. Issue also disappears. BUT Drawback: Activating the DSO causes the transformations to deactivate.Then we used the program RSDG_TRFN_ACTIVATE to activate all transformations. And then the issue disappeared.
Want to know what the root cause for this. From some SDN threads, mentioned BDLS job in the post refresh steps are not correctly done during system copy may cause this issue. How did the BDLS run wrongly cause this issue? And what is the exact correct way? We ran BDLS for each source systems inlcuding the target refreshed BW system itself by the default selection - conversion of Client-Dependent and Client-Independent Tables; because we used database copy
for the system refresh.
We also restored all source systems in RSA1 inlcuding the refreshed BW system own in the post-refresh steps.
Thank you very much for your information and suggestion.