issues after deleting a navigational attribute

[former_member730190]

We deleted a navigational attribute from an infoobject before un-checking it in the relevant multiproviders and cubes. This caused the cubes and multiproviders to be inactive. We were able to manually go in and activate all of them. Every thing got collected in a transport. But the transport generated an error code of 12.

Majority of the relevant cubes are active in QA but two of them are inactive. Checking the log and ST22, we can see that it was failing to activate a transformation. We activated the transformation thru the program RSDG_TRFN_ACTIVATE. We will try a reimport and see if that works.

I wanted to check if there is any thing else that needs to be done. I know we should have unchecked it in the multiproviders and cubes before removing it. But mistakes happen. If we are unable to activate the cube in QA, can we put the attribute back and then go from there? What other options do we have? Thanks.

[Loed · Accepted solution]

Hi Uday,

Did you still encounter any error on this? Can you post it?

Regards,

Loed

[former_member730190 · Accepted solution]

After 2 reimports, we were able to get the transport in Prod without errors. I had to activate a transformation thru the program and then do a reimport. That worked. I think it was getting stuck on that one transformation, and as soon as it failed, it aborted the transport. So once that got fixed, the reimport was fine.

[RamanKorrapati · Accepted solution]

if issue was resolved please close the thread by choosing correct or assumed answer.

[RamanKorrapati]

Hi Uday,

Your transformations may have inconsistency,

so please check them thru prorgam - RSTRAN_ROUT_RSFO_CHECK .

Later again collect problematic(after checking thru above program)transformations from dev and move to target system thru transports.

Some time at Qualitys server thru programs also not suggestable to activate objects. because same action may need to repeat at prod as well. so better to handle thru transports.

Thanks

[former_member401488]

Hi there,

Please post some more details around the error 12 that you have while doing the transport.

Have you got any repair transport request in QA with the objects that you manually activate there? maybe that is why your transport are failing with an error code 12.

[former_member730190]

I just used an ABAP program to activate the transformations, not thru an open repair request. The error occured twice before I activated it. The first time after the transport, a bunch of cubes were inactive. We tried a reimport and some of the cubes that were inactive got activated, but not all. A 2nd reimport did not change anything. We are yet to do a reimport after I activated the transformations. We will do that tomorrow and I will post the result.

The transport log in Dev only shows that the return code is 12 and tells to check the QA system for further information about the error. The failed job names are RDDEXECL (most with that name succeeded but some failed). For the original transport, the error in the corresponding job log in QA system says "Internal session terminated with a runtime error GETWA_NOT_ASSIGNED". For the reimports, the job log says UNCAUGHT_EXCEPTION. Upon checking it further in ST22, it said there was an error trying to activate a transformation. Hope this sheds some light.